Launcher Issues with the launcher (sample way to write a thread)

[Suolakeksi]

Hello!

Long time lurker finally deciding to post on this forum. I'm having a quite peculiar issue with the mb2 launcher at the moment which makes me unable to install mb2 at all on my computer, after I decided to reinstall my whole OS to fix a couple things. The issue I'm having is that after downloading the launcher from your website (the link in the downloads page gives the old version of the launcher from some reason) and updating it, the launcher will give a NET. Framework error which I haven't been able to solve. I've provided the error log down below and all the info I can think of that could help you with diagnosing the issue.

As stated above I don't have mb2 anymore installed as I reinstalled my whole computer a couple days ago, and now I'm trying to get the the launcher to work but apparently it doesn't for some reason.

Also could the one responsible for the website please fix the launcher download link to download the latest launcher version, as there is no point in having to download a obsolete launcher that is locked and then downloading through it the latest (You won't get the error on the old launcher, but it's locked and says that you have to update the launcher to download MB2).

With my minor knowledge in coding, it looks as if the latest launcher is trying to find files for MB2, but as there are none yet it can't figure out what to do and throws an NET. Framework 3.5 error (why not use 4.5 as it's been out for ages? :O) instead of just downloading the correct file to fix the issue. The AutoUpdate.exe file is not also deleted due to the error, and the MBII_Launcher folder generates a folder called cache, but it's empty.

TL;DR - Launcher doesn't work with fresh install of win10 and 'NET. Framework'. Tries to find a file but can't, and instead gives an 'NET. Framework' error (that I've posted below).


Notes:
- I have all the .NET frameworks installed and updated
- I have all the necessary directX files installed
- File permissions are setup correctly
- No files are read-only
- Removed every single launcher file (even the ones in appdata/local)
- Reinstalled Jk3
- No my anti-virus program is not blocking it

Specs:
OS: Windows 10 Home 64-bit - Version: 1511 - Build: 10586.122
Steam installed on C: drive (128GB SSD)
All my steam games are on the D: drive (1TB Hard drive)
CPU: Intel i5-6300HQ
GPU: Intel HD 530 + Nvidia GTX 950M (2GB)

Spoiler: Picture of folder structure and error

Spoiler: Error log

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.DirectoryNotFoundException: Could not find a part of the path 'D:\Steam\steamapps\common\Jedi Academy\GameData\MBII\mbc.dat'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize)
at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding)
at System.IO.File.WriteAllText(String path, String contents, Encoding encoding)
at MB2Launcher.LauncherMainF.updateMBCdat(String value, Boolean usemd5)
at MB2Launcher.LauncherMainF.FuncOnStart()
at MB2Launcher.LauncherMainF.Form1_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at MB2Launcher.LauncherMainF.WndProc(Message& keyPressed)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
MBIILauncher
Assembly Version: 2.0.0.0
Win32 Version: 2.0.0.0
CodeBase: file:///D:/Steam/steamapps/common/Jedi%20Academy/GameData/MBIILauncher.exe
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8681 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8679 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Core
Assembly Version: 3.5.0.0
Win32 Version: 3.5.30729.8693 built by: QFE
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Thanks in advance, and I hope we get this annoying issue solved so that anyone who gets this error in the future can also get it fixed

EDIT: Fixed the TL;DR to be better

 

[Puppytine]

Yeah, I just renamed my MBII folder and got same error.
So solution is simple: create MBII directory inside GameData directory, run Launcher again.

why not use 4.5 as it's been out for ages? :O

4.5 isn't available for Windows XP.

 

[Suolakeksi]

Yeah, I just renamed my MBII folder and got same error.
So solution is simple: create MBII directory inside GameData directory, run Launcher again.

4.5 isn't available for Windows XP.

Well I'll be damned, making the directory fixed the issue instantly. Still confused how that could fix it when it still needed the mbc.dat file as stated in the error, but thanks for the help

