BlackSoldierB

I found the following bug. Create a vessel where you have two docking ports connected. Like this: Set on of the docking ports to have staging enabled Launch vessel quicksave Load quicksave Result: Vessel is decoupled I have also tested this against the dev version (posted above).

I will remove those two mods and see if it still happens Edit: I think it will only happen if you have the decouple action in your state bar. Removing Tweakable everything fixes this issue.

I have the following set-up. After loading the save the bottom part will become decoupled. Anyone knows why this is happening? Workaround: Replace the bottom docking port with a decoupler fixes this problem.

With the latest Deadly Reentry, a lot of exceptions will be thrown if the Life Boat is used. Removing the DRE.cfg will fix this issue. I also made an issue on the GitHub page. The engine won't decouple when it is radially attached.

I deleted/renamed the DRE.cfg from the UmbraSpaceIndustries/SrvPack folder. This fixes the exceptions.

But if i would create an new ship with the USI Life boat, this error won't happen again?

My space station is generation a lot of exceptions. [EXC 20:14:25.583] NullReferenceException: Object reference not set to an instance of an object DeadlyReentry.ModuleHeatShield.FixedUpdate () [EXC 20:14:25.583] NullReferenceException: Object reference not set to an instance of an object DeadlyReentry.ModuleHeatShield.FixedUpdate () The .craft is located here. Is there something i can do to fix this? I tried to remove every ModuleHeatShield in my save, but it didn't work. Edit: Found something. When removing the Life Boats from USI it won't happen anymore.

Sweet, thanks for fixing the launch clamp teleportation bug, it destroyed my ship a few times .

When adding a Launch Clamp in the VAB, a lot of exceptions will be thrown. I have created a issue on the GitHub page.

Yup, removed it, and (most of) the errors went away. The only errors i am getting now are: Is that normal?

I am seeing the following errors in my log. Anyone else seen these errors?

EDIT: Nvm, not your mod. Keep up the good work

First of all, you are running out of memory. KSP is 32bit and can only use around 3.2 gb.

Do you have the latest version?

You are running out of memory. See error.log. If you have mods with a lot of parts, it will still use a lot of memory.

This is a known issue with DRE. I think you have to update your ModuleFlightIntegrator. See this post

You can use this to replace the auto detected mods.

First of all, a windows 32 bit process cannot use more that 3.2 gb of ram. A know leak are the thermal indicators. press F10 to disable them at every launch. Are this all the mods you have? No mods with a lot of parts?

KAS is the only one that is not compatible with 1.02 Others are atleast 1.0. EDIT: When i removed NuFar and ModuleFlightIntegrator, the issue went away. Apparently my CKAN didn't update to FAR to 15.1. In this update the following issue is fixed. EDIT2: Apparently is had enabled the AoA and Pitch button in the FAR dialog. (Which also work in space for some weird reason)

KSP: 1.02 Windows 32bit Problem: After i EVA'ed with Jeb to get some science. My pitch control is doing weird. When i hold 'S', i see the pitch indicator go to the bottom. After turning some bit, i see the pitch indicator go the the top (while still pressing 'S'). Anyone else noticed this behavior? Restarting KSP didn't help. EDIT: It doesn't seem related to EVA or Remote Tech. When i launch a new aircraft this also happens. Mods installed: ModuleFlightIntegrator NuFar List from CKAN. Get the savegame here. Reproduction steps: Lauch rocket. Hack gravity. Hold 'S'. The rocket stops turning ~45 degrees. Log: Didn't find any exceptions that could have caused this. Will add one, if I have better reproduce steps.

Did you install Remote Tech? Because I see the green symbol in the top left corner. After 3 km it turns red, because you have no signal. Probes have a integrated antenna of 3km. I suspect that this won't happen with manned capsules.

During the loading screen i got a lot of Null pointer exceptions.

After i docked with my space station i saw this a lot in the log. Anyone also had this behavior? EDIT: After reloading the game, this error doesn't show up anymore.

Do you mean by lately since the upgrade to 0.90? The reason i ask, is because a lot of new parts got added. Are these all the mods you have installed? Do you have ATM installed? NOTE: First run after installing ATM may take up to an hour, with a lot of mods installed.

Cheers, already found your "Anomaly" mod. Going to test it now