John Dowson

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

First, you posted in the FAQ section - I have moved your post to the main Support forum. Please post all support requests here. When you unpack the FSUIPC installer (you do not say which version you are using) you should find the installer exe (Install FSUIPC5.exe or Install FSUPC4.exe) together with a manual telling you what is installed and where, and how to register. When you run the installer, it should also create an installer log file (FSUIPC5 Install.log or FSUIPC4 Install.log) in both the directory where you ran the installer and in the install location. If you ran the installer, FSUIPC will be installed in a folder called 'Modules' under your FS directory. Under this will be another folder called FSUIPC Documents where the manuals for FSUIPC are installed as explained in the Installation and Registration manual. If you ran the installer and FSUIPC is installed correctly, you should see an FSUIPC... entry in the Add-on menu. If you open FSUIPC and go to the Logging tab, there is also a button called something like Open Log Folder which will open an Explorer window showing the contents of the Modules folder, where FSUIPC is installed. John

This can't happen, unless you remove the calibration entries from the ini file. Check that the axis haven't been re-assigned in P3D - its better to disable controllers completely in P3D if you are doing all your assignments in FSUIPC. Anyway, glad your problem is solved. John

In your Modules folder, under your P3D installation directory, where FSUIPC5 is installed. You can also use the button 'Open Folder' in the FSUIPC Logging tab which will open an Explorer window showing you the location & contents of this folder.If you cannot see the file, you may have to change your Explorer view options to see the file extension (you need to un-check the option 'Hide extensions for known file types'). John

FSUIPC5 runs as a dll within P3Dv4. It cannot possibly be running without the sim running - you will not see it in the task manager, only P3D itself. And if P3D is still running, you should not be able to restart it until you have closed the one already running. Did you try closing down P3D fully and restarting? If you still have your issue, please attach your FSUIPC5.log file (after you have closed down P3Dv4) and also a pic of the actual message you are getting. John P.S. You posted in the Announcements section. I have moved your post for you. Please post all support requests here, in the main support forum, thanks.

Are you running both the FS and FSRADIOPANEL as administrator? Both programs need to be ran at the same privilege level. The firewall shouldn't affect communication between processes on the same machine, but that depends on the configuration so you may wish to check this. You could post your .log and .ini files and I'll take a quick look to see if there is anything unusual. Other than that, I think you would be better off contacting the support for FSRADIOPANEL Are you getting any errors at all? John

You also seem to have not calibrated your spoilers correctly: 1=0Z,B,0,0,66067,16383 -{ DIRECT: SpoilersEntering=SPOILERS_ARM_OFF }- 2=0Z,B,0,0,66066,15000 -{ Entering=SPOILERS_ARM_ON }- 3=0Z,B,-16384,10237,66068,0 -{ Entering=SPOILERS_ARM_SET }- You have conflicting ranges: 0-0 for both SPOILERS_ARM_OFF and SPOILERS_ARM_ON, and -16384 - 10237 for SPOILERS_ARM_SET. You are probably better off calibrating a null zone for your spoiler. From the FSUIPC User Guide (section: The Easy Step-by-Step way to calibrate your controls, P42): The Spoiler (speed brake) control is a little special. It has no “centre” as such, but the facilities for setting a centre in FSUIPC are used to calibrate a zone on your lever in which the spoiler should be “armed”. You don’t need to do this, it is options: if the two centre calibration values are the same (i.e. there is no centre “zone”), then there is no arming action taken by FSUIPC. If, however, you do calibrate with a centre zone, then the values from “minimum” (the left most value), or lower, up to the lowest of the Centre values will all select spoilers down (i.e. parked). The centre zone will arm the spoilers, and the range from the higher of the two centre values up to the maximum (the right-most value) will actually operate the full range from 0% to 100% deployed. Note that if you arm the spoilers when on the ground, P3D will deploy them to 100%, as if you have just touched down. However, they should return to the “armed” position when the throttles are advanced. John

Looks like you didn't activate the logging for Axis controls, or you activated and clicked the 'New Log' button so you started a new log file which you did not attach. Could you do this again please, make sure the Axis control is being logged, and not start a new log so I can see the complete log file. Thanks, John

Can you check your assignments in FSX - if you are assigning everything in FSUIPC it is better to disable controllers completely in FSX. If that is not the issue, then I will need further information. Please activate logging of axis controls (from the FSUIPC logging tab, start the sim, load your aircraft and then move your spoiler axis through its full range, then close the sim. Post again and attach your FSUIPC4.ini and .log files and I'll take a look. John

As SIOC is installed in your 'Program Files (x86)', you probably need to run this as an Administrator. If you do this, you must also run your sim with the same privileges, i.e. also as Administrator. Have you tried this? Anything connecting to FSUIPC needs to be ran at the same privilege level, and as FSUIPC is embedded in the sim, this means that you have to run your sim at the same privilege level as SIOC. If thats not the issue, then you really need to continue your support with SIOC. Also, I take it (hope!) that you are running both SIOC and your sim/FSUIPC on the same pc? If not, it (obviously?) wouldn't connect - if you are running SIOC on a separate PC then you would need WideFS for it to be able to talk to FSUIPC on a separate PC. If SIOC and your sim (FSX or FSX-SE) are running on the same machine, the firewall shouldn't be an issue. John Later: do you have an error code from SIOC from the connection failure? This may also help....

Yes, your registry entries look a right mess with conflicting/duplicated GUIDs for different devices. It would have been a lot easier to resolve these issues if you had used the 'JoyLetters' facility (please read about this in the User manual), but its to late for this now, although you should activate this once your problems have been solved. You say: Do you mean that you have added the Flight Illusion GSA-055, as this is now recognised? I think the best way forward with this is if you could do the following: 1. First, disconnect your new devices (Flight Illusion GSA-055 and Brunner Yoke) and uninstall any software/device drivers for these. Then reboot. 2. Start P3D. load an aircraft and then stop the sim. 3. Attach the newly generated log, ini and JoyScan.csv files - better to attach the complete files rather than copy/paste. Once that is done, we can use the files to work out what needs to be removed from your registry and ini files. After that, you can reconnect your devices and install any software needed and then we can take a look at the files again. John

If you have fps issues for a complex add-on only, it wouldn't be your sound interface. If you think you have an issue with FSUIPC, please raise a separate topic/thread explaining your problem, but I can't remember any fps issues that are due to FSUIPC so I think your problem lies elsewhere. Sometimes stuttering/low fps can be caused by the autosave option being used with complex aircraft add-ons, so if it is only happening on autosave you could check that. John

Presumably he's talking about the P3D Sound options 'Windows Sound Devices', where you an select the sound devices used for primary, voice and voice capture (mic). These default to the windows default sound devices. I've no idea why this would affect the FPS so much though.... John