DrDave- Posted October 31, 2023 Report Posted October 31, 2023 I have received type errors on entries in the myOffsets.txt, shown in the FSUIPC7.log. They are: 8406 *** myOffsets.txt: Invalid type 'Bool' specified for offset entry 0x66C0 and will not be added *** 8656 *** myOffsets.txt: Invalid type 'Bool' specified for offset entry 0x66C1 and will not be added *** 8656 *** myOffsets.txt: Invalid type 'Bool' specified for offset entry 0x66C2 and will not be added *** The entries in myOffsets.txt are: // myOffsets.txt to FSUIPC7 folder // // offset, size, simvar, type, units [, w] 0x66C0, 1, GENERAL ENGINE STARTER ACTIVE:1, Bool, Bool, w 0x66C1, 1, GENERAL ENGINE STARTER ACTIVE:2, Bool, Bool, w 0x66C2, 1, ATC, Bool, Bool, w "Adding Simulator variables (simvars) to FSUIPC offsets" in The the FSUIPC7 for Advanced Users doesn't mention a Bool type. I did copy the entries from a reply to a previous post I entered. Can you let me know what type it should be? Errors_myOffsets.txt
John Dowson Posted October 31, 2023 Report Posted October 31, 2023 1 hour ago, DrDave- said: "Adding Simulator variables (simvars) to FSUIPC offsets" in The the FSUIPC7 for Advanced Users doesn't mention a Bool type. Because there is no such type. Why don't you just follow what it says in the manual - use I32 for the type. The manual even gives an example: Quote 0x66C1, 1, ATC HEAVY, I32, Bool, w John
DrDave- Posted November 2, 2023 Author Report Posted November 2, 2023 On 10/31/2023 at 2:10 PM, John Dowson said: Because there is no such type. Why don't you just follow what it says in the manual - use I32 for the type. The manual even gives an example: John Thanks, couldn't figure that out.
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