Page 1 of 1

nasty bug - s3d won't start on multiple screens windows 10

Posted: Wed Oct 09, 2019 10:29 pm
by arhi
This was not happening to me on win7 but on win10 I'm constantly having issues of s3d not wanting to start (opens the main window and then it stays white and app is not responding) ... I clean the registry key and it works (all settings lost) .. works for few days, then stop again .. etc etc..

today, the same thing happened to me with prusa slicer 2.0 ... (not same but similar, it opened menus and interface but when it was about to init the 3d view it stopped and became unresponsive), but, I noticed similarity, both prusa slicer 2 and simplify3d were opening on left screen (negative X !!! ) so I assumed it had to do something with that, and as I remembered that developer mentioned that "geometry" key in the registry is "position of windows" I deleted only that key and dang s3d opened properly on the main screen (positive X) ... so, the issue I was fighting is - I move s3d to the left monitor, close it, it tries to start on the left monitor (negative X) and cannot.

PLEASE FIX !!! should be simple :D .. if there's an issue of starting on negative X (I'm now finding more and more 3d apps that have same issue, looks like it might have to do with Qt) just reset it back to main screen but start :)

Re: nasty bug - s3d won't start on multiple screens windows 10

Posted: Fri Oct 11, 2019 7:45 am
by arhi
debugging prusaslicer (since I don't have access to s3d source :D ) and what fails is

wxGLCanvas::SwapBuffers()

so seems to be combo of nvidia studio driver and windows 10 that's preventing normal operation ...

Re: nasty bug - s3d won't start on multiple screens windows 10

Posted: Fri Oct 11, 2019 2:19 pm
by arhi
this def. is not s3d bug, def something with my registry is %@^#^%&(#$% that prevents any app from opening wxGLCanvas outside of main monitor. It's not NV driver as I tested on second machine .. it's not even system settings as I tested as other user on the same box and it works ok... so something in my user registry is preventing s3d (and any other app using wxGLCanvas) to start on non-main monitor. All the "fixes" so far were just hiding the real issue... now trying to debug what could be the registry issue will probbly take time but.. at least I know where the problem is... maybe would be possible to remove the whole thread from the forum not to cause any confusion...

Re: nasty bug - s3d won't start on multiple screens windows 10

Posted: Sun Oct 13, 2019 12:47 am
by klabautermann
I can confirm this issue. I came here looking for an answer as to why my S3D install was freezing on every load. The fix of deleting the "geometry" key resolved this instantly. Def an issue with the software and the position of the window.

Re: nasty bug - s3d won't start on multiple screens windows 10

Posted: Mon Oct 14, 2019 3:00 pm
by arhi
klabautermann wrote:
Sun Oct 13, 2019 12:47 am
I can confirm this issue. I came here looking for an answer as to why my S3D install was freezing on every load. The fix of deleting the "geometry" key resolved this instantly. Def an issue with the software and the position of the window.
make another user on your system
start s3d there
move the s3d to another screen
close it
start it
it will start properly on the second screen

there's something messed up with mine (and your) registry that's doing this :(
I have the same problem with prusa slicer and some other apps too (netfabb for e.g. too) ... I traced it to wxGLCanvas::SwapBuffers() function that never finishes .. it's opengl.dll nothing prusaslicer can do (I assume exactly same thing happening with s3d) ... but it only happens on my user, only on this one windows 10 .. I tried on another windows 10 (also with 3 and 4 screens) - no issues, pinged few friends to try, they can't reproduce, exactly the same win10 build as mine, exactly the same nvidia drivers version .. I spent 5 hours comparing registry between two users on same machine, one working other not, and could not find what's the issue making the problem :( but is def. a registry issue.. anyhow I'm now super careful not to close s3d moved on non-primary screen :(

Re: nasty bug - s3d won't start on multiple screens windows 10

Posted: Wed Oct 16, 2019 3:19 am
by arhi
klabautermann wrote:
Sun Oct 13, 2019 12:47 am
I can confirm this issue. I came here looking for an answer as to why my S3D install was freezing on every load. The fix of deleting the "geometry" key resolved this instantly. Def an issue with the software and the position of the window.
hm, I spent bunch of time migrating to other profile and the bug is here now again :( ...

there's something we both have that's messing up the s3d (and prusa slicer and ..) ... do you maybe use synergy ( https://symless.com/synergy ) ?

Re: nasty bug - s3d won't start on multiple screens windows 10

Posted: Wed Oct 16, 2019 3:52 am
by arhi
this is mighty weird .. so I really think we can figure out whats a common denominator between our boxes ..

I uninstalled synergy as that I was suspecting on, no change

but check this out

now I have 2 admin accounts on this win10 that have s3d installed (I actually use prusa slicer for testing as it's easier just to edit ini file than to edit registry, as they behave identical with this bug)

I removed "auto login" feature to have better contro

reboot computer
login as A
wxGLCanvas::SwapBuffers() won't pass trough
login (without signing out) as B
wxGLCanvas::SwapBuffers() works, app starts no problem on any screen
switch back to A
wxGLCanvas::SwapBuffers() won't start
reboot
login as B
wxGLCanvas::SwapBuffers() won't pass, app don't start
sign in as A (B still signed in)
wxGLCanvas::SwapBuffers() works, app starts
switch to B
wxGLCanvas::SwapBuffers() don't work
sign out B, switch to A
wxGLCanvas::SwapBuffers() does not work

?!?!?!?

so the "first logged in user" can't start the app on non-main screen, second logged in user works ok, when you logout the first one and second becames only it won't work also ?!?!?!?!?!?!???!?!?!?!?!?!?!

what magic is this

Re: nasty bug - s3d won't start on multiple screens windows 10

Posted: Wed Oct 16, 2019 9:01 am
by arhi
wxwidgets bug reported: https://trac.wxwidgets.org/ticket/18532

hopefully...

Re: nasty bug - s3d won't start on multiple screens windows 10

Posted: Wed Oct 16, 2019 2:31 pm
by arhi
wxwidgets just calls win gdi swapbuffers() :( .. and there is no (afaic) source for gdi32.dll :(

can you who are affected by this get a md5() or sha1() of your gdi32.dll so we can compare them?
https://support.microsoft.com/en-us/hel ... for-a-file
fciv dl: http://download.microsoft.com/download/ ... 86-enu.exe

also, is there anyone with desktop computer (looks like laptops are not affected) with multiple monitors (ideally 3) check if they are affected and get your md5() or sha1() of the gdi32.dll please

Code: Select all

D:\bin\fciv>fciv -md5 -sha1 c:\windows\system32\gdi32.dll
//
// File Checksum Integrity Verifier version 2.05.
//
                MD5                             SHA-1
-------------------------------------------------------------------------
4e7fbe38e5a7b6054dc7c33c62b87651 58e8edfb95889e9fbc59cc88fb832295953ba448 c:\windows\system32\gdi32.dll

D:\bin\fciv>fciv -md5 -sha1 c:\windows\syswow64\gdi32.dll
//
// File Checksum Integrity Verifier version 2.05.
//
                MD5                             SHA-1
-------------------------------------------------------------------------
4e7fbe38e5a7b6054dc7c33c62b87651 58e8edfb95889e9fbc59cc88fb832295953ba448 c:\windows\syswow64\gdi32.dll

D:\bin\fciv>fciv -md5 -sha1 C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~18362.418.1.9\amd64_microsoft-onecore-reverseforwarders_31bf3856ad364e35_10.0.18362.418_none_f84061b4fe389745\f\gdi32.dll
//
// File Checksum Integrity Verifier version 2.05.
//
                MD5                             SHA-1
-------------------------------------------------------------------------
fa7e6a21201531c21eddf633fbc460f5 ecc76e04d5f7ac3b5df60aa2223843cf7191bd5b c:\windows\servicing\lcu\package_for_rollupfix~31bf3856ad364e35~amd64~~18362.418.1.9\amd64_microsoft-onecore-reverseforwarders_31bf3856ad364e35_10.0.18362.418_none_f84061b4fe389745\f\gdi32.dll

D:\bin\fciv>fciv -md5 -sha1 C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~18362.418.1.9\amd64_microsoft-onecore-reverseforwarders_31bf3856ad364e35_10.0.18362.418_none_f84061b4fe389745\r\gdi32.dll
//
// File Checksum Integrity Verifier version 2.05.
//
                MD5                             SHA-1
-------------------------------------------------------------------------
8b9fa7cbae407661374d405d8ec06fde 1873629d206309b67f2a8067f7b632d33d467bbc c:\windows\servicing\lcu\package_for_rollupfix~31bf3856ad364e35~amd64~~18362.418.1.9\amd64_microsoft-onecore-reverseforwarders_31bf3856ad364e35_10.0.18362.418_none_f84061b4fe389745\r\gdi32.dll

D:\bin\fciv>fciv -md5 -sha1 C:\Windows\WinSxS\amd64_microsoft-windows-gdi32_31bf3856ad364e35_10.0.18362.1_none_2bdc19f7c689fa4b\gdi32.dll
//
// File Checksum Integrity Verifier version 2.05.
//
                MD5                             SHA-1
-------------------------------------------------------------------------
2839609118f48dea292084e43faa72d8 9e91d74d5b9bf64a3d4be8c5ea3594f5da2bc299 c:\windows\winsxs\amd64_microsoft-windows-gdi32_31bf3856ad364e35_10.0.18362.1_none_2bdc19f7c689fa4b\gdi32.dll

D:\bin\fciv>fciv -md5 -sha1 C:\Windows\WinSxS\wow64_microsoft-windows-gdi32_31bf3856ad364e35_10.0.18362.1_none_3630c449faeabc46\gdi32.dll
//
// File Checksum Integrity Verifier version 2.05.
//
                MD5                             SHA-1
-------------------------------------------------------------------------
4e7fbe38e5a7b6054dc7c33c62b87651 58e8edfb95889e9fbc59cc88fb832295953ba448 c:\windows\winsxs\wow64_microsoft-windows-gdi32_31bf3856ad364e35_10.0.18362.1_none_3630c449faeabc46\gdi32.dll

D:\bin\fciv>