Create a Win10 64 Bit bottle and call it.Download the SWTOR installer from the SWTOR website.Well, it's not that hard, but you have to get used to some Windows terminologies. When I get it, I will post my results here.Įdit: Do NOT use swtor_fix.exe as it is no longer being maintained and not compatible with newer versions of TOR and CrossOver! I'm still waiting on my M1 MB Air to arrive so I can test this theory out (I'm still on my Skylake Hacky with a GTX 1070, thus I'm limited to High Sierra as my OS). As you've experienced, it doesn't work under Big Sur (and probably Catalina as well), because both don't support 32 Bit code. It is mainly a problem with the two main processes of TOR not being able to communicate with each other, thus the handoff to the main process is never happening.įor example, SWTOR runs flawlessly in CrossOver 20.0.2 in a WIN10 64Bit bottle under High Sierra, which still supports 32 Bit code, so CrossOver doesn't need to substitute its own 32 Bit libs. I think that the removal of all 32 Bit code in Catalina, and the re-introduction of these libraries in CrossOver lead to revival of the same error that made swtor_fix.exe necessary. Here comes some speculation of my own, so take this with a huge shovel of salt. In later versions of Wine and CrossOver, swtor_fix.exe actually introduced new issues (crazy latency for one), as it hasn't been maintained since 2016 AFAIK. Yes, swtor_fix.exe was originally created to fix this, but once newer versions of Wine and CrossOver fixed the problem (probably inadvertently), it was no longer needed and maintained. It's probably the same issue that has plagued SWTOR under Wine and CrossOver from the beginning.
0 Comments
Leave a Reply. |