-
Notifications
You must be signed in to change notification settings - Fork 12
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
Incompatibility with General Improvements #133
Comments
will do, thanks for report |
done, let me know if that work |
Thanks for the rapid response! Unfortunately it doesn't seem to fixing this issue. It might not be this code after all. This is my current mod list: This is UseBetterMonitors ON in GeneralImprovements without LethalExpansion: And this is the same setup, only with LethalExpansion enabled: For the internal ship camera, GeneralImprovements does the following to access the internal ship material: case MonitorNames.InternalCam:
targetMat = _oldMonitorsObject.GetComponent<MeshRenderer>().materials[2];
break; I'm not sure what else the issue could be. Do you think the issue might be better off resolved on GeneralImprovement's side? |
Did you enabled the compatibility patch I added? It's a setting in the mod setting menu And oh.. the main camera monitor |
Yea, I tried the latest update with the compatibility setting enabled and still saw the issue. I'm reaching out on the GeneralImprovements thread to have them look into it. Thanks for the help! |
Hi! The issue has been patched in the latest GeneralImprovements update. Feel free to remove the compatibility setting as it's no longer needed. Thanks again! |
Hello |
Playing this mod with General Improvements makes it so that the ship internal camera becomes a blank monitor (UseBetterMonitors = true). It appears to be because of the following code:
General Improvements relies on
materials[2]
being the internal ship camera. Would it be possible to add a compatibility setting for this mod?The text was updated successfully, but these errors were encountered: