200 m lag or crash at rendezvous in v0.9

[lajoswinkler]

The title is pretty much self explanatory. When you approach a vehicle, first there's the lag at 2.2-2.3 km because of the actual rendering which starts to happen at that distance.

But ever since v0.9, even more serious lag happens at the 200 m barrier. If the total part count is considerable, it can even crash the whole game.

I've noticed this immediately after the upgrade back then, but never reported it.

So, what happens at 200 m and can I avoid it?

[gmpd2000]

My guess would be that the physics load.

Only way to avoid it would be to reduce part count.

[katateochi]

a while back there used to be a horrible bug that would cause craft to explode around the 200m mark when approaching. (although you first had to depart from that craft, go outside 2.5km and then return for it to happen). I wonder if this is a form of the same sort of issue.

What sort of part count are you dealing with? and does it happen in a pure stock install?

[lajoswinkler]

The physics load happens at 2.2 km as usual. What I've noticed is that if you have your craft rotating and you switch to another craft inside that radius, the first one stops rotating. Any angular momentum is preserved in 200 m radius exclusively.

What is happening? Stock or not, it's the same. I don't like it.

[Bill Phil]

First, 0.9 is a different update. Docking ports didn't even exist back then!

I have no idea what causes this. Are you playing with any game changing mods? (I never noticed this bug, and my hardware isn't the best of the worst).

[Master Tao]

<moderation>Moved to Support (unmodded installs).</moderation>

It would help if you could narrow down the reproduction steps and provide your logs (see the [thread=92230]Stock Support and Bug Reporting Guide[/thread]). The 200m distance is an excellent start – can you narrow down the parts to a small range, or a different measure, like memory usage?

If nothing else, that would give us some ideas for how to avoid the problem.

[MartGonzo]

The physics load happens at 2.2 km as usual. What I've noticed is that if you have your craft rotating and you switch to another craft inside that radius, the first one stops rotating. Any angular momentum is preserved in 200 m radius exclusively.

What is happening? Stock or not, it's the same. I don't like it.

That's strange, I wonder why 200m?

I don't know what's causing it so I can't say what would fix it but I do know that antialiasing causes a big hit on high part count ships, I found that turning it off in game and using the nvidia control panel instead gives better results with lower overhead.

program settings tab / KSP.exe

Enhance the Application settings at 2x or 16xQ CSAA and FXAA on, also I recommend setting Maximum pre-rendered frames as high as possible.

I don't know about ATI cards but I'd guess there are similar settings in the control panel for that

[Claw]

The best course for a bug like this is if you can provide a stock save file with the two ships outside of physics range (or at least that the two craft are all stock parts). If this is something that consistently happens with a save file, upload it and I (or someone else) will try to have a look and see if we can tell what is going on.

Cheers,

~Claw