Sign in to follow this  
Followers 0
AHWULF

Please post Mac bugs here

78 posts in this topic

Thread 0 Crashed:

0 com.playnet.ww2ol 0x00177de2 0x1000 + 1535458

1 com.playnet.ww2ol 0x003f970f 0x1000 + 4163343

2 com.playnet.ww2ol 0x003f974f 0x1000 + 4163407

3 com.playnet.ww2ol 0x003f9856 0x1000 + 4163670

4 com.playnet.ww2ol 0x003f9b81 0x1000 + 4164481

5 com.playnet.ww2ol 0x00179222 0x1000 + 1540642

6 com.playnet.ww2ol 0x001747ce 0x1000 + 1521614

7 com.playnet.ww2ol 0x0002d51c 0x1000 + 181532

8 com.playnet.ww2ol 0x0003daa6 0x1000 + 248486

9 com.playnet.ww2ol 0x0009cb5d 0x1000 + 637789

10 com.playnet.ww2ol 0x0003deb0 0x1000 + 249520

11 com.playnet.ww2ol 0x0003df5c 0x1000 + 249692

12 com.playnet.ww2ol 0x0016a675 0x1000 + 1480309

13 com.playnet.ww2ol 0x0016a77e 0x1000 + 1480574

14 com.playnet.ww2ol 0x00133366 0x1000 + 1254246

15 com.playnet.ww2ol 0x0016d1bd 0x1000 + 1491389

16 com.apple.Foundation 0x9283c2de __NSFireTimer + 199

17 com.apple.CoreFoundation 0x9082d7e2 CFRunLoopRunSpecific + 3341

18 com.apple.CoreFoundation 0x9082cace CFRunLoopRunInMode + 61

19 com.apple.HIToolbox 0x92ded8d8 RunCurrentEventLoopInMode + 285

20 com.apple.HIToolbox 0x92decfe2 ReceiveNextEventCommon + 385

21 com.apple.HIToolbox 0x92dece39 BlockUntilNextEventMatchingListInMode + 81

22 com.apple.AppKit 0x93273465 _DPSNextEvent + 572

23 com.apple.AppKit 0x93273056 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 137

24 com.apple.AppKit 0x9326cddb -[NSApplication run] + 512

25 com.apple.AppKit 0x93260d2f NSApplicationMain + 573

26 com.playnet.ww2ol 0x00002c8a 0x1000 + 7306

27 com.playnet.ww2ol 0x00002bb1 0x1000 + 7089

Thread 1:

0 libSystem.B.dylib 0x90009cd7 mach_msg_trap + 7

1 com.unsanity.ape 0xc0001cac __ape_agent + 307

2 libSystem.B.dylib 0x90024227 _pthread_body + 84

Thread 2:

0 libSystem.B.dylib 0x90009cd7 mach_msg_trap + 7

1 com.apple.CoreFoundation 0x9082d2b3 CFRunLoopRunSpecific + 2014

2 com.apple.CoreFoundation 0x9082cace CFRunLoopRunInMode + 61

3 com.apple.Foundation 0x9282aa0f +[NSURLConnection(NSURLConnectionInternal) _resourceLoadLoop:] + 259

4 com.apple.Foundation 0x927f52e0 forkThreadForFunction + 123

5 libSystem.B.dylib 0x90024227 _pthread_body + 84

Thread 3:

0 libSystem.B.dylib 0x90009cd7 mach_msg_trap + 7

1 com.apple.CoreFoundation 0x9082d2b3 CFRunLoopRunSpecific + 2014

2 com.apple.CoreFoundation 0x9082cace CFRunLoopRunInMode + 61

3 com.apple.Foundation 0x92851bc2 +[NSURLCache _diskCacheSyncLoop:] + 206

4 com.apple.Foundation 0x927f52e0 forkThreadForFunction + 123

5 libSystem.B.dylib 0x90024227 _pthread_body + 84

Thread 4:

0 libSystem.B.dylib 0x9001a1cc select + 12

1 libSystem.B.dylib 0x90024227 _pthread_body + 84

