https://bugs.winehq.org/show_bug.cgi?id=56912
--- Comment #8 from stormtrackertony@gmail.com --- Do you recall if you were able to see radar data on the map with the new version (instead of just a blank map?)
One thing I noticed that may or may not be important. Though the error happens in the same manner, the backtrace is different between Wine version 8.0.1 and 9.0...When the program developer first said the problem was ldsl , it was because of the backtrace on 8.0.1 (just attached in the post above)...It includes:
0x0043a534 gr2analyst+0x3a534: ldsl %eax,%esi
and does not even mention vcmpps...The backtrace I originally posted here was after upgrading to Wine 9.0 which replaced that ldsl line with:
0x0043a534 gr2analyst+0x3a534: vcmpps $0x0e, %xmm0, %xmm1, %xmm2
Does seeing this old file with ldsl mention change your thoughts?
Also, I have confirmed that my system does not support AVX. Though, my understanding is the program does not use AVX, but instead uses SSE2 instructions (which my system does support).
Interesting aspect to this is there was a significant speed improvement between the older Visual Studio 2008 compilation and the new Visual Studio 2022 compilation which the program developer could not explain. He said "Render times for radar data have been cut in half for the VS2022 compilation, but I'm not sure where the performance boost is coming from. Both are set to use SSE2 instructions, so that has not changed."
I'm not a programmer myself, so my knowledge is limited on this stuff. But I'm wondering if he could have somehow accidentally added AVX (or AVX2) instead of the intended SSE2. If so, that could potentially explain both the performance boost of the new version and why my system is crashing on it.....I mean, old version uses SSE2, which is supposed by my system and works on my system. New version is supposed to still use SSE2, yet does not work on my system, gives AVX error (not supported by my system) for some unknown reason and a mysterious significant performance boost in the software...Seems coincidental?