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
The voices are getting louder to control remotetech differently between save games and or disable/tweak remotetech settings without restarting ksp. Here are my ideas:
add disable/enable option to the remotetech settings
try to set the remotetech_settings.cfg into the current save game folder
first start opens a popup for the first configuration
Configuration window
Toolbar button to open the configuration window
disable RemoteTech for Training missions
Second idea: RT option Window
I'll add an option button to the Space Center (top right) to open an option dialog, maybe the same as our debug-window: #347 without the API-Tester, GUID-Reader, Logviewer and the Cheatoption (Signal through bodys)
The text was updated successfully, but these errors were encountered:
- saves the remotetech_settings.cfg into the current save game folder
- added disable/enable option for remotetech
- disables RemoteTech for training missions
- some preparations for the option Window are made
RemoteTechnologiesGroup#482
Peppie84
added a commit
to Peppie84/RemoteTech
that referenced
this issue
Sep 20, 2015
- Finalized the Option window
- For the first start of RemoteTech the option window will be shown
- Added a new APi Method to check whether RemoteTech is enabled or not
- Deleted all RTOptions from the Debug window
- Remote station dots can now colored via the settings file (also with
the option window)
RemoteTechnologiesGroup#482
Peppie84
added a commit
to Peppie84/RemoteTech
that referenced
this issue
Sep 21, 2015
The voices are getting louder to control remotetech differently between save games and or disable/tweak remotetech settings without restarting ksp. Here are my ideas:
Second idea: RT option Window
I'll add an option button to the Space Center (top right) to open an option dialog, maybe the same as our debug-window: #347 without the API-Tester, GUID-Reader, Logviewer and the Cheatoption (Signal through bodys)
The text was updated successfully, but these errors were encountered: