Replies: 7 comments 7 replies
|
Convenient CKAN file generated from the Log: WannabeKerbal.ckan.zip |
0 replies
|
I installed the CKAN file generated on the previous post, except Principia - I doubt it would be causing any trouble and I never managed to run it on my MacPotato anyway. It's a pristine KSP 1.12.5 installment, without savegames, previous logs, thumbs, physics, partdatabase, settings and that runtime generated jazz. It also have both DLCs installed (MH and Serenity). Follows the dataset for this first run - I just reached the Main Men and quit the game before copying the logs. (late night - analysis is a fight for another day) |
0 replies
|
First problem: But I have the latest Mono (6.12) installed! https://www.mono-project.com/download/stable/#download-ma Not sure about what to do now. |
4 replies
|
JESUS FSCKING CHRIST. The path is being built wrongly
The correct path is Workaround: |
|
Crap. Still got the message, but now I'm sure the pathname is reachable. |
|
Oukey, now trying another stunt. Created a executable script called And now edit #!/bin/sh
MYPATH=$(dirname $0)
/Library/Frameworks/Mono.framework/Commands/mono ${MYPATH}/bcl.bin "$@"
Testing the thing: |
|
SUCCESS. At least Burst is now working on my rig! |
|
Now with a "cleaner" log without potential Exceptions thrown by the the lack of a Working Burst, I can trust the missing Assemblies exceptions. Since there's no B9PS neither Waterfall installed on this rig right now, I'm removing these packages. |
0 replies
|
Now with a "cleaner" log without potential Exceptions thrown by the the lack of a Working Burst, I can trust the missing Assemblies exceptions. Since there's no B9PS neither Waterfall installed on this rig right now, I'm removing these packages. |
0 replies
|
Oukey. Now I have something reliable to work with - without the KSP Burst borking (and, then, I don't know in which situation anything relying on it would be), and without the First thing I detected: since I concocted a CKAN file and used it to start up a test bed for this task, all the dependencies were automatically installed, and I (finally, I could had detected it sooner to tell you the truth) that WannabeKerbal's log is missing the 
Since the user is installing things manually, they surely had missed this. This also explains why MechJeb2 is borking in his rig and not on mine: 
Next step is to suggest the user to install |
1 reply
|
Or not... I just realized that my test bed have 
Hummm... I should had installed it by accident, perhaps? Anyway, uninstalled it and rebuilding the log. |
|
Oukey, new logs. |
2 replies
|
Bleh. The MJ2 Exception didn't happened on my test bed. 
Trying to figure out what could be causing it... |
|
For reference, full Exception from the user's log |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
NOTE TO MY FUTURE SELF
This is unrelated to Modular Management. I'm doing it here because as I need somewhere to do it, and this sounded the less wrong place. :)
See https://forum.kerbalspaceprogram.com/topic/228588-errors-in-rorssprincipia-saves-not-sure-if-okay-to-have-them/#findComment-4477043
Log: KSP.log1(2).zip
All reactions