Sign in to follow this  
Followers 0
AHWULF

1.30.2 Bugs

55 posts in this topic

You can't mark the map if you are a mission leader is still broken. It's some kind of server side issue KFS has to fix.

Viewing the people's names on the plane with you is still broken, although oddly enough riding on a Axis HT it worked correctly. This is a bug in the javascript stuff which I don't have access to.

Share this post


Link to post
Share on other sites

I got the auto update for 1.30.2 but when I try to install it I get a Installation error. It says " The following install step failed: preflight script for World War II Online". How do I fix this?

Starting to get very frustrated with the new 1.30 versions!!!!!!!!

Share this post


Link to post
Share on other sites

Both 1.31 and the new 1.32 still can't mark as leader.. gives me a submission error.... I can submit marks to the mission leader, just can't make marks AS leader..... problem was not there previous to the last 2 updates..

Great Work .. Thanks Tom.

North Pole.

Share this post


Link to post
Share on other sites
I got the auto update for 1.30.2 but when I try to install it I get a Installation error. It says " The following install step failed: preflight script for World War II Online". How do I fix this?

Starting to get very frustrated with the new 1.30 versions!!!!!!!!

Try downloading the latest full version and apply updates again.

Share this post


Link to post
Share on other sites

Re Storm66's problem - I tried to download the whole game and then carry out the update with exactly the same result.....

The following install step failed: preflight script for World War II Online

Any ideas ?

S! Bodach

Share this post


Link to post
Share on other sites

Suggestion - why not allow us to play on and ignore an update until we find out the the update has been updated and the fix has been fixed. These buggered updates are all too common.

As it stands, we can't get in game every time there is one of these issues.

Playing with and putting up with a bug or bugs is one thing but being shut out in an effort to fix these bugs is plain stupid.

Keep up the good work Ahwulf and keep pushin' those buttons

S! Bodach.

Share this post


Link to post
Share on other sites

Suggestion - why not allow us to play on and ignore an update until we find out the the update has been updated and the fix has been fixed. These buggered updates are all too common.

As it stands, we can't get in game every time there is one of these issues.

Playing with and putting up with a bug or bugs is one thing but being shut out in an effort to fix these bugs is plain stupid.

Needless to say, I'm sure I'm not the first to suggest this approach.........

Keep up the good work Ahwulf and keep pushin' those buttons

S! Bodach.

Share this post


Link to post
Share on other sites

sry for double post - system said it was too busy to receive my post - go figure .............

Share this post


Link to post
Share on other sites

Yeah this forum is flakier than a french biscuit.

You can't really play with the old version since there may be features that are incompatible between versions. The server and client have to be synced. Unlike mmo's which are instanced (and thus you can find and play the same older version) here we only have one server.

Anytime you get an error in the installer, before you quit it, go to the Log menu and copy everything (not just the errors) and either post it or email it to my playnet email.

Did you try installing into a different directory or volume? It does get confused sometimes if you do something undefault.

Share this post


Link to post
Share on other sites

I tried moving the program and then downloading to the new location - same result - here's the download log...... let me know if this helps you figure out what's going on ......

Jun 30 17:34:48 Macintosh Installer[23475]: --- Package authoring error: Duplicate receipts detected ---

Jun 30 17:34:48 Macintosh Installer[23475]: I'm looking for a receipt for a package named wwiiol13011302 with a bundle identifier 'com.playnet.ww2ol-installer' and found the following:

Jun 30 17:34:48 Macintosh Installer[23475]: Name:wwiiol12831284 Identifier:com.playnet.ww2ol-installer

Jun 30 17:34:48 Macintosh Installer[23475]: Name:wwiiol12841285 Identifier:com.playnet.ww2ol-installer

Jun 30 17:34:48 Macintosh Installer[23475]: Name:wwiiol12851286 Identifier:com.playnet.ww2ol-installer

Jun 30 17:34:48 Macintosh Installer[23475]: Name:wwiiol12861287 Identifier:com.playnet.ww2ol-installer

Jun 30 17:34:48 Macintosh Installer[23475]: Name:wwiiol12871290 Identifier:com.playnet.ww2ol-installer

Jun 30 17:34:48 Macintosh Installer[23475]: Name:wwiiol12901291 Identifier:com.playnet.ww2ol-installer

Jun 30 17:34:48 Macintosh Installer[23475]: Name:wwiiol12911292 Identifier:com.playnet.ww2ol-installer

Jun 30 17:34:48 Macintosh Installer[23475]: Name:wwiiol12921293 Identifier:com.playnet.ww2ol-installer

