I have all the other parts of the program done. its just a simple satellite that reaches orbit. but when i want to stop the engines at 130,000km the program wont stop the engines. i cant figure out why.
GENERAL INFO
- Created On: Android
- Game Version: 0.9.509.0
- Price: $14,774k
- Number of Parts: 91
- Dimensions: 43 m x 4 m x 4 m
PERFORMANCE
- Total Delta V: 8.7km/s
- Total Thrust: 3.8MN
- Engines: 7
- Wet Mass: 2.14E+5kg
- Dry Mass: 19,705kg
STAGES
| Stage | Engines | Delta V | Thrust | Burn | Mass |
|---|---|---|---|---|---|
| 1 | 3 | 4.2km/s | 3.2MN | 2.4m | 2.14E+5kg |
| 3 | 1 | 2.8km/s | 551kN | 1.8m | 33,878kg |
| 6 | 3 | 1.7km/s | 98kN | 1.7m | 8,149kg |
2 Comments
- Log in to leave a comment
-
0 Nortorn+4 3.8 years ago
You're telling the program to
"wait until Orbit Apoapsis = 130000" ,
which wont trigger if the game skips a frame or you're just moving too fast.
Use "wait until Orbit Apoapsis >= 130000"
instead
No Upvotes
Log in in to upvote this post.
Because the computer operation "=" will be two numbers exactly the same. And the track variable is a floating number, if you want to achieve "AP = 100", the CPU will be crazy to calculate to 99. 99999 There will be countless 9's behind, which is obviously unrealistic. Because of the limited computing power of the device, it is impossible to calculate every frame to the limit. If you want to get high precision parameters, first you have to intercept the precision. Then make sure that the number is calculated in any frame.