Hi, first off thanks for the creation of this patch, and the time it took. I have had a number of crashes with no log of why it happened. the common occurance is on instant action I am playing scion vs. isdf and a sabre is in the picture. sometime myself or my men are attacking it.
I also had a av with a log, sorry I don't remember the situation at the time.
---- Battlezone II Log File ----
//=====================================================
App version: Patch 1.3pb4 EDITOR Jun 9 2008 22:21:16
Exception code: C0000005 (ACCESS VIOLATION) READING from 00000350h
Message : Exception
Error occurred at 7/14/2008 16:53:46.
C:\Program Files\Battlezone II 1.3 pb4\BZ2Edit.exe, run by Mag.
2 processor(s), type 586.
Process Memory : 1774 MB free out of 2048 MB total
Physical memory: 492 MB free out of 1023 MB total
Page(swap) file: 2018 MB free out of 2460 MB total
Fault address: 00426E6A 01:00025E6A C:\Program Files\Battlezone II 1.3 pb4\BZ2Edit.exe
Registers:
EAX:00000000
EBX:0E431F90
ECX:0AAA497C
EDX:E88051EC
ESI:00000005
EDI:000FFFFF
CS:EIP:001B:00426E6A
SS:ESP:0023:0228FA3C EBP:0228FAC8
DS:0023 ES:0023 FS:003B GS:0000
Flags:00210202
Call stack:
Address Return Function SourceFile
00426E6A 00000000 0042C07F Attacker::Execute+0x00000710
0042C07F 00000000 004016A1 ExecuteSchedPlans+0x0000054C
004016A1 00000000 00401F4B AiMission::Update+0x00000103
00401F4B 00000000 0046C170 AI_Update+0x00000006
0046C170 00000000 0046CCEB MoveOneTurn+0x00000109
0046CCEB 00000000 0057CF20 MissionHandler::State::RunState::Process+0x000003BE
0057CF20 00000000 0046A5F1 RunCodes::Process+0x0000019F
0046A5F1 00000000 0057CF20 MissionHandler::Process+0x00000011
0057CF20 00000000 0057C941 RunCodes::Process+0x0000019F
0057C941 00000000 00455EED Main::MessagePump+0x0000004A
00455EED 00000000 00455BD7 HandledMain+0x00000444
00455BD7 00000000 00453701 HandledMain+0x0000012E
00453701 00000000 0058D126 WinMain+0x00000059
0058D126 00000000 7C816FD7 memset+0x00000192
7C816FD7 00000000 00000000 RegisterWaitForInputIdle+0x00000049
I will also add my comment about the other post about stupid scavs, I noticed (hard not too) the scavs and healers like to run into extracters and gun towers instead of going around them.
Readme Before Posting Bugs (http://www.bzuniverse.com/forum/index.php/topic,7932.0.html)
I've read it, what's your point?
Quote from: Commando on June 17, 2008, 04:07:39 AM
3. If your AV has the following under CallStack, there is no need to post your AV. A good 60% of the AVs posted are identical and involve the following. It is a known issue that has been addressed.
Quote
Call stack:
Address Return Function SourceFile
00426AC1 00000000 0042BD30 Attacker::Execute+0x00000710
Thats my point :P
that's your point huh, maybe you should learn how to read before posting. the address and function have different numbers.
Ignorant fool (always wanted to say that :P) The first line says all, its the infamous pb4 Attacker crash.
If you want to be dumb and deny this (anyone), be my guest......
The numbers in the first and third columns are slightly different, because they were reported in bzone.exe vs bz2edit.exe. The function name and offset (Attacker::Execute+0x00000710) is identical, which is the most important part.
-- GSH
Quote from: GSH on July 25, 2008, 08:14:19 PM
The numbers in the first and third columns are slightly different, because they were reported in bzone.exe vs bz2edit.exe. The function name and offset (Attacker::Execute+0x00000710) is identical, which is the most important part.
-- GSH
Quite possibly need to add that to the Readme
"Blah Blah Blah Attacker::Execute and such for BZone.exe"
And
"Bleh Bleh Bleh Attacker Execute and the like for BZ2edit.exe"
Would help to avoid confusions like this.
Bit of a touchy topic.
NO!! Don't touch it!!!
Can't...
Resist...
POKE
N1s finger is ripped off and eaten by the topic.
Luckily my voodoo powers can regrow my finger...
I am pretty sure the numbers would be irrelevant no matter what they were (though 0x00000000 might need posting), its still a crash in the same function of the same class.
Congratulations, you guys have successfully run mag off.
:lol:
Naw, He's part of the family now...
:)
But really, Thats the first AV reported I think...it's been fixed in pb4a.
almost run off, from the childish people on here.
that wasn"t my main topic. It was about bz closing with no reason why, no log file.
I should have left the secound part off, I didn't realize that the last number was all that mattered.
also I think it might have been mentioned, but I noticed that some of the maulers are partly below ground some of the time.
just putting this info out for those that need to know.
Ok, the maulers being BELOW ground.... besides on building, i've never seen it..... could be worth looking at...
I've seen it many times.
playing against the computer on insane mode fighting the isdf im playing scion on chill
---- Battlezone II Log File ----
//=====================================================
App version: Patch 1.3pb4 Jun 9 2008 22:18:35
Exception code: C0000005 (ACCESS VIOLATION) READING from 00000350h
Message : Exception
Error occurred at 7/30/2008 08:54:00.
C:\Program Files\Battlezone II\bzone.exe, run by Accident.
2 processor(s), type 586.
Process Memory : 1626 MB free out of 2048 MB total
Physical memory: 471 MB free out of 1023 MB total
Page(swap) file: 1972 MB free out of 2462 MB total
Fault address: 00426AC1 01:00025AC1 C:\Program Files\Battlezone II\bzone.exe
Registers:
EAX:00000000
EBX:16E99218
ECX:065BDF4C
EDX:90C03DA4
ESI:00000006
EDI:000FFFFF
CS:EIP:001B:00426AC1
SS:ESP:0023:022BFA1C EBP:022BFAA8
DS:0023 ES:0023 FS:003B GS:0000
Flags:00210202
Call stack:
Address Return Function SourceFile
00426AC1 00000000 0042BD30 Attacker::Execute+0x00000710
0042BD30 00000000 004016D0 ExecuteSchedPlans+0x0000054C
004016D0 00000000 00401F8C AiMission::Update+0x00000103
00401F8C 00000000 00461261 AI_Update+0x00000006
00461261 00000000 00461E0C MoveOneTurn+0x0000011E
00461E0C 00000000 0056475F MissionHandler::State::RunState::Process+0x000003CC
0056475F 00000000 0045F691 RunCodes::Process+0x000001BF
0045F691 00000000 0056475F MissionHandler::Process+0x00000012
0056475F 00000000 00564BD4 RunCodes::Process+0x000001BF
00564BD4 00000000 00455A95 Main::MessagePump+0x00000064
00455A95 00000000 0045578C HandledMain+0x000003F4
0045578C 00000000 0045343D HandledMain+0x000000EB
0045343D 00000000 0055567D WinMain+0x00000059
0055567D 00000000 7C816D4F fabs+0x00000191
7C816D4F 00000000 00000000 RegisterWaitForInputIdle+0x00000049
Another chill crash, on insane mode
---- Battlezone II Log File ----
//=====================================================
App version: Patch 1.3pb4 Jun 9 2008 22:18:35
Exception code: C0000005 (ACCESS VIOLATION) READING from 00000350h
Message : Exception
Error occurred at 7/30/2008 09:28:08.
C:\Program Files\Battlezone II\bzone.exe, run by Accident.
2 processor(s), type 586.
Process Memory : 1753 MB free out of 2048 MB total
Physical memory: 474 MB free out of 1023 MB total
Page(swap) file: 1970 MB free out of 2462 MB total
Fault address: 00426AC1 01:00025AC1 C:\Program Files\Battlezone II\bzone.exe
Registers:
EAX:00000000
EBX:061DB6B0
ECX:05F2F514
EDX:85A0984E
ESI:00000006
EDI:000FFFFF
CS:EIP:001B:00426AC1
SS:ESP:0023:022BFA1C EBP:022BFAA8
DS:0023 ES:0023 FS:003B GS:0000
Flags:00210206
Call stack:
Address Return Function SourceFile
00426AC1 00000000 0042BD30 Attacker::Execute+0x00000710
0042BD30 00000000 004016D0 ExecuteSchedPlans+0x0000054C
004016D0 00000000 00401F8C AiMission::Update+0x00000103
00401F8C 00000000 00461261 AI_Update+0x00000006
00461261 00000000 00461E0C MoveOneTurn+0x0000011E
00461E0C 00000000 0056475F MissionHandler::State::RunState::Process+0x000003CC
0056475F 00000000 0045F691 RunCodes::Process+0x000001BF
0045F691 00000000 0056475F MissionHandler::Process+0x00000012
0056475F 00000000 00564BD4 RunCodes::Process+0x000001BF
00564BD4 00000000 00455A95 Main::MessagePump+0x00000064
00455A95 00000000 0045578C HandledMain+0x000003F4
0045578C 00000000 0045343D HandledMain+0x000000EB
0045343D 00000000 0055567D WinMain+0x00000059
0055567D 00000000 7C816D4F fabs+0x00000191
7C816D4F 00000000 00000000 RegisterWaitForInputIdle+0x00000049
-_-..... im loosing my patience for people who dont read the av list...
Already reported, its the attacker av, its been fixed for the emergency patch that will come out (hopefully before late August).
sorry i will not post any more crashes
Maybe someone should post a temp ban who posts the avs we already know of for like 2 days?
Why? some people on these forums have been around for a long time... they don't like to put up with simple problems like this...
I figure I wouldn't yell at someone for coming into a forum like this person did posting a AV crash.. he could be new at the game...
Quote from: Killer AK on July 31, 2008, 12:39:38 AM
sorry i will not post any more crashes
Just not the Attacker crash or the pilot weapon pickup crash, those two are already known. (Also, the former is in the Readme at the top of the subforum)
Reporting crashes are good, just reporting the same one that has identical information as any others then becomes noise and is extra information to parse through...
(http://www.overminddl1.com/image_scripts/image_sig.php?type=ODL1signitures&image/sig.gif)
Generated by OvermindDL1's Signature Auto-Add Script (http://overminddl1.com) via GreaseMonkey (http://greasemonkey.mozdev.org/)
Can it really be that hard to just search the forum for information before posting about it??
Readme before posting bugs (http://www.bzuniverse.com/forum/index.php/topic,7932.0.html)
It's a sticky, always will be toward the top of the list. It will always be there and is easy to find.
PLEASE keep reporting bugs it helps make PB4a better for everyone, but BEFORE posting the bug make sure you read the sticky.