Jun 30 17:34:48 Macintosh Installer[23475]: Name:wwiiol12541255 Identifier:com.playnet.ww2ol-installer

Jun 30 17:34:48 Macintosh Installer[23475]: Name:wwiiol12551260 Identifier:com.playnet.ww2ol-installer

Jun 30 17:34:48 Macintosh Installer[23475]: Name:wwiiol12501251 Identifier:com.playnet.ww2ol-installer

Jun 30 17:34:48 Macintosh Installer[23475]: Name:wwiiol12511252 Identifier:com.playnet.ww2ol-installer

Jun 30 17:34:48 Macintosh Installer[23475]: Name:wwiiol12521253 Identifier:com.playnet.ww2ol-installer

Jun 30 17:34:48 Macintosh Installer[23475]: Name:wwiiol12531254 Identifier:com.playnet.ww2ol-installer

Jun 30 17:34:48 Macintosh Installer[23475]: Name:wwiiol12601261 Identifier:com.playnet.ww2ol-installer

Jun 30 17:34:48 Macintosh Installer[23475]: Name:wwiiol12611270 Identifier:com.playnet.ww2ol-installer

Jun 30 17:34:48 Macintosh Installer[23475]: Name:wwiiol12701271 Identifier:com.playnet.ww2ol-installer

Jun 30 17:34:48 Macintosh Installer[23475]: Name:wwiiol12711280 Identifier:com.playnet.ww2ol-installer

Jun 30 17:34:48 Macintosh Installer[23475]: Name:wwiiol12801281 Identifier:com.playnet.ww2ol-installer

Jun 30 17:34:48 Macintosh Installer[23475]: Name:wwiiol12821283 Identifier:com.playnet.ww2ol-installer

Jun 30 17:34:48 Macintosh Installer[23475]:

Jun 30 17:35:00 Macintosh Installer[23475]: --- Package authoring error: Duplicate receipts detected ---

Jun 30 17:35:00 Macintosh Installer[23475]: I'm looking for a receipt for a package named wwiiol13011302 with a bundle identifier 'com.playnet.ww2ol-installer' and found the following:

Jun 30 17:35:00 Macintosh Installer[23475]: Name:wwiiol12831284 Identifier:com.playnet.ww2ol-installer

Jun 30 17:35:00 Macintosh Installer[23475]: Name:wwiiol12841285 Identifier:com.playnet.ww2ol-installer

Jun 30 17:35:00 Macintosh Installer[23475]: Name:wwiiol12851286 Identifier:com.playnet.ww2ol-installer

Jun 30 17:35:00 Macintosh Installer[23475]: Name:wwiiol12861287 Identifier:com.playnet.ww2ol-installer

Jun 30 17:35:00 Macintosh Installer[23475]: Name:wwiiol12871290 Identifier:com.playnet.ww2ol-installer

Jun 30 17:35:00 Macintosh Installer[23475]: Name:wwiiol12901291 Identifier:com.playnet.ww2ol-installer

Jun 30 17:35:00 Macintosh Installer[23475]: Name:wwiiol12911292 Identifier:com.playnet.ww2ol-installer

Jun 30 17:35:00 Macintosh Installer[23475]: Name:wwiiol12921293 Identifier:com.playnet.ww2ol-installer

Jun 30 17:35:00 Macintosh Installer[23475]: Name:wwiiol12541255 Identifier:com.playnet.ww2ol-installer

Jun 30 17:35:00 Macintosh Installer[23475]: Name:wwiiol12551260 Identifier:com.playnet.ww2ol-installer

Jun 30 17:35:00 Macintosh Installer[23475]: Name:wwiiol12501251 Identifier:com.playnet.ww2ol-installer

Jun 30 17:35:00 Macintosh Installer[23475]: Name:wwiiol12511252 Identifier:com.playnet.ww2ol-installer

Jun 30 17:35:00 Macintosh Installer[23475]: Name:wwiiol12521253 Identifier:com.playnet.ww2ol-installer

Jun 30 17:35:00 Macintosh Installer[23475]: Name:wwiiol12531254 Identifier:com.playnet.ww2ol-installer

Jun 30 17:35:00 Macintosh Installer[23475]: Name:wwiiol12601261 Identifier:com.playnet.ww2ol-installer

Jun 30 17:35:00 Macintosh Installer[23475]: Name:wwiiol12611270 Identifier:com.playnet.ww2ol-installer

Jun 30 17:35:00 Macintosh Installer[23475]: Name:wwiiol12701271 Identifier:com.playnet.ww2ol-installer

