interplanetary vessel bug. really frustrating

[mikey117]

Hi folks , So I play on console an am at my wits end with this game.

so to give you a bit of info on my current situation, I really love and am addicted to this game,however I am constantly having to downgrade/down size my missions .

for a start, I built an epic space station only to have it be unusable due to the lag/frame rate drop being really bad once I tried docking more vessels to it(to be fair though It was over 300parts when completed)This I found frustrating as I have seen people on you tube with stations double the size and working fine.

So I then started building some ssto's, and this is where I came to realise that any vessel over 150parts on console just bugs the game out. Cant even use my mk3cargo ssto with any kind of decent frame rate.

so ok I say to myself its a big enough ask this being on console anyway, so maybe I should just watch my part count and get on with enjoying the game.

and this is where things get really annoying.

So I done some testing an building and after a wee while, had myself a Duna expedition ready to go.

The plan was to send 5x vessels(1x duna lander,1xfuel tank station to be left in orbit of Duna, 1xsat/mini lander cluster and 1xlander and 1xsat cluster for Ike) to utilise the transfer window a bit better this time(only sent a probe first time then thought damn I should have sent more).

So once I had my epic one shot mission ready to go I put all 5 vessels making the transfer burn up into parking orbit ready to eject to duna.Next step I done all of the transfer burns to Duna, Then this is where the game begins to royally screw me over. After doing all the burns i was finally ready to go so I switched to my first vessel and BOOM! It explodes.OMG I say to myself what is going on here ?so I change to the next one KABOOM! Exact same thing happens with every single vessel.

So I loaded up my earlier save(thank god I'm so poophole about making a save all the time)and I tried to do the transfer burn for only the Duna lander and the fuel tank(which was needed forr my lander design, couldn't come home without refueling)

The same god damm thing happened they both went pop. So I checked the mission report. And apparently one of my vessels crashed into eve and the other crashed into a plane?

what the hell???????

ended up having to dock my lander and fuel tank stages onto each other and then do ejection burn. And it worked , I got to the Duna system and done my manned mission in the end,Finally.

so I made my peace with the fact I can only send one vessel interplanetary at a time(lame as f###k) and carried on playing

Now however I am experiencing the same thing now that I am trying to capture an asteroid.

for some reason the klaw I was using just would not grab on after repeated attempts. So i went back to the space center and done a resart(usually gives u a good 20-30mins of the game actually working if u keep resarting on console)

So went to tracking station selected my vessel an yup you guessed it KABOOM!!!!!!

For some reason the game/bad console port. Cannot handle multiple vessels being in interplanetary space.

so after the long explanation.

I am curious to know, does this happen on PC aswell,and if so I there a remedy?

and if I does not ,then this is something that must be fixed before this new port comes out Blitworks please actually test this port before releasing it and push it with the testing . Build a 300 part station on orbit and if it works fine you k ow you are dong better than Squad. Please please test the interplanetary bug .

Finally please just don't even release another port if we cant have a decent part count / multiple vessels travelling through space ,in a goddamn space game seems pretty basic to me.

(final note for moderators please do not move my post I have put it in the questions forum as I am asking PC players If they have encountered this. Also because it will be completely ignored if it goes into the console forum)

 

[Foxster]

7 minutes ago, mikey117 said:

...I play on console...

That's basically your problem right there. 

KSP has been terrible on consoles since day 1 and I personally think it should never have been ported as it is not a game that is suited well to consoles. 

A new port is being worked on but don't hold your breath. 

If you love the game then beg, steal or borrow a PC to play it on because those problems don't happen there. Plus you get to use some of the essential mods. 

 

[mikey117]

probably a pipe dream but I'm kind of hoping it will play well on the scorpio/xbox one x (stupid name I think,lol)

(TAKE NOTE SQUAD)

either that or they release the actual PC version with/without mods to Scorpio users.

I see no reason why they could not as It in no way contradicts xbox's one family of consoles stance (ie. Anything released to the Scorpio has to be released to xbox one also)

it will technically be available for both consoles just a better version on the scopio.(so noone is left behind just ,just frustrated on the xbox one version lol)

[Weywot8]

Commiserations on your exploding situation. Have played on and off since just before 1.0. Maxed out multiple stations at over 300 parts. Never had your situation happen to me. The game just crashes after a few scene switches back in the day. 

Perhaps others might have a different take?

[HebaruSan]

36 minutes ago, mikey117 said:

I have seen people on you tube with stations double the size and working fine.

FYI, some of those people do have slow frame rates, but they speed them back up to normal speed when they are editing their recorded videos. They know that a slide show video would not be very fun to watch.

[bewing]

I will certainly test having multiple ships flying around Kerbin SOI and interplanetary on the Blitworks port.

However, the memory requirements for large ships go up very fast. And consoles have extremely limited memory in the first place. The Blitworks version is going to have better memory management than the Flying Tigers port that you are running on now -- but the tendency is always for players to go crazy with parts. Keep in mind that older KSP versions only had decent performance with 75 part ships, max! The Blitworks port will be better than that, but keep yourself under control on consoles when it comes to part counts. If you want big ships, as said above, play on a PC with 16Gb RAM.

 

[Wanderfound]

Given what everybody has said above about console processing limits...your other option is to build for part efficiency.

It's entirely possible to make a Mk3 interplanetary ISRU-equipped SSTA with less than a hundred parts.

 

102 parts on that one, but you could drop twenty from that if you removed the seaplane floats and hydrofoils.