[Bug 48383] New: Home Designer Suite 21.3.1.1x64 encounters "a serious error" when attempting a 3D view
https://bugs.winehq.org/show_bug.cgi?id=48383
Bug ID: 48383 Summary: Home Designer Suite 21.3.1.1x64 encounters "a serious error" when attempting a 3D view Product: Wine Version: 5.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: 74.schutt@gmail.com Distribution: ---
Created attachment 66142 --> https://bugs.winehq.org/attachment.cgi?id=66142 Wine terminal outout
I'm testing Home Designer Suite 21.3.1.1x64 on 5.3-rc3 with the patch from bug 48371 applied, and using "winetricks vcrun2017" as suggested in bug 48377.
After starting home designer and opening a new plan, I am trying to get a 3D view of my first enclosed space.
First, I use the external wall tool to draw an enclosed space with four walls.
Then, from the Home Designer menu bar I select "3D -> Create Camera View -> Full Camera". That creates a camera cursor on cross-hairs, which I can move around with the mouse to where I want to position the camera. Then I left-mouse-button down and drag to point the camera in some direction.
When I release the mouse button, the Home Designer window goes blank, and I get a popup that says "A serious error occurred. ... Please restart the program and contact Technical Support." I can use "File -> Exit" to leave the program.
I've attached the terminal output from Wine.
https://bugs.winehq.org/show_bug.cgi?id=48383
Louis Lenders xerox.xerox2000x@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox.xerox2000x@gmail.com
--- Comment #1 from Louis Lenders xerox.xerox2000x@gmail.com --- Hi, i tested this but for me the 3d full camera view seems to work fine. I only used native ucrtbase and vcomp140. I can view walls and move view with mouse.
Maybe you could try only setting those two dlls to native, though i don`t really think that is the cause of your crash
If that doesn't help than maybe it`s a graphics card issue (opengl caps?) but that`s just a shot in the dark from me.....
https://bugs.winehq.org/show_bug.cgi?id=48383
--- Comment #2 from Jim Schutt 74.schutt@gmail.com --- Louis,
I've set the ucrtbase and vcomp140 dlls to native, and set the others supplied by vcrun2017 to builtin, but as you suspected it didn't affect my problem where I can't use the 3D full camera view.
Any other suggestions on what to try, or how to get some output that might suggest what else I could try, are greatly appreciated.
https://bugs.winehq.org/show_bug.cgi?id=48383
--- Comment #3 from Louis Lenders xerox.xerox2000x@gmail.com --- (In reply to Jim Schutt from comment #2)
Louis,
I've set the ucrtbase and vcomp140 dlls to native, and set the others supplied by vcrun2017 to builtin, but as you suspected it didn't affect my problem where I can't use the 3D full camera view.
Any other suggestions on what to try, or how to get some output that might suggest what else I could try, are greatly appreciated.
What graphics card and driver do you have? As i said the only thing i can think of is a difference in our setup in that direction. Do other opengl programs work fine? Maybe running with WINEDEBUG=+wgl might reveal something but i don`t have the knowledge to see something from such a log, but maybe others have. And for now it`s just a bit guessing i must say, as i cannot reproduce the error....
https://bugs.winehq.org/show_bug.cgi?id=48383
--- Comment #4 from Jim Schutt 74.schutt@gmail.com --- (In reply to Louis Lenders from comment #3)
(In reply to Jim Schutt from comment #2)
Louis,
I've set the ucrtbase and vcomp140 dlls to native, and set the others supplied by vcrun2017 to builtin, but as you suspected it didn't affect my problem where I can't use the 3D full camera view.
Any other suggestions on what to try, or how to get some output that might suggest what else I could try, are greatly appreciated.
What graphics card and driver do you have? As i said the only thing i can think of is a difference in our setup in that direction.
I have a Radeon HD7750 w/ 1 GB RAM. I use the radeon kernel driver in kernel.org kernels that I compile myself. I'm currently running 5.3.18. I'll attach a dmesg output showing the kernel probing/setting up my card.
Do other opengl programs work fine?
I don't do a lot of 3D graphics, but I have used sketchup8 extensively on wine 4.x with no trouble. I've also used the linux version of Google Earth Pro a few times.
Maybe running with WINEDEBUG=+wgl might reveal something but i don`t have the knowledge to see something from such a log, but maybe others have. And for now it`s just a bit guessing i must say, as i cannot reproduce the error....
I'll attach such a log, in hopes it might help someone. A quick scan of the log revealed many lines like "0009:warn:wgl:wglGetProcAddress Function <blah> unknown".
If it will help I also have configure logs for my 32 and 64 bit builds.
https://bugs.winehq.org/show_bug.cgi?id=48383
--- Comment #5 from Jim Schutt 74.schutt@gmail.com --- Created attachment 66155 --> https://bugs.winehq.org/attachment.cgi?id=66155 kernel dmesg output for probing my graphics card
https://bugs.winehq.org/show_bug.cgi?id=48383
--- Comment #6 from Jim Schutt 74.schutt@gmail.com --- Created attachment 66156 --> https://bugs.winehq.org/attachment.cgi?id=66156 terminal output w/ WINEDEBUG=+wgl for failing 3D view attempt
https://bugs.winehq.org/show_bug.cgi?id=48383
--- Comment #7 from Louis Lenders xerox.xerox2000x@gmail.com --- I never had radeon card, but nvidia; in the past i had sometimes some luck playing with env variables like LIBGL_ALWAYS_SOFTWARE=1 (https://www.mesa3d.org/envvars.html) but i do not even know if they apply for your situation/driver, so don`t shoot me if i speak nonsense but maybe you could play with a few of them.
https://bugs.winehq.org/show_bug.cgi?id=48383
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #8 from joaopa jeremielapuree@yahoo.fr --- Does the bug still occur with wine-6.5?
-
WineHQ Bugzilla