Thread 5:

0 libSystem.B.dylib 0x90009cd7 mach_msg_trap + 7

1 com.apple.CoreFoundation 0x9082d2b3 CFRunLoopRunSpecific + 2014

2 com.apple.CoreFoundation 0x9082cace CFRunLoopRunInMode + 61

3 com.apple.audio.CoreAudio 0x9146941e HALRunLoop::OwnThread(void*) + 158

4 com.apple.audio.CoreAudio 0x91469239 CAPThread::Entry(CAPThread*) + 93

5 libSystem.B.dylib 0x90024227 _pthread_body + 84

Thread 6:

0 libSystem.B.dylib 0x900248c7 semaphore_wait_signal_trap + 7

1 OpenThreads 0x1ff01f6f OpenThreads::Condition::wait(OpenThreads::Mutex*) + 79

2 com.playnet.ww2ol 0x000fea01 0x1000 + 1038849

3 OpenThreads 0x1ff025b7 0x1ff00000 + 9655

4 libSystem.B.dylib 0x90024227 _pthread_body + 84

Thread 7:

0 libSystem.B.dylib 0x90047dd7 semaphore_timedwait_signal_trap + 7

1 com.apple.audio.CoreAudio 0x9147665c CAGuard::WaitFor(unsigned long long) + 212

2 com.apple.audio.CoreAudio 0x9147657e CAGuard::WaitUntil(unsigned long long) + 66

3 com.apple.audio.CoreAudio 0x91474efa HP_IOThread::WorkLoop() + 690

4 com.apple.audio.CoreAudio 0x91474c43 HP_IOThread::ThreadEntry(HP_IOThread*) + 17

5 com.apple.audio.CoreAudio 0x91469239 CAPThread::Entry(CAPThread*) + 93

6 libSystem.B.dylib 0x90024227 _pthread_body + 84

Thread 8:

0 libSystem.B.dylib 0x90037b57 mach_wait_until + 7

1 libSystem.B.dylib 0x9003a222 usleep + 82

2 com.playnet.ww2ol 0x002f8515 0x1000 + 3110165

3 com.playnet.ww2ol 0x002b09bc 0x1000 + 2816444

4 libSystem.B.dylib 0x90024227 _pthread_body + 84

Thread 0 crashed with X86 Thread State (32-bit):

eax: 0x00000000 ebx: 0x54d83ffc ecx: 0x00000000 edx: 0x54d840a4

edi: 0x00177dd4 esi: 0x54d84000 ebp: 0xbfffebf8 esp: 0xbfffebf8

ss: 0x0000001f efl: 0x00010216 eip: 0x00177de2 cs: 0x00000017

ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037

Share this post


Link to post
Share on other sites

Actually I'd have liked it to have simply worked. The updated crashed out on me, and now it appears I have to redownload the entire basic installer and start over. The PREFLIGHT script doesn't seem to have any ability to recover from or test for a partial update. I suppose I could hack together something that would launch on the server, but if any of the message formats changed I could end up sh**storming everyone else.

Anyone else have trouble on a Mac (Mines PPC) installing the updater?

Share this post


Link to post
Share on other sites
I suppose I could hack together . . .

And I did, a quick alteration of the preflight script so that it would replace the playarc files AGAIN if it had too, simply by eliminating the exit error case on a bit of bad unix scripting. . . .

Ignore all this, see below

Enjoy

Caligula

Still The Best Darn Systems Engineer!

Share this post


Link to post
Share on other sites

I even tried updating a clean 1.270 install on my Intel machine, and I got an error in the preflight script just as on my rather "contaminated" development machine. There has to be a nasty error embedded in that code that simply bites things on the butt. Can't figure what it is, but it COULD be a typo somewhere and is going missing for either being unprintable, or codeblindness.

Either way, if you have problems with the updater, it looks like DL'ing the full install is your best bet . . . You can TRY to patch it a chunk at a time, if you really know what the heck you're doing, but I don't trust that . . . too easy to miss something.

