Jump to content
Korean Random
Sign in to follow this  
fsdgsg

[1.6.1.3/8.1.6_6] Does XVM work on Mac Mojave?

Recommended Posts

I have mac Mojave and the xvm works in garage but not in battle, the minimap also doesn't show last known location for unspotted enemies. had this issue since the transfer from standalone launcher to WGC

xvm.log python.log

Edited by Mixaill

Share this post


Link to post

Short link
Share on other sites

Currently there are several problems with a) 64-bit clients b) new Catalina-compatible CrossOver wrapper. 

 

We have some progress (in the last release we fixed the sound loading) but the fact that all my attempts to install the hackintosh didn't succeed slows down the progress.

 

By the way, for macOS versions prior to Catalina, there is workaround to use generic Wine instead of Wargaming wrapper to launch World of Tanks.

 

----

 

@fsdgsg You also have various other mods, such as mod_calculator_rankings_battle, which may be incompatible with macOS because of differences in the working directory for Windows and MacOS. We fixed this for our mod, but other mods usually do not contain this fix.

 

It will be fixed in the vanilla WoT no earlier than 1.7.0 (end of November, I think).

Edited by Mixaill

Share this post


Link to post

Short link
Share on other sites

Hi,

I'm playing on Mojave and High Sierra. There is one feature working 'in battle', the life bar above other player's tanks shows the little tag in the colour according to the rating; rating itself is shown when cmd key is pressed.
Stats are not shown in garage.

Edited by Juan_M_65

Share this post


Link to post

Short link
Share on other sites

The WG Game Center Mac Wrapper, regardless of macOS version, is 64-bit - most likely to ensure compatibility with macOS Catalina as that version does not support any 32-bit code at all.

 

CodeWeavers, who produced the WG Game Center Mac Wrapper for Wargaming, has just released Crossover 19 which appears to allow 32-bit code on macOS as a 64-bit process [wine32on64].  This may be significant in that it may allow developers who cannot/will not update to 64-bit to continue to use 32-bit code - e.g., XVM

 

However IMHO anything that enables 32-bit code to run is a determent to the game running on a 64-bit OS as it requires the OS to run a compatibility layer, maintain both 32-bit and 64-bit libraries, require 32-bit code to be installed and take up space on your storage devices, etc.

 

64-bit only OSes are on the ascendance and should be getting attention by developer as eventually 64-bit will be the standard. 32-bit is in its twilight and spending resources on 32-bit code may not be the best value as eventually it will no longer be available. 

 

Apple made the right decision of only allowing 64-bit code. This has been painful for some but they need to remember that Apple has been telling developers for several years that a 64-bit ONLY environment was coming which clearly puts the fault on the developer.  Perhaps they could look at how CodeWeavers handled the situation ...

 

Before you start stating that macOS users are not relevant - why would Wargaming produce a 64-bit version of World of Tanks if macOS users were not relevant?

 

 

Edited by macOS User

Share this post


Link to post

Short link
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...