Battlezone Forums

Battlezone 2 v1.3.6.2
Fleshstorm Mod Chapter: A New Alliance

After clearing the base for the new allies the cut scene plays. However after hitting any key to terminate the cut scene the game crashes. Otherwise the cut scene never seems to finish.
I tried looking for crash log but couldn't find one.

Image: https://docs.google.com/file/d/0B6us8R_ ... ndQcmF1SDA

Crash Log:
---- Battlezone II Log File ----
//=====================================================
App version: bzone 1.3.6.2 Public Beta Jul 29 2011 21:43:22
Windows version: Windows Version: 6.1.7601 'Service Pack 1' PlatformID=2

Last few battlezone.log lines (may or may not be relevant):
DIAG| runcodes:159 |02:18:18|775088 |[Mission] Entering run code [ESCAPE]
DIAG| runcodes:159 |02:18:18|775089 |[View] Entering run code [PauseScreen]
DIAG|MissionHandler_oldcode:1246 |02:18:18|775089 |Expanded game UI file of 'bzescape_enter_1920x1080.cfg' not found. Using default of 'bzescape_enter.cfg'
DIAG| iface:1430 |02:18:23|780564 |UnsetModal: throwing away [DEAD]
DIAG| runcodes:159 |02:18:24|780949 |[Mission] Entering run code [RUN]
DIAG|MissionHandler_oldcode:1246 |02:18:24|780950 |Expanded game UI file of 'bzescape_exit_1920x1080.cfg' not found. Using default of 'bzescape_exit.cfg'
DIAG| runcodes:159 |02:18:24|781003 |[View] Entering run code [COCKPIT]
DIAG| runcodes:159 |02:18:45|802139 |[View] Entering run code [CINERACTIVE]
(done)

Exception code: C0000005 (ACCESS VIOLATION) READING from 00000000h
Message : Exception
Error occurred at 10/1/2013 02:19:32.
D:\Installed\Battlezone II 1.3.6.2 PB\bzone.exe, run by
D:\Installed\Battlezone II 1.3.6.2 PB\bzone.exe, run by
CPU: 8 processor(s), Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz
Intel64 Family 6 Model 42 Stepping 7
Process Memory : 1348 MB free out of 2048 MB total
Physical memory: 5329 MB free out of 8170 MB total
Page(swap) file: 13077 MB free out of 16337 MB total
This exe is using 358 MB (135 MB dlmalloc), peak use 365 MB

Fault address: 0149468E 01:0011368E D:\Installed\Battlezone II 1.3.6.2 PB\bzone.exe

Registers:
EAX:1883C994
EBX:1888EAB8
ECX:00000000
EDX:20000000
ESI:1883C600
EDI:1883C9F4
CS:EIP:0023:0149468E
SS:ESP:002B:007BE228 EBP:007BE358
DS:002B ES:002B FS:0053 GS:002B
Flags:00010246

