Bug #23962
MK3 Cockpit Lights Broken
100%
Description
The MK3 Cockpit (Shuttle) 'Toggle Lights' button is broken. It only says 'Toggle' and will throw an NullReferenceException when clicked.
When adding the part to SPH/VAB, the console prints the following message:
ModuleAnimateGeneric: Could not find animation component 'Mk3Cockpit_Shuttle' - on part mk3Cockpit.Shuttle failed to load! Check the model file
History
#1 Updated by Anth12 about 5 years ago
- File screenshot1.png screenshot1.png added
- File screenshot2.png screenshot2.png added
- File screenshot3.png screenshot3.png added
- Status changed from New to Confirmed
- % Done changed from 0 to 10
Confirmed
Screenshot 1: shows the can not find animation component
Screenshot 2: shows that the action menu doesnt even have the option for lighting
Screenshot 3: shows exception when trying to turn on the light via the key 'U'
#2 Updated by jclovis3 about 5 years ago
Could be related to Bug #23915 "Lights won't turn on with keyboard shortcut or lights icon from next to altimeter"
#4 Updated by Cybot about 5 years ago
- Expansion Breaking Ground, Making History added
the mk3 cockpit is also causing excessive 'bouncing' when any landing gear is used. no stress on landing gear is registered during the bouncing.
#5 Updated by vrampal about 5 years ago
Looks like the following issues are related:
https://bugs.kerbalspaceprogram.com/issues/23915
https://bugs.kerbalspaceprogram.com/issues/23962
Cockpit Mk3 lights are broken.
#6 Updated by klesh about 5 years ago
I can confirm that this is fixed in 1.8.1. I cannot move Status to Resolved.
#7 Updated by victorr about 5 years ago
- Status changed from Confirmed to Ready to Test
- Target version set to 1.8.1
- % Done changed from 10 to 80
#8 Updated by Anth12 about 5 years ago
- File screenshot0.png screenshot0.png added
- File screenshot1.png screenshot1.png added
- File screenshot2.png screenshot2.png added
- Status changed from Ready to Test to Resolved
- % Done changed from 80 to 100
No NullRefs or unusual log entries. Resolved
#9 Updated by chris.fulton about 5 years ago
- Status changed from Resolved to Closed