Bodies that aren't connected to the main body tend to cause problems in the fuel capacity and part staging, making parts appear and dissapear and the total capacity go to weird values.
View |
12 Comments
- Log in to leave a comment
-
Dev AndrewGarrison
@pedro16797 Okay, thanks. I'm behind on going through bug reports. I'm working on a website update that's going out today. I plan to go through the bug reports tomorrow.
-
Dev Pedro
@AndrewGarrison if you try this version of the craft you'll see the monoprop bug reported here
Remove the unconnected parts (the two next to the tower) and problem fixed. So I think both bugs are related. I'm going to change the description to fit the bug so both can be merged -
Dev Pedro
@AndrewGarrison nice, I have to force the inputcontrollers to behave in unexpected ways for the automatic propulsive landing
And if I open the comand box it's spammed with error messages xd -
Dev AndrewGarrison
@pedro16797 Okay, it's also spewing out null ref exceptions every frame, but I tweaked the code so it won't do that anymore.
-
-
Dev AndrewGarrison
Thanks! That made it easy to figure out. This craft you linked does have some issues with piston(s) that cannot access their input controller. I added some code to spit out error messages when that happens.
-
Dev Pedro
@AndrewGarrison oh, thanks to the ghost engine not showing up I've found the origin of the bug.
The staging shows parts that aren't attached to the engine once you launch, but not in the editor.
Launch this and you'll see 4 engines, delete the SRB that is appart and after launching you'll see 3 engines in the 1st stage. -
Dev Pedro
@AndrewGarrison after 3 days having the ghost engine today I've launched the game and it's not there :/
-
Dev Pedro
@AndrewGarrison now in the staging I have 3 engines but once I launch the staging shows a 4, but there's no 4th engine, I've tried to find if any engine from other stage was getting activated and nope it's just a ghost engine
-
-
Dev AndrewGarrison
Let me know if you see this again. I did refactor some of this code with 0.7.0.5, so I very likely caused this.
@AndrewGarrison cool