Call stack:
Address Offset1 Offset2 Module SourceFile
0149468E +0011468E 000000B0 bzone (bzone): : TargetingGun::TargetingGun
014951CE +001151CE 00000019 bzone (bzone): : TargetingGunClass::Build
014BAFD8 +0013AFD8 0000000E bzone (bzone): : OrdnanceClass::Build
01494B25 +00114B25 0000039B bzone (bzone): : TargetingGun::Simulate
013ED54E +0006D54E 00000033 bzone (bzone): : Carrier::Simulate
013F569D +0007569D 000001ED bzone (bzone): : Craft::SimulateCarrier
013F54A7 +000754A7 00000559 bzone (bzone): : Craft::Simulate
013FBE47 +0007BE47 00000145 bzone (bzone): : Deployable::SimulateDeployed
01437C99 +000B7C99 00000024 bzone (bzone): : TurretTank::SimulateDeployed
013FB9BE +0007B9BE 00000402 bzone (bzone): : Deployable::Simulate
014374E0 +000B74E0 0000002B bzone (bzone): : TurretTank::Simulate
01488106 +00108106 0000020D bzone (bzone): : ENTITY::SimulateAllLocal
013D9DF5 +00059DF5 00000182 bzone (bzone): : MoveOneTurn
013DA969 +0005A969 00000365 bzone (bzone): : MissionHandler::State::RunState::Process
0157C87F +001FC87F 000001BF bzone (bzone): : RunCodes::Process
013D8164 +00058164 0000001E bzone (bzone): : MissionHandler::Process
0157C87F +001FC87F 000001BF bzone (bzone): : RunCodes::Process
01583D74 +00203D74 00000064 bzone (bzone): : Main::MessagePump
013CAE6D +0004AE6D 000004F1 bzone (bzone): : HandledMain
013CAB1F +0004AB1F 000001A3 bzone (bzone): : HandledMain
013C7AB7 +00047AB7 0000005E bzone (bzone): : WinMain
0152B30F +001AB30F 00000191 bzone (bzone): : strcat
768A336A +0001336A 00000012 kernel32 (kernel32): : BaseThreadInitThunk
773E9F72 +00039F72 00000063 ntdll (ntdll): : RtlInitializeExceptionChain
773E9F45 +00039F45 00000036 ntdll (ntdll): : RtlInitializeExceptionChain

Any help?

Any suggestions please?

Cut out of the cutscenes as soon as they start, dont allow them to run.
Worked for me ..

Sorry that doesn't work for me. I kept hitting the space bar even before the cut scene started.
Is there a way to disable cut scenes? Perhaps by some configuration or deleting a file?

Sometimes in FS1 you have to wait until cutscenes finish. If you attempt to skip, they crash the game.

Since about 1.3pb5 (perhaps earlier), cameraPath cutscene settings in old DLLs had their decimal points shifted and thus are significantly longer and slower than they should be. The only way to fix this is to alter the numbers in the DLL files. They were all made with the DLL scriptor so it wouldn't take too long to fix.

bigbadbogie wrote:Sometimes in FS1 you have to wait until cutscenes finish. If you attempt to skip, they crash the game.

Since about 1.3pb5 (perhaps earlier), cameraPath cutscene settings in old DLLs had their decimal points shifted and thus are significantly longer and slower than they should be. The only way to fix this is to alter the numbers in the DLL files. They were all made with the DLL scriptor so it wouldn't take too long to fix.

In the mean while lets hope that /nomovies switch works.

No that doesn't work for the cutscenes.

That crash is because a targeting gun used on a ship (not sure which from the logs) has a bad ordnance type. 1.3 ever since pb4 (released over 5 years ago now) has gotten stricter about this in order to catch mods that use bad items. Did you notice the warning printed by the 1.3 installer that said to only install/run mods marked as compatible with that 1.3 patch? If you don't have the technical skills to fix the problem, I suggest you pay attention to that warning.

If it didn't crash there, it would be logging out this message about targeting gun ordnance:
pb4 requires classLabel = "leader" for ordnance, not "targeting"

-- GSH

Thank You GSH. Sorry I don't recall noticing this message but I haven't installed patches in a few months. However in retrospect during my exploration I did notice that the mod was compatible with 1.3.3. However I tried it on 1.3.6.2 & it crashes.
So I should run it on 1.3 pb 3 right?

Fleshstorm 1.0 is 1.3.6.3 compatible, but later patches (I think it's up to Fleshstorm v1.3) were compatible with TA5.1 when I was working on it.

AHadley wrote:Fleshstorm 1.0 is 1.3.6.3 compatible, but later patches (I think it's up to Fleshstorm v1.3) were compatible with TA5.1 when I was working on it.

A noob question. But what is TA5.1?

1.3.5 was where 1.3 made the switch between DX6 and DX9, so it was referred to as Tech Alpha instead of Public Beta.