Jump to content

[WIN/MAC/LINUX] KSP Trajectory Optimization Tool v1.6.10 [Major LVD Improvements!]


Recommended Posts

  On 5/19/2016 at 12:49 PM, awang said:

Would it be possible to compile a prerelease executable for OS X?

Expand  

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: 

 

Link to comment
Share on other sites

  On 5/19/2016 at 2:22 AM, 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?

Expand  

Yes, you are correct!  Start the maneuver at the time indicated by the node. 

Link to comment
Share on other sites

  On 5/19/2016 at 1:03 PM, 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: 

 

Expand  

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!

Link to comment
Share on other sites

  On 5/19/2016 at 1:43 PM, 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!

Expand  

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. 

Link to comment
Share on other sites

  On 5/19/2016 at 1:03 PM, 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: 

 

Expand  

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.

Link to comment
Share on other sites

  On 5/19/2016 at 6:53 PM, 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.

Expand  

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.

Link to comment
Share on other sites

  On 5/19/2016 at 9:02 PM, 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.

Expand  

You're the first report I've had since releasing it.  Can I see the KSP TOT log file?

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

  On 5/19/2016 at 9:02 PM, 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.

Expand  

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 by awang
Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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?

Link to comment
Share on other sites

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 by awang
Link to comment
Share on other sites

  On 5/19/2016 at 11:19 PM, 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?

Expand  

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...

Link to comment
Share on other sites

  On 5/19/2016 at 11:40 PM, 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

Expand  

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 by awang
Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...