Bryn Posted April 14, 2013 Report Posted April 14, 2013 Hi, The documentation says that 0x3130 doesn't work for writing in FSX. However, I just stumbled on having this work for writing when I also wrote a new flightplan to the sim via 0130. Anyway, that's that, for verification. Cheers, Bryn.
Luke Kolin Posted April 14, 2013 Report Posted April 14, 2013 Fascinating. So to confirm, you just wrote the new PLN to 0x130 and 0x3130 got updated? Cheers! Luke
Bryn Posted April 14, 2013 Author Report Posted April 14, 2013 FSUIPC_Write(0x3130, 12, fn, &dwResult); FSUIPC_Write(0x0130, 256, a, &dwResult); FSUIPC_Process(&dwResult); where fn is a pointer to the flightplan, and a is a pointer to the flight number.
Bryn Posted April 14, 2013 Author Report Posted April 14, 2013 Woops, a is the flightplan, and fn the flight number.
Pete Dowson Posted April 15, 2013 Report Posted April 15, 2013 The documentation says that 0x3130 doesn't work for writing in FSX. However, I just stumbled on having this work for writing when I also wrote a new flightplan to the sim via 0130. Hmm. Interesting. I'm not sure whether this means it ONLY works if you first set a flight plan, or whether it was a change in SP1, SP2 or Acceleration after the initial tests on 3130 were done. I wonder ifyou can change the tail number and airline name used by ATC too (offsets 313C and 3148)? Seem less likely because they are paint jobs too. Obviously it is more useful to be able to change the flight number in any case. Anyway, that's that, for verification. Thanks. I'll update the doc ready for the next release, whenever. Regards Pete
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