1.     Please make sure you check the Support FAQ and relevant Guides before you create a new thread in this section!

Technical Issue What happened to... OpenJK?

Discussion in 'Support' started by Ahsoka Tano, Jun 1, 2018.

  1. Ahsoka Tano

    Ahsoka Tano

    Posts:
    23
    Likes Received:
    0
    Now i have Steam version. Should i place that (incorrectly worked) files to the JKA folder or better just to download new ones? I am interested in what will happen...
     
  2. Puppytine

    Puppytine Slayed dreamer

    Posts:
    1,996
    Likes Received:
    1,285
    Better download new files using Launcher, probably.
    But make sure that you placed MBIILauncher.exe into GameData of Steam JA, AND that path in Launcher's settings is set to Steam location, not to old directory.
     
  3. Ahsoka Tano

    Ahsoka Tano

    Posts:
    23
    Likes Received:
    0
    Absolutely same...... Downloaded mb2 to Steam JKA folder, only JAMP engine is able to run and join, but, as i said many times, unplayable with such fps... "VM_CreateLegacy on ui failed" this time, not cgame.
     
  4. Ahsoka Tano

    Ahsoka Tano

    Posts:
    23
    Likes Received:
    0
    SOOOOOOOLVED

    My actions:
    (0. Downloaded Steam version)
    1. Copied uix86.dll file to "base" folder from MBII.pk3
    2. Copied uix86.dll and cgamex86.dll to "MBII" folder from MBII.pk3
    3. Started launcher
    4. In settings unchecked "Steam integration", chose MBII Engine, checked "Steam integration"
    5. "Play"
    6. Launcher deleted cgamex86.dll and uix86.dll from MBII folder, but right after that i recopied it there. The game didn't delete it second time.
    7. Chose server, joined and it works!!!


    The question is... Why game deletes these files from MBII folder itself?... I have to manually place that files there each time game deletes them... o_O

    Another problem now is switching off that auto-deleting files...
     
    Last edited: Jun 5, 2018
  5. Puppytine

    Puppytine Slayed dreamer

    Posts:
    1,996
    Likes Received:
    1,285
    I'm glad it's solved, but...
    This is very strange because dlls from "base" folder aren't supposed to be in use even in case of jamp, not to mention MBII Client.
    This is very strange because game engine is supposed to extract libraries from MBII.pk3 on its own.
    And this is strange as well because MBII Client isn't supposed to write files into "GameData\MBII".
    MBII Client unpacks dlls and place them into Windows temporary files directory.
    jamp unpacks dlls and place them into "GameData\MBII".

    What you are saying is more usual for jamp, not for OpenJK/MBII Client.
    Literally no idea.
    The issues you faced are truly weird and barely have any logical explanation.
    The possible reasons are:
    1. Broken MBII or Jedi Academy installation,
    2. Some general Windows malfunction,
    3. Anti-virus software,
    4. Computer viruses/malware.
     
    Ahsoka Tano likes this.

Share This Page