Closed RaZeR-RBI closed 1 year ago
Lowering the BOGUS_RANGE back to (1 << 14) instead of (1 << 20) inside mathlib.h fixes the issue for me.
Is there any specific reason why it was increased? Is it possible to revert this change?
BOGUS_RANGE is used multiple places for different things. I raised it for purpose of higher map limits with unintended consequences. Solution will be to regress and use a different one for map range.
Try the exe under 'Artifacts' at bottom of https://github.com/qbism/q2tools-220/actions/runs/4094825113
https://github.com/qbism/q2tools-220/commit/0ea7ffc6bc3663c70074551ad286a43971a52266
I've encountered disappearing triangles bug with recent versions of the compiler. After bisecting, the offending commit seems to be b23900e6c14237dbb5900cfd74d45f2cd89abf00.
Before that commit everything is good:
On this commit (and on the current version) the result looks like this:
Here's how it looks in the editor (TrenchBroom):
A sample map for reproduction:
I'm aware that floating-point coordinates is a potential source for bugs and already tried snapping to both integer and grid, but nothing helps.
Sadly I'm also encountering these issues with way simpler and more 'regular' geometry than the one I'm showing here (without those long skinny triangles) like rotated arches.
I'll investigate further and report my findings, and hopefully a pull request to fix that.