Patch Notes: Reentry has been updated to version 0.6535
First of all, thank you all for reporting issues and for contributing to the simulator. This patch had a long delay due to a blocking issue surrounding Rendezvous in Gemini. This bug was triggered by some major logic changes needed to fix a few if the issues reported. However, we should be good to go again!
This patch aims to fix some of the critical issues reported from the 0.65 update, and has the following fixes:
- Infinite Roll Program Rates fixed during the ROLL PROGRAM on Gemini ascent.
- Bad save state in Gemini: Due to a bug, when loading a save state, the free play mission state was loaded instead.
- EVA offset position is fixed and you will spawn next to the spacecraft.
- Radar range and Encoder now works when docked.
- Mercury abort in Atlas had a bug that would bring the capsule into a proper orbit. This is now fixed can the campaign mission should be working agian.
- New feature: Launch Azimuth logic and inclination (see below).
- Exit button should be visible and longer scrollable main menu, for those using wide screen.
- Gemini thruster volume reduced.
- Agena engine is tuned down.
- Gemini FDAI sphere texture.
Still looking into some of the other bugs reported but this is a start.
New features:
Azimuth calculations (basics)
Special thanks to pclaurent for helping me with the new azimuth calculations logic. This is just a start, and will be the basis for improved ascent guidance algorithms.
Using the OBC, can you insert the target inclination into the OBC Core 09, and it will automatically calculate the roll needed in the roll program, and reconfigure the OBC (Core 10 and 11). You will need to run the pre-launch program to align the platform. Keep in mind that the target inclination can not be less than your launch latitude, and should not deviate too much from 28.5 and 32.5.
Ap, Pe and ascending/descending node markers in Gemini orbit view
New markers are placed to easier visualize where the orbits apogee and perigee is located. These points are important as they are used to move the point on to opposite side of the orbit in or out. The ascending and descending nodes are the points where it's best to perform inclination/plane changes. These are still WIP, but I wanted to start testing the logic.
If the IVIs show a dV in the middle field (plane change), you should null this at the ascending or descending node.
This patch aims to fix some of the critical issues reported from the 0.65 update, and has the following fixes:
- Infinite Roll Program Rates fixed during the ROLL PROGRAM on Gemini ascent.
- Bad save state in Gemini: Due to a bug, when loading a save state, the free play mission state was loaded instead.
- EVA offset position is fixed and you will spawn next to the spacecraft.
- Radar range and Encoder now works when docked.
- Mercury abort in Atlas had a bug that would bring the capsule into a proper orbit. This is now fixed can the campaign mission should be working agian.
- New feature: Launch Azimuth logic and inclination (see below).
- Exit button should be visible and longer scrollable main menu, for those using wide screen.
- Gemini thruster volume reduced.
- Agena engine is tuned down.
- Gemini FDAI sphere texture.
Still looking into some of the other bugs reported but this is a start.
New features:
Azimuth calculations (basics)
Special thanks to pclaurent for helping me with the new azimuth calculations logic. This is just a start, and will be the basis for improved ascent guidance algorithms.
Using the OBC, can you insert the target inclination into the OBC Core 09, and it will automatically calculate the roll needed in the roll program, and reconfigure the OBC (Core 10 and 11). You will need to run the pre-launch program to align the platform. Keep in mind that the target inclination can not be less than your launch latitude, and should not deviate too much from 28.5 and 32.5.
Ap, Pe and ascending/descending node markers in Gemini orbit view
New markers are placed to easier visualize where the orbits apogee and perigee is located. These points are important as they are used to move the point on to opposite side of the orbit in or out. The ascending and descending nodes are the points where it's best to perform inclination/plane changes. These are still WIP, but I wanted to start testing the logic.
If the IVIs show a dV in the middle field (plane change), you should null this at the ascending or descending node.