salajander Posted May 19, 2016 Share Posted May 19, 2016 11 minutes ago, awang said: Would it be possible to compile a prerelease executable for OS X? Someone with access to MATLAB for OS X needs to do this, and no one has been able to for some time. You can, however, run the latest builds (I haven't tested 1.5.4 prerelease) using WINE. See my post here: Quote Link to comment Share on other sites More sharing options...
Arrowstar Posted May 19, 2016 Author Share Posted May 19, 2016 10 hours ago, DivisionByZero said: Quick question regarding the finite time burns: I'm guessing that because the length of time is taken into account already, that the burn in-game should begin at t=0 for the maneuver. That is, one shouldn't split the burn before and after the node? Is that correct? Yes, you are correct! Start the maneuver at the time indicated by the node. Quote Link to comment Share on other sites More sharing options...
awang Posted May 19, 2016 Share Posted May 19, 2016 33 minutes ago, salajander said: Someone with access to MATLAB for OS X needs to do this, and no one has been able to for some time. You can, however, run the latest builds (I haven't tested 1.5.4 prerelease) using WINE. See my post here: Hmmm... Would a student version of MATLAB work? I don't have it at the moment, but I may be able to obtain access to one. I'll give WINE a shot. Thanks! Quote Link to comment Share on other sites More sharing options...
Arrowstar Posted May 19, 2016 Author Share Posted May 19, 2016 1 hour ago, awang said: Hmmm... Would a student version of MATLAB work? I don't have it at the moment, but I may be able to obtain access to one. I'll give WINE a shot. Thanks! If you're just running it yourself from source code, student version should work. I don't think you'll be able to compile on that though. Could be wrong though. Quote Link to comment Share on other sites More sharing options...
awang Posted May 19, 2016 Share Posted May 19, 2016 5 hours ago, salajander said: Someone with access to MATLAB for OS X needs to do this, and no one has been able to for some time. You can, however, run the latest builds (I haven't tested 1.5.4 prerelease) using WINE. See my post here: Not sure if I'm doing something wrong... But it seems WINE doesn't support 64-bit executables on OS X, and attempting to run TOT throws back a "Bad EXE format for <path_to_TOT>. And from what I read, 64-bit support will probably never come. I installed WINE using Homebrew, so I'm hoping that the install isn't the issue. Quote Link to comment Share on other sites More sharing options...
salajander Posted May 19, 2016 Share Posted May 19, 2016 2 hours ago, awang said: Not sure if I'm doing something wrong... But it seems WINE doesn't support 64-bit executables on OS X, and attempting to run TOT throws back a "Bad EXE format for <path_to_TOT>. And from what I read, 64-bit support will probably never come. I installed WINE using Homebrew, so I'm hoping that the install isn't the issue. No idea - I installed WINE Staging directly from https://www.winehq.org/download, and KSPTOT 1.5.1 works just fine with 64-bit. I'm running wine 1.9.8. @Arrowstar Have you had other report success with 1.5.4? I'm getting a "Could not successfully parse URI string." dialog at launch, before the KSPTOT splash screen. I fully expect this is something weird with WINE, but figured I'd check anyway. Quote Link to comment Share on other sites More sharing options...
Arrowstar Posted May 19, 2016 Author Share Posted May 19, 2016 10 minutes ago, salajander said: No idea - I installed WINE Staging directly from https://www.winehq.org/download, and KSPTOT 1.5.1 works just fine with 64-bit. I'm running wine 1.9.8. @Arrowstar Have you had other report success with 1.5.4? I'm getting a "Could not successfully parse URI string." dialog at launch, before the KSPTOT splash screen. I fully expect this is something weird with WINE, but figured I'd check anyway. You're the first report I've had since releasing it. Can I see the KSP TOT log file? Quote Link to comment Share on other sites More sharing options...
salajander Posted May 19, 2016 Share Posted May 19, 2016 It's empty, 0-length. And judging by the time stamp, it's not even from this run. I suspect something's going south with MCR, perhaps? The installer for R2015b, MCR_R2015b_win64_installer.exe, claimed to be successful. Quote Link to comment Share on other sites More sharing options...
Arrowstar Posted May 19, 2016 Author Share Posted May 19, 2016 Huh. Are you running on Windows or OSX? Quote Link to comment Share on other sites More sharing options...
salajander Posted May 19, 2016 Share Posted May 19, 2016 I'm running it on OS X under WINE Quote Link to comment Share on other sites More sharing options...
Arrowstar Posted May 19, 2016 Author Share Posted May 19, 2016 2 minutes ago, salajander said: I'm running it on OS X under WINE Ah okay. Yeah, it's hard to say. Do you have a way to run it on Windows and see if you get the same error? Quote Link to comment Share on other sites More sharing options...
salajander Posted May 19, 2016 Share Posted May 19, 2016 Not really. I'll see if I can rustle something up. Quote Link to comment Share on other sites More sharing options...
awang Posted May 19, 2016 Share Posted May 19, 2016 (edited) 1 hour ago, salajander said: No idea - I installed WINE Staging directly from https://www.winehq.org/download, and KSPTOT 1.5.1 works just fine with 64-bit. I'm running wine 1.9.8. I got it! Sort of... Actually got the exact same error, except TOT exited immediately afterwards. For Arrowstar: Also running under OS X on WINE. Edited May 19, 2016 by awang Quote Link to comment Share on other sites More sharing options...
Arrowstar Posted May 19, 2016 Author Share Posted May 19, 2016 3 minutes ago, awang said: I got it! Sort of... Actually got the exact same error, except TOT exited immediately afterwards. For Arrowstar: Also running under OS X on WINE. Anything in the ksptot.log file? Quote Link to comment Share on other sites More sharing options...
awang Posted May 19, 2016 Share Posted May 19, 2016 No log is produced. Looks like the problem may be on my end, though (this shows up when WINE is run through its terminal): wine: Call from 0x7b43b75a to unimplemented function msvcr110.dll.??0event@Concurrency@@QEAA@XZ, aborting Which is weird, because I *literally* just installed the VS 2012 redistributable. Quote Link to comment Share on other sites More sharing options...
awang Posted May 19, 2016 Share Posted May 19, 2016 Well, turns out it *is* implemented, but as a stub function: https://source.winehq.org/WineAPI/msvcr110.html Aaaaand the current development version of WINE crashes with an unhandled exception. Wonderful. Backtrace is here: https://www.dropbox.com/s/h3fnof4686k70xf/backtrace.txt?dl=0 Not sure how useful it might be. The top of the stack seems to be code in TOT? Quote Link to comment Share on other sites More sharing options...
Arrowstar Posted May 19, 2016 Author Share Posted May 19, 2016 4 minutes ago, awang said: The top of the stack seems to be code in TOT? It's a fairly large file, which function call is that? Quote Link to comment Share on other sites More sharing options...
awang Posted May 19, 2016 Share Posted May 19, 2016 (edited) Sorry, that dump was pretty much it. There's this line from the terminal: wine: Unhandled exception 0xc06d007e in thread 53 at address 0x7b43b1aa (thread 0053), starting debugger... There's a second log here: https://www.dropbox.com/s/4m0d4ykg96g0urp/backtrace2.txt?dl=0 But I doubt it'll provide any new info. I just realized it's almost exactly the same as the first, so it won't help at all. Was the TOT prerelease compiled with debug symbols? Edited May 19, 2016 by awang Quote Link to comment Share on other sites More sharing options...
Arrowstar Posted May 19, 2016 Author Share Posted May 19, 2016 1 minute ago, awang said: Sorry, that dump was pretty much it. There's this line from the terminal: wine: Unhandled exception 0xc06d007e in thread 53 at address 0x7b43b1aa (thread 0053), starting debugger... There's a second log here: https://www.dropbox.com/s/4m0d4ykg96g0urp/backtrace2.txt?dl=0 But I doubt it'll provide any new info. Was the TOT prerelease compiled with debug symbols? Thanks. Yeah, doesn't help much but thanks for providing it. Unfortunately you can't compile MATLAB applications with debug symbols as far as I know. I can investigate though... Quote Link to comment Share on other sites More sharing options...
awang Posted May 19, 2016 Share Posted May 19, 2016 Looks like you just need to pass a -g flag to the compiler? Quote Link to comment Share on other sites More sharing options...
Arrowstar Posted May 19, 2016 Author Share Posted May 19, 2016 16 minutes ago, awang said: Looks like you just need to pass a -g flag to the compiler? Right you are! Here's a version compiled with the -g flag. Tell me how it works out for you: https://dl.dropboxusercontent.com/u/29126891/KSPTOT_v154_prerelease1_debug.zip Quote Link to comment Share on other sites More sharing options...
awang Posted May 20, 2016 Share Posted May 20, 2016 (edited) 34 minutes ago, Arrowstar said: Right you are! Here's a version compiled with the -g flag. Tell me how it works out for you: https://dl.dropboxusercontent.com/u/29126891/KSPTOT_v154_prerelease1_debug.zip No difference, unfortunately. Looks like the WINE debugger can't read those symbols... Only thing I can think of now is to look at the disassembly to figure out the offsets, but that's hardly fun stuff. Not to mention I'm not sure if it's treating TOT as one giant executable, in which case those offsets would be worse. Found the WINE debugging page, so I'll be trying for more detailed logs and/or the WINE debugger itself. Edited May 20, 2016 by awang Quote Link to comment Share on other sites More sharing options...
awang Posted May 20, 2016 Share Posted May 20, 2016 Full logs: https://www.dropbox.com/s/ya7d3pzz7k0frta/ksp_tot_full_logs.txt?dl=0 I'll be taking a look at the debugger too, see if I can't get more info Quote Link to comment Share on other sites More sharing options...
Arrowstar Posted May 20, 2016 Author Share Posted May 20, 2016 6 minutes ago, awang said: Full logs: https://www.dropbox.com/s/ya7d3pzz7k0frta/ksp_tot_full_logs.txt?dl=0 I'll be taking a look at the debugger too, see if I can't get more info Right, thanks! Quote Link to comment Share on other sites More sharing options...
awang Posted May 20, 2016 Share Posted May 20, 2016 Shorter version of the logs here:https://www.dropbox.com/s/k9s1z2i6blzxcri/ksp_tot_relay_logs.txt?dl=0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.