Oooh dear. ETQWOSX issues.

(taw_m0nsta) #21

created a .txt file here: http://monsta.nl/taw/dump/Console.txt

(timestart) #22

You seem to still have arcis pro at /Users/Monsta/Library/Application Support/ETQW/base/zmap_arcis_a2_pro.pk4.

(Donnovan) #23

You have many many old versions maps loading on your ETQW launch up.

(taw_m0nsta) #24

[QUOTE=timestart;381615]You seem to still have arcis pro at /Users/Monsta/Library/Application Support/ETQW/base/zmap_arcis_a2_pro.pk4.[/QUOTE] Wt… will delete it again

Should that matter really? Will clean it up asap.

(taw_m0nsta) #25

@ Donnavan

From this location, when I do one more step forward it kicks me out. I’m now gonna remove that old pro map again, and test again.

(taw_m0nsta) #26

Does this help? Dived in my crash reporter:
Filtered this thread out since its giving errors. I’m kinda worried that the full crash report includes stuff that shouldn’t be shared public…

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000c50ba024
Crashed Thread:  9

Thread 9 Crashed:
0   libSystem.B.dylib                 0x99a759ae pthread_join + 607
1   com.aspyr.etqw                    0x00220134 0x1000 + 2224436
2   com.aspyr.etqw                    0x0021b72e 0x1000 + 2205486
3   com.aspyr.etqw                    0x0021fb7f 0x1000 + 2222975
4   libSystem.B.dylib                 0x99a6105b _sigtramp + 43
5   ???     

Thread 9 crashed with X86 Thread State (32-bit):
  eax: 0xc50ba000  ebx: 0x99a75763  ecx: 0xb06a2008  edx: 0xc50ba000
  edi: 0xb06a2000  esi: 0x00000003  ebp: 0xb020f9c8  esp: 0xb020f970
   ss: 0x0000001f  efl: 0x00010286  eip: 0x99a759ae   cs: 0x00000017
   ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037
  cr2: 0xc50ba024

I switched to GDF for a change, as soon as I turn around and see this picture, the game freezes and closes.

I also removed pretty much all older map versions.

(Donnovan) #27

Is you trying to run it on QWTA mod?

(taw_m0nsta) #28

No I selected it when the game was in Vanilla

(taw_m0nsta) #29

I guess the crash reporter isnt very usefull. When trying it in ProMod, the console says:

Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000014
Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
0   game.so                           0x35461084 idWeapon::UpdateScript() + 84
1   game.so                           0x35288a22 idPlayer::UpdateWeapon() + 194
2   game.so                           0x352a2b20 idPlayer::Think() + 6352
3   game.so                           0x34f7b9a3 idGameLocal::RunFrame(usercmd_t const*, int) + 1507
4   com.aspyr.etqw                    0x00081fb5 0x1000 + 528309
5   com.aspyr.etqw                    0x00086420 0x1000 + 545824
6   com.aspyr.etqw                    0x000342c0 0x1000 + 209600
7   com.aspyr.etqw                    0x002b5b7a 0x1000 + 2837370
8   com.aspyr.etqw                    0x002256bc 0x1000 + 2246332
9   com.apple.Foundation              0x95fd2efc _nsnote_callback + 345
10  com.apple.CoreFoundation          0x96760793 __CFXNotificationPost + 947
11  com.apple.CoreFoundation          0x9676019a _CFXNotificationPostNotification + 186
12  com.apple.Foundation              0x95fc7cf0 -[NSNotificationCenter postNotificationName:object:userInfo:] + 128
13  com.apple.Foundation              0x95fd50fd -[NSNotificationCenter postNotificationName:object:] + 56
14  com.apple.AppKit                  0x99c55216 -[NSApplication _postDidFinishNotification] + 125
15  com.apple.AppKit                  0x99c55126 -[NSApplication _sendFinishLaunchingNotification] + 74
16  com.apple.AppKit                  0x99dac339 -[NSApplication(NSAppleEventHandling) _handleAEOpen:] + 274
17  com.apple.AppKit                  0x99dabf59 -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 101
18  com.apple.Foundation              0x96008298 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 511
19  com.apple.Foundation              0x9600805c _NSAppleEventManagerGenericHandler + 228
20  com.apple.AE                      0x91347f5c aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*) + 166
21  com.apple.AE                      0x91347e5b dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 43
22  com.apple.AE                      0x91347d65 aeProcessAppleEvent + 197
23  com.apple.HIToolbox               0x9228a197 AEProcessAppleEvent + 50
24  com.apple.AppKit                  0x99c257d2 _DPSNextEvent + 1420
25  com.apple.AppKit                  0x99c24dd6 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156
26  com.apple.AppKit                  0x99be71f3 -[NSApplication run] + 821
27  com.aspyr.etqw                    0x00225d64 0x1000 + 2248036
28  com.aspyr.etqw                    0x00003072 0x1000 + 8306
29  com.aspyr.etqw                    0x00002f99 0x1000 + 8089


Thread 0 crashed with X86 Thread State (32-bit):
  eax: 0x00000000  ebx: 0x35461041  ecx: 0x359be380  edx: 0x489b6c04
  edi: 0x000001af  esi: 0xffffffff  ebp: 0xbfffe648  esp: 0xbfffe610
   ss: 0x0000001f  efl: 0x00010246  eip: 0x35461084   cs: 0x00000017
   ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037
  cr2: 0x00000014
(Donnovan) #30

[QUOTE=taw_m0nsta;381643]Wt… will delete it again

Should that matter really? Will clean it up asap.[/QUOTE]

It matters, Consite have missing lights because a SDK modified file not renamed on other map. Old files can conflict with new files. Conflicts can sure happens with new files itself, but leaving all the old version active will just increase your chance to create more conflicts.

(Donnovan) #31

BTW, i will take a general look at Andes code on this end of week.

You tryed to remove /Users/Monsta/Library/Application Support/ETQW/base/zmap_arcis_a2_pro.pk4?

(Ashog) #32

he should because it it is the first obvious thing to do…

(taw_m0nsta) #33

yes removed zmap_arcis_a2_pro.pk4