• Content count

    938
  • Joined

  • Last visited

  • Battles

    3262

Community Reputation

164 Valued poster

About ForgMaxtor

Recent Profile Visitors

116 profile views
  1. I'm not sure what the worst ship is right now. As far as ships I'm actually playing right now, the one I'm enjoying least is Zuiho -- I made the mistake of not finishing the grind through Zuiho before they removed manual drops from T4-5 CVs now I'm stuck finishing the grind to Ryujo (which I want mostly for operations) using autodrops only and it reeeealy sucks. About 1/2 my games I'm in a T6 match where I have to try to find a way to keep my very small air wing alive against Clevelands, Bayerns, and New Mexicos. When I do get a T5 match, about 1/2 the time I'm up against an AS Bogue. An AS Bogue can easily shut down a Zuiho as long as the Bogue player has half a clue. Not that the AS Bogue player can then do much to affect the match outcome once he's shot down all the Zuiho's planes because his damage potential is so low. But the end result is that in my experience a Zuiho vs. AS Bogue match ends with both CVs near the bottom of their team's XP tally. Only fun games I get are when it's a Zuiho vs. Zuiho match. Still not as fun to play as when manual strafe and dropping was an option, but at least it's (mostly) a m. I'd say the least pleasurable grind experience I've had thus far overall has been the Karlsruhe. She used to really suck. She had no advantages over the Kuma, Phoenix and Svietlana (RN cruisers hadn't been released yet) -- Kraparuhue had lowest hp of all of the T4 cruisers, also the slowest, meh guns, just two meh torpedoes per side, lightly armored, and worst AA. She didn't even have best T4 cruiser concealment -- Svietlana beat her pretty handily in this area. Her only saving grace was that it doesn't take very long to grind through a T4 no matter how sucky the ship is. That was many patches ago, though -- she's received some fairly significant buffs since so I imagine she's more palatable now.
  2. I can't open up the game right now to verify, but if I read the description correctly, the Gallant I mission -- Be among the 5 XP earners in a winning battle -- is a once/day mission. The Gallant II mission - Be top XP earner in a winning battle -- is a once only per account mission. This rewards a "Large" Dunkirk container, tho, so I assume you get a lot more swag. Probably if you buy Gallant and make it a point to achieve the Gallant I mission daily until it expires, you're going to achieve the Gallant II mission as well at some point.
  3. 2.0.10 Mac Wrapper is cooperating with WoWS 0.6.8 just fine for me as well. Thanks WG and Codeweavers!
  4. Yeah; if given stats and an airwing size similar to what the historical ship was actually planned to carry, T6 would be a good fit for her. The 70+ air wing depicted in the T8 version of the ship currently in supertest is simply fantasy.
  5. Talk about quick service! Apparently a fix for the 0.6.8 issue has already been achieved. From thread I already linked above: I won't be able to apply and confirm that it works for me until tonight, but hopefully there will be no issues. Thanks to Codeweavers and WG for responding so quickly to this!
  6. That was quick. Thanks for the heads up! I won't be able to apply the fix until tonight, but hopefully this will fix the issue. For ease of reference, here's a paste of the info about how to install the fix (again, see thread I linked above for the original):
  7. I'm definitely curious to give her a second chance now. 9.9km radar at Tier 7 is actually kind of a big deal; none of the other T7 radars come close to having this range. This radar plus the potent USN 203mm AP could make her a really nasty threat to smoke cruisers like Belfast, Fiji, and Kututzov especially.
  8. Just so eveyone in the Mac community is aware, WG has confirmed they are aware of the 0.6.8 issue and a fix is being worked on. From:
  9. Since this seems to be one of the most popular WoWs Mac support threads, even though it's not the official one: WG is aware of the 0.6.8 issue and a solution is being worked on. From this thread: So they're on it. Hopefully, it won't take too long and we'll all get some time to enjoy the Dunkirk missions and the rest of Ranked.
  10. Yep; 0.6.8 and Mac Wrapper appear to be a zero-day hard crash for many, if not all, Mac players (including myself). More info on this thread: I have already sent a report and a system log capture of my crash to ports@codeweavers.com. If anyone at WG support would also like files, please contact me and I'm happy to provide.
  11. Yep. Same issue. It sounds like this may be a universal zero-day fail for 0.6.8 on the Mac Wrapper. If anybody is NOT experiencing this issue with the Mac Wrapper and 0.6.8, please report.
  12. MAC WRAPPER FAIL with 0.6.8 As per thread linked below. WoWs 0.6.8 is causing a hard crash for many of us Mac wrapper players. In fact, I haven't yet heard of anyone who is able to get 0.6.8 to work via the Mac Wrapper. I did experience this issue with the 0.6.8 Public Test, and reported it as a bug, but evidently the report was ignored. At least for me, 0.6.7 was very stable on the Mac Wrapper. Good performance, no crashes, so this is definitely a new issue with 0.6.8.
  13. OK so it's not just me then; this is exactly the same error I'm getting. I reported this as a bug during the Public Test but evidently my report was ignored. It sounds like this is at the very least a widespread Mac Wrapper bug with 0.6.8. It might be universal -- is the Mac Wrapper working for ANYBODY with 0.6.8?
  14. Uh oh. I am now having this issue with the 0.6.8 Public Release. Game is completely broken for me as of this morning. I don't have a lot of time to troubleshoot right now, but I'll try to look into it tonight. Going to be a difficult problem to track down though -- as noted above, the crash does not seem to be producing any kind of error message or crash log so I don't have much to go on. EDIT: I found some information in the general system log. Just in case it's helpful, here it is: 7/19/17 8:23:47.895 AM launchservicesd[82]: SecTaskLoadEntitlements failed error=22 7/19/17 8:23:47.904 AM launchservicesd[82]: SecTaskLoadEntitlements failed error=22 7/19/17 8:23:48.436 AM appleeventsd[53]: SecTaskLoadEntitlements failed error=22 7/19/17 8:23:53.193 AM launchservicesd[82]: SecTaskLoadEntitlements failed error=22 7/19/17 8:23:53.193 AM launchservicesd[82]: SecTaskLoadEntitlements failed error=22 7/19/17 8:23:55.112 AM World of Warships[5763]: -[NSProgressIndicator animate:] is deprecated. 7/19/17 8:23:55.115 AM launchservicesd[82]: SecTaskLoadEntitlements failed error=22 7/19/17 8:23:56.581 AM launchservicesd[82]: SecTaskLoadEntitlements failed error=22 7/19/17 8:23:56.589 AM launchservicesd[82]: SecTaskLoadEntitlements failed error=22 7/19/17 8:23:56.591 AM launchservicesd[82]: SecTaskLoadEntitlements failed error=22 7/19/17 8:23:56.597 AM appleeventsd[53]: SecTaskLoadEntitlements failed error=22 7/19/17 8:23:56.639 AM launchservicesd[82]: SecTaskLoadEntitlements failed error=22 7/19/17 8:23:56.646 AM launchservicesd[82]: SecTaskLoadEntitlements failed error=22 7/19/17 8:23:56.648 AM launchservicesd[82]: SecTaskLoadEntitlements failed error=22 7/19/17 8:23:56.654 AM appleeventsd[53]: SecTaskLoadEntitlements failed error=22 7/19/17 8:23:58.864 AM launchservicesd[82]: SecTaskLoadEntitlements failed error=22 7/19/17 8:23:58.871 AM launchservicesd[82]: SecTaskLoadEntitlements failed error=22 7/19/17 8:23:58.873 AM launchservicesd[82]: SecTaskLoadEntitlements failed error=22 7/19/17 8:23:58.879 AM appleeventsd[53]: SecTaskLoadEntitlements failed error=22 7/19/17 8:24:00.227 AM launchservicesd[82]: SecTaskLoadEntitlements failed error=22 7/19/17 8:24:01.617 AM launchservicesd[82]: SecTaskLoadEntitlements failed error=22 7/19/17 8:24:01.617 AM launchservicesd[82]: SecTaskLoadEntitlements failed error=22 7/19/17 8:24:04.613 AM com.apple.xpc.launchd[1]: (com.codeweavers.worldofwarships.52512[5763]) Service exited with abnormal code: 4
  15. Understood. However, as previously mentioned, I have not been seeing particularly long queue wait times for Ranked battles this season, and if waiting an extra 30 seconds would mean better matchmaking, I wouldn't mind. Mind you, I don't play Ranked at really off times when the population is low, but IMHO you're kinda asking for long waits and/or strange matchups at these times.