Oddly enough though, if I had WWIIOL installed in my HOME directory rather than the system applications directory, the updater worked fine. I don't know if you can move it, update the app, then move it again, but it might be worth a try as long as its your first attempt at an update.

-Caligula

Who thinks there may be a permissions issue or somesuch going down here.

Share this post


Link to post
Share on other sites

Yepper, for some reason 1.27.1 will ONLY install/update in your HOME directory, no matter the default directory listed in the installer.

I doubt there's anything keeping your from moving it to the Applications folder after you're done, but for the meantime it'd probably be safer to assume they pathed everything to ~ rather than /Applications and run it from there.

( ~ is a system alias for the home directory of the current user)

Share this post


Link to post
Share on other sites

Hmm, i only let it install/update in /Applications. Methinks your Mac is haunted by something evil :-) Maybe that nasty Roman emperor...

It wouldn't surprise me if it doesn't work unless its in /Applications. Rick is working on the new game engine and installer issues are not high priority as long as you can get the game to run. Heck I think Gophur builds the installers now.

Share this post


Link to post
Share on other sites

Yeah the installers have always been "whatever you can get to work", and there were transition pains between using VISE and when Apple's installer finally got good enough to do diffs without choking. Ironing out those issues has to take backseat to a ton of others. e.g. I'd LOVE to see a Mac64bit build with universal binaries for G5's and Xeon's.

Might actually cause me to replace my G5 with an Intel machine, though for now the speeds are so close there's no reason to do it.

I couldn't get it to install to Applications, by default it installed to my user folder, though I admit my user folder is kind of bent already. Some time ago I found a way to make it invisible unless you were specifically logged in as me, or using the command line. I suspect that might cause SOME problems, though not this one. I just wish I could remember HOW I did it so I could reverse it and find out ;-)

Share this post


Link to post
Share on other sites

Actually with 127.1 the intel binary is much faster than the PPC, at least for the latest Intel macs. In some cases it doubled.

Share this post


Link to post
Share on other sites

I'm back on the 7-day trial, after a 2-year break. I was in Eindhoven early Saturday and got behind two atgs. I put two MG clips into each unit but got only one kill for another rifleman I had killed earlier.

About 1/2 an hour ago, I was defending the SAB at Luxembourg. Two ei walked (one with a high-ranking uniform), and I got them both. No kills recorded for those either.

Share this post


Link to post
Share on other sites

The scoring system is not perfect. However, remember that just because you see them fall after you shoot, doesn't mean someone else didn't get the kill shot in first. Sometimes I get credit for killing something in CSR later that didn't show up in the after mission screen. The rats know this but redoing the scoring from the ground up is a big undertaking, but it will be done.

Share this post


Link to post
Share on other sites

CTD'ed twice for no apparent reason.

On both occasions it was while fighting in town.

MacPro . 2 x 2.66 . 2Gb mem

Bodach

Share this post


Link to post
Share on other sites

First CTD with 127. Was on a FB attack near Etain, not particularly much going on.

Date/Time: 2007-10-14 22:28:36.001 +0900

OS Version: 10.4.10 (Build 8R218)

Report Version: 4

