galaio Posted January 21, 2015 Report Posted January 21, 2015 Hello Peter. Can you tell me what is the new offset value for the FSX Steam version? Its 11? Regards, João
Pete Dowson Posted January 21, 2015 Report Posted January 21, 2015 Can you tell me what is the new offset value for the FSX Steam version? Its 11? No, it indicates FSX, because the offsets etc should be the same as FSX. I was considering having the Steam version indicator available separately, as I've done for P3D 1.1 - 2.4. Do you need to differentiate FSX and FSX-SE? Originally, in my first release for FSX-SE (build 62607) it was indicating that FSX-SE was ESP, because I put it into the vacant ESP slot in my tables. But this wrecked compatibility for a number of programs. Fixed that quickly. Best if it still indicates FSX, as that is really what it is. After all, I never indicated FSX-RTM, FSX-SP1, FSX-SP2 and FSX-ACC. Pete
Luke Kolin Posted January 21, 2015 Report Posted January 21, 2015 If you have the time, an offset to provide this data (whether the user is running FSX SE) would be really helpful, as well as minor version number of available like what you did with P3D. Cheers! Luke
Pete Dowson Posted January 22, 2015 Report Posted January 22, 2015 If you have the time, an offset to provide this data (whether the user is running FSX SE) would be really helpful, as well as minor version number of available like what you did with P3D. Ok. I'll use the same offset. It'll be in the next interim update, probably this weekend. 4.938d. Pete
Luke Kolin Posted January 23, 2015 Report Posted January 23, 2015 Thanks - I really appreciate it. Cheers! Luke
epwatson Posted January 26, 2015 Report Posted January 26, 2015 What is the offset that is used to distinguish between P3D V1 and V2? I can't seem to find it anywhere and I've read most of this forum and all the documentation, it is possible I might have missed it.
Pete Dowson Posted January 26, 2015 Report Posted January 26, 2015 What is the offset that is used to distinguish between P3D V1 and V2? I can't seem to find it anywhere and I've read most of this forum and all the documentation, it is possible I might have missed it. Please see the Changes document included in the ZIP for 4.938f. Documentation takes longer to update. All recent changes are always covered in the Changes document. Pete
epwatson Posted January 26, 2015 Report Posted January 26, 2015 Much Appreciated Pete, keep up the good work. Eamonn
Luke Kolin Posted March 10, 2015 Report Posted March 10, 2015 Would anyone be able to validate what value is returned by Acceleration? I have SP2 that returns 2 (not 3 as the documentation suggests), so I assume Accel returned 3. It doesn't appear to be, but I don't have a copy to test against. Cheers! Luke
Pete Dowson Posted March 10, 2015 Report Posted March 10, 2015 Would anyone be able to validate what value is returned by Acceleration? I have SP2 that returns 2 (not 3 as the documentation suggests), so I assume Accel returned 3. It doesn't appear to be, but I don't have a copy to test against. Ah, did I write that up wrongly? I'll check. It might be 0-3 not 1-4 as I put. Certainly Acceleration will be one up from SP2. On the other hand I might have deliberately started at 1 to distinguish it from the earlier FSUIPC builds where the value would not have been provided. In that case SP2 should be 3 not 2. What FSX build is reported in the FSUIPC4.LOG file? I'll get back to you when I've checked it out. Pete
Pete Dowson Posted March 11, 2015 Report Posted March 11, 2015 Okay. It is as intended, 1-4, no 0. FSUIPC definitely sets offset 0x3124 as follows: FSX build <= 60905 (ie RTM) == 1 FSX build <= 61357 (ie SP1) == 2 (the Russian version was 61357, all others 61355) FSX build <= 61472 (ie SP2) == 3 else == 4 (Acceleration = 61637) So please check the build number on your FSX.EXE. It is a bit odd if you think it is SP2 yet the EXE has a build number less than 61358! Pete
Luke Kolin Posted March 11, 2015 Report Posted March 11, 2015 No, you were right, Pete - I am battling the flu and didn't see that I was decrementing the value by one to map to a zero-offset array. Even after 28 years, I still make these kinds of mistakes. :( Thanks for looking into it. I'll make some more debug builds to give to my users to see what is going on. Cheers! Luke
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now