svocapri wrote:Does the GIT version support 3.0.3v? I would like to test if it does.
I don't want to answer for Dave but since there are some ini changes and the signature has changed, I can only assume that MegaTunix doesn't yet support it.
svocapri wrote:Does the GIT version support 3.0.3v? I would like to test if it does.
I don't want to answer for Dave but since there are some ini changes and the signature has changed, I can only assume that MegaTunix doesn't yet support it.
Jean
Correction to my previous reply. MegaTunix supported the latest 3.03 that I tested about a month ago, so if something new came out and broke the api/memory layout yet again, then mtx wont talk to it until i incorporate the differences, which won't be for at least a week, maybe less, as I'm tied up with other projects.
svocapri wrote:Does the GIT version support 3.0.3v? I would like to test if it does.
I don't want to answer for Dave but since there are some ini changes and the signature has changed, I can only assume that MegaTunix doesn't yet support it.
Jean
Correction to my previous reply. MegaTunix supported the latest 3.03 that I tested about a month ago, so if something new came out and broke the api/memory layout yet again, then mtx wont talk to it until i incorporate the differences, which won't be for at least a week, maybe less, as I'm tied up with other projects.
Dave,
The memory layout is not broken. It has changed because this is an evolving project so new features are added which need new data. This is not a monolithic program with a fixed predetermined set of data which is why there is something like the ini file. I know you don't like it but nothing gets broken in the other tuning software when the ini changes and the work for the new features is done by the firmware developers (without having to touch the tuning software or recompile it).
I have no problem with whatever approach you want to take with your software but don't say things are broken when they're not. If you can foresee what features and data set will be required for the remaining life of MS2/Extra (and why not MS3) then I'll be happy to put placeholders in the memory layout for these and it will never change again.