Force Sense game crash

[Enette]

Hello,
firstly as it is my first post on the forum I would like to greet everyone

So, when it comes to the topic. Yesterday I installed the new 1.4.2 and had crashes while playing as a Jedi.
At first I had no idea what was the cause, sometimes it happened in the first round of my play, sometimes it happened after 30 minutes.
However tonight, not so long ago I found that it always happens when I activate Force Sense (level 2 if that matters).
The game is simply turning off without any window as one can see while the Jedi Academy is starting, there is just my desktop.
I don't know if anyone else has this problem, but I want others to know about that. As my main class is Jedi/Sith, it's unfortunately not possible to enjoy the game.
Hopefully someone will be able to help with that issue.

 

[Chaos the Chaotic]

Support section would be better for this.

So, whats your system - vista, windows 7, 8, 9 10, 11?
Using cd version or steam? Mac?

In the launcher there's a "check integrity" in settings,. Did you try that?
Could be faulty install, drivers being out of date or too updated or gremlins. They're shorter than trolls, bigger ears, hairier and while not crashing planes they lurk in computers, waiting for their chance to commit wickedness.

Did you try switching from jamp to openjk/mbclient or vice versa?
Be warned as your fx and keyboard binds might reset to default or older versions if/when you do this.

Could be one of the issues I had. The last update for me I had to manually delete old files as they were messing with the new content. Could be that...

If all else fails. You must chant these 3 words.

@Puppytine
@Puppytine
@Puppytine

edit; Don't tell me Subaru disabled mentions??

 

[ent]

Any crash logs in GameData?

 

[Puppytine]

Well, I can suggest only generic things in this case, and @Chaos the Chaotic already mentioned them.

MBII Launcher => Settings => check "Enable logging" => Repair installation.
Post latest log from "Jedi Academy\GameData\MBII_Launcher\logs" here.

