![]() Happening a lot when I move/delete a part. Trying to de-bug my frequent crashing in VAB. If you'd like to help to develop RT in any way feel free to PM me. If you'd like to see a new feature implemented or a bug fixed then you'll probably have to write the necessary code yourself and submit a pull request here. We do not have a lot of manpower here and sadly RT development is now limited mostly to KSP compatibility releases and only the most urgent bug fixes. We're not always following this thread and they might easily be overlooked.Ģ. I've noticed that a lot of you guys talk about bugs here. This is mostly an update of 1.7 to make it work with KSP 1.1.3.Ĭan be downloaded through usual channels.ġ. Is this the likely issue and is there a fix? Is there something else I should check or do to fix this? It kind of sucks wasting all that time and effort on the lander to lose it like this, and I don't really want to temporarily disable RT for this. I suspect that it has something to do with the part of the lander that was attached to the separator is a monoprop tank and not a probe core, so it might be the root part which has lead to issues in the past. I have an extended Communotron 32, a Comms DTS-M1 targeted at the satellite (which targets it back with the same and also has extended Comm. However when the lander gets ~11km or so away from the comm satellite, connection is lost. Beneath it was the lander which was to use the drive section to de-orbit and land. Comm satellite was the top portion and separated by a stack separator. I launched a single rocket to Duna with two ships on it, a comm satellite and a lander. Now with 1.1.2 out I have to wait for my CKAN mods to update before I can try re-creating the crash.Facing a rather peculiar bug. Player.log shows the crew report but nothing about the subsequent crash. I'd been playing for a couple of hours and had just done the crew report when it crashed to desktop. Had a crash to desktop last night while flying a plane to do an observation contract that left no information in the Player.log file. Until then, I'm running full screen.ġ.1 had other problems, though. I really hope they can bring back the ability to run in a maximized window. The update removed the maximize button, and now the windows must be a standard screen size. The first time I started 1.1 it crashed on startup, and subsequently it started in a standard sized window. Before 1.1 I used to run KSP in a maximized window. I think the startup crash has to do with the Unity 5 update not allowing nonstandard window sizes. I have an nVidia card and had crashes on startup with 1.1, and other crashes on 1.1.1. ![]() Send us a message with proof, and we'll give you some flair to show it! Disable header animation Enable header animation Δ | Support/bug reports | KerbalAcademy | ConsoleKSP Last contest's winner: forteefly1998! Have you developed a mod? See this page for more infoĬommunity Teamspeak Server Refrain from submitting images that involve real life space disasters that resulted in loss of lifeĭon't post/discuss mirrors or torrents of any version of KSP ![]() See the discussion on misc posts for more info No posts unrelated to KSP or memes and image macros. ![]() Please remain kind and civil at all times ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |