mazoola
Advanced Member
USA
Joined: Mar 25, 2015
Post Count: 153
Status:
Offline
|
|
Re:
Sweet Home 3D does not start for directx issues
|
I've also discovered 5.x will close with a DirectX error message if a window is positioned so that a portion of it appears on two monitor screens driven by different graphics cards.
Currently, I have two monitors to my front left and right, both driven by a single older Nvidia GeForce of some sort [8600 GT, maybe?], plus a third monitor on a swing arm to my hard right that's driven by on-board video from the Intel motherboard. Typically, I use monitors 1 and 2 for sw3d, with the main UI on 1 and the 3D window on 2. Monitor 3 I use for support: web searching solutions, hunting textures, searching and downloading new models.
Should the 3D window be moved accidentally onto monitor 3 (and that might mean only the end of the window frame, without including any portion of the image), sh3d announces it's about to close itself because of a Direct X mismatch.
At this point every subsequent attempt to start the app will fail. The only way I've been able to clear the problem has been to go to Window's Display Properties menu (right click on the desk top; choose 'Graphic Properties'). Go to the 'settings' tab and disable the offending monitor. When you next invoke sh3d, it will start entirely in the two remaining monitors.
My memory of 4.6 (?) is that it didn't mind my dragging windows to any of the screens. If faced with a particularly time-consuming render, I'd occasionally drag the render UI to the third monitor, begin rendering, and then return to monitors 1 and 2 to continue editing while the render kept on.
|
[Oct 30, 2015, 7:37:25 PM]
|
|
[Link]
|
|