Bug #10087
Satelite orbit is changing with no input
100%
Description
There was a similar thread in 1.1.2 and they said it was fixed in 1.1.3 but it is still there.
I completely deleted my game, I reinstalled, I even moved its folder so its a new version in new folder. And of course started new game.
I still experience my apoapse changing even faster than before in 1.1.2.
I set a polar orbit 88.6km/910.15km (4 hour 00 minute 00 second) around mun so i can set two satellite opposite side (910.25x910.25 its 8hour 00minute) easily.
Everything works fine around Kerbin, then when I go to Mun it starts going crazy.
At the periapse as soon as I finished my burn to set the apoapse , it starts dropping fast... in couple of second from 910 its going down under 900... even during my burn it already drops... I turned RCS off still experiencing the same. If I time warp it doesnt change but when I stop it starts all over again. and my apoapse start dropping crazily... I even checked if fuel or monopropellant is being used but they stay on same level.
I attached save file... I dont know if you know can check because I use good few mods.
And finally sorry for my bad english. :D
In the save file, go to the "Comsat Launcher" ship around mun and check how it apoapse is changing without input!
| quicksave - bug is still here.sfs (2.27 MB) quicksave - bug is still here.sfs | [email protected] | ||
| record1.mp4 (2.74 MB) record1.mp4 | [email protected] | ||
| list.ckan (2.54 KB) list.ckan | mod list | ||
| Mun.Body.log (29.4 KB) Mun.Body.log | from kerbalspaceprogram\logs\Kopernicus folder | ||
| output_log.txt (2.36 MB) output_log.txt | after quitting game | ||
| list2.ckan (1.75 KB) list2.ckan | the second list | ||
| screenshot1.jpg (301 KB) screenshot1.jpg | [email protected] | ||
| screenshot2.jpg (161 KB) screenshot2.jpg | [email protected] | ||
| mods.jpg (385 KB) mods.jpg | [email protected] | ||
| quicksave -bug reproduced.sfs (733 KB) quicksave -bug reproduced.sfs | [email protected] |
Related issues
History
#1
Updated by Crusoe over 8 years ago
Updated by - File record1.mp4 record1.mp4 added
I was trying to find out if I did something wrong I didn't find anything. I tried save/reload to fix it. I tried many things. After all tries failed I was making this video 1-2 minute after after I left the periapsis (where I finished my burn making the apoapse to 910.25km) and so after 1-2 minute "flying" and its already dropped 2-3km without.
#2
Updated by Crusoe over 8 years ago
- File list.ckan list.ckan added
- File Mun.Body.log Mun.Body.log added
- File output_log.txt output_log.txt added
And here I am adding some more files/information that I may have missed.
I'm running the game on windows 10 pro, 64 bit. Version 1.13, I'm launching it from Steam.
My Pc: Intel i5-45701 @ 3.2 GHz core, 8 GB memory. NVIDIA Geforce GTX 650 Ti graphic card. (If you need more details I can say)
My mod list. I'm using CKAN for modding, I'll attach the ckan export file here. In that you can see (even with just notepad) the list of mods (or I guess You can import in ckan to get same version as I use)
While I was searching for logs I found this mun.body.log file, I added one log from log\Kopernicus maybe its relevant.
Just to make clean again. I'm using a new install.
Started new game few days ago.
Not using any saved files/craft files or anything like that.
Did not modify any .cfg files or anything like that.
Didn't even change anything in the options menu (except screen resolution, graphic settings, music volume and things like that) and debris count.
build id = 01289
2016.06.21 at 20:49:32 CEST
Branch: master
version is 1.1.3
#3
Updated by Crusoe over 8 years ago
The bug I mentioned from 1.1.2 was #9619.
#4
Updated by Crusoe over 8 years ago
- File list2.ckan list2.ckan added
I reinstalled the game, and I installed a bit less mods. I left out these mods (some of them I left out, some of them dependent with those mods that I left out):
KerbalAlarmClock, TriggerAu-Flags, BetterCrewAssignment, KerbalJointReinforcement, StockVisualEnhancements, LaunchNumbering, FerramAerospaceResearch,
PlanetShine, PlanetShine-Config-Default, RoverWheelSounds, StationScience, TacFuelBalancer, ProceduralFairings-ForEverything, FirespitterCore, ProceduralFairings, ProceduralParts
Right now, without these mods, the bug did not showed up yet. I'm realy suspicous about the procedural parts/fairings causes this bug, because also they look buggy in the VAB (green bubbles/attachment points show up in the air) and also I think the bug appeared after I installed those mods. Maybe I'm wrong but I'd check those first. (To be fair I only checked it twice, once with hyperedit, and after it worked I also sent one spaceship with two satellites, now they are perfectly working, no orbit changes occur).
The new modlist I will attach. So those mods which are not on this list but they are on the first list could cause the bug.
#5
Updated by Claw over 8 years ago
Updated by - Severity changed from High to Very Low
While we aren't trying to ignore add-ons, we really need the situation to be replicated in stock in order to effectively track down the bug. If you have a stock save file, that would help the best in this particular case.
#6
Updated by Crusoe over 8 years ago
Sorry, I'm not sure what is a stock save file? I think I uploaded it already its the first file I attached.
Named: "quicksave - bug is still here.sfs"...
Or if this is not the one You looking for.. tell me where I find it. I copied the whole KSP folder (in case) before I installed a new one. I think I still have it somewhere. I can look for it.
#7
Updated by Crusoe over 8 years ago
Well If You mean the bug comes from a mod, yes that is probably the case... I still use mods but one or two (I suspected causing this bug) like procedural fairings/parts I actually don't use them anymore and the bug is gone. Where can I report that bug then? At the modder's forum? I pretty much think its the procedural parts or fairings... NathanKell's stuff (I thought he work for Squad too btw.)
#8
Updated by Crusoe over 8 years ago
The bug come back in my new install... now explain me how I get a "stock" save? Should I build a ship with just stock parts? Should I uninstall all my mods and look if the bug is still there and get a save file?
#9
Updated by Crusoe over 8 years ago
- File screenshot1.jpg screenshot1.jpg added
- File screenshot2.jpg screenshot2.jpg added
- File mods.jpg mods.jpg added
- File quicksave -bug reproduced.sfs quicksave -bug reproduced.sfs added
I tried few things, and I think I was able to reproduce the bug.
I went to mun again and the bug appeared again so I designed a simple ship to test if it appears only on my "crazy" designs or any ship. So I desingned a ship with just few parts on it. See schreenshot1.
The bug didnt appear on that ship. So I tested 1-2 ships addig parts, adjusting (moving/rotating) things the way I used to to test if thats the problem.
I built a ship where I hidden half of a battery inside the fueltank. Bug didn't come up. (I have no screenshot of that).
I built a 3rd ship (screenshot2) where I put a parachute on top of that battery (attached under and moved up) and also a small light (that comes from a mod). So 3 parts sitting on the same spot and I think that may be the reason for the bug. I hope this help to investigate.
I've made a video of the operation as well, but it was too big to upload here so I uploaded to Youtube.
https://youtu.be/7DgHy46q2Ew
I hope this will help you to find and fix the bug.
This time i'm using only a few mods (very few that can affect physics) maybe just tweakscale, infernal robotics.. But I'll just give a screenshot its easer than write all them down.:D
I add a save file too finally.
If you require any other saves, craft file or something I can get, let me know.
Thanks
Robert
#10
Updated by Crusoe over 8 years ago
The above situtiation, that was just a guess, but now I'm not sure because I've made a new ship to land at Minmus. That ship doesn't have parts moved like that inside eachtoer... yet it did do orbit decay (it was a lander). Interestingly after I landed and went to orbit again first a lower orbit 10x10km and I get decay again...after that I went to a higher 100km orbit and the decay disappeared.. or it was so small it become unnoticable.
#11
Updated by Crusoe over 8 years ago
May I ask why someone changed this "GAME BREAKING" thing to low priority? It is HIGH if not critical!
There is this.
And this #9619 (saying its solved but its not). I reported it earlier they said its a dublicate of #9619 and that is "solved". Now I have to say it is not solved. It's still there.
And this #10104.
How can I play this game if in orbit of Minmus/Mun all my ships from 20km / 20km orbit become 18km/22km in like 30 seconds.. how can I even play? This bug is completely GAME BREAKING! Should be at least HIGH priority if not even CRITICAL.
I realy dont understand this why some1 set it to Low....
I can't play properly now for months. I dont use any rare mods, I use commonly used mods like mechjeb, tweakscale and infernal robotics, KIS/KAS. And a few more that I'am 100% sure do nothing with game phyisics (like BetterBurnTime, chatterer, camera focus changer).
Earlier my game run without any problem with a ton of mods. There is this giant, game breaking bug, and noone even working on it saying "we can't reproduce in stock game save file"...
#12
Updated by Crusoe over 8 years ago
I'm going to start now a new stock game. And I may add 1-1 mods until I find the guilty mod. I just can't exist without this game, sorry I'm addict to it. This Bug has to be found.
#13
Updated by TriggerAu over 8 years ago
Updated by - Related to Bug #9619: Orbital Decay/ Orbit changes without user input added
#14
Updated by TriggerAu over 8 years ago
- Related to Bug #10330: Orbit changes without reason at Mun, not fixed. added
#15
Updated by TriggerAu over 8 years ago
- Status changed from New to Duplicate
- % Done changed from 0 to 100
Linking this one to the root issue #9619 and closing this as a duplicate. It is marked as high priority
#16
Updated by jclovis3 about 2 years ago
Updated by 
Related to issue 24354, with any orbit with Pe below 100 km and Ap above it, while the craft is below 100 km the AP increases. When the craft rises above 100 km, then the AP stops changing. I noticed this while aerobraking on Duna and Eve after exiting the atmosphere altitudes (50km and 90km respectively) that the AP began to rise until the craft reached 100 km.