But why would anyone still use windows XP? It doesn't have almost any support, modern programs don't run (well at least) on it and the user friendly parts it had in the past aren't anymore there :O

Btw nice video you have linked in your signature, too bad nightwish isn't the same as it was back then :3

EDIT: small typo

 

[Suolakeksi]

Moving the prefix back as not solved (tested it on another computer and as I haven't seen any response from the devs to this issue), as the launcher will still bug for any new players or anyone who is doing a fresh reinstall of MB2/JK3. This is a bug that should be fixed quite quickly in my opinion to avoid losing any new players, as they won't know that they have to create a folder in gamedata called MBII to get it to work.

Easiest solution for this is to change the launcher to auto create the MBII folder and the issue will be fixed.

 

[LoU]

There is new launcher version with fix applied (news section).

Also sorry for late response.

Offtopic but ontopic:
This is the best thread in this section. I want it sticky, this is how everyone in the world should troubleshoot before posting any thread in support section.

 

[Suolakeksi]

There is new launcher version with fix applied (news section).

Also sorry for late response.

Offtopic but ontopic:
This is the best thread in this section. I want it sticky, this is how everyone in the world should troubleshoot before posting any thread in support section.

Thanks for the quick response and no problem!

And yeah, I hate it when people post about issues/errors/bugs and never supply one with enough information to be able to even figure out what's wrong with the thing and help them. Have had the issue too many times myself when running communities and servers when people have some problems, and they only scream "you suck" & "fix my problem omg" without saying what the issue even is.

 

[Fletcher Time]

Yeah, I just renamed my MBII folder and got same error.
So solution is simple: create MBII directory inside GameData directory, run Launcher again.

4.5 isn't available for Windows XP.

I know this is old, but I'm having this problem on a machine I haven't used in a while. Could you go into more detail with this? Maybe I'm misunderstanding something. This is my current GameData folder.

Spoiler

 

[Puppytine]

I know this is old, but I'm having this problem on a machine I haven't used in a while. Could you go into more detail with this? Maybe I'm misunderstanding something. This is my current GameData folder.

Spoiler

View attachment 1750

What problem do you have, exactly?
Also I cannot see MBIILauncher.exe in your GameData...

 

[Fletcher Time]

What problem do you have, exactly?
Also I cannot see MBIILauncher.exe in your GameData...

Well let's start from the beginning. So I install Movie Battles on a clean JKA and use the most recent launcher. These are the two errors that first appear.

Spoiler

I tried installing those .dll files into both System32 and into the GameData folder. After that is would read the following.

Spoiler

I looked up that error code to find multiple reasons why the application wont start. So far I have:

• Updated windows (WIN10)
• Updated DirectX
• Multiple Uninstalls/Reinstalls
• Checking installation integrity on start
• Repair Installation

I still get the same error. Any ideas?

Edit: Those .dll files I manually installed, are 64bit. Do you think getting the 32bit versions would change anything?

 

[Noob]

did you check you have the required redistributables? I think its Visual c++ 2013 correct me if im wrong.

 

[Puppytine]

Oh come on, that was disscussed so many times, use search next time
And it has nothing to do with this thread
And you need 32-bit runtime
And VC 2015, not 2013
[SOLVED] - MSVCP140.dll and VCRUNTIME140.dll are missing from your computer

 

[ent]

Edit: Those .dll files I manually installed, are 64bit. Do you think getting the 32bit versions would change anything?

The game is compiled as an x86 application and it uses only x86 modules (dlls). Get x86 VC++ 2015 Redistributables from the link above.
Also Windows 10 comes with VC++ 2015 Redistributables.

 

[Fletcher Time]

Oh come on, that was disscussed so many times, use search next time
And it has nothing to do with this thread
And you need 32-bit runtime
And VC 2015, not 2013
[SOLVED] - MSVCP140.dll and VCRUNTIME140.dll are missing from your computer

Thank you. I thought that the error code I received was the problem, and this thread seemed to cover that issue. Sorry.