Jump to content


  • Content Сount

  • Joined

  • Last visited

  • Battles


Community Reputation

18 Neutral

About andarragh21

  • Rank
    Petty Officer
  • Insignia

Recent Profile Visitors

430 profile views
  1. New client works for me. Thanks for such a quick response.
  2. Never mind. Got it sorted, I think. Just didn't install right.
  3. After today's update to the WGC, I have not been able to get it to open. Is anyone else having this problem?
  4. I think I have a workaround (same thing happened to me). Go to your documents folder and double click the WoWs alias folder. If you switch to column view in the finder window, you can scroll back a few folders until you find a "World of Warships 3.1.2" folder (file path is something like ~/User/Library/Application Support/World of Warships/World of Warships 3.1.2, where Library is normally invisible). Inside that is the new Wargaming Game Center app/new wrapper. I played through that and it seems a fair bit improved.
  5. Am I missing something with this? When I go to download it in any of the locations, including your links, the only thing that downloads is the old 2.0.29 WoWs Launcher wrapper. Is that the new one, or is something not linking right for me?
  6. iOS is not MacOS. The main reason more companies don't do mac native games is the graphics part is that Apple has held fast to its own, proprietary graphics drivers that are completely different from the DirectX ones Windows uses. I'm not saying it can't be done (Blizzard has always done it), but most games will be published for Windows only and eventually be brought to Mac by a specialist publisher like Aspyr or Feral Interactive. Otherwise, because of those fundamental programing differences, the original publisher would have to have two entirely separate development teams, one for Mac and one for Windows. Using a WINE wrapper, WG can bypass the need for a Mac dedicated team, but are reliant on CodeWeavers to keep up with changes to their client. There's plenty of blame to go around on these problems. The best we can do is keep providing feedback, now that WG is paying attention.
  7. The problem is that so much has changed in the last few months, let alone 2 years, that finding the actual culprit(s) would be basically impossible. The main problems are going to be the shift to DirectX11 and having been running a 64bit client on a 32bit wrapper. The real problems with these are on CodeWeavers' end with the wrapper not having been kept up to date in those two years. They're just now getting around to finally working on updating it.
  8. I wonder if that's the reason for the WargamingErrorMonitor.exe spam I've been getting in the activity monitor since the PT runs for 0.8.3. Would certainly explain why the game bogs down when being asked to keep up with more moving elements, like large numbers of shells on screen.
  9. The lagging FPS that I have had so far on the x64 client (and this dates back to the PTS for 0.8.3) seems to be related to the number of projectiles on screen. You really notice it when two secondary BB's get in close. As well, once I closed out the game, my activity monitor had a bunch of open instances of WargamingErrorMonitor.exe that I manually had to force quit. I don't know if this is a problem for all players, or just mac and having to do with the wrapper. Hopefully someone can get the FPS fixed. It's not game breaking at the moment, but it is annoying.
  10. Make sure you get their test wrapper from the d_gladkov post at the top of the page. It at least fixed the torp lead issue for me. Video is still a little sluggish, but it was certainly playable for me.
  11. I've also noticed that activity monitor, under the "disk" tab on my computer, is showing a mass amount of WargamingErrorMonitor.exe instances. It doesn't look like they are actually actively doing anything, though. I wanted to see if anyone else is having this happen (in which case we might want to let WG and codeweavers know) or if it's just me.
  12. The new wrapper seems to have fixed that problem. Thanks for checking in.
  13. After re-downloading for about the 8th time, it finally worked this morning. Thanks.
  14. @JAKeller @dbw86 How were you able to get the 3.1.0 beta wrapper running? Every time I try to run it, it says the application is broken. The 3.0.1 wrapper from WoWp was working (sort of) for me. Any help would be appreciated.