![]() ![]() SAS, RCS, Light, Gears, etc.) on the vessel flight computer and when the delay time is elapsed, pop the command and execute it. The plan for RT 2.x is to remove all the locks altogether and "hijack" the KSP buttons so RT knows that they are pressed before the click goes to KSP, push the command (e.g. The original intent was to tell players that the vessel was not under direct / local control. the vessel is not crewed), RemoteTech is locking the KSP GUI so clicks don't pass through and never get to KSP. If you can read C# it happens here: if you don't have local control of the vessel (i.e. No, technically the color is dimmer because the GUI is locked. Oh now i see, the r key is working actually, but something interesting, take a look at this :Īs you see the color is dim, that is why I didn't noticed this in my own game because the gui is smaller, also, that color gave me a thought, can it be that your mod is causing a duplication of nav ball gui or some kind of gui overlay that is almost transparent but at the same time stops the mouse click on itself and not letting the click to pass through? that would explain the color on the gui and the mouse click not working !!!!Īs you see the color is dim, that is why O didn't noticed this in my own game because the gui is smaller, also, that color gave me a thought, can it be that your mod is causing a duplication of nav ball gui or some kind og gui overlay that is almost transparent but at the same time stops the mouse click on itself and not letting the click to pass through? that would explain the color on the gui and the mouse click not working !!!! I remember testing this for RT 1.8.2 but the conditions under which I made my tests might be different from yours. Hmmm there's definitely something wrong if key bindings don't work. We plan to fix this issue for the RT 2.x branch. There are multiple issues about that (#605 and #646 at least) and it would require a big amount of work to be able to use those buttons through the UI. Something changed in KSP at some point (around KSP 1.0 release). The fact you can't use the buttons on the navball (you have to use key bindings instead) is there since at least 1.7.0. Maka a save backup before installing RT if you are not sure RT doesn't have the interface option of turn on CommNet anymore (due to the RT/stock conflicts) until RT 2.x Orrrr turn on RT's cheat of configuring antennas in event of connection loss.ģ) Your stock satellites will still be there but see (4).Ĥ) You need to edit this "EnableCommNet = False" in your persistent.sfs to get CommNet back. 1) If I install RemoteTech v1.8.2, will my current geostationary satellites function (but now using remotetech instead of commnet) with the stock antenna's on them?Ģ) Does RT v1.8.2 come with any non-stock parts?ģ) If i de-install RT v1.8.2, will any of the satellites disappear from my saves, assuming they only have stock parts attached to them? (and also assuming that RTv1.8.2 comes with NO additional parts that are non-stock)Ĥ) If de-installing RT v1.8.2 AND satellites do NOT disappear, will they automatically work again with the ingame CommNet?ġ) For the first time, the stock antennas on your satellites will reset to the default RT state (editor/launch state aka not extended) so your satellites will float dead . You need to launch their replacements. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |