John Dowson

Ah, one more thing that is relevant to this request.... Currently this facility is only available to registered/licensed copies of FSUIPC. I can allow this facility to be used in unlicensed copies if needed/requested. I have no issues allowing this. I was previously going to allow this but decided not to due to some strange responses from other freeware developers when I broached this subject... John

Hi Volker, I will not be adding/allocating offsets for lvars for specific aircraft. If I started doing this, there would be endless requests for this in MSFS - I hope you understand this. I have implemented a mechanism to allow users to add any lvar to a free offset area. This is, hopefully, relatively straightforward to do. Please see the Advanced User guide, P44 section Adding Lvars to Offsets. If you have any issues doing this, I can help. To be clear, this post concerns adding simvars, or A type variables, not any other variable types. Regards, John

Where have you installed FSUIPC? If you have installed in a windows protected folder, such as under Documents or Program Files, then re-install under a different location. There must be an ini and log somewhere, or FSUIPC will not function as expected. Try re-installing in a different location. I really cannot help you without seeing these files, and they must be in the same location as the FSUIPC6.dll, the FSUIPC6 installation folder. John

Activate logging for Buttons & Key presses in the FSUIPC logging tab, and also activate logging for events to see the events from the FS. Yes - use the DontLogThese ini file option - see the Advanced User guide for details. Many aircraft, especially in MSFS, continually send various events, which are different for each aircraft. You can ignore these by using that ini parameter, best used in the [Profile.xxx] sections as they are different for each aircraft. John

Do you have an FSUIPC4.key file in your installation folder? The error message indicates that this file is not available. Have you tried entering your registration details again to validate/re-register?

So the gear lever button isn't recognise, in FSUIPC SPAD.next or the sim? Are the other buttons/switches recognised? If it is just the buttons for the lever, then this would indicate that the buttons on the gear lever are no longer working. Does it still work in FSX? If so, and this is configured in FSUIPC4, then the same config should also work with MSFS. And are you assigning in SPAD.next or FSUIPC? If assigning in SPAD.next, then you should contact support for that program. John

Your log and ini files will be in the same folder as the FSUIPC6.dll. As I said: Check if you have numlock on or off - this will affect what is being sent when using the numeric keys. John

Have you assigned the switches in FSUIPC? Does FSUIPC recognise the switches so that you can assign? I really think that you need to contact support for from OpenCockpits on how to configure this device. Have you tried that? John

Me neither! Let me know how you get on. I could look into adding an MWV sentence at some point if absolutely required, although I'm not sure when I will have time to look into this at the moment. I will add it to my 'todo / to investigate' list, and let you know when I get time to look into this in more detail. I am currently very busy just keeping up with the MSFS releases (as well as the P3D ones....)! John

Then maybe ask in that forum about this... I can't really help when you just keep saying 'it doesn't work'. What are you trying to do exactly with FSUIPC? What gave you tried? Are you talking about a button or key press, or something displayed? I really have no idea what your issues is at the moment... If using PMDG aircraft, then many standard offsets and controls do not work. To use this aircradt with FSUIPC, you need to use the provided PMDG SDK (custom controls), and for display/output/.read offsets you should look at the provided document Offset Mapping for PMDG 737NGX.pdf. Maybe also take a look at this FAQ entry: John

FSUIPC will not affect any features like this in P3D. Maybe try renaming the FSUIPC6.dll to FSUIPC6.dll.unused (temporarily) so that it is not running to see if this is still working as you expect in P3D. So shift+2 is assigned to accomplish this (default assignment) in the sim? This should still work, unless you have changed this or assigned the same keypress in FSUIPC. So you had the red button assigned in P3D to achieve this? Did you assign to the same control in FSUIPC? Do you have controllers still active in P3D or are they disabled? I am still unsure of what your actual issue is, or where your assignments are. Can you attach your FSUIPC6.log and FSIOPC6.ini files which may give me more of a clue as to what you are asking... Your FSUIPC6.log and FSUIPC6.ini files are located in your FSUIPC6 installation folder. If you do not know where that is (you should do - you installed it and chose or accepted the default installation location...) then use the Open Folder button in the FSUIPC6 logging tab. This will open a windows explorer panel showing the FSUIPC6 installation folder. If you cannot see the .log and/or .ini files, you have explorer configured to hide known file types. Change your explorer options so that you can see the correct file extensions (consult the appendix in the installation manual if you do not know how to do this). No idea what this means! What 'signature'? John

