LM Ascent bug: CSI and TPI Hohmann burn requests return inaccurate orbit and MET values

[idle crown]

In this example from the LM campaign 4, Mission 6 "The Ascent", I requested TPI at 69 Hours MET and got given a MET of 1551 hours!

This issue has been occurring in both the LM campaign 4, Mission 6 "The Ascent", which is fairly restricted in how off script the user can go, as well as in "free play" mode.

Extra information: I had finished the previous P41 RCS program for the CSI burn by pressing PRO until getting P00 before requesting TPI.

I am not sure if this is relevant, I feel it is worth mentioning that I did get a "LANGERR" message immediately after pressing CSI request in both the campaign and free play modes.

It seems someone else also had the same issue here
https://discord.com/channels/510845247404769331/1502077900856492073

[idle crown]

I feel it is worth mentioning that I did get a "LANGERR" message after pressing CSI request in both the campaign and free play modes.

[idle crown]

I have more information after testing it yet again using LM Campaign 4, mission 6 "The Ascent".
It would seem the issues start earlier in the ascent when I press the "Request CSI" from the [C]OMMUNICATION window.
I noticed that the N42 orbit values on the PAD are 982.3 nmi Ha and 982.3 nmi Hp whereas the current LM orbit is 44.1 nmi x 8.9 nmi and the current CSM orbit is 59.2 x 59.2 nmi.
The proposed LM circular orbit of 982.3 / 59.2 = 16.59 times larger than the current CSM circular orbit.
Something is very wrong here.
That being said, when I run P30, it does calculate a more realistic orbit of 44.4 x 43.8 and I can perform the CSI burn.

The CSI pad request has a problem that doesn't appear to completely break the mission yet, until after that when you request the TPI Hohmann request PAD, that is when the TPI request has a more serious mission breaking issue as the LM will run out of power and O2 before that PAD time can be reached.

[idle crown]

LM Ascent bug: CSI and TPI Hohmann burn requests return inaccurate orbit and MET values

[idle crown]

Raised at https://github.com/ReentryGame/ReentryBugsAndWiki/issues/177

[willow mist]

Well this is mighty frustrating. I'm running into the same issue. Requesting TPI at 70 hours for a burn at 104 hours. LM never makes it on battery power long enough.

Specifically running into the problem during the Ascent mission in Campaign 4

[idle crown]

Can I ask if you remember getting a LANGERR message when requesting CSI prior to your TPI request?

I was looking through the recent 1.0.84 patch notes and saw these potentially relevant changes which might have broken the lunar ascent related requests:

• Lunar Ascent burn request labelling fixes
• Fixed an issue preventing players using the French translation from requesting a Lunar Ascent.

From Patch 1.0.84 - Mercury Game Over, Apollo fixes, bug fixes - https://store.steampowered.com/news/app/882140/view/681874975890604926 @ping-steam-updates

For the record I was on en-au (Australia English) and have now changed to en-us (United States English) and still have the problem.

[willow mist]

Yeah, got LANGERR every time

[idle crown]

I have now uninstalled reentry, and cleared the contents of
%localappdata%low\Wilhelmsen Studios\ReEntry
except for
the subfolder
%localappdata%low\Wilhelmsen Studios\ReEntry\System
i then re-installed and just re-did the campaign 4 mission 6 and still got 900+nmi orbit pads and langerr message, but was able to complete the mission this time as it gave realistic burn times that occured within the next orbit.

[idle crown]

Not sure how relevant this is, but when running the mission again, i just noticed these 2 lights for the Control Electronics System

[real iris]

they are reset with the gyro test switch

[spice dagger]

Giving this mission a go later today and will debug whats going on with it