Bug #4915
Spacecraft closer than 1000 km to Jool are incorrectly prevented form non-physical time warp due to being "under acceleration"
100%
Description
Whenever I send a craft into the Jool system and do my insertion burn close to Jool (say 200 km), I cannot use non-physical time acceleration until I get above 1000 km altitude. The reason stated by the game is that I am under acceleration, which is not correct.
I have labeled this as 1.0.1, but I am playing 1.0.2, there's just no option for it.
History
#1 Updated by phcorcoran over 9 years ago
I have experienced this issue as well, although it so far only seems to occur if there is a heat shield (ablator) part of the craft. It seems the issue disappeared once I separated from the shield, however it is difficult to be sure.
I am also on Windows, version 1.0.2. The only mod installed is the latest MechJeb at this time.
#2 Updated by Geschosskopf over 9 years ago
- Status changed from New to Confirmed
- % Done changed from 0 to 10
Confirmed.
1.0.2, Windows 32-bit.
Heatshield makes no difference to me, but I suggest trying this with and without just to be sure.
REPLICATION:
1. Transfer something to Jool and put the Jool Pe at like 180-190km to aerocapture.
2. Run regular warp up to 1000x all the way until you hit the atmosphere.
3. Use physics warp while you're in the atmosphere.
4. Once you exit the atmosphere, stop physics warp and try to do regular warp again. The game won't let you use regular warp, saying that "the ship is under acceleration", even with no engines running and no longer in the atmosphere.
5. Physics warp still works, however. You can use this to get high enough above Jool's atmosphere for regular warp to work again. This distance appears to be between 500-1000km.
NOTE: Some people in the forum report that their Ap INCREASES while the game is saying the ship can't warp due to acceleration. I cannot confirm that part of this.
#3 Updated by phcorcoran over 9 years ago
After some further testing, I was also able to reproduce the issue with or without a heat shield, I had not noticed the part where it only happens if you actually enter the sub 200km zone. I must have stayed higher than that in my tests when I didn't have a heat shield.
On an unrelated note, I have tried to reproduce the issue in the OS X version, and the result is similar.
#4 Updated by Talib over 9 years ago
Same Issue here. I'm around Jool, aiming for Pol and ship was under acceleration until 1000km above. This wasnt a problem just after aerobrake at Jool, but it is after a few orbits. All stock parts except the scansat scanners, heatshield still on board as part of an upper stage (stock fairing for heatshield disappeared some time before, looks like its not connected at all). ksp 1.0.2 @win7
#5 Updated by Squelch over 9 years ago
- Platform Win32 added
- Platform deleted (
Windows)
#6 Updated by Geschosskopf over 9 years ago
In other news, this problem seems only to affect ships in more-or-less equalqtorial orbits. Ships in polar orbits have no problem.
Also, if it affects a ship, it will do so on both sides of the atmosphere. Set the Pe say at 250km and warp towards it until you're just below 1Mm. Stop warp and you won't be able to start it again until you're back above 1Mm
#7 Updated by Neutrality about 9 years ago
I get this as of 1.0.5. I regular-time-warped in to about 220,000m, passed through the atmosphere, and was unable to regular-time-warp until almost exactly 1,000,000m. I was able to do physics time warp, but regular time warp did not work and said the craft was accelerating until 1,000,000m.
One successful workaround I found was quicksaving, reloading, and starting time-warp before physics kicked in
Edit: So I made an insertion burn to a 300,000m orbit and was able to regular time warp. Perhaps the bug has something to do with suborbital trajectories, the shape of the orbit, or your speed at the lower altitudes
#8 Updated by TimZ about 9 years ago
I'm seeing the behavior in 1.0.5 too.
After aerobraking at 160km through Jool's atmosphere I could no longer use non-physics time warp - this also prevents you from exiting to the space center without losing your progress. I slogged though the very long process of circularizing my orbit through multiple aerobraking passes, and noticed that once I got my apoapsis down to somewhere around 3 million km the issue went away and I could time warp normally once out of the atmosphere at 200km.
This makes me also suspect the the issue has to do with the high acceleration resulting from Jool's gravity when coming in from high apoapsis or interplanetary transfer. Perhaps tripping a threshold that doesn't happen on other lower gravity planets?
#9 Updated by MarkRobinson about 9 years ago
I, too, am experiencing this bug.
#10 Updated by AmoebaMan almost 9 years ago
Confirming the same behaviors described above. Non-physical time acceleration is not allowed below around 1000km above Jool.
Also adding to the table: there are very minute changes in the Apoapsis and Periapsis (on the order of a few meters of adjustment per second) while this bug is in effect. The apoapsis increases and the periapsis decreases. This seems to suggest a radial acceleration. It seems likely to me that there actually is a force being exerted, and not just that the time-warp acceleration check is failing.
#11 Updated by Cerberus738 over 8 years ago
I'm getting this bug in 1.1 dunno if i should submitt a new report??
Playing the scenario Aerobrake at Jool i'm getting this same bug. You can time warp at the start of the scenario but if you stop time warp you cannot enter it again.
http://steamcommunity.com/sharedfiles/filedetails/?id=661141056
also the first kerbal portrait has the bottom blacked out??
#13 Updated by TriggerAu over 8 years ago
- Status changed from Confirmed to Needs Clarification
- % Done changed from 10 to 0
#14 Updated by sal_vager about 8 years ago
- Status changed from Needs Clarification to Resolved
- % Done changed from 0 to 100
This was changed, you can check in the 'Aerobrake at Jool' scenario.
#15 Updated by sal_vager about 8 years ago
- Status changed from Resolved to Ready to Test
- % Done changed from 100 to 80
#16 Updated by JPLRepo about 8 years ago
- Status changed from Ready to Test to Closed
- % Done changed from 80 to 100