Command: World War ][ Online

Path: /Users/tiborg/Games/World War ][ Online.app/Contents/MacOS/World War ][ Online

Parent: WindowServer [101]

Version: 1.27.1 (???)

PID: 16179

Thread: 0

Exception: EXC_BAD_ACCESS (0x0001)

Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000030

Thread 0 Crashed:

0 com.playnet.ww2ol 0x00169988 0x1000 + 1477000

1 com.playnet.ww2ol 0x00446df4 dyld_stub_inflateEnd + 423892

2 com.playnet.ww2ol 0x00446f54 dyld_stub_inflateEnd + 424244

3 com.playnet.ww2ol 0x00447304 dyld_stub_inflateEnd + 425188

4 com.playnet.ww2ol 0x0016aa64 0x1000 + 1481316

5 com.playnet.ww2ol 0x0002decc 0x1000 + 184012

6 com.playnet.ww2ol 0x0003b5e0 0x1000 + 239072

7 com.playnet.ww2ol 0x00094bcc 0x1000 + 605132

8 com.playnet.ww2ol 0x0003ba9c 0x1000 + 240284

9 com.playnet.ww2ol 0x0003bb8c 0x1000 + 240524

10 com.playnet.ww2ol 0x0015bc4c 0x1000 + 1420364

11 com.playnet.ww2ol 0x0015bd8c 0x1000 + 1420684

12 com.playnet.ww2ol 0x00120f14 0x1000 + 1179412

13 com.playnet.ww2ol 0x0015ec5c 0x1000 + 1432668

14 com.apple.Foundation 0x92be3f68 __NSFireTimer + 116

15 com.apple.CoreFoundation 0x907f1578 __CFRunLoopDoTimer + 184

16 com.apple.CoreFoundation 0x907ddef8 __CFRunLoopRun + 1680

17 com.apple.CoreFoundation 0x907dd4ac CFRunLoopRunSpecific + 268

18 com.apple.HIToolbox 0x93298b20 RunCurrentEventLoopInMode + 264

19 com.apple.HIToolbox 0x932981b4 ReceiveNextEventCommon + 380

20 com.apple.HIToolbox 0x93298020 BlockUntilNextEventMatchingListInMode + 96

21 com.apple.AppKit 0x9377dae4 _DPSNextEvent + 384

22 com.apple.AppKit 0x9377d7a8 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 116

23 com.apple.AppKit 0x93779cec -[NSApplication run] + 472

24 com.apple.AppKit 0x9386a87c NSApplicationMain + 452

25 com.playnet.ww2ol 0x000030cc 0x1000 + 8396

26 com.playnet.ww2ol 0x00002dd0 0x1000 + 7632

Share this post


Link to post
Share on other sites

Maybe this has already been mentioned, but the fuel-guage needle in the Hurricane doesn't show up where it should be...its often in the empty round dial to the left of the fuel guage, if it shows at all.

Share this post


Link to post
Share on other sites
Yeah but who every runs out of fuel in this game? I'll mention it' date=' maybe its a quick fixer.[/quote']

You know I use to think the same thing, until I was in a Hurri intercepting some He111's when low and behold, no fuel. Motor stopped, no smoke, no hits on me, just stopped. I was warned by others in the flight group that the huri can run out of gas.

Share this post


Link to post
Share on other sites

Several CTDs lately crash report below:

Model: PowerMac8,2, BootROM 5.2.5f1, 1 processor, PowerPC G5 (3.1), 2 GHz, 1.5 GB

Graphics: kHW_ATIrv351Item, ATY,RV351, spdisplays_agp_device, 128 MB

Memory Module: DIMM0/J4000, 512 MB, DDR SDRAM, PC3200U-30330

Memory Module: DIMM1/J4001, 1 GB, DDR SDRAM, PC3200U-25440

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x4318), Broadcom BCM43xx 1.0 (4.170.25.8)

Modem: Jump, V.92, Version 1.0

Bluetooth: Version 2.0.0f20, 2 service, 1 devices, 1 incoming serial ports

Network Service: Built-in Ethernet, Ethernet, en0

Serial ATA Device: WDC WD2500JD-40HBC0, 232.89 GB

Parallel ATA Device: PIONEER DVD-RW DVR-K04L

USB Device: USB2.0 Hub, high_speed, 500 mA

USB Device: iPod, Apple, high_speed, 500 mA

USB Device: SideWinder Precision 2 Joystick, Microsoft, low_speed, 500 mA

USB Device: Bluetooth USB Host Controller, Apple, Inc., full_speed, 500 mA

USB Device: USB to PS2 Adaptor v1.12, Composite USB PS2 Converter, low_speed, 500 mA

USB Device: Hub in Apple Extended USB Keyboard, Mitsumi Electric, full_speed, 500 mA

USB Device: Apple Extended USB Keyboard, Mitsumi Electric, full_speed, 250 mA

