(2024-02-05, 22:34)Roland Melkert Wrote: FBO is an OpenGL thing, it allows for offscreen rendering. LDCad uses this to only update changed regions of the screen.
If the option is disabled it will always render everything unless the fallback 'hack' option of 'reuse frontbuffer' is enabled, but that option shouldn't be used on newer hardware as it will most likely corrupt the rendering output. This because modern hardware uses triple or more buffering under the hood.
To be sure check frameRenderMethod in main.cfg it should be
frameRenderMethod=FBO
or
frameRenderMethod=normal
But nether option should affect normal gui dialogs.
OK, I've recently gotten the crash/freeze where the program window came back at normal size and I didn't get the FBO initialization warning. I checked just now and the render method is set to "basic" (normal). I've re-set it to FBO, and we'll see if the next crash leads to the error message coming back.
I just wondered if there was a reason that LDCad would try (and fail) to enable FBO, that would give a clue as to why the program had misbehaved previously.
By the way, this is now happening under the wine-staging environment, not the Crossover variant that was causing the issue before. The difference is, whereas that issue came up any time I used a drop-down menu in a dialog box, this one seems to be occasional/sporadic/unpredictable (and doesn't seem to be related to dropdown menus, just dialogs in general).