http://bugs.winehq.org/show_bug.cgi?id=29168
--- Comment #262 from Alex alexzk@mail.ru 2013-07-23 14:52:00 CDT --- I think because patch itself is dumb :/ Nobody wants to update timer's counter using separated thread. Idea must be revised by someone with deep wine's knowledge and he must to proper update when all timings are done (my opinion).
My guess was to make exe-debugger, which puts HW breakpoints at this address on access and updates it when SWTOR tries to read it. But well, i'm lazy too :D
----------- Also you can try now just exe with NOT patched 1.5.18 - it should go. And if it is, this means latest wines changed something related to shared memory:
1. No shares - each exe gets own copy. 2. Enchanced Security - exe can't modify "kernel" memory. 3. Most unlikelly - address of the share is changed.
As usually while it goes on 1.5.18 - who cares :)