|Version:||6.6.0 Beta 6|
|Latest Wine Version Tested:||6.7|
Maintainers: About Maintainership
Opening map editor, opening model editor, basic manipulations, OpenGL renderer, compiling the map, and launching the game with the map.
What does not
What was not tested
Many special features.
A patch has been released to fix some Wine-issues: http://quark.sourceforge.net/download.php#patches
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Ubuntu 18.04 "Bionic" amd64 (+variants like Kubuntu)||Apr 25 2021||6.7||Yes||Yes||Yes||Silver||DanielPharos|
|Show||Ubuntu 18.04 "Bionic" amd64 (+variants like Kubuntu)||Apr 16 2021||5.0.5||Yes||Yes||Yes||Silver||DanielPharos|
|Show||Ubuntu 18.04 "Bionic" amd64 (+variants like Kubuntu)||Apr 09 2021||6.6||Yes||Yes||Yes||Silver||DanielPharos|
|Show||Ubuntu 18.04 "Bionic" amd64 (+variants like Kubuntu)||Mar 26 2021||6.5||Yes||Yes||Yes||Silver||DanielPharos|
|Show||Ubuntu 18.04 "Bionic" amd64 (+variants like Kubuntu)||Mar 26 2021||5.0.4||Yes||Yes||Yes||Silver||DanielPharos|
|Bug #||Description||Status||Resolution||Other apps affected|
|3548||.lnk file is created on the desktop together with the program icon...||NEW||View|
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
by DanielPharos on Saturday March 16th 2019, 8:04
Due to a copy-paste of assembly code from the Glide 2 programming guide, both the software and Glide (3Dfx) renderers in QuArK disable floating point exceptions when they are first initialized, and leave them off. This explains why using the software renderer before switching to the OpenGL/Direct3D renderer makes the error go away for that session.
The latest nightly builds of QuArK 6.6.0 Beta 7 contain a FP-exception workaround for the OpenGL renderer, enabled by default. Floating point exceptions are disabled when the call to OpenGL to render the viewport is made, and re-enabled when that call returns. But because this issue is restricted to OpenGL implementations (as this issue is not know to occur with Direct3D on Windows), the workaround is currently not implemented for the Direct3D renderer. In other words, if the used Direct3D implementation in Wine translates Direct3D-calls to OpenGL, this error can still happen. Note also that together with the implementation of this FP-exception workaround, the floating point exception disabling behavior of the software and Glide renderers has been corrected (i.e. removed), so that particular workaround no longer functions.
As can be seen from the test results, it appears that Wine started triggering this behavior between 3.0-rc4 and 3.0-rc5; my guess would be commit 5020fb7c478a080461df8655a3eac629648c4488. (This commit cannot cleanly be reverted on later versions of Wine, due to commit a83532d8dd5e99226dbccf0398083b052f033b9a, and probably more changed after that.) I haven't tested reverting this commit, as the commit is not the problem: the bug is in the OpenGL implementation, not QuArK or Wine. Also visible in the test results is that the error can sometimes disappear (my test results from Jan 22 2019 to Mar 08 2019 were good, but Mar 16 2019 is bugged again); this is probably due to the OpenGL implementation or drivers in the OS being updated or otherwise changed. Hopefully at some point the developers of these OpenGL implementations will correct their bugs, so that the floating point exception doesn't happen anymore in the first place.
by DanielPharos on Saturday March 16th 2019, 8:05
The "invalid floating point operation" error explained
, but the website decided to eat it.)