Oolite Bulletins

Cholmondely wrote: ↑Thu Aug 28, 2025 12:08 pm

RockDoctor wrote: ↑Thu Aug 28, 2025 10:30 am

Come in, Number 5, your time is up!

They're all too busy hiding in the tunnels!

Talking about tunnels (sort of caves), I'd suggest Descent game series, where most of the action happens in mining tunnels across the solar system.

<still pursuing the possibility of a hybrid build>
Did you check that there is no msys-*.dll dependency for your Oollite.exe?

I've been experimenting with building Oolite on a newly downloaded MSYS2 environment. [...] MSYS2? Why would you try that, and not, say, cygwin64? MSYS uses also some POSIX wrappers around windows calls part of their msys-2.0.dll. I'm using another_commander's mingw64 build bundle, and it works as ...

another_commander wrote: ↑Tue Jul 29, 2025 8:06 pm

New pre-release with the fix is now up: revision 720da94

@Commander_X thanks for your patience and for helping with debugging accross time zones.

Glad I could be of help!
Pulled, compiled and I can confirm the dialog doesn't come up

I think that's my mistake again. You can see that it has successfully recognized that the 5B55 is not an active monitor, though. Can you try this build please? I changed it to go through each and every monitor of each adapter. Download: https://drive.google.com/file/d/1y-Dif6KSI9nGzUzpZR9yC5ahwGmQI...

Oolite test executable: https://www.filemail.com/d/rjwoyejafmlgpsh Alas, the dialog still pops up. Latest.log relevant: 14:01:42.710 [rendering.opengl.shader.support]: Shaders are supported. 14:01:42.739 [searchPaths.dumpAll]: Resource paths: Resources 14:01:42.741 [MSAA.setup]: Multisample anti-al...

I am sorry, I think I made a mistake somewhere. Here is a hopefully bug fixed version of the utility. Could you please give this a try? Download: https://www.filemail.com/d/vvqbnaqmdrbsugf Yes, the "monitor is attached/monitor active" seem to reflect "the situation on the ground"...

Very interesting. Can you please try running this version of the utility? I am testing whether we can distinguish the monitor of interest using its reported stateflags. Download: https://www.filemail.com/d/zrkqsjnlwwntzkv Here are the new results: EnumDisplayDevices i: 0 cb: 840 DeviceName: \\.\DIS...

Thanks but I was actually talking about this one here: https://www.filemail.com/d/urmcpsulrsujkbd Run it in a cmd window and you can also send the output to a file like enumdisp.exe > enumdispResult.txt Sorry, I thought it was about the little utility I mentioned. Here's the output of the one you l...

Can you please send the output of the little utility linked a few posts up? I think it would really help with understanding what is happening. I guess the best outputs related with IDing the monitors are these: Monitor Device Name: "\\.\DISPLAY1\Monitor1" Monitor Name: "27GL650F"...

Oh, that is disappointing. Just to be sure, in the VM under Windows settings->Display the GSM is marked as the primary monitor, correct? [...] Yes, the "GSM5B71" (not the detected "GSM5B55") is the primary monitor. Somehow, though, both Windows Settings and NVidia Control Panel ...

Nope, it seems the method still detected the disabled monitor. Log's second half for confirmation: 08:43:35.117 [dataCache.notFound]: No data cache found, starting from scratch. 08:43:35.118 [searchPaths.dumpAll]: Resource paths: Resources 08:43:35.140 [MSAA.setup]: Multisample anti-aliasing not req...

I looked through the Device Manager at the monitors registered with WIndows. "GSM5B55" monitor seems to be the disabled monitor (reported as "LG FULL HD") also fed by RTX 2070 SUPER (my third monitor, non-HDR). Incidentally, that's also the (Linux) monitor (which is running throu...

Continuing the discussion from this post in the alternative binary distribution thread: https://bb.oolite.space/viewtopic.php?p=301844#p301844 @Commander_X: OK, I will need your help with this. I have prepared a test exe with checkpoints similar to the one I made for phkb, but this time it includes...

I will look at any data you send in a while once I get home. In the meantime, could you please try disabling the MS Basic Display Adapter in the vm? You had this issue in the past and you had reported that disabling the adapter fixed it. I disabled it, but no luck, still getting the dialog. I might...