csatlos

Thanks for the idea but unfortunately nothing in the event log. It did give me an idea to double-check Norton Security logs but no dice there either. I also tried uninstalling MATLAB to see if I would get the error about the runtime being missing and sure enough I did. Then when I reinstalled MATLAB, I'm back to no errors and no log entries. The only other option I can think of is to run it inside a Windows VM to see if perhaps it's something with my configuration.

I checked my environment variables (both user and system) and there is only one entry for MATLAB which is the path to the current install. Thanks anyways for the tip! Not sure what else I can try due to a lack log files.

Hi everyone, I seem to be having some issues getting KSP TOT to run. I was away for a while and was running 1.5.7 so I decided to upgrade to 1.6.3. I installed the new MATLAB runtime 2017b but whenever I try to start KSP TOT, i see a spinning cursor for about 1-2 seconds and then it disappears and the application doesn't load. A look at Windows Task Manager reveals that the process does spawn but then dies shortly thereafter each time I try to launch. A log file is created on launch but it's empty so no clues about any errors. I've tried reinstalling the runtime to no avail and have also tried v1.6.4 pre-release 3 with no luck. I'm not even sure where to start trouble-shooting due to a lack of errors and logs. Anyone have any ideas? Thanks!

Machine is Windows 10, 64-bit. Here are the steps I took to try and get it working (note I started with the MATLAB v9.0 runtime installed for TOT 1.5.7): Uninstalled Runtime v9.0; Restarted PC; Installed Runtime v9.3; Tried to run KSP TOT v1.5.10. Did not start but no errors/warnings; Uninstalled Runtime v9.3; Restarted PC; Tried to run KSP TOT v1.5.10 to see if I'd get errors that runtime was missing (I did, so that's good); Reinstalled Runtime v9.3; Restarted PC; Tried to run KSP TOT v1.5.10. Again, no errors/warnings and no message about missing Runtime (suggesting that it could find it OK??); Reinstalled old Runtime v9.0 (now both 9.0 and 9.3 installed); Restarted PC; Tried KSP TOT v1.5.7 and it works fine. Uninstalled Runtime v9.3; Gave up and came here for advice...

Has anyone else experiences issues getting KSP TOT to work after updating to the new MATLAB runtime? I was running KSP TOT 1.5.7 with MATLAB 9.0 fine but it seems no matter what I do, I can't get 1.5.10 to launch. I receive no errors or warnings; it just does nothing. I've tried reinstalling the runtime several times but no luck. I believe KSP TOT can find the runtime because if I try to run it when they're not installed, I get the expected message about not being able to find v9.3 of the runtime. The KSP TOT log file is 0 bytes so the application isn't even launching and then failing. Anyone have any ideas?

@Drew Kerman, Thanks for looking into this. Here's the ksptot.log and I've also included another the KSP game log file from the same instance that was used to get the TOT error in case you want to look at both together.

@Arrowstar, first I just wanted to thank you for a great tool and all the time you've put into it. I think I've run into some kind of bug in v1.5.8 which is preventing operation of the TOTConnect in order to get real-time data from my local machine (same one that runs the game). I originally ran into the error on KSP v1.2.2 (with RSS and Realism Overhaul plus a bunch of other mods) but I've re-tested on KSP v.1.3.0 (with a few mods, but nothing huge). I can open the MCC Real Time System UI and when I click on "Test Connect to Remote Host", I get an accurate list of vessel (which leads me to believe the plugin is correctly loaded); however, when i select a vessel and click, "Connect to Real Time System", I hear a windows error chime in the background and nothing connects. A dive into the KSP.log shows some KSPTOT Connect errors such as, "". I've links the full logs from both v1.3.0 and v1.2.2 in case it helps. I went back to KSP TOT v1.5.7 and it seems to connect OK even using the KSP TOT Connect plugin from 1.5.8 (suggesting perhaps a change to the main program and not the plugin is causing the issue).