Benoit Hage

Does it happen all the time when you reload that save or did it happen only once? And if only once, are you sure about being on perfectly circular orbit?

I think this is not the proper log file needed. You need to upload output_log.txt instead.

It's pretty hard to tell what is happening from your GIF as its resolution is quite low. Can you elaborate your problem? Are you already in an escape trajectory? Is your velocity decreasing while burning or after?

What did you change in your game folder since your last save game?

The link to your video does not work as the video is private.

Try ascending at lower speed. Most of the time, the rocket flipping is due to a too important drag force from your vertical speed.

Are you using Mechjeb? Did you leave the SmartASS on? If not, can you tell us your mod list? Try also to upload a screenshot. It's hard to tell anything without it.

It's probably due to an outdated version of Module Manager I think. Try downloading the last version and install it manually. Do the same with KIS and KAS to be sure.

It's just a guess, but I would look more into the driver of your graphic card. Is it updated? While it is true that 47 mods is quite a lot, you would be able to notice if it was a bug from the lack of memory. Check your task manager to see how much ksp.exe is using.

We'll need a picture of your rocket. It's hard to tell without it.

Having several launchpads would actually be useful when multiplayer mode is added in the future.

What about the opening of your drogues and parachutes and the jettison of the heat shield? Those would alter your estimated landing zone as you are human input.

We need your mod list and a screenshot would help too. Are you sure all the mods you use are up to date?

Did you try to select to show all types of ships in the map screen?

https://github.com/linuxgurugamer/KW-Rocketry-Community-Fixes that's your solution right there.

I'm not sure about this ( It's been a while ) but I think you need to modify the .cfg files of your KW engines to fit the module animated emissive of Hotrockets. I'm not sure which is which, but browse in your hotrockets folder and you'll find it easily.

There

Good news! Can you please modify the title of this thread with a more accurate one and put it as answered. It may help others in their research.

sorry for the dull question but have you installed those? "This pack REQUIRES BDArmory 0.9.5 or later, earlier versions will NOT work with this mod! Also Requires BDArmory Community Addon Library (Thanks Prometheus!)"

Bad news: I tried to read few pages on the net about that graphic card. It seems that because it is still a quite recent card, it is still not fully supported by several Linux OS repositories. But what is clear is that your driver isn't the proper one. I've found several way to install some unofficial driver via the ppa:xorg-edgers. However, this do not seems to be a common solution and I do not dare posting it here as I'm clearly not sure that it would be a solution. I'm afraid this goes beyond my knowledge... For me, your best bet is to run ksp.exe via Windows. However, if you do not want to wait for 1.1, try some more research about your "Device 13c0" and get ready to backup your system and do some testing. Just a curiosity: Are you able to change your screen resolution in Mint above 1024x768?

I don't think it will be possible in one time, like what if the desired planet is out of reach? Sometimes, with a bit of luck and everything in the right place and time, you can target the desired body and do a Hohmann tranfer while waiting for circularization burn after a launch. I manage one or two with the Mün (...)

I don't know about the rover speed, but in the dev build of the 6th of January, Sarbian did fix few NRE concerning the rover waypoint system. My guess is get the latest dev build and try it out. With a bit of luck... we never know. Mechjeb latest dev

Sure with notepad, it should work. You'll see at the 6th or 7th line if there were some RAM left available. Watch out that ksp.exe is a 32bit application. It means it can not use more than 2e31 minus few thing octets. So no more than 3.5 or 3.6 GB if i'm right. What are the textures you use for the RSS? 8K ones or 4K? The 4K's ones use much less memory. Beside this, there is not much else to help you reduce the RAM consumption, as you already have most of the tricks I know of. Normally, you should be able to play RSS and RO + dependencies without problem, after all, we are all using the same amount of RAM, as the ksp.exe is a 32 bits application. Having 8GB do not change anything as for now, but as soon as KSP 1.1 is out, it will be a 64bit application, and then you 8GB will matter, as the application will uses 2e63 octets of available memory for its bits adressing. I guess the wait for 1.1 won't be too long anymore! Courage mate.

This reminds me of an old bug with Kerbpaint where the areo surfaces would broke the SRB's smoke trail. see here: http://forum.kerbalspaceprogram.com/index.php?/topic/45999-023-kerbpaint-paint-layering-for-parts-september-23rd-same-old-still-works/&do=findComment&comment=645668 I guess the problem should be somehow related. By any chance, are you using the last version?

If you go in settings -> system -> details, do you see you the correct graphic card? If not, you might have to add the backport in your sources.list