Process: World War ][ Online [295]

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

Identifier: com.playnet.ww2ol

Version: 1.27.1 (???)

Code Type: PPC (Native)

Parent Process: launchd [98]

Date/Time: 2007-12-14 15:03:11.177 +1100

OS Version: Mac OS X 10.5.1 (9B18)

Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGBUS)

Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000030

Crashed Thread: 0

Thread 0 Crashed:

0 com.playnet.ww2ol 0x00169988 0x1000 + 1477000

1 com.playnet.ww2ol 0x0003b5dc 0x1000 + 239068

2 com.playnet.ww2ol 0x0003bb88 0x1000 + 240520

3 com.playnet.ww2ol 0x0015ec58 0x1000 + 1432664

4 com.apple.Foundation 0x93ab9b24 __NSFireTimer + 284

5 com.apple.CoreFoundation 0x94ca9af0 CFRunLoopRunSpecific + 2992

6 com.apple.HIToolbox 0x934cdab4 RunCurrentEventLoopInMode + 264

7 com.apple.HIToolbox 0x934cd8d8 ReceiveNextEventCommon + 412

8 com.apple.HIToolbox 0x934cd718 BlockUntilNextEventMatchingListInMode + 84

9 com.apple.AppKit 0x90faa7a0 _DPSNextEvent + 580

10 com.apple.AppKit 0x90faa1f0 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 112

11 com.apple.AppKit 0x90fa3eac -[NSApplication run] + 736

12 com.apple.AppKit 0x90f7492c NSApplicationMain + 440

13 com.playnet.ww2ol 0x000030c8 0x1000 + 8392

14 com.playnet.ww2ol 0x00002dcc 0x1000 + 7628

Thread 1:

0 libSystem.B.dylib 0x957c09d8 mach_msg_trap + 8

1 libSystem.B.dylib 0x957c78fc mach_msg + 56

2 com.apple.CoreFoundation 0x94ca9664 CFRunLoopRunSpecific + 1828

3 com.apple.CFNetwork 0x91c9ccf8 CFURLCacheWorkerThread(void*) + 292

4 libSystem.B.dylib 0x95802bf8 _pthread_start + 316

Thread 2:

0 libSystem.B.dylib 0x957c09d8 mach_msg_trap + 8

1 libSystem.B.dylib 0x957c78fc mach_msg + 56

2 com.apple.CoreFoundation 0x94ca9664 CFRunLoopRunSpecific + 1828

3 com.apple.Foundation 0x93ae2bec +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 280

4 com.apple.Foundation 0x93a8bd9c __NSThread__main__ + 1004

5 libSystem.B.dylib 0x95802bf8 _pthread_start + 316

Thread 3:

0 libSystem.B.dylib 0x95825064 select$DARWIN_EXTSN + 12

1 com.apple.CoreFoundation 0x94cb4ab4 __CFSocketManager + 764

Thread 4:

0 libSystem.B.dylib 0x957c0a58 semaphore_timedwait_signal_trap + 8

1 libSystem.B.dylib 0x95803e9c _pthread_cond_wait + 1320

2 com.apple.Foundation 0x93ac9140 -[NSCondition waitUntilDate:] + 384

3 com.apple.Foundation 0x93ac8f6c -[NSConditionLock lockWhenCondition:beforeDate:] + 268

4 com.apple.AppKit 0x91005dfc -[NSUIHeartBeat _heartBeatThread:] + 660

5 com.apple.Foundation 0x93a8bd9c __NSThread__main__ + 1004

6 libSystem.B.dylib 0x95802bf8 _pthread_start + 316

Thread 5:

0 libSystem.B.dylib 0x957c73ec __semwait_signal + 12

1 libSystem.B.dylib 0x95803fa0 _pthread_cond_wait + 1580

2 libGLProgrammability.dylib 0x950f3a78 glvmDoWork + 120

3 libSystem.B.dylib 0x95802bf8 _pthread_start + 316

Thread 6:

0 libSystem.B.dylib 0x957c09d8 mach_msg_trap + 8

