Sorry for no pull requests, I don't have a git environment setup at the moment.
While working on converting ASET prop/avionics props over to MAS, I found that both of these functions are returning an iterator out of range exception. Looking at MASFlightComputerProxy:4820 for the problem on the toggle function, where the for loop iterator is starting on a +1 index range. Trivial fix would be to change vc.multiModeEngines.Length to vc.multiModeEngines.Length - 1 on both functions.
The second issue is that switching the multimode engines from 0 to 1 causes numerous props (Like the TWR and TWRMAX props for example) to return zero-ed data, I'm guessing the multimode engine switch is equal to a craft change and requires invalidating the saved module lists and rebuilding them?
Sorry for no pull requests, I don't have a git environment setup at the moment.
While working on converting ASET prop/avionics props over to MAS, I found that both of these functions are returning an iterator out of range exception. Looking at MASFlightComputerProxy:4820 for the problem on the toggle function, where the for loop iterator is starting on a +1 index range. Trivial fix would be to change vc.multiModeEngines.Length to vc.multiModeEngines.Length - 1 on both functions.
The second issue is that switching the multimode engines from 0 to 1 causes numerous props (Like the TWR and TWRMAX props for example) to return zero-ed data, I'm guessing the multimode engine switch is equal to a craft change and requires invalidating the saved module lists and rebuilding them?