Manuel Lauss

> FYI, I am running on the “Broadcom V3D 4.2.12” OpenGL renderer (or Broadcom VideoCore 6 GPU), aka the Raspberry Pi 4B GPU. Anyway, I have tried running gdb. >...

> > Did you catcht the error code returned by `glGetError()`? > > Right, now that the `assert()` does not cause the program to abort before logging the error value,...

> > Nice, I have not tried it with Mesa 3D’s software renderer. So, there is a GL error after all. > > Interesting, Mesa 3D’s software renderer does not...

> 7 theforceengine(+0x1642 > @mlauss2 I have tested your `test2` branch and it looks to run flawlessly. The new GL debug callback throws a bunch of Mesa 3D stats but...

Eh, the abort is due to the "Critical" in "[Critical : GPU] Cannot initialize GPU/Window." there's an assert in the logging code which trips when a critical log message is...

Hello All, if you still have this problem on launch, can you please build TFE with debug symbols enabled, run it under gdb and show the backtrace? at the root...

with the default build instructions, cmake does add the -DNDEBUG and there are no assert()s left. ``` $ readelf -Wa theforceengine | grep assert 7259: 00000000002430d0 1117 FUNC WEAK DEFAULT...

> > with the default build instructions, cmake does add the -DNDEBUG and there are no assert()s left. > > ```shell > $ cmake --version > cmake version 3.29.6 >...

FWIW, I see a similar issue, but much less pronounced, also on Adreno/WindowsARM64:  Since the Adreno Windows OpenGL driver is based on Mesa (mesa-to-d3d12), this *might* be...

How far away is far away? When continuously alt-firing weapon 6, the distance of the first rendered frame to the weapon sprite seems to "cycle" between 3 positions (closest, next,...