1 libSystem.B.dylib 0x957c78fc mach_msg + 56

2 com.apple.CoreFoundation 0x94ca9664 CFRunLoopRunSpecific + 1828

3 com.apple.audio.CoreAudio 0x93e9ee3c HALRunLoop::OwnThread(void*) + 212

4 com.apple.audio.CoreAudio 0x93e9ec80 CAPThread::Entry(CAPThread*) + 104

5 libSystem.B.dylib 0x95802bf8 _pthread_start + 316

Thread 7:

0 libSystem.B.dylib 0x957c0a58 semaphore_timedwait_signal_trap + 8

1 libSystem.B.dylib 0x95803e9c _pthread_cond_wait + 1320

2 com.apple.audio.CoreAudio 0x93eb0884 HP_IOThread::WorkLoop() + 488

3 com.apple.audio.CoreAudio 0x93eb0684 HP_IOThread::ThreadEntry(HP_IOThread*) + 12

4 com.apple.audio.CoreAudio 0x93e9ec80 CAPThread::Entry(CAPThread*) + 104

5 libSystem.B.dylib 0x95802bf8 _pthread_start + 316

Thread 8:

0 libSystem.B.dylib 0x957c0a38 semaphore_wait_signal_trap + 8

1 libSystem.B.dylib 0x95803eac _pthread_cond_wait + 1336

2 OpenThreads 0x1ff0291c OpenThreads::Condition::wait(OpenThreads::Mutex*) + 84

3 com.playnet.ww2ol 0x000f0e18 0x1000 + 982552

4 OpenThreads 0x1ff03790 0x1ff00000 + 14224

5 libSystem.B.dylib 0x95802bf8 _pthread_start + 316

Thread 0 crashed with PPC Thread State 32:

srr0: 0x00169988 srr1: 0x0200f030 dar: 0x00000030 dsisr: 0x40000000

r0: 0x2758da20 r1: 0xbfffdd40 r2: 0x00000143 r3: 0x29bd2240

r4: 0x00000000 r5: 0x00169984 r6: 0x29bd78f0 r7: 0x00169984

r8: 0x4146bcb9 r9: 0x43431800 r10: 0xead14604 r11: 0x0054a184

r12: 0x00169984 r13: 0x00000000 r14: 0xa09c6478 r15: 0x7fffffff

r16: 0x01fd6208 r17: 0x00000001 r18: 0x00000000 r19: 0x00000000

r20: 0x00000000 r21: 0x00000000 r22: 0x01fd6308 r23: 0x01fd62fc

r24: 0x00000000 r25: 0x00510000 r26: 0x00000400 r27: 0x00980000

r28: 0x29bd2240 r29: 0x00169984 r30: 0x43431800 r31: 0x434317fc

cr: 0x88042404 xer: 0x20000000 lr: 0x00446d98 ctr: 0x00169984

vrsave: 0x00000000

Share this post


Link to post
Share on other sites
CTD'ed twice for no apparent reason.

On both occasions it was while fighting in town.

MacPro . 2 x 2.66 . 2Gb mem

Bodach

CTD'ed x 3 in about 15 mins, outside town under attack, in town running around and on D in bunker, all in same town.

This is unusual - only thing I changed recently is I added a home theater surround sound thingy - this uses optical output.

Bo

Share this post


Link to post
Share on other sites

Back after 6 months out, have to say the latest game version is a big improvement over the one I left on. Well done CRS folks!

However, 2 problems. CTDs (three tonight, no obvious commonality) with no crash reports offered. Just one second in game, next at the desktop. Bang.

And cmd-tab or whatever never works no matter what screen I'm on. Doesn't go to the desktop, just locks the game totally. Can't even force-quit. Sadly I have to force shut down which is bad news.

MacBook Pro 2ghz dual core. 2gb ram. OS 10.4.11. Video ATI Radeon X1600 128mb.

I debated running this in PC land using Bootcamp, but since I prefer the Mac side (and have more HD space free in that partition) decided to go Mac. Did I get the right client? Is there a specific Universal Binary download or is this a Rosetta program?

