icaruza

I think I was too eager with my feedback. The crashes have returned; behaviour unchanged since when I reinstalled.

Hey all, Just wanted to share my experience. Macbook Pro, running Yosemite 10.10.3. using Steam to manage my KSP install. I have experienced all the issues recurring through this thread related to texture (management) resulting in crashes, particularly at scene changes. Yesterday I did the following: 1. Made a copy of my save directories 2. Deleted the the local game files from the Steam UI 3. Manually deleted the remaining Kerbal Space Program folder at ~Library/Application Support/Steam/SteamApps/common 4. Manually deleted the Save Application State folder at ~Library/Save Application State/unity.Squad.Kerbal Space Program.savedState 5. Instructed Steam to do a reinstall 6. Restored my save folders/files I have not had a crash since, even operating on full texture resolution (6 hours of game play); I was getting at least a crash every 60-90 minutes on quarter texture res. YMMV. I suspect that through all the incremental updates of KSP, something got broken. It seems to be a lot better now.

Deleting toolbar-settings.dat sorted it out

I am also getting this issue (not showing up in VAB/SPH). Has anyone figured out how to resolve it?

Did more testing. I am only getting ASAS issues with the SMALL stock parts (ie Mk1 pod/RC001S etc).

[Operating System]: Mac OS X 10.8.4 [Memory]: 8GB [ASAS Trouble (Y/N)]: No [Mods installed, pre-patch]: None [Mods installed, post-patch]: None [Description of problem (keep it short)]: STEAM INSTALL & UPDATE. Using SAS built into capsule. No problems flying rockets (hold heading nicely). In my opinion, planes are finally enjoyable to fly; also, no problems here. Will continue testing to see if I can find any combos that break it. UPDATE: Added ASAS to rocket and things still work as expected

Yes, tried 8080, 8085, 80, and 8087. Same result. Am I editing the correct file? config.xml in GameData/Telemachus/Plugins/PluginData/Telemachus It currently looks like this: <?xml version="1.0" encoding="utf-8"?> <config> <int name="PORT">8087</int> <string name="IPADDRESS">127.0.0.1</string> </config>

Hi, I have the latest version off SpacePort. For some reason my datalink doesn't connect at startup. I have edited config.xml and inserted 127.0.0.1 (I have also tried my local IP address, and the default -1 that was in the file). Here are the debug messages I get: [Log]: [Telemachus] Telemachus data link starting [Log]: Parsing int [Log]: Parsing string [Log]: [Telemachus] No such host is known [Log]: [Telemachus] at System.Net.Dns.hostent_to_IPHostEntry (System.String h_name, System.String[] h_aliases, System.String[] h_addrlist) [0x00000] in <filename unknown>:0 at System.Net.Dns.GetHostByName (System.String hostName) [0x00000] in <filename unknown>:0 at System.Net.Dns.GetHostEntry (System.String hostNameOrAddress) [0x00000] in <filename unknown>:0 at Servers.AsynchronousServer.Server.startListening () [0x00000] in <filename unknown>:0 at Servers.MinimalHTTPServer.Server.startServing () [0x00000] in <filename unknown>:0 at Telemachus.TelemachusBehaviour.startDataLink () [0x00000] in <filename unknown>:0 [Log]: PartLoader: Compiling Part 'Telemachus/Parts/TelemachusAntenna/part/ant' The host not known thing is strange as 127.0.0.1 is pretty well known I'm running on a Mac, OS X 10.8.3 Any ideas?

I think transparent windows are a nice improvement. Not sure if it's an OS related thing, but the transparently does not affect readability for me at all.

For a moon mission you will see huge improvement by removing RCS thrusters and RCS fuel tanks altogether. You don't need them as the command pod can adjust attitude without them (there's a big gyro inside, I guess). RCS is only needed for translation (changing position while holding attitude; used when docking). Also, if you're going with the small command pod, rather use the smaller tanks (FL-T200), and the smaller motor (LV-909). It has a much higher specific impulse (which is the measure of how effectively it turns fuel into thrust). Lastly,go with the smaller landing struts. Try that with the rest of your setup; you should get better range and have a more controllable lunar lander at the other end.

I used to be able to see which SOI I am in. Where can I find this info on 2.0?

Is there some fundamental simulation/model change that happens around 30000m? I have noticed that some of my craft designs (usually ones involving radial tanks + engines) will chose this altitude to perform a graceful flip and eventual spectacular disintegration.

Thanks, that worked brilliantly. Why the hell hadn\'t I downloaded the Damned Robotic parts? They are great!

What are you guys using as camera mounts? I have used the light pod from the Bigtrak, but that\'s a bit unwieldy.

This is fantastic. Been wanting this functionality for a while now (been watching SpaceX launches As has been mentioned previously, it would be great to be able to adjust camera views in the same way that one does with the default camera positions. (pan etc)