Game closing abruptly when trying to droideka

Posts
280
Likes
250
I was on the TR Deathstar server, my view was in first person mode, I tried to spawn as a Droideka with power managment, projector 1, shield 2 or 3, hull 2, firepower3( or 2 if the points don't add up). When I get to spawn, the game just close, no crash-log, nothing. I checked the event viewer logs and couldn't find anything related to the incident. It happened twice in a row.
 

ent

Movie Battles II Team
Posts
848
Likes
390
You sure there are no crashlogs in GameData? Are you on MBII Client?
 
Posts
280
Likes
250
The launcher stayed active but JKA just closed. I'm lauching the MB2 laucher from steam. But it's the first time I'm having this issue. I'll try to duplicate using 3rd person view from the get-go and fiddle with other vars to check.

Edit: Did some further testing, the trigger seems to be starting the round in first person as the second droideka skin, starting with the black one( last skin) didn't trigger the crash but the second one did.
 
Last edited:
Posts
280
Likes
250
Answer, please.
Here's the crash log, all of them are identical.
===================================
JKA Movie Battles II Crash Log
===================================
Process File Name: C:\Program Files (x86)\Steam\steamapps\common\Jedi Academy\GameData\jasp.exe
Module File Name: cgamex86.dll (cgame)
Exception Code: 0xC0000005 (Access Violation)
Exception Address: 0x5AF6B810 (cgamex86.dll+0x7B810)

-----------------------------------
Register Dump
-----------------------------------
General Purpose & Control Registers:
EAX: 0x5D3DD4A8, EBX: 0x00000001, ECX: 0x00000000
EDX: 0x00000000, EBP: 0x00000000, EDI: 0x5D262D14
EIP: 0x5AF6B810, ESI: 0x5D297498, ESP: 0x01B7FBD4

Segment Registers:
CS: 0x00000023, DS: 0x0000002B, ES: 0x0000002B
FS: 0x00000053, GS: 0x0000002B, SS: 0x0000002B

-----------------------------------
Call Stack Trace
-----------------------------------
cgamex86.dll(dllEntry+0x4A10) [0x5AF6B810]
 
  • Like
Reactions: ent
Posts
145
Likes
141
The launcher stayed active but JKA just closed. I'm lauching the MB2 laucher from steam. But it's the first time I'm having this issue. I'll try to duplicate using 3rd person view from the get-go and fiddle with other vars to check.

Edit: Did some further testing, the trigger seems to be starting the round in first person as the second droideka skin, starting with the black one( last skin) didn't trigger the crash but the second one did.
In the Launcher, go to settings, Disable Steam Integration, change Client from JAMP to MBII client try that, cause for some reason, steam makes MBII run Autisticly
 
Posts
280
Likes
250
In the Launcher, go to settings, Disable Steam Integration, change Client from JAMP to MBII client try that, cause for some reason, steam makes MBII run Autisticly
Ok thanks, I'll try that and the next time I play I'll see if the same error occurs. Thanks again Viz.
 
Posts
280
Likes
250
Got same crash, here's the log with the MB2 client.

===================================
JKA Movie Battles II Crash Log
===================================
Process File Name: C:\Program Files (x86)\Steam\steamapps\common\Jedi Academy\GameData\mbii.x86.exe
Module File Name: OJKAC09.tmp (cgame)
Exception Code: 0xC0000005 (Access Violation)
Exception Address: 0x5AE5B810 (OJKAC09.tmp+0x7B810)

-----------------------------------
Register Dump
-----------------------------------
General Purpose & Control Registers:
EAX: 0x5D2C6B48, EBX: 0x00000001, ECX: 0x00000000
EDX: 0x00000000, EBP: 0x00000000, EDI: 0x5D152D14
EIP: 0x5AE5B810, ESI: 0x5D17D688, ESP: 0x01F7F470

Segment Registers:
CS: 0x00000023, DS: 0x0000002B, ES: 0x0000002B
FS: 0x00000053, GS: 0x0000002B, SS: 0x0000002B

-----------------------------------
Call Stack Trace
-----------------------------------
OJKAC09.tmp(dllEntry+0x4A10) [0x5AE5B810]
 

ent

Movie Battles II Team
Posts
848
Likes
390
Send me cgamex86.dll via PM, please. You can find it in GameData/MBII/ (check if it has today/yesterday date).
 
Posts
280
Likes
250
Was anyone able to replicate this error or am I the only one getting it? If I'm the only one a fix isn't needed but if it's an underlying problem that could affect others then I'm glad I could bring it up.
 
Top