John Dowson

You don't need a registered version of FSUIPC to to use the 3rd party interface (to allow 3rd party applications to communicate to the sim via the FSUIPC API/offsets). Is this from the ACARS log? Sounds like its at least connecting to FSUIPC. Are there any errors in the FSUIPC4 log file? Are you running ACARS at the same privilege level as FSX-SE? i.e. if you run your sim with admin privileges, you also need to run programs that connect via FSUIPC with admin privileges. Sorry, but I know nothing about ACARS. Have you tried their support? John

Just checked and it looks like this was a mistake caused by the word processor deciding to auto-number.... I'll change it back to going from bit 0 for the next release. But as I said, the actual bit used hasn't changed! Cheers, John

The only change in the documentation seems to be the bit numbering - it went from 0-12 in the 5.15 documentation and 12 was Instant Replay (Recording Playback was 11), and it the later documentation the bit numbering starts at 1. The actual bits used hasn't changed. Not sure why I changed the numbering...it seems that sometimes we count from bit 0 and others from bit 1. Sorry for the confusion. John P.S. Latest version is 5.155

Hi Luke, bit 11 is not set, for Instant replay its bit 13 - bit 11 is Recording Active. Try monitoring the offset as U16 hex (to log). If you then look at the log, you should see the value together with the log of the mode. John

Take a look at offset 2900. John

Can you not just load the auto-save flight and then save it again with an appropriate name....

Yes, sorry - don't know what happened there. Also looks to be the wrong version (or at least the document). I've just re-packaged and uploaded, so please try again. Sorry about that. John

FYI, FSUIPC 5.155 has been released, containing this fix. John

I will not be including the version number in the zip file name, for reasons that Pete has already explained. The version properties of the installer should reflect the version of FSUIPC that it installs, but I sometimes forget to update this. I'll try to remember in future. I will close this topic.

I think its worth releasing this as a new version (5.155) once its verified. If you could push the changes I'll merge them into the 5.154 release and release later this week. John

Glad you've solved your issue, and thanks for posting the solution!

You can download from SimMarket, or from here: http://fsuipc.simflight.com/beta/FSUIPC5.zip Once the file is downloaded, you will need to extract/unzip it. This is usually achieved by double-clicking the file in Windows explorer. If that doesn't work for some reason, you can right-click and select "Extract All...' (or something similar). Once extracted, there will be two files - a manual (in pdf format) to guide you through the installation and registration process, and an installer (a.exe). Read the manual and run the installer. The registration process starts (in the installer) once FSUIPC has been installed. John

I have no idea what that is - maybe that is your problem - have you tried their support? ...ah, just see you have replied.... yes, what I was going to suggest... What you could also do is monitor offset 0D0C using the FSUIPC logging facilities. You can then verify what you think the software is setting with what FSUIPC is actually receiving. Monitor as U16 and hex, and send to log file (and also FS title bar so that you can see the value). You can then check what FSUIPC is receiving, and we can explain what those values mean. You can also activate the different lights and see the values in that offset change, which may help you. Cheers, John

the offset value is not relevant. Only 10 bits of the available 16 bits are used. No, not as expected. If you set the 2nd bit (bit 1), then this will activate the beacon lights. If it isn't, you are doing something wrong (or you are using an add-on aircraft that doesn't support standard FS controls - you should initially at least try with a default aircraft). As expected? No longer "exists"? What are you talking about! The offsets are always there. The value (decimal or hex) is not important in this offset, you should only be interested in what bits are set or not. If you set that value, then the Beacon lights will be activated (and all other lights turned off). This is basically what the Offset Word Togglebits does with that offset and parameter 0x2 (except that uses a mask so ONLY toggles the 2nd bit) What does not make sense is this sentence! ...I see Pete has also replied. Sorry, but its is really not worth going through the rest of your post. As Pete says, please read the documentation and re-read our previous answers. You seem to have a basic misunderstanding of how this offset works, and we can only explain so many times.... John

Hi Reinhard, I've flagged this to look into when time permits. We're quite busy at the moment (and for the foreseeable future!), so this may take quite a while. Regards, John

First, you posted in the wrong place. Please post all new support requests here, in the main Support Forum - you posted in the Announcements section. Secondly, i do not understand what your problem is. Which version of FSUIPC are you trying to install, and for which flight sim? Did you run the installer? If you are having problems with the installation, please explain more clearly what these are, and attach your install log file. Thanks, John

You could try assigning a button or keypress to the FS control 'Offset Word Togglebits', giving the offset as 0x0D0C, and one of the following parameters 0x0001 - for Navigation lights (bit 0) 0x0002 - Beacon lights (bit 1) 0x0004 - Landing lights (bit 2) 0x0008 - Taxi lights 0x0010 - Strobes 0x0020 - Instruments 0x0040 - Recognition 0x0080 - Wing 0x0100 - Logo 0x0200 - Cabin

I will reoccur unless you disable controllers completely within P3D, as it has a habit or re-assigning. Also, its a good idea to update to use JoyLetters to prevent problems if your Joy Ids get re-assigned (just change AutoAssignLetters=No to AutoAssignLetters=Yes in the [JoyNames] section of your ini). ...saw Pete just replied: Its at the bottom of the 'Controls - Other' page John

You are still misunderstanding! Please read what Pete said, as well as the documentation. There are 16bits for the light toggles (only 10 used), starting at offset 0D0C: You said: No! Its the 5th BIT at offset 0D0C that you want. Not 0D0C + 5 BYTES = 0D11 Its the second BIT (bit 1, from lo to hi) of the 2 bytes at offset 0D0C. As Thomas has said, there are no offsets for these lights (they are non-standard). John

No bother 😉

Las: the key you copied is for FSUIPC4, for FSX, not FSUIPC5 for P3Dv4. The key is therefor not valid. FSUIPC5 is a different product than FSUIPC4 and requires a new key. There are so many topics covering this problem. Please check first before posting. John

There is no '.' after .com - remove that!

No, I've not received anything....How are you doing this? Just forward your registration email to me at jldowson@gmail.com. John

Could you PM me your key details (ie. copy your registration/purchase email from SimMarket, do not post them publicly) and I'll check them for you. John

Can you not calibrate using the Steering Tiler calibration on page 9 (of 11) of the Axis Calibration tab? You should be able to set a null range there. John