Good luck all!

Share this post


Link to post
Share on other sites

THere is only one client, its universal. Nothing odd about your hardware, I have a similar MBP and it works fine for me (although I am on Leopard now). cmd-tab has always had random behavior, it only crashes when you are in game, it seems to work perfectly if you are spawned out. Some people never see a crash.

Try the beta, it should have more debug info in it.

Share this post


Link to post
Share on other sites

I think you are jumping to conclusions. I am pretty sure you are not seeing a freeze up. When you are playing on the live server and do this, do the sounds continue playing as usually (ie, things are still happening) or do they lock up and repeat? If they continue, thats because the game is not frozen at all. In fact, (if you have a joystick) you can probably continue controlling vehicles.

I that case, just keep hitting cmd-tab over and over (talking a couple dozen times, no joke) until you see your desktop. You should be seeing yourself back fully in the game about every 3 key-presses (MAKE SURE TO RELEASE BOTH BUTTONS EACH TIME) even though it may take 20 to see the desktop.

Alternately, to force quit in the above case, you "should" be able to do it by doing the force quit and hitting enter. The reason is you are actually on the desktop, but your video is not refreshing so you can't see it. Hitting force quit only brings up the dialog box with wwiiol selected, and the button "force quit" must be pressed to do so, but you can't see it to click it, so you should hit enter. The game just is hogging the video (why I don't know) so it doesn't

let the finder show up, and you have to keep trying until it finally lets it go. If you set your resolution to anything non-native (like 1024X768) you should not have any trouble at all, because the screen will refresh every single time.

If it is really a crash, then you should be hearing sounds repeating constantly over and over in the most annoying way (ie, map screen music: Da..da...da...da...da...da...da..da "kill me now!"). Sorry if I have trouble believing you that the whole computer crashes. That is incredibly unlikely in OSX. The memory is protected and it should be close to impossible for a program to crash the system, but it can happen, very rarely. In 3 years with this computer, and tons of programs crashing, I may have had to force maybe 2 restarts.

Share this post


Link to post
Share on other sites
THere is only one client, its universal. Nothing odd about your hardware, I have a similar MBP and it works fine for me (although I am on Leopard now). cmd-tab has always had random behavior, it only crashes when you are in game, it seems to work perfectly if you are spawned out. Some people never see a crash.

Try the beta, it should have more debug info in it.

Since 1.27 it works perfectly spawned in game. (minus the video refresh thing which can be worked around by using non-native resolution)

Share this post


Link to post
Share on other sites

If it is really a crash, then you should be hearing sounds repeating constantly over and over in the most annoying way (ie, map screen music: Da..da...da...da...da...da...da..da "kill me now!"). Sorry if I have trouble believing you that the whole computer crashes. That is incredibly unlikely in OSX. The memory is protected and it should be close to impossible for a program to crash the system, but it can happen, very rarely. In 3 years with this computer, and tons of programs crashing, I may have had to force maybe 2 restarts.

Actually sometimes the game dies but the video system doesn't release the screen. This means you can't do anything other than turn off the power. Technically it's not the OS freezing (you can log in remotely via ssh and it's still there) just the video not being updated.

I have had the game come back with many cmd-tabs sometimes.

Share this post


Link to post
Share on other sites
Actually sometimes the game dies but the video system doesn't release the screen. This means you can't do anything other than turn off the power. Technically it's not the OS freezing (you can log in remotely via ssh and it's still there) just the video not being updated.

I have had the game come back with many cmd-tabs sometimes.

That what I'm talking about though. It might take 20 tries with cmd-tab to get the desktop. I don't think the game ever died, just the video is not refreshed. And like I said, when you use a non-native resolution, the system has to switch the video back to your native resolution to see the desktop so the video is forced to refresh. I'm not sure about intel systems, but I couldn't understand why the system would crash. Then again, I don't even understand why the video gets screwed up in the first place.

One of the great mysteries of wwiiol. Just don't give up without trying cmd-tab about 100 times :D

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.