• Announcements

    • HEAVY265

      New Forum Lead!   11/17/2019

      It's with great pleasure to announce B2K as the new Forum Lead.   I am very confident he will be good for the forums, he has great ideas and direction for the future of the forums.
      Good luck sir and GOD speed.
Sign in to follow this  
Followers 0
AHWULF

1.30.3 Bugs

38 posts in this topic

The readme doesn't mention any Mac fixes, but I did fix some minor irritants. The mission leader submission invalid issue is still there, waiting on Oliver. There may be a 130.4 in a couple of weeks, so there is hope yet.

Most of 130.3 was so that China could start their beta. They are supposed to go live October 1. Assuming they get a big draw, it could mean a lot of Yuan in the Rat bank.

1.31 will have some major memory management improvements which will help eliminate stutters from both platforms, as well as the Windows-only smartheap out of memory error. Still a ways to go on 1.31 however.

Share this post


Link to post
Share on other sites

This "we can't be bothered to fix the Mac" stuff is really bullsh*t... I'm seriously considering unsubbing because of it. How am I supposed to OIC my squad if I can make waypoints or make marks on the map?

Share this post


Link to post
Share on other sites

It's not "we can't be bothered to fix the Mac" I am the Mac fixer.

This is a server problem that I can't do without Oliver's help. Getting the China beta up so that on October 1 the Chinese can start selling the game is more important since the $ it will bring in will keep our game in business.

The data the mac client is sending is somehow being rejected by the server. I can make whatever changes are necessary but only if I know what the server is choking on. All the #$@# changes the Chinese wanted have server code and only Oliver can work on it. Thus the financial future of the game may depend on 100,000 Chinese players paying massive Yuan which won't happen if the server blows Chinese chunks.

Sure it sucks (and I hate being ML too) but thats the way it is. Once the Chinese spin up their live beta Ollie should be able to check our little problem out.

Share this post


Link to post
Share on other sites

And I'm not blaming you bud. I hope you realize that I truly appreciate the work you do for us and hope you get reimbursed immensely by CRS down the line.

And I also understand the pressure of the China release. Hopefully it will be as amazing for the company as we all hope, but its just unfortunate that the current customers are put in the back seat in the meantime. For the mac users, it sometimes feels like the trunk... Hopefully once Ollie has either saved or doomed us all, we can work out the pile of issues that has slowly been gathering in the corner (map bugs, sound issues, etc)

**********************************************************

On a side note, I find that if I turn gamer tags and the HUD off, I get a 5-10x jump in FPS. Do you know why that is?

Share this post


Link to post
Share on other sites

5-10 frames or 5-10 times FPS (I assume frames)? People on both platforms have reported this, but no one knows why. If your mac/video is weak it might make sense, what's your mac/ram/video?

Yeah the China thing was supposed to be long done, but the $ is incredibly important as the rats get 20% of every Yuan. Right now $ is what's keep a ton of things from getting done. Including my being hired.

I could make perfect sound if they could afford to buy a decent sound framework - $9000.

Performance will increase but only in 1.31 and it's a lot of work. I've tried to fix most of the crasher bugs (you'd be amazed at how much less the mac version crashes on average than the PC version). They really need at least 2 more programmers fulltime.

I get a little money from the rats, plus they paid me to analyze why the PC version runs out of memory. But I am looking for fulltime work (have Apple phone interview next week).

Share this post


Link to post
Share on other sites

GL with the interview!! Fingers crossed. Although it might mean you will no longer have the time to dedicate fixing wwii bugs, I wish you get that job.

Share this post


Link to post
Share on other sites
5-10 frames or 5-10 times FPS (I assume frames)? People on both platforms have reported this, but no one knows why. If your mac/video is weak it might make sense, what's your mac/ram/video?

Yeah the China thing was supposed to be long done, but the $ is incredibly important as the rats get 20% of every Yuan. Right now $ is what's keep a ton of things from getting done. Including my being hired.

I could make perfect sound if they could afford to buy a decent sound framework - $9000.

Performance will increase but only in 1.31 and it's a lot of work. I've tried to fix most of the crasher bugs (you'd be amazed at how much less the mac version crashes on average than the PC version). They really need at least 2 more programmers fulltime.

I get a little money from the rats, plus they paid me to analyze why the PC version runs out of memory. But I am looking for fulltime work (have Apple phone interview next week).

I meant 5-10 TIMES the FPS. Its really crazy and I don't play with my HUD up or gamer tags on anymore (unless I'm flying). I'm using a Mac Mini 1.83GHz with a gig of RAM. I'm hoping to upgrade to the newer Mac Mini (2.xx GHz 4GB RAM, etc) in the near future (in time for 1.31 perhaps?).

Ahwulf needs to get full-time Rat status and the pay grade to reflect all the work he's done for us.

Share this post


Link to post
Share on other sites

Your Mac mini is below the minimum, does this one have Intel video or something better?

1 GB is too little, plus having a lame video card would make extra textures (like fonts) drag you down. Not sure if 1.31 will even run on your current mini.

Share this post


Link to post
Share on other sites
Your Mac mini is below the minimum, does this one have Intel video or something better?

1 GB is too little, plus having a lame video card would make extra textures (like fonts) drag you down. Not sure if 1.31 will even run on your current mini.

Its an intel, but definitely not a graphics screamer...

Share this post


Link to post
Share on other sites

Intel graphics are not supported actually, JAEGER specifically said that some time back, that there are too many opengl bugs to work around, which would explain your issues. If it works you are lucky. I can guarantee it won't work with 1.31.

Share this post


Link to post
Share on other sites

So I'm confused... will the newer mac mini run the game even if its an intel chip? Here's the specs on what I want to get:

2.0GHz Intel Core 2 Duo

4GB Ram

NVIDIA GeForce 9400M

Share this post


Link to post
Share on other sites

That's fine, its the Intel Onboard Graphics that are not supported (Apple used those in early iMacs and Mini's). The CPU is Intel but then again so is virtually everyone's these days, that's not any problem. The 9400M should be fine. You should get pretty decent FPS.

