Pages: [1]
Author Topic: KFZW map inputs a bit weird in ME7.1.1  (Read 1671 times)
R32Dude
Full Member
***

Karma: +45/-10
Offline Offline

Posts: 248



« on: May 13, 2023, 04:51:10 AM »

I need a little help understanding why KFZW is not using the usual rl and nmot  in the following code.  The zwkfzw0 becomes zwgru eventually, but what are esst_snm16zuuw, esst_srl12zuuw and the map  SRL12ZUUW? 


FLASH_CODE3:8D68EA                 mov     r12, #1F68h     ; map KFZW
FLASH_CODE3:8D68EE                 mov     r13, #3264h     ;  map SRL12ZUUW ; what is this map doing here, what is it?
FLASH_CODE3:8D68F2                 mov     r14, esst_snm16zuuw ; probably nmot, but why the long name?
FLASH_CODE3:8D68F6                 mov     r15, esst_srl12zuuw   ; must be rl ?
FLASH_CODE3:8D68FA                 calls   0, gkf_ipol_S8
FLASH_CODE3:8D68FE                 movb    zwkfzw0, rl4 ;most raw timing value not only uses KFZW like in me7 FR, but uses SRL12ZUUW too?
Logged
prj
Hero Member
*****

Karma: +1072/-480
Offline Offline

Posts: 6035


« Reply #1 on: May 13, 2023, 05:09:14 AM »

Because the axis lookup is done in a different place and the result already stored as a code optimization to not look it up every single time for every map.
That way the axis has to be looked up once instead of four times.

It also makes sure that the same place is read in every map.
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.012 seconds with 16 queries. (Pretty URLs adds 0s, 0q)