Jun 30 17:35:00 Macintosh Installer[23475]: Name:wwiiol12711280 Identifier:com.playnet.ww2ol-installer

Jun 30 17:35:00 Macintosh Installer[23475]: Name:wwiiol12801281 Identifier:com.playnet.ww2ol-installer

Jun 30 17:35:00 Macintosh Installer[23475]: Name:wwiiol12821283 Identifier:com.playnet.ww2ol-installer

Jun 30 17:35:00 Macintosh Installer[23475]:

Jun 30 17:35:01 Macintosh Installer[23475]: Install failed: The following install step failed: run preflight script for World War ][ Online. Contact the software manufacturer for assistance.

Jun 30 17:35:01 Macintosh Installer[23475]: Displaying 'Install Failed' UI.

Share this post


Link to post
Share on other sites

It looks like it can't find 1.30.1 I assume you are running the updater? You have to run them in order 1.30.0 full, then 1.30.0 -> 130.1 and then 130.1->130.2.

Easier though is the full installer:

ftp://downloads.wwiionline.com/wwiiol0001302.dmg

Please delete the app if you installed it anywhere but the /Applications directory. Normally this isn't necessary, the full installer deletes the old one if its in the install location.

Share this post


Link to post
Share on other sites
You can't mark the map if you are a mission leader is still broken. It's some kind of server side issue KFS has to fix.

Viewing the people's names on the plane with you is still broken, although oddly enough riding on a Axis HT it worked correctly. This is a bug in the javascript stuff which I don't have access to.

I also CTD 1 out of every 10 0r 15 times I bring up the map, on top of no marking as ML and 1/3 of the FPS I had before the patch...I know the world cares not for Mac users, but I really do love this game...but I will have to give it up if it cannot run well enough to be fun. It did before 1.3.

Share this post


Link to post
Share on other sites

FPS issues are happening to PC users as well, its not a mac issue and its quite random.

When you CTD bringing up the map, can you post the crash report (at least as much as will fit), this might be something i can check into.

What Mac/ram/OS/video card do you have?

Share this post


Link to post
Share on other sites

I am having the same CTD problem that Capt Ken notes.

By which I mean when I am in game and I open the map I will CTD at times.

This happens even as I am having good fps, like 50 or better.

It usually happens at night CST (larger number of players on line it seems), not usually during the day, so I think it is related to server communication, player density etc...

I am on a typically good cable connection.

So who knows. It is frustrating no doubt.

Share this post


Link to post
Share on other sites

Need that crash report, I have to get an idea of where its coming from - also report mac model/ram/os/videocard.

Share this post


Link to post
Share on other sites

Ahwulf, please don't hate me, but...

I crashed again when I scrolled over a guy with a 10-character name. I even did the fix you suggested. I need to test again to be sure, but I'm pretty sure that's what caused it... :(

Share this post


Link to post
Share on other sites

Crashreport will tell me what happened, otherwise I shall remain clueless. I fixed the problem we've had, but that doesn't mean it wasn't hiding another one. This code is like a hydra, kill one head and more appear to bite you in the ***.

But still, crashreport is the best defense.

*** *** ***, it doesn't like me to say donkey.

Share this post


Link to post
Share on other sites

This crash happened when bringing up the map:

Process: World War ][ Online [32923]

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

Identifier: com.playnet.ww2ol

Version: 1.30.2 (release) (???)

Code Type: X86 (Native)

Parent Process: launchd [182]

Interval Since Last Report: 172879 sec

Crashes Since Last Report: 1

Per-App Interval Since Last Report: 98412 sec

Per-App Crashes Since Last Report: 1

Date/Time: 2009-07-06 22:12:55.481 +0900

OS Version: Mac OS X 10.5.7 (9J61)

Report Version: 6

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

Exception Type: EXC_BAD_ACCESS (SIGBUS)

Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000

Crashed Thread: 0

Thread 0 Crashed:

0 com.playnet.ww2ol 0x002eb637 FTLibrary::GetLibrary() const + 1077

1 com.playnet.ww2ol 0x002ef715 float FTFontImpl::AdvanceI(wchar_t const*, int, FTPoint) + 179

2 com.playnet.ww2ol 0x002ee2ab FTPoint::Yf() const + 5065

3 com.playnet.ww2ol 0x002ed504 FTPoint::Yf() const + 1570

4 com.playnet.ww2ol 0x003a27b1 ScriptFilter::~ScriptFilter() + 3787

5 com.playnet.ww2ol 0x003b9af5 phui::TextContainer::TextContainer() + 5555

6 com.playnet.ww2ol 0x003b9d08 phui::TextContainer::TextContainer() + 6086

7 com.playnet.ww2ol 0x003cb842 phui::Panel::MinSize(float*, float*) + 5396

8 com.playnet.ww2ol 0x003cba7e phui::Panel::MinSize(float*, float*) + 5968

9 com.playnet.ww2ol 0x003c63fb std::map, std::allocator >, phui::ref_ptr, std::less, std::allocator > >, std::allocator, std::allocator > const, phui::ref_ptr > > >::operator[](std::basic_string, std::allocator > const&) + 4127

10 com.playnet.ww2ol 0x003c3f7d std::map, std::allocator >, memio, std::less, std::allocator > >, std::allocator, std::allocator > const, memio> > >::operator[](std::basic_string, std::allocator > const&) + 13105

11 com.playnet.ww2ol 0x001b5b24 std::vector >, std::allocator > > >::resize(unsigned long, std::vector > const&) + 12470

12 com.playnet.ww2ol 0x003c1999 std::map, std::allocator >, memio, std::less, std::allocator > >, std::allocator, std::allocator > const, memio> > >::operator[](std::basic_string, std::allocator > const&) + 3405

13 com.playnet.ww2ol 0x001b2bc9 std::vector >, std::allocator > > >::resize(unsigned long, std::vector > const&) + 347

14 com.playnet.ww2ol 0x003ad5d2 __gnu_cxx::__normal_iterator*, std::vector, std::allocator > > > std::find<__gnu_cxx::__normal_iterator*, std::vector, std::allocator > > >, phui::MessageFilter*>(__gnu_cxx::__normal_iterator*, std::vector, std::allocator > > >, __gnu_cxx::__normal_iterator*, std::vector, std::allocator > > >, phui::MessageFilter* const&) + 458

15 com.playnet.ww2ol 0x003ad6fa __gnu_cxx::__normal_iterator*, std::vector, std::allocator > > > std::find<__gnu_cxx::__normal_iterator*, std::vector, std::allocator > > >, phui::MessageFilter*>(__gnu_cxx::__normal_iterator*, std::vector, std::allocator > > >, __gnu_cxx::__normal_iterator*, std::vector, std::allocator > > >, phui::MessageFilter* const&) + 754

16 com.playnet.ww2ol 0x001a7578 std::map, std::less, std::allocator > > >::operator[](unsigned int const&) + 17242

17 com.playnet.ww2ol 0x0006648d MATERIALPROP::MATERIALPROP() + 7835

18 com.playnet.ww2ol 0x000664c9 MATERIALPROP::MATERIALPROP() + 7895

19 com.playnet.ww2ol 0x002da71c std::vector >::resize(unsigned long) + 37230

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

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

22 com.playnet.ww2ol 0x002d39d7 std::vector >::resize(unsigned long) + 9257

23 com.apple.Foundation 0x90cf4517 __NSFireTimer + 279

24 com.apple.CoreFoundation 0x92e91ac5 CFRunLoopRunSpecific + 4469

25 com.apple.CoreFoundation 0x92e91c78 CFRunLoopRunInMode + 88

26 com.apple.HIToolbox 0x95dfb28c RunCurrentEventLoopInMode + 283

27 com.apple.HIToolbox 0x95dfb0a5 ReceiveNextEventCommon + 374

28 com.apple.HIToolbox 0x95dfaf19 BlockUntilNextEventMatchingListInMode + 106

29 com.apple.AppKit 0x930f6d0d _DPSNextEvent + 657

30 com.apple.AppKit 0x930f65c0 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128

31 com.apple.AppKit 0x930ef5fb -[NSApplication run] + 795

32 com.apple.AppKit 0x930bc834 NSApplicationMain + 574

33 com.playnet.ww2ol 0x00002542 0x1000 + 5442

34 com.playnet.ww2ol 0x00002469 0x1000 + 5225

Share this post


Link to post
Share on other sites

This is not the 10 char bug, but something new in the initialization of the map view. Probably has been in there before but people may have reported it as the 10char bug.

Ticketed as Ticket #3053

Share this post


Link to post
Share on other sites

Hmm, I think its a similar problem in a different place to the 10 char. I bet its the squad list or the mission list that doesn't handle the name correctly either. I guess I will review every place in the code where the name is referenced. Argh...

Share this post


Link to post
Share on other sites

This happened just as i turned off the map. A mortar also just fired near me, but not in sight:

Process: World War ][ Online [6602]

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

Identifier: com.playnet.ww2ol

Version: 1.30.2 (release) (???)

Code Type: X86 (Native)

Parent Process: launchd [184]

Interval Since Last Report: 145551 sec

Crashes Since Last Report: 1

Per-App Interval Since Last Report: 61604 sec

Per-App Crashes Since Last Report: 1

Date/Time: 2009-07-12 00:03:37.944 +0900

OS Version: Mac OS X 10.5.7 (9J61)

Report Version: 6

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

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x000000007497bffc

Crashed Thread: 0

Thread 0 Crashed:

0 com.playnet.ww2ol 0x00289b83 void std::__unguarded_linear_insert<__gnu_cxx::__normal_iterator > >, Particle*, int (*)(Particle*, Particle*)>(__gnu_cxx::__normal_iterator > >, Particle*, int (*)(Particle*, Particle*)) + 29

1 com.playnet.ww2ol 0x00289bd1 void std::__unguarded_insertion_sort<__gnu_cxx::__normal_iterator > >, int (*)(Particle*, Particle*)>(__gnu_cxx::__normal_iterator > >, __gnu_cxx::__normal_iterator > >, int (*)(Particle*, Particle*)) + 47

2 com.playnet.ww2ol 0x0028b31e void std::__final_insertion_sort<__gnu_cxx::__normal_iterator > >, int (*)(Particle*, Particle*)>(__gnu_cxx::__normal_iterator > >, __gnu_cxx::__normal_iterator > >, int (*)(Particle*, Particle*)) + 80

3 com.playnet.ww2ol 0x0028b3ad void std::sort<__gnu_cxx::__normal_iterator > >, int (*)(Particle*, Particle*)>(__gnu_cxx::__normal_iterator > >, __gnu_cxx::__normal_iterator > >, int (*)(Particle*, Particle*)) + 113

4 com.playnet.ww2ol 0x002888e2 EFFECT::EFFECT() + 8362

5 com.playnet.ww2ol 0x00281045 std::map, std::allocator >, bool (*)(XMLLoader*, _xmlNode*, bool, void*), std::less, std::allocator > >, std::allocator, std::allocator > const, bool (*)(XMLLoader*, _xmlNode*, bool, void*)> > >::operator[](std::basic_string, std::allocator > const&) + 1851

6 com.playnet.ww2ol 0x00050123 std::vector >::clear() + 7109

7 com.playnet.ww2ol 0x0004e5ad std::vector >::clear() + 79

8 com.playnet.ww2ol 0x00065b27 MATERIALPROP::MATERIALPROP() + 5429

9 com.playnet.ww2ol 0x000664d6 MATERIALPROP::MATERIALPROP() + 7908

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

11 com.playnet.ww2ol 0x002da80c std::vector >::resize(unsigned long) + 37470

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

13 com.playnet.ww2ol 0x002d39d7 std::vector >::resize(unsigned long) + 9257

14 com.apple.Foundation 0x90042517 __NSFireTimer + 279

15 com.apple.CoreFoundation 0x95b53ac5 CFRunLoopRunSpecific + 4469

16 com.apple.CoreFoundation 0x95b53c78 CFRunLoopRunInMode + 88

17 com.apple.HIToolbox 0x9188c28c RunCurrentEventLoopInMode + 283

18 com.apple.HIToolbox 0x9188c0a5 ReceiveNextEventCommon + 374

19 com.apple.HIToolbox 0x9188bf19 BlockUntilNextEventMatchingListInMode + 106

20 com.apple.AppKit 0x94a2fd0d _DPSNextEvent + 657

21 com.apple.AppKit 0x94a2f5c0 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128

22 com.apple.AppKit 0x94a285fb -[NSApplication run] + 795

23 com.apple.AppKit 0x949f5834 NSApplicationMain + 574

24 com.playnet.ww2ol 0x00002542 0x1000 + 5442

25 com.playnet.ww2ol 0x00002469 0x1000 + 5225

Share this post


Link to post
Share on other sites

That's the particle memory stomper bug. One of my targets for next week. This usually happens around lots of explosions and smoke.

Share this post


Link to post
Share on other sites

No crash but I am having serious USB(?) problems.

I have reported the same problem before but it is becoming really frustrating.

The symptoms are similar to the inf jitter but the mouse doesn't seem to be affected. In this case its USB devices like a joystick. All sudden an axis will begin moving in stops an starts with tremendous lag in response. A big drop in FPS doesn't seem to be associated with the occurrence of symptoms. Game becomes completely unplayable. Quitting game with restart will not fix the problem. The symptoms seem worse the busier the scene gets. It feels like an event-handling issue and I have never noticed this issue in prior releases.

config: iMac 24", 10.5.7, ati 2400

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.