Hello everybody, During the past three years, I regularly tested SolidWorks http://appdb.winehq.org/objectManager.php?sClass=version&iId=8983 with Wine. At the beginning, it was just for fun, as it was really far from working. But now, things has changed : the application installs out of the box and is really close to work. There are some bugs remaining, but the situation is not worse than it was for Autocad a few months ago, for example. But there is is still a big problem with OpenGL http://bugs.winehq.org/show_bug.cgi?id=13195 , that prevents any use. Without this bug, the application will be rated bronze or maybe silver ! The OpenGL problem was partially solved from times to time by some patches, but 0.9.47 introduced a big regression. Now OpenGL is definitely broken, with two blocking bugs. The problems are related to Pixelformat choice, child windows management, and offscreen rendering. I tried to investigate it by myself, but unfortunately I know about nothing of OpenGL and wgl in wine, so I was just able to file bug reports, and some partial workarounds allowing the application to run, but with big display issues ( see bug 13195). So my question is : is SolidWorks the only application impacted by these OpenGL issues ? I understand that most of the games are using only one OpenGL window so they are not impacted, but there are many other OpenGL apps with multiple windows/viewports. I dig Appdb and bugzilla, and found nothing recent related. So if some other users can report to bugzilla similar problems with different GL apps, it may help to narrow the problem ! Thanks
The main problem you may find is that applications that are not open source and written for windows are mostly using DirectX instead of OpenGL. How do you also define that an application is using OpenGL or DirectX apart from the errors? Sometimes you are also using both, like my application (actually a dual application) where the installer is using OpenGL, half of the dual application seems fine with OpenGL/is written in Java (apart from child window management and a buggy refreshing rate) and the other half is at the time being crashing because of a DirectX error.
The main problem you may find is that applications that are not open source and written for windows are mostly using DirectX instead of OpenGL. How do you also define that an application is using OpenGL or DirectX apart from the errors? Sometimes you are also using both, like my application (actually a dual application) where the installer is using OpenGL, half of the dual application seems fine with OpenGL/is written in Java (apart from child window management and a buggy refreshing rate) and the other half is a script application and at the time being crashing because of a DirectX error.
Most of the professional 3D CAD/CAM apps. are pure OpenGL. But I agree, there are few open-source ones. So it is quite difficult to find something useful for debugging. An option should be to write testcases, but it is out of my skills...
My problem is another. It looks like that the child window is not inheriting the template or whatever it is and it sets itself back to a standard Windows window. Problem is however when no such standard window had been planed, maybe you end up with a window without anything around it and making you unable to move or resize it, let alone open it if this was minimized. I have this bug in an editor with a mainframe and another frame for the text file whereby you have the possibility to maximize the test file and it ends up with only one window. I just checked an open source editor and the frame was missing, it froze with everything around it.