You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You're calling game.Input.Flight.Enable() and game.Input.Flight.Disable, but these have zero effect. When using your mod, it will correctly detect that the player has clicked in the renaming input field and indicate (incorrectly) that game input is disabled. If you press "." or "," while in the input field timewarp is accelerated/decelerated respectively. There's nothing wrong with your decision logic in OnGui, but what you need is to call GameManager.Instance.Game.Input.Enable() and GameManager.Instance.Game.Input.Disable() to get the effect you're seeking.
I've used your logic with this call in a mod of mine and that seems to work. I learned it from ShadowDev's NoteBook mod for KSP2: https://github.com/Bit-Studios/NoteBook
The text was updated successfully, but these errors were encountered:
I did use that global input disable toggle at one point, but had an issue where after enabling again if you went to the map everything got disabled again until you used the UI button to return to flight.
I'll check if this is no longer the case and push an update.
You're calling game.Input.Flight.Enable() and game.Input.Flight.Disable, but these have zero effect. When using your mod, it will correctly detect that the player has clicked in the renaming input field and indicate (incorrectly) that game input is disabled. If you press "." or "," while in the input field timewarp is accelerated/decelerated respectively. There's nothing wrong with your decision logic in OnGui, but what you need is to call GameManager.Instance.Game.Input.Enable() and GameManager.Instance.Game.Input.Disable() to get the effect you're seeking.
I've used your logic with this call in a mod of mine and that seems to work. I learned it from ShadowDev's NoteBook mod for KSP2: https://github.com/Bit-Studios/NoteBook
The text was updated successfully, but these errors were encountered: