Arctictech wrote:
i was beginning to think of ways to import the tables. but im not that familiar with this program just yet. it has a shorter learning curve than UTEC and FAR better interface (utec does not have a sourced GUI)
ROM disassembly for finding maps really isn't all that difficult if you have a ROM you can cross reference. It's how I was able to define your ROM, actually. Just pulled up CF48D and CM30B in wols and searched for the CF48D values in CM30B haha Unfortunately, I have to do it manually so it takes a decent bit of time. Hence why I always promote others to take up disassembling their own ROM. It's really not as difficult as many think once you get past the initial learning curve and with a ROM like CF48D to cross reference, it's basically the easiest ROM disassembly could possibly be
The main issue arises with ROMs from vehicles other than G35's and Z's, as they don't line up quite so well.
Arctictech wrote:
BTW, i looked at your current rom. that thing is soooo B.A.
I appreciate the kind words! But I wish I could show you the real thing haha What's provided is just a sliver of the total maps actually defined for CF48D. But the issue is that most of them are values and aren't easily comprehensible, so a majority of them would be of no use to others until I eventually analyze their logic. But it has taken quite some time and effort to get it to where it is now
I’m always glad to help! A great place to start would be to open CF48D and CM30B in wols, then go to the location of the ignition timing maps for both. You should be able to look at the surrounding data and start seeing some patterns. Definitely checkout the wols guide I linked in the Updated A2L definitions thread