Search the Community

ok, so I've downloaded the .zip and unpacked to a folder on my desktop. When I try to run KSP2_x64 all I get is "Failed to load mono" I've clearly done something wrong, but what?

Just after installing a couple mods, I get this issue from the crash log for this "mono.dll caused a access violation" I tried everything. I don't want to rip apart the mods cause I don't want to mess any of my ships up. If someone could point out what mod or anything is breaking the game, please tell me! Thanks. Crash Log here

I have a modded instance of Kerbal installed via the steam client (1.3.0) that I recently updated to 1.3.1 on accident, and it broke most of my mods because of compatibility issues. I reverted to 1.3.0 through steam and used CKAN to reinstall the older versions of the mods, since it had updated only some of them, as they hadn't all come to support 1.3.1 yet. upon launching, after everything loads and it goes to the splash screen right before the main menu I encountered a crash, which gave me an error message and printed out a folder of the errors and a stack trace. Attached is a compressed version of all the different crashes, both after updating the mods to 1.3.0 and before. replies and suggestions are welcome! https://cdn.discordapp.com/attachments/359240957545414666/366711903843778560/Desktop.rar

So I was in sandbox mode test out, how to setup Satellite array I noticed that my Rcs ports on my launch craft where pulling monopropellant from my Satellites tanks first and not the one nearest to them (they changed it to this in 0.23.5 and I did not notice) and yes I know you can disable the tanks so that fuel can not be pulled from them. I when't back to the VaB and did some testing using This and found out that 1. Monopropellant is pulled form the upper stages first 2. Even though you can do so, changing the fuel flow priority on monopropellant tanks, does not change any thing and 3. Monopropellant does not obey the crossfeed rules on decouplers. So I had some ideas for a mod that would change this and if knew how to do so I would make it myself, but I do not, so I throw myself upon the tender mercies that are the great mod makers in this community. (these ideas are listed in what I believe would be the most useful to the least useful) Idea 1. For stock decouplers create an option in the right click menu, i.e when you right click a decoupler there would be an option below crossfeed, that would say Monopropellant Crossfeed and when you clicked it, it would enable/disable monopropellant crossfed and would prevent any rcs ports below the decoupler from being able to pull fuel from the tanks above the decoupler, forcing the rcs port to pull fuel from the neatest tank it can. Idea 2. Make it so that the fuel flow priority system works for monopropellant tanks. i.e you could set, for example, a satellites monopropellant tanks to -1 and set the main crafts monopropellant tanks to 0 and it would pull fuel from the main crafts tanks first. Idea 3. Change how monopropellant works back to how it was pre 0.23.5, which in and of it self has some problems and can annoy you just as bad, why am i even listing this one, oh well. I am not sure how difficult this would be, but I do hop someone takes up the challenge, if anyone has any questions leave a comment. Thank you for reading this far , Kage Sendo.

My game crashes when entering buildings (VAB, Tracking, SPH, etc.), sometimes on vehicle launch, sometimes when switching to another vehicle. My computer specs: Windows 10 64-bit 16GB DDR3 Ram Nvidia 950 GTX (Yes it is up-to-date with drivers) AMD A8 5500 CPU 3.2GHZ Things I have tried: Disable PPFX Highlighting Install Active Texture Manager (or whatever it's called) Fresh Install Mods Installed: KSPI-E, SCANsat, KAS, KIS Error Log/Crash Log: http://pastebin.com/nE7H4pjK

I run KSP on linux mint/cinnamon In my performance settings Mono heap & Mono heap used remain at 0 (zero) I have never seen them have a value. What are they for? Are they actually being used? Could someone explain to me why they remain at zero?