Share this post


Link to post
Share on other sites

First crash under 10.6:

Process: World War ][ Online [460]

Path: /Applications/World War ][ Online.app/Contents/MacOS/World War ][ Online

Identifier: com.playnet.ww2ol

Version: 1.30.3 (release) (???)

Code Type: X86 (Native)

Parent Process: launchd [183]

Date/Time: 2009-08-29 17:47:01.115 +0900

OS Version: Mac OS X 10.6 (10A432)

Report Version: 6

Interval Since Last Report: 28336 sec

Crashes Since Last Report: 2

Per-App Interval Since Last Report: 1828 sec

Per-App Crashes Since Last Report: 1

Anonymous UUID: 07E5CF36-D3B4-47F0-86EB-D6CFE96BED51

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x00000000806a386b

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Thread 0 Crashed: Dispatch queue: com.apple.main-thread

0 com.playnet.ww2ol 0x0033948f FTVector::push_back(unsigned long const&) + 292495

1 com.playnet.ww2ol 0x003908c9 FTVector::push_back(unsigned long const&) + 649929

2 com.playnet.ww2ol 0x0030800f FTVector::push_back(unsigned long const&) + 90639

3 com.playnet.ww2ol 0x0009b75f boost::detail::sp_counted_impl_p >::~sp_counted_impl_p() + 7897

4 com.playnet.ww2ol 0x0033b754 FTVector::push_back(unsigned long const&) + 301396

5 com.playnet.ww2ol 0x0034b446 FTVector::push_back(unsigned long const&) + 366150

6 com.playnet.ww2ol 0x0033bfb8 FTVector::push_back(unsigned long const&) + 303544

7 com.playnet.ww2ol 0x003079fa FTVector::push_back(unsigned long const&) + 89082

8 com.playnet.ww2ol 0x00307954 FTVector::push_back(unsigned long const&) + 88916

9 com.playnet.ww2ol 0x00307864 FTVector::push_back(unsigned long const&) + 88676

10 com.playnet.ww2ol 0x003a516f std::pair::pair(std::string const&, int const&) + 1649

11 com.playnet.ww2ol 0x0039e45c SliderDrawer::SliderDrawer(phui::View*, phui::Viewport*, phui::GraphicsContext::TextureInfo (*)(char const*, bool)) + 5578

12 com.playnet.ww2ol 0x003b032e phui::MessageLoop::MessageQueue::MessageQueue() + 114

13 com.playnet.ww2ol 0x003b055f phui::MessageLoop::MessageQueue::MessageQueue() + 675

14 com.playnet.ww2ol 0x001a824c std::map, std::less, std::allocator > > >::operator[](unsigned int const&) + 17938

15 com.playnet.ww2ol 0x00066951 MATERIALPROP::MATERIALPROP() + 7835

16 com.playnet.ww2ol 0x0006698d MATERIALPROP::MATERIALPROP() + 7895

17 com.playnet.ww2ol 0x002db45c std::vector >::resize(unsigned long) + 37232

18 com.playnet.ww2ol 0x002db54c std::vector >::resize(unsigned long) + 37472

19 com.playnet.ww2ol 0x002095c1 std::vector >::push_back(void (* const&)(weapWeapon*)) + 543

20 com.playnet.ww2ol 0x002d4717 std::vector >::resize(unsigned long) + 9259

21 com.apple.Foundation 0x955e6a61 __NSFireTimer + 282

22 com.apple.CoreFoundation 0x98145eee __CFRunLoopRun + 6846

23 com.apple.CoreFoundation 0x98143d34 CFRunLoopRunSpecific + 452

24 com.apple.CoreFoundation 0x98143b61 CFRunLoopRunInMode + 97

25 com.apple.HIToolbox 0x92a23fec RunCurrentEventLoopInMode + 392

26 com.apple.HIToolbox 0x92a23da3 ReceiveNextEventCommon + 354

27 com.apple.HIToolbox 0x92a23c28 BlockUntilNextEventMatchingListInMode + 81

28 com.apple.AppKit 0x916d9b99 _DPSNextEvent + 847

29 com.apple.AppKit 0x916d940e -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156

30 com.apple.AppKit 0x9169b5fb -[NSApplication run] + 821

31 com.apple.AppKit 0x91693695 NSApplicationMain + 574

32 com.playnet.ww2ol 0x00002992 0x1000 + 6546

33 com.playnet.ww2ol 0x000028b9 0x1000 + 6329

Share this post


Link to post
Share on other sites

I've seen that one reported on 10.5 as well but its pretty rare. What was on the screen when it died?

Share this post


Link to post
Share on other sites

I was just outside a FB as a bofor, not much action going on. It died just as I did a quick look to the left and was about to look forward again. I should have been looking at just foliage and my gun barrel, but there might have been something else in the distance.

Share this post


Link to post
Share on other sites

Most of the stack crawl is meaningless, but from the little that is actually real, it looks like the UI was being drawn.

Share this post


Link to post
Share on other sites

Hi,

Just yesterday I started getting really wierd staggered mouse movement and also very slow keyboard reaction times. You have to hold a button for much longer than usual to pull up the map or even stand from a prone postion. Moving an inf unit with the mouse produces a lag-like frame by frame effect but I am getting 30-50 FPS. I read another post and was wondering if this could be the "Mouse Jitter Bug". This all started only yesterday. Before everything was fine. maybe this has to do with the OS X update (not snow leopord) and Java update that I installed.

Not really sure what to do here. The game is close to unplayable. Are there others experiencing this or am I the only one?

Setup:

Imac

OS X version 10.5.8

Processor: 2.4 GHz Intel Core duo

1 GB of ram.

Share this post


Link to post
Share on other sites

Sounds the mouse jitter bug fix is unstuck. Try

Launch /Applications/Utilities/Terminal

Type in

defaults read com.playnet.ww2ol

Do you see alt-game-mouse-tracking = 1 ?

If you see it in the list, do

defaults delete com.playnet.ww2ol alt-game-mouse-tracking

If not, type in or copy/paste and follow with the enter key:

defaults write com.playnet.ww2ol alt-game-mouse-tracking 1

Does that change it?

The mouse jitter fix is in the latest patch, its possible if you had fixed it earlier for the prior version it now turns off the fix.

Share this post


Link to post
Share on other sites

OK, clearly your computer was haunted, but I sent some ghost hunters over the internet to your computer and they solved the problem.

Share this post


Link to post
Share on other sites

Got this 10.6 crash when it was waiting for the AAR to come up after despawning.

Process: World War ][ Online [561]

Path: /Applications/World War ][ Online.app/Contents/MacOS/World War ][ Online

Identifier: com.playnet.ww2ol

Version: 1.30.3 (release) (???)

Code Type: X86 (Native)

Parent Process: launchd [122]

Date/Time: 2009-09-18 17:17:24.161 +1000

OS Version: Mac OS X 10.6.1 (10B504)

Report Version: 6

Interval Since Last Report: 106540 sec

Crashes Since Last Report: 1

Per-App Interval Since Last Report: 22420 sec

Per-App Crashes Since Last Report: 1

Anonymous UUID: 40AE4238-C914-4B13-8C64-C3B9F04A9E45

Exception Type: EXC_BAD_ACCESS (SIGBUS)

Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000100

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Thread 0 Crashed: Dispatch queue: com.apple.main-thread

0 com.playnet.ww2ol 0x00168fa0 Covert::operator+=(short const&) + 42462

1 com.playnet.ww2ol 0x0016b548 Covert::operator+=(short const&) + 52102

2 com.playnet.ww2ol 0x00067843 MATERIALPROP::MATERIALPROP() + 11661

3 com.playnet.ww2ol 0x00068d44 MATERIALPROP::MATERIALPROP() + 17038

4 com.playnet.ww2ol 0x00068ecc MATERIALPROP::MATERIALPROP() + 17430

5 com.playnet.ww2ol 0x000760b9 std::stack > >::stack(std::deque > const&) + 29439

6 com.playnet.ww2ol 0x0006ce38 MATERIALPROP::MATERIALPROP() + 33666

7 com.playnet.ww2ol 0x000fb476 _drawObject(OBJECT*) + 148

8 com.playnet.ww2ol 0x000fb6b1 _drawUnsorted() + 263

9 com.playnet.ww2ol 0x000fa566 Covert::Covert(unsigned int const&) + 17790

10 com.playnet.ww2ol 0x00066914 MATERIALPROP::MATERIALPROP() + 7774

11 com.playnet.ww2ol 0x0006698d MATERIALPROP::MATERIALPROP() + 7895

12 com.playnet.ww2ol 0x002db45c std::vector >::resize(unsigned long) + 37232

Share this post


Link to post
Share on other sites

I got this crash again. Circumstances were similar to the last time, I was glancing in one direction (this time as a rifle), and when I should have been looking forward again, it crashed.

Process: World War ][ Online [1183]

Path: /Applications/World War ][ Online.app/Contents/MacOS/World War ][ Online

Identifier: com.playnet.ww2ol

Version: 1.30.3 (release) (???)

Code Type: X86 (Native)

Parent Process: launchd [181]

Date/Time: 2009-09-18 21:34:20.924 +0900

OS Version: Mac OS X 10.6.1 (10B504)

Report Version: 6

Interval Since Last Report: 80327 sec

Crashes Since Last Report: 1

Per-App Interval Since Last Report: 33920 sec

Per-App Crashes Since Last Report: 1

Anonymous UUID: 07E5CF36-D3B4-47F0-86EB-D6CFE96BED51

Exception Type: EXC_BAD_ACCESS (SIGBUS)

Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Thread 0 Crashed: Dispatch queue: com.apple.main-thread

0 ??? 0x00aa545b 0 + 11162715

1 com.playnet.ww2ol 0x00233f9d std::map, std::allocator > >, std::less, std::allocator, std::allocator > > > > >::operator[](unsigned int const&) + 16645

2 com.playnet.ww2ol 0x000fb53c _drawObject(OBJECT*) + 346

3 com.playnet.ww2ol 0x000fba22 _drawSorted() + 286

4 com.playnet.ww2ol 0x000fa5b3 Covert::Covert(unsigned int const&) + 17867

5 com.playnet.ww2ol 0x00066914 MATERIALPROP::MATERIALPROP() + 7774

6 com.playnet.ww2ol 0x0006698d MATERIALPROP::MATERIALPROP() + 7895

7 com.playnet.ww2ol 0x002db45c std::vector >::resize(unsigned long) + 37232

8 com.playnet.ww2ol 0x002db54c std::vector >::resize(unsigned long) + 37472

9 com.playnet.ww2ol 0x002095c1 std::vector >::push_back(void (* const&)(weapWeapon*)) + 543

10 com.playnet.ww2ol 0x002d4717 std::vector >::resize(unsigned long) + 9259

11 com.apple.Foundation 0x98987a61 __NSFireTimer + 282

12 com.apple.CoreFoundation 0x98f22eee __CFRunLoopRun + 6846

13 com.apple.CoreFoundation 0x98f20d34 CFRunLoopRunSpecific + 452

14 com.apple.CoreFoundation 0x98f20b61 CFRunLoopRunInMode + 97

15 com.apple.HIToolbox 0x947b4fec RunCurrentEventLoopInMode + 392

16 com.apple.HIToolbox 0x947b4da3 ReceiveNextEventCommon + 354

17 com.apple.HIToolbox 0x947b4c28 BlockUntilNextEventMatchingListInMode + 81

18 com.apple.AppKit 0x96c6ec95 _DPSNextEvent + 847

19 com.apple.AppKit 0x96c6e50a -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156

20 com.apple.AppKit 0x96c3069b -[NSApplication run] + 821

21 com.apple.AppKit 0x96c28735 NSApplicationMain + 574

22 com.playnet.ww2ol 0x00002992 0x1000 + 6546

23 com.playnet.ww2ol 0x000028b9 0x1000 + 6329

Share this post


Link to post
Share on other sites

When flying a plane my joystick pulls hard right so much I can't fly. I didn't do this before the update. The audio is still a mess as well making it hard to play when you can't tell where incoming is at. FPS is still bad in big battles. The number of F-up things going on right now makes it really hard to keep playing this game.

Share this post


Link to post
Share on other sites
When flying a plane my joystick pulls hard right so much I can't fly. I didn't do this before the update. The audio is still a mess as well making it hard to play when you can't tell where incoming is at. FPS is still bad in big battles. The number of F-up things going on right now makes it really hard to keep playing this game.

Is it a Saitek? I've heard lots of people with Saiteks doing this recently.

Avi

Share this post


Link to post
Share on other sites

You probably tried this but...

I had the same problem, and solved it by using the re-calibrate option in the settings before you start the game.

Settings > Joystick 1 > Calibrate.

Share this post


Link to post
Share on other sites
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.