MBII Launcher => Settings => uncheck "Steam integration" (skip if there's no such checkbox) => Engine => MBII Client => Play.
If you already use MBII Client, select jamp.

Search for crash log in "Jedi Academy\GameData".

edit; Don't tell me Subaru disabled mentions??

No he didn't.

 

[Enette]

I use Windows 7 and CD version of game, check integrity option as well. I also made a full installation, but it considers only the maps as I noticed.
Like Chaos the Chaotic adviced I reinstalled everything but the problem is still the same.
At first I used MBII client to start the game, I could not enter any server as I've seen information that my version 1.4.1 is not valid for a 1.4.2, although I had installed the newest one. Yet it worked when I changed to JAMP and could join a server.
Now after reinstallation I have to use MBII client to enter any server, yet sense bug still appears.
Ent, I have one crash log from today which I upload in this post.
Puppytine, I tried everything that you wrote.
By the way, I use the launcher to start the mod, or should it be something different?

===================================
JKA Movie Battles II Crash Log
===================================
Process File Name: C:\Games\Jedi Academy\GameData\mbii.x86.exe
Module File Name: OJK93D3.tmp
Exception Code: 0xC0000005 (Access Violation)
Exception Address: 0x2C48026C (OJK93D3.tmp+0x7026C)
-----------------------------------
Register Dump
-----------------------------------
General Purpose & Control Registers:
EAX: 0x00000001, EBX: 0x2C4EE850, ECX: 0x462ADCBE
EDX: 0x00152814, EBP: 0x2C4DDA82, EDI: 0x3AD2DDC0
EIP: 0x2C48026C, ESI: 0x3AD2DDC0, ESP: 0x0015286C

INFO: Launcher checks if MBII is installed > YES
Movie Battles II Log file Created on: 2016-09-09 11:15:34
===================================================

Current Launcher's configuration
===================================================
Installation type (Complete/Basic): BASIC
Installation folder: C:\Games\Jedi Academy\GameData\
Client: JAMP
Custom launch parameters:
===================================================

Additional Informations
===================================================
OS: WINDOWS Microsoft Windows 7 Home Premium
GPU: Intel(R) HD Graphics
===================================================
INFO: Found version info file > 1.4.2
INFO: Launcher checks for new version
INFO: Launcher checks if MBII is installed > YES
INFO: Repair installation started.
FILE CHECKING: 1 MBII/MBAssets2.pk3 - F0EEBBFC6DDFB6129A3EBD4BF0BC1474 OK
FILE CHECKING: 2 MBII/MBAssets3.pk3 - EBEC13F45EEE35DDC9608407E199AF59 OK
FILE CHECKING: 3 MBII/MBAssets.pk3 - 335EB8F104C78D417FF16757B048BF19 OK
FILE CHECKING: 4 MBII/z_MB_BaseAssets.pk3 - 4482665DA46DD2379B04D24A1C0C1712 OK
FILE CHECKING: 5 MBII/FAMBModels.pk3 - B82C3805E507BE0176279694D832A793 OK
FILE CHECKING: 6 MBII/MB_Effects.pk3 - C6017FFE2567969E8A2429544FCADEBD OK
FILE CHECKING: 7 MBII/MBHilts.pk3 - 3FCDDA2228E5851E52D5AFAAE79B9BEF OK
FILE CHECKING: 8 MBII/zz_MBModels2.pk3 - B7532C5DAB2ECB80A9D00DB2E938B492 OK
FILE CHECKING: 9 MBII/zz_MBModels.pk3 - 8505FA9700766EF53BDAB6F45047C7AD OK
FILE CHECKING: 10 MBII/MBII_Mac.pk3 - FEBAC029C7AA140B45244B154B8F556C OK
FILE CHECKING: 11 MBII/MBII.pk3 - 069C049680E63B3E2D7C59CEAFA73B77 OK
FILE CHECKING: 12 MBII/cgamei386.so - 761EFBF192909FEFF94B5AF0425EAF02 OK
FILE CHECKING: 13 MBII/jampgamei386.so - 80ACB39E1032445AED974F8E6D1AC9CB OK
FILE CHECKING: 14 MBII/uii386.so - C8D5E130C9B797BBB1D1BA6D8089FC1C OK
FILE CHECKING: 15 MBII/mb2_alderaan.pk3 - 09AAAF1B52B715028DDE4B22C51E68DF OK
FILE CHECKING: 16 MBII/mb2_boc.pk3 - E62612AF1675DAE89DD2100D5A045383 OK
FILE CHECKING: 17 MBII/mb2_cloudcity.pk3 - F779B92F39603E10EA4536312062A9A8 OK
FILE CHECKING: 18 MBII/MB2_Commtower.pk3 - A2EDF29B9A71BEB226C89F69EAB40A4F OK
FILE CHECKING: 19 MBII/mb2_corellia.pk3 - F45558B212452F3AD4652E6E56315857 OK
FILE CHECKING: 20 MBII/mb2_Coruscant_chase.pk3 - 1359F2627A954C6F8813CCA9C55A1165 OK
FILE CHECKING: 21 MBII/mb2_deathstar.pk3 - 73BB13142B151062913F81C3D8C396DC OK
FILE CHECKING: 22 MBII/mb2_dotf.pk3 - 78F6A6F5883F81479C6A7B001E4F0205 OK
FILE CHECKING: 23 MBII/mb2_duel_emperor.pk3 - 6A34D8A3105D562536F5978241F41EBC OK
FILE CHECKING: 24 MBII/mb2_duel_malachor.pk3 - 981254E4ECB6AD72D6D9AE3C542B7C91 OK
FILE CHECKING: 25 MBII/mb2_duel_office.pk3 - 80336F71A8C1BDE63C9729BF5E455F0B OK
FILE CHECKING: 26 MBII/mb2_duel_ravager.pk3 - 339171BA8CC7B79742CA32D9CC87BB65 OK
FILE CHECKING: 27 MBII/mb2_duel_revan.pk3 - 547A2FA235377D09DA6FEB2BFE4C010D OK
FILE CHECKING: 28 MBII/mb2_duel_sabh.pk3 - 0BF8FD69C4ACEA83D2C3DC30FF50A1DC OK
FILE CHECKING: 29 MBII/mb2_duel_senate.pk3 - 20061CD04063F7F6E51F61D64FB7B398 OK
FILE CHECKING: 30 MBII/mb2_duel_starforge.pk3 - 61CF1DB4AA6E03237A9898BC005C2546 OK
FILE CHECKING: 31 MBII/mb2_duel_starkiller_base.pk3 - 6CE27088F4A9826AB0D0D962904F85D9 OK
FILE CHECKING: 32 MBII/mb2_duel_utapau.pk3 - B786AF2E79A92B787D5037ED98E297D5 OK
FILE CHECKING: 33 MBII/mb2_duel_votj.pk3 - 43C0AAFD0A17C84792FE3E30DAA06CDA OK
FILE CHECKING: 34 MBII/mb2_duel_yavin4.pk3 - 212283F5BE396A80038CD641CA259B82 OK
FILE CHECKING: 35 MBII/mb2_echobase.pk3 - 1C91914C49916204C7B4AEC922DBE6E2 OK
FILE CHECKING: 36 MBII/mb2_enclave.pk3 - 01F1F38B99B29FF42EA5AEB4F5E8F57D OK
FILE CHECKING: 37 MBII/mb2_eravana.pk3 - 85E8EF0A7FD47C7978B0E52EF5BB61B5 OK
FILE CHECKING: 38 MBII/mb2_jabba.pk3 - 9EE3A36D266954D05725AC2B8EBB5CE7 OK
FILE CHECKING: 39 MBII/mb2_jeditemple.pk3 - 273C58FFF6F6970819CA76C17179FEF3 OK
FILE CHECKING: 40 MBII/mb2_kamino.pk3 - F4481C36481A799D77DDEC9259EA553C OK
FILE CHECKING: 41 MBII/mb2_korriban.pk3 - F8E65DFFECFC474696CB0BE213FE1201 OK
FILE CHECKING: 42 MBII/mb2_lunarbase.pk3 - 99B7A0351112057F0E765A323932582C OK
FILE CHECKING: 43 MBII/mb2_moseisley.pk3 - 01A5962FC16011F21CC7C9E740325286 OK
FILE CHECKING: 44 MBII/mb2_mustafar.pk3 - 217F0B62A5C73AA0939C3D5E443217F7 OK
FILE CHECKING: 45 MBII/mb2_mygeeto.pk3 - 2801D63B2879C445F61A0474840E53BE OK
FILE CHECKING: 46 MBII/mb2_rc_hangarC.pk3 - 8CEBE8939A20CF38075257E2B975A315 OK
FILE CHECKING: 47 MBII/mb2_republiccruiser.pk3 - 161A17D8953370ADEB17A6535C5F662F OK
FILE CHECKING: 48 MBII/mb2_SDestroyer.pk3 - 7E8700227BE66C5FEBC688A986702F57 OK
FILE CHECKING: 49 MBII/mb2_smuggler.pk3 - A67CDD85AEAB38C925946E0854AB8A59 OK
FILE CHECKING: 50 MBII/mb2_tantiveIV.pk3 - 3E7C549E71D771930930B0DA7918BEA3 OK
FILE CHECKING: 51 MBII/mb2_tatooine.pk3 - 71E01B31BE73B69E47284DCDFCF7FC67 OK
FILE CHECKING: 52 MBII/mb2_theed.pk3 - BA2ED9B0B3319E5AAF94493B94EB203B OK
FILE CHECKING: 53 MBII/mb2_tradefed.pk3 - 3644FB43919E8D8546A6A2E26EF95142 OK
FILE CHECKING: 54 MBII/mb2_um_assets2.pk3 - 9347886EA6C6B69B553070385708C29A OK
FILE CHECKING: 55 MBII/mb2_um_assets3.pk3 - 80128660D5A487951488D47BFF154C5B OK
FILE CHECKING: 56 MBII/mb2_um_assets.pk3 - CFCE066D95AF1F8FDF3BA295D3A37799 OK
FILE CHECKING: 57 MBII/MB2_yavinassault.pk3 - 16E4A1D0B12D5D9DA4512EABBE48D51A OK
FILE CHECKING: 58 MBII/forcecfg/blue/BH/Specialist.fcf - C0DFC94F4FE26678A562C991FB3B992E OK
FILE CHECKING: 59 MBII/forcecfg/blue/BH/Default.fcf - 2A229DAC8168F8F30A8816B99D452307 OK
FILE CHECKING: 60 MBII/forcecfg/blue/BH/Assault.fcf - 2B647B5C3AC50FC3C54C884F40E41F29 OK
FILE CHECKING: 61 MBII/forcecfg/blue/soldier/Default.fcf - 2EC21A932B467BD446B6085781FAB26A OK
FILE CHECKING: 62 MBII/forcecfg/blue/soldier/Versatile.fcf - 2CBFD962A012B9E4802F2ADB66DB3822 OK
FILE CHECKING: 63 MBII/forcecfg/blue/soldier/Assault.fcf - 7F0283A406D3B9F053E551837D9D9C7A OK
FILE CHECKING: 64 MBII/forcecfg/blue/manda/Specialist.fcf - ADD6A10540C93AE45D011C364382DC6B OK
FILE CHECKING: 65 MBII/forcecfg/blue/manda/Default.fcf - E17DBEC9C798F136CCA8F5843F014807 OK
FILE CHECKING: 66 MBII/forcecfg/blue/manda/Assault.fcf - 734FAE030FE849247B16619CCA5D45B1 OK
FILE CHECKING: 67 MBII/forcecfg/blue/SBD/Specialist.fcf - 50720BEA1B1C7E586573B8F85991AC27 OK
FILE CHECKING: 68 MBII/forcecfg/blue/SBD/Default.fcf - EDA21E04BAF0F52C7B8F7D71C40A18D9 OK
FILE CHECKING: 69 MBII/forcecfg/blue/SBD/Assault.fcf - 7A4159ACE8103218F8A878E403F0B3D4 OK
FILE CHECKING: 70 MBII/forcecfg/blue/sith/Specialist.fcf - 03BFCA37241B414F771CEBC2E6F46BB1 OK
FILE CHECKING: 71 MBII/forcecfg/blue/sith/Default.fcf - B41EC43CFFE540C6F55116E471B198B9 OK
FILE CHECKING: 72 MBII/forcecfg/blue/sith/Assault.fcf - 6EB443DCCE02E6A81555D23E73419768 OK
FILE CHECKING: 73 MBII/forcecfg/blue/commander/Default.fcf - BD26A44EC2F6B34BA3AEFF4BBA3A676D OK
FILE CHECKING: 74 MBII/forcecfg/blue/commander/Versatile.fcf - 3DCF3E526A9E399DB1C17981AEF5BE02 OK
FILE CHECKING: 75 MBII/forcecfg/blue/commander/Assault.fcf - 1F0371F5168799A177084B76BD3C0562 OK
FILE CHECKING: 76 MBII/forcecfg/blue/deka/Specialist.fcf - 4AC07CB1E511EF2C6525C6BA89E65D58 OK
FILE CHECKING: 77 MBII/forcecfg/blue/deka/Default.fcf - A331469E7AC9FAE06B808E9197FFDDB9 OK
FILE CHECKING: 78 MBII/forcecfg/blue/deka/Versatile.fcf - 53FF8577AEF7B2165887B7E223B1B431 OK
FILE CHECKING: 79 MBII/forcecfg/red/soldier/Default.fcf - CFC15972D56E2C2AA0124B7653DF8B16 OK
FILE CHECKING: 80 MBII/forcecfg/red/soldier/Versatile.fcf - 7376C6D792386FCE9E3D7F057E355511 OK
FILE CHECKING: 81 MBII/forcecfg/red/soldier/Assault.fcf - 2BD7396A6CDE9BCBB3A418A986AA59D4 OK
FILE CHECKING: 82 MBII/forcecfg/red/clone/Specialist.fcf - D98E0AAE1B8B2235BD50DA5B58243731 OK
FILE CHECKING: 83 MBII/forcecfg/red/clone/Default.fcf - C64BD0257181579A47C42C38BCB6DB17 OK
FILE CHECKING: 84 MBII/forcecfg/red/clone/Assault.fcf - CAA7E253B97C41BA66DE471DFA65C756 OK
FILE CHECKING: 85 MBII/forcecfg/red/wookiee/Specialist.fcf - 09E5463A860340C35AD56A4B209D74BC OK
FILE CHECKING: 86 MBII/forcecfg/red/wookiee/Default.fcf - 427E51921DA99F8588AF566D4A3D72FF OK
FILE CHECKING: 87 MBII/forcecfg/red/wookiee/Assault.fcf - 7B49C9FFA0CF1E3ED8E5A4FFAA418AA3 OK
FILE CHECKING: 88 MBII/forcecfg/red/jedi/Specialist.fcf - 220E324E36A7FECE27100487FD6413E1 OK
FILE CHECKING: 89 MBII/forcecfg/red/jedi/Default.fcf - E70562CF2A95498591ECD303585BEA38 OK
FILE CHECKING: 90 MBII/forcecfg/red/jedi/Assault.fcf - AFE1917295E070E3EC27622DB3A4B42F OK
FILE CHECKING: 91 MBII/forcecfg/red/arc/Specialist.fcf - DEE0512291446D0BFA02F5B86922FE41 OK
FILE CHECKING: 92 MBII/forcecfg/red/arc/Default.fcf - FA60FC1663A00D86896FBEE6F095C312 OK
FILE CHECKING: 93 MBII/forcecfg/red/arc/Assault.fcf - 552ADDC618B34CB571E23DF8E5F53BFB OK
FILE CHECKING: 94 MBII/forcecfg/red/hero/Pistol.fcf - C586A0E425A5EC89991691EBF111F19C OK
FILE CHECKING: 95 MBII/forcecfg/red/hero/Specialist.fcf - 0599D6A6F3DF15BB442C7E8FCAA317E2 OK
FILE CHECKING: 96 MBII/forcecfg/red/hero/Default.fcf - 1DB3B8485A1B1B18FE91834A70949CDA OK
FILE CHECKING: 97 MBII/forcecfg/red/hero/Assault.fcf - 8EF0C60CB7940432806A01A4A154344D OK
FILE CHECKING: 98 MBII/forcecfg/red/commander/Default.fcf - BB0055BF44BC055663D8D2F74AE11BA7 OK
FILE CHECKING: 99 MBII/forcecfg/red/commander/Versatile.fcf - C6987523C3CDEBBF9B0B60A846408C37 OK
FILE CHECKING: 100 MBII/forcecfg/red/commander/Assault.fcf - FCD0F5031E848E15836B9D88F8D7F743 OK
FILE CHECKING: 101 MBII/server_config_default.cfg - E491511B3EE2DEC80CA047ED8863949B OK
FILE CHECKING: 102 MBII/campaignrotation.mbcr - F824F1E40D71955508521DFFF7B7E7F8 OK
FILE CHECKING: 103 MBII/oldtrilogy.mb2c - 01D5AE197665C428119AECDF8ABE7943 OK
FILE CHECKING: 104 MBII/prequels.mb2c - 6F354F07BD22194E8EA92A261FE3718F OK
FILE CHECKING: 105 MBII/jampgame.pdb - ABF02B0FE11913DB646F684B70772F52 OK
FILE CHECKING: 106 MBII/mb2_newicons.ico - B369FA4B001CA48971230169D0DF1DDB OK
FILE CHECKING: 107 MBII/mb2_um Map List.txt - 41CE6365C2720FED3998986950F65DA8 OK
FILE CHECKING: 108 MBII/MBII Credits.pdf - 33DDB027C15DB4C6D612B23EB634D6AA OK
FILE CHECKING: 109 MBII/MBII Maps-Models Credits.txt - 63C6B0643DED6F7B32D7273F8C1398D2 OK
FILE CHECKING: 110 MBII/MBII Readme.html - 790A070F838A3F16CD2105850C437A47 OK
FILE CHECKING: 111 MBII/OJP_readme.txt - 76F311C5408AD146D9297503B0B17077 OK
FILE CHECKING: 112 MBII/OpenJK Readme.txt - 213CC4A60A444D135452A1386EEB81A7 OK
FILE CHECKING: 113 MBII/version.info - 17B7FFB6CC1F3588D20DDA49FFB651F0 OK
FILE CHECKING: 114 mbii.x86.exe - C5F488CC5FE168BECAD9C998176F714A OK
FILE CHECKING: 115 rd-vanilla-mbii_x86.dll - 29D0B45EF4C33ADD2C69C523A02DAFA7 OK
FILE CHECKING: 116 SDL2.dll - AE58662A16410481B477B78B8D47460B OK
FILE CHECKING: 117 Play_MBII.bat - E662EC4C5CABC6844131A02D05DE248D OK
FILE CHECKING: 118 Play_MBII_CustomOJK.bat - CA707ECDC3C4B33DC28E4D85835CFADB OK
FILE CHECKING: 119 mmeMBII/cgamex86.dll - 640C7278FDD1E73B6B758987141A0DE2 OK
FILE CHECKING: 120 mmeMBII/demos/put_MBII_demos_here - D41D8CD98F00B204E9800998ECF8427E OK
FILE CHECKING: 121 mmeMBII/uix86.dll - B0821414348FAF5AC27372FCD74947D6 WRONG CHECKSUM - LOCAL = 8191C44B176060EED2B5A5AF0F4F84D4
FILE CHECKING: 122 Get jaMME.txt - A8071E82C31B5BC39B59DC44625A2E7C OK
FILE CHECKING: 123 RTVRTM.zip - 80D5ABB7EB756845FC450168EF5BC74D OK

Segment Registers:
CS: 0x0000001B, DS: 0x00000023, ES: 0x00000023
FS: 0x0000003B, GS: 0x00000000, SS: 0x00000023
-----------------------------------
Call Stack Trace
-----------------------------------
OJK93D3.tmp(vmMain+0x2B04C) [0x2C48026C]
OJK93D3.tmp(dllEntry+0x2238201) [0x2E6BED11]
mbii.x86.exe(dllEntry+0x3FAD934) [0x30434444]

 

[ent]

The crash log is not completed. There is missing Call stack.

 

[Chaos the Chaotic]

So how does it crash again?

Level 2 force sense? Any other times? Level 2 is when you can visually see player models through walls.
My performance typically takes a bit of a hit depending on amount and proximity due to having glow on and a crappy computer.
Same thing when I'm in Gen with a ton of saber users...

Could be ur card just dying out I have to manually start mine with a paper clip, the little fan doesnt start to spin otherwise
Haven't had a blue screen in 1 year! It's important to wrap the paperclip with some paper. In case it sparks again.

 

[Enette]

Thank you for answers ent and Chaos the Chaotic.
When it comes to crash log I checked the file if I missed some part, but I am sure there was nothing more.
It could not happen by accident that I edited the file as it wasn't even once, so that is how it looks like.

The thing about sense. The same was happening with level 3. I noticed that the radar in the right upper corner looks now different than in previous version.
When it is activated there is no recognition of enemy and ally color. I still see enemies but there is no differentiation. And as I mentioned, sometimes crash happened in the first round of game, sometimes later. There was no regular occurence.
My PC is old and you might be right about graphic card, it is integrated one, though everything always worked fine in such old games.

 

[Chaos the Chaotic]

Open your launcher, go to Settings on the bottom left, where it says engine - switch it to jamp.

It sounds like you were using the classic jamp version and the update screwed/messed something up and switched the engine to mbclient/openjk.

One of the differences between the two is that mbclient doesn't have color differentials on the radar between ally/enemy.
And usually your config gets messed up. Mine got completely wiped switching between them.

Other notable differences is that mbclient/openjk supposedly give you a performance boost...I guess for people with newer pcs this is a plus.
So it might be people with older models should stick to jamp.

Regardless, the launcher sucks. You hear me Devs! It is a bug infested colony of annoyed wonderment.

Once you switch to jamp, test it out, see if you crash.
Just remember to check your config and fx settings.
And don't forget to redo the whole:

/rate
/com_maxfps
/cl_maxpackets
/snaps

Stuff.

Good luck and may the force be with you. I have channeled my inner dork. But its ok.
If not here, then where!?

 

[ent]

And usually your config gets messed up. Mine got completely wiped switching between them.

MBII Client loads openjk.cfg from My Documents(etc), jamp - jampconfig.cfg from GameData/MBII.

Other notable differences is that mbclient/openjk supposedly give you a performance boost

No any boost at all.

When it comes to crash log I checked the file if I missed some part, but I am sure there was nothing more.
It could not happen by accident that I edited the file as it wasn't even once, so that is how it looks like.

Just crash once again and show a new crash log?

 

[Enette]

Okay, so I tried to do what you adviced. Rate, maxpackets and so on were set to default.
Like I wrote in the first post, it wasn't possible to even enter any server on jamp option.
This is what I see every time( look at the picture below). It's possible to play only when I change to mbclient, but as we know at that time occurs sense problem.
I also want to mention that I start mb launcher as administrator, compatibility is set for Windows XP as well.

I paste two crash logs.

===================================
JKA Movie Battles II Crash Log
===================================
Process File Name: C:\Games\Jedi Academy\GameData\mbii.x86.exe
Module File Name: OJK93D3.tmp
Exception Code: 0xC0000005 (Access Violation)
Exception Address: 0x2C48026C (OJK93D3.tmp+0x7026C)

-----------------------------------
Register Dump
-----------------------------------
General Purpose & Control Registers:
EAX: 0x00000001, EBX: 0x2C4EE850, ECX: 0x462ADCBE
EDX: 0x00152814, EBP: 0x2C4DDA82, EDI: 0x3AD2DDC0
EIP: 0x2C48026C, ESI: 0x3AD2DDC0, ESP: 0x0015286C

Segment Registers:
CS: 0x0000001B, DS: 0x00000023, ES: 0x00000023
FS: 0x0000003B, GS: 0x00000000, SS: 0x00000023

-----------------------------------
Call Stack Trace
-----------------------------------
OJK93D3.tmp(vmMain+0x2B04C) [0x2C48026C]
OJK93D3.tmp(dllEntry+0x2238201) [0x2E6BED11]
mbii.x86.exe(dllEntry+0x3FAD934) [0x30434444]

===================================
JKA Movie Battles II Crash Log
===================================
Process File Name: C:\Games\Jedi Academy\GameData\mbii.x86.exe
Module File Name: OJK645B.tmp
Exception Code: 0xC0000005 (Access Violation)
Exception Address: 0x50B1026C (OJK645B.tmp+0x7026C)

-----------------------------------
Register Dump
-----------------------------------
General Purpose & Control Registers:
EAX: 0x00000001, EBX: 0x50B7E850, ECX: 0xE4B398BB
EDX: 0x002625F4, EBP: 0x50B6DA82, EDI: 0x4681DDC0
EIP: 0x50B1026C, ESI: 0x4681DDC0, ESP: 0x0026264C

Segment Registers:
CS: 0x0000001B, DS: 0x00000023, ES: 0x00000023
FS: 0x0000003B, GS: 0x00000000, SS: 0x00000023

-----------------------------------
Call Stack Trace
-----------------------------------
OJK645B.tmp(vmMain+0x2B04C) [0x50B1026C]
OJK645B.tmp(dllEntry+0x2238201) [0x52D4ED11]
mbii.x86.exe [0x30434444]

 

[Puppytine]

This is what I see every time( look at the picture below).

Interesting... when you run mb2 via jamp, it says your version is outdated, but the log above clearly shows that your MBII installation is 1.4.2:

INFO: Found version info file > 1.4.2

And you can join servers through MBII Client...

Make sure you DON'T have a file "C:\Games\Jedi Academy\GameData\uix86.dll".
If there is such file, remove it.
Launch Movie Battles using jamp once again.

Also try:
Move file "C:\Games\Jedi Academy\GameData\MBII\jampconfig.cfg" to some unrelated folder, or delete it.
Launch MBII via jamp once again.

 

[Chaos the Chaotic]

MBII Client loads openjk.cfg from My Documents(etc), jamp - jampconfig.cfg from GameData/MBII.

No any boost at all.

Just crash once again and show a new crash log?

Not a boost maybe but defintely some upgrades. I remember reading the thread that identified some key differences and from what I recall openjk/mbclient offered some minor improvements to visuals.

So ENT, I deny you! Repent ye wicked sinner.

..........................................................................................

She should give a screenshot of her folder and filepaths tbh. It's almost like she has multiple installs that are crosswired.
I know, because, I got good instincts and in tech. that's all you need.
Not some ridiculous background in coding or speaking foreign languages like Commoncore +!

 

[Enette]

Make sure you DON'T have a file "C:\Games\Jedi Academy\GameData\uix86.dll".
If there is such file, remove it.
Launch Movie Battles using jamp once again.

I found uix86.dll file in base and MBII folder, jampconfig.cfg in base. There is also a similiar file jaconfig.cfg, I moved it to other folder too.

Move file "C:\Games\Jedi Academy\GameData\MBII\jampconfig.cfg" to some unrelated folder, or delete it.
Launch MBII via jamp once again.

I hope I understood that correct..
Tried to launch game game through jamp, but it's still the same.

She should give a screenshot of her folder and filepaths tbh. It's almost like she has multiple installs that are crosswired.

Do you mean such screeshot?

 

[Puppytine]

I found uix86.dll file in base and MBII folder

Are you sure you don't have a file "C:\Games\Jedi Academy\GameData\uix86.dll"?

Delete then uix86.dll from those both folders and try launching mb2 with jamp again.

If that won't help:
I've attached a file to this post, and this is what you have to do:

1. Download that file
2. Unpack it into "C:\Games\Jedi Academy\GameData"
3. Start Movie Battles using jamp
4. Run "MBII.vbs"
5. Wait till a message box appears
6. Upload a file "My Documents\MBII diag mods.txt" to this thread

 

[Chaos the Chaotic]

Polish technical terms, my weakness.
Next to medical terms.

 

[Enette]

If I could change it to English, I would surely do that for you

I downloaded MBII.vbs, but it has no txt extension. Still made it to vbs again format and placed in gamedata.
Started MB launcher with jamp and opened MBII.vbs but it's still txt file. Strange.
Besides there is no MB diag.mods.txt file in My Documents, and I swear there was never such thing on my PC

 

[Puppytine]

I downloaded MBII.vbs, but it has no txt extension. Still made it to vbs again format and placed in gamedata.
Started MB launcher with jamp and opened MBII.vbs but it's still txt file. Strange.

It has .txt extension, but due your Windows' settings that extension simply isn't showing.
And I see on your screenshot .exe extensions are hidden as well.
You should turn on displaying all extensions:
https://support.microsoft.com/kb/865219

But in case you won't change that setting, I've uploaded the script inside of zip archive and updated my previous post.

Besides there is no MB diag.mods.txt file in My Documents, and I swear there was never such thing on my PC

Indeed you don't have that file, it's created by my script.
After script finishes working, "MB diag.mods.txt" will appear in "My Documents".
It will have an important information about your mb2 installation.

Also, there is an easier way:

1. Launch Movie Battles using jamp
2. Start => Run => msinfo32 => System Summary => Software Environment => Loaded Modules
3. Find uix86.dll
4. Make a screenshot of full path of uix86.dll and post it here

 

[Enette]

Firstly sorry about late response. I wasn't online recently.
Secondly I managed to work out the both described ways. It seemed to be difficult but after a while I made it.
So, here are two files. I haven't found uix86 in the loaded modules somehow.
By the way, today I had a chance to install JA and MBII on other computer and it worked without any problems.
So now it can be said that it is definitively my PC's poblem.

 

[Puppytine]

I haven't found uix86 in the loaded modules somehow.

Indeed you didn't, because you were supposed to start Movie Battles and only AFTER THAT run script and/or make a screenshot, as it's said in my previous reply.
Apparently, MBII weren't running when you opened Modules tab in msinfo, so there was no uix86 in the list.
"MBII diag mods.txt" doesn't have any information about modules as well (only files).

So I suggest:

1. Launch Movie Battles using jamp
2. Keep it running
3. Start the script once again
4. Do not close MBII
5. Make a screenshot of Modules page
6. Post that screenshot and new log file here

Also,

1. Start Movie Battles
2. Open a console by pressing Shift + ~ (aka Shift + `)
3. Type:

   /condump l.txt

4. Upload "C:\Games\Jedi Academy\GameData\MBII\l.txt" to this thread