Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detaching from a Modular Launchpads base causes the screen to go black #343

Open
Tonas1997 opened this issue Dec 12, 2021 · 3 comments
Open
Assignees
Labels

Comments

@Tonas1997
Copy link

Title. As identified here, if a capsule with an IVA configured by MAS stages from a MLP pad the screen will turn black, breaking map view as well.

@MOARdV MOARdV self-assigned this Dec 13, 2021
@MOARdV MOARdV added the bug label Dec 13, 2021
@MOARdV MOARdV added this to To Do in MAS Features / Bugs via automation Dec 13, 2021
@MOARdV
Copy link
Owner

MOARdV commented Dec 13, 2021

When you say "screen will turn black", do you mean MFD screens in IVA, or do you mean the KSP screen?
Can you post the KSP.log file, so I can see if there are hints about the failure?

@Tonas1997
Copy link
Author

Tonas1997 commented Dec 13, 2021

Sorry, I should have been more specific 😅

Here's what happens. The glitch starts occurring as soon as I stage away from the launch platform. The capsule I'm using comes from NearFutureSpacecraft and is patched by the Vexarp IVA which adds in some MAS elements.

2021-12-13.13-33-11.mp4

I was able to trace the problem to the crew access arm you see on top of the launch tower: when I removed that part, I was able to launch without any issues. This part has crew capacity and a very barebones IVA, as seen in the image below:

screenshot312

(note: I'm not sure this particular IVA is relevant to the issue, as it isn't modified by MAS as far as I know.

KSP.log comes attached in a zip file, as I had a lot of logspam caused by AvionicsSystems and the file grew too large to post elsewhere.

KSP.zip

@MOARdV
Copy link
Owner

MOARdV commented Dec 13, 2021

Okay. That helps a lot. It looks like there are a lot of exceptions upstream of MAS going nuts, so MAS is in a bad state. I can suppress the spam of exceptions pretty easily, but I suspect the MFDs will still be non-functional due to whatever is making it misbehave. Although maybe the other errors MAS is reporting earlier are a hint. I'll look into it.

(Note for myself for when I have time - the MFDs are reporting errors related to the crew count. The vessel just staged and a crew-capable component just got detached. Maybe there's something not updating correctly when that happens)

@MOARdV MOARdV moved this from To Do to In Progress in MAS Features / Bugs Dec 13, 2021
MOARdV added a commit that referenced this issue Dec 13, 2021
If Start() fails, currentPage is probably null.  I already added null checks or exception traps where it's otherwise accessed.  Addresses log spam from Issue #343
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
MAS Features / Bugs
  
In Progress
Development

No branches or pull requests

2 participants