25-11-2015, 11:59 PM
Development News
Not technical version of the news:
All goes well, I retrieve the offsets in P3D 3.0 version, it should not be too long.
Technical version for those that are intterested:
Retrieving the fuels offset at each new version was always a pain in the ***. also copying the small numbers embedded in a very long asm code was
subject to errors, in brief: A waste of time and not a 100% reliable work.
So, I'm working on a little function that will automatically search the offsets and write them all in a file ready to copy/paste into my code:
Much more faster and 100% reliable. I loose a bit more time yet, but it will be an overall gain on the long time for future updates.
![[Image: 2015-11-25_232605fueldetection.jpg]](http://orbiter.dansteph.com/screenshot/dansteph/2015-11-25_232605fueldetection.jpg)
For those interested in the code detail: I know more or less where are located those offsets in memory, I assign each tank a very specific content
value like "94.11", "95.22" and scan the memory for those values.
I get a file with the C++ lines of codes ready to copy/past. No risk of errors.
![[Image: 2015-11-25_232605fueldetection1.jpg]](http://orbiter.dansteph.com/screenshot/dansteph/2015-11-25_232605fueldetection1.jpg)
(And no, I don't use simconnect for tank fuel because in some circumstance, the delay is too long)
Not technical version of the news:
All goes well, I retrieve the offsets in P3D 3.0 version, it should not be too long.
Technical version for those that are intterested:
Retrieving the fuels offset at each new version was always a pain in the ***. also copying the small numbers embedded in a very long asm code was
subject to errors, in brief: A waste of time and not a 100% reliable work.
So, I'm working on a little function that will automatically search the offsets and write them all in a file ready to copy/paste into my code:
Much more faster and 100% reliable. I loose a bit more time yet, but it will be an overall gain on the long time for future updates.
![[Image: 2015-11-25_232605fueldetection.jpg]](http://orbiter.dansteph.com/screenshot/dansteph/2015-11-25_232605fueldetection.jpg)
For those interested in the code detail: I know more or less where are located those offsets in memory, I assign each tank a very specific content
value like "94.11", "95.22" and scan the memory for those values.
I get a file with the C++ lines of codes ready to copy/past. No risk of errors.
![[Image: 2015-11-25_232605fueldetection1.jpg]](http://orbiter.dansteph.com/screenshot/dansteph/2015-11-25_232605fueldetection1.jpg)
(And no, I don't use simconnect for tank fuel because in some circumstance, the delay is too long)