RomRaider

Does anyone have access to the cruise/non-cruise status when logging?
I see they mention it in the HolyCrapItsFast tuning guide but I've never seen any discussions related to defining that parameter

So many tables are split in to cruise/non-cruise on the 32 bit ecu is everyone just applying their corrections to both equally at all times?

Edit below-
I must have glanced over the "TD_D" part ten times, does this refer to Test-driven development? is anyone familiar with that concept or seen any discussion applying it to logging? I guess this implies this is not as simple as finding an address and making a definition.

"
Tip: TD_D, This is experimental, but the logic is sound. In
opensource, you can now log the cruise / non cruise parameter
(0 or 1). You can use this to further refine the cruise vs. non
cruise tables accurately.
"
-George’s (AKA HolyCrapItsFast) Guide to Street Tuning. Subaru STi, GD, (GR) Rev 1.8, 02/17/2016

TD-D is a user on here who posted that, also very smart cookie so worth searching by the user account and seeing what other knowledge can be gained

FYI, I've just been looking at this in my 2010 JDM STI, and there is a parameter that moves between 0 and 1 (0 closed , 1 open), and it pro-rate the cruise vs non-cruise table values based on that parameter (so when its changing state it could be like 0.68 for example), so will use 68% of the non-cruise value and 32% of the cruise table, which is quite nice, it transitions between the two rather than a hard cut over.

I imagine this (RAM) address will be completely different by Rom, mine is FFFF87CC (single precision float type) for Rom AZ1G800S