You posted in the sub-support forum that is specifically for FSUIPC7 / MSFS - I have moved your post to the FSUIPC4/5/6 support forum. Do you mean P3D v4.3? FSUIPC versions 5 and 6 are compatible with that version. Or are you using FSX with FSUIPC4? Please clarify, and make sure that you are using the latest (and only supported) version of FSUIPC for the FS you are using. No idea! What exactly is the problem? What do you mean by ' I can't get it to work'? Does it work without FSUIPC? What are you trying to do with FSUIPC? Thats no problem, but you still need to describe what your issue actually is. Maybe also try support for the EFIS opencockpit, id your issue is with that software... John

Please check for similar topics before posting....see John

Ok. Please also see the following post, and also the links that it references: John

The Gear Up and Gear Down work fine in those aircraft for me, so something else must be going on. Can you please do as I previously advised: Thanks, John

What is the problem with assigning to this button - is it recognised by FSUIPC when you press it? Not sure what you mean by 'clickable area' on this context - what has this got to do with key presses? Can you please explain. Are you sending key presses to P3D via button assignments, or assigning key presses in FSUIPC to send controls? Could you show me your FSUIPC6.ini and FSUIPC6.log files. For the latter, activate logging first for Buttons & Keypresses as well as for Events (non-axis controls), and generate a log where you press your keys or buttons that are not working as expected, and I will take a look. John

event.intercept intercepts offset writes, not actual events. I don't see how this can prevent the flight plan from being deleted (if that is the case...), intercepting this can only prevent the location of the flight plan held in the offset from being overwritten. The current flight plan path is held in offset 0x0130. You can try to intercept that and prevent that being cleared, but you would still want to write the actual flight plan to that offset when it is received. You could possibly copy the floght plan to another location when received, of you can set the location for the flight plan in the other add-ons that use this. Otherwise, I would try to stop the add-on deleting the flight plan on touchdown, if possible. Maybe contact the support for this add-on to see if that can be done. John

So you cannot even assign the axis in the axis assignment panel? Is anything on your device recognised - any axis or button? No mod will fix the controller not being recognised - this is a windows issue. Can you please show me your FSUIPC7.log, FSUIPC7.ini and FSUIPC7.JoyScan.csv files and I will take a look. John

Hi Draci, This is VERY strange! I don't really have a clue on what could be causing this.... The 'Mode: FREEZE_ATT...' log line is just a log message of events received from the FS - FSUIPC just logs these and takes no action, so it should not affect any functionality. There are no messages indicating simconnect data stalled or FSUIPC reconnected either, so it looks like data is still being received. FSUIPC is not quitting. In fact, you have a log message from a lot later: 12464485 **** Restarting traffic scanning due to non-reception **** and no shutdown messages, so either FSUIPC was still running when you attached the log file, or it has crashed. If P3D is still running, then FSUIPC is still running. Vheck the windows event viewer though, to see if windows is logging anything there when this occurs - show me anything relevant you find there. Try setting the stall times to negative numbers - this will then just log a message when stalled rather than re-connecting. Use the following: TrafficStallTime=-1 NormalStallTime=-1 Also activate logging for Buttons & Key presses as well as Events. If you do this, the next time you get this issue try pressing an assigned button and see what gets logged - you can attach the log again here and I will take a look. John

Maybe it will. What wind smoothing options have you set? See the Advanced User guide for details on wind smoothing options. May be better to ask on those posts what wind smoothing settings should be used to counter-act this problem with Rex. John

👍

Do you have any references/links? That sounds like a problem with Rex and I have no idea why anyone would think just installing FSUIPC would solve this issue. Sounds like you need Rex support really... John

Ok, thats strange. This was certainly working last time I checked, I will check again. Ok, I have them - I'll check tomorrow and let you know. I understand...I haven't done any recreational flying for a long long time now, only short flights to look into other peoples issues... John

Hi. I have no idea what problem you are referring to, or why you would think that installing FSUIPC4 would solve this problem. What led you to believe it would? John

Isn't that where I said it should be, and where you should be putting your *.hvar files?