John Dowson

Button assignments are greyed out when they have multiple assignments. That assignment is on Joystick 4 button 8, and assigned to THROTTLE3_DECR, so must be this one: That should be obvious, especially if you check the format of the button assignments in the manuals... These are the other assignments on that button:

Strange - maybe check the power management settings on your USB hubs... I will check to see if I get the same behavior, just out of interest. I don't think it can be related to your actual trim wheel, more to do with the JF Arrow I would think... John

Strange, as they should be fired regardless of how triggered, but that must be due to the PMDG implementation. I guess its ok for you as long as you only change the state via 3rd party apps that use the custom control. You could check to see if any lvars hold the states you require, as suggested by Paul, which would be more reliable (if there are any!). John

The latest version of FSUIPC6 is only compatible with P3Dv4.3 and later. You should update your P3Dv4 installation to the latest available - there is no reason not to do this, it is a free upgrade. Compatibility with P3Dv4.1 was removed many versions ago... I cannot see how this happened after a mainboard battery change either, unless you (or your customer) was previously using an older v4.1 compatible version of FSUIPC6. Regards, John

Hmm, sounds strange - especially as you say only sometimes.... You could try logging (Buttons + Switches and keypresses) to see if the log reveals anything when you need to press twice. And what do you mean by 'first press takes me to wherever I was looking at'? If you are already 'looking at that', then do you mean there is no change in the view on the first press? Ok, but probably not of much interest. Its just a lua script that cycles between camera views. John

Adding to what Paul has said, MSFS sends various pause/unpause events while starting-up and I think the ready-to-fly flag also changes during start-up, but this behavior has changed over the various updates and am not sure of the status of this offset at the moment, I will check it when I get a chance, However, a useful offset for MSFS in 0x062B (PLANE IN PARKING STATE). This contains 1 when in the main MSFS menu system, and 0 otherwise, and so can be used as an indicator if a plane is loaded or not, regardless if the pause state. John

I have moved your post to the MSFS/FSUIPC7 forum. I don't know. Why don't you try it? I time-limited trial license is available in a post at the top of this forum. John

The events should be logged, and you should be able to intercept them using the event.control lua function, as Paul said. I don't know why you are not seeing those (or any) events logged...maybe they aren't being used? Try assigning a button press to those events, and see if they are logged when you send them. John

No, I didn't think it would make much difference... Ah, ok....I should have asked to see your logs first.... Yes, forget that version I posted - I will remove. Ok. Did you try closing the com object before FSUIPC exited? You can do this in an event.terminate function. John

These are SimConnect controls, and can be seen in the exported controls list document, in your FSUIPC document folders. No, they won't - the camera system is very different in MSFS. To implement a 'pan reset' function, you can do the following: - first, create a 'custom camera' for your view. You can do this by hitting Ctrl + Alt + a numpad key (0-9). The number will be the number of the view. You can then switch to this view using Alt + the assigned numpad key you selected - assign your button to the Alt + numpad key in FSUIPC, using the left-hand side of button assignments dialog I recently provided a lua script to cycle between views for another user - see the following if interested: John

The throttle configuration can be tricky for the aerosoft airbus. There is plenty of information on the various support forums that may help, but I don't have this aircraft and can't really advise. Also, you don't say what FS or version of FSUIPC you are using, or what type of controllers you have... The following links may help with the throttle configuration: https://forum.aerosoft.com/index.php?/topic/143380-airbus-professional-fsuipc-settings/ https://www.avsim.com/forums/topic/561341-aerosoft-airbus-professional-throttle-settings-using-fsuipc/ There are also various posts on using lvars and/or Linda with the airbus. But it really depends on what you want to achieve - your question is far too general to help any further. I suggest you try and configure and post more specific questions if you have any issues (and can't find an answer already posted!). John

No idea. I'll try switching to using an axis control here to see if its the same for me. But I don't think this is an issue to be worried about. John

But using an axis is fine. Just reverse it in a profile specific calibration for the JF Arrow. Why don't you just try that? John

No, just one of them. You cannot run both at the same time (well, you can by changing the class name of the WideClient, but there should be no need to run both...). I'm a bit busy at the moment but will post the details when I can....within the next few days, sorry but I can't do this any earlier. John

I don't know, but if using the PMDG 777, you should look at the PMDG SDK for that aircraft to see if the information is held in the PMDG-specific offsets. First thing to do is to check the PMDG_777X_SDK.h file to see if anything in there looks like what you need. John

WideFS7 is what you need then. However, this should also work with FSUIPC7 running on the client machine, and would save you having to buy an additional license. So try FSUIPC7 on the client machine first, otherwise I will look into providing you with a trial license for WideFS7. Sure. I will create a separate topic for this later today or tomorrow. John

First, you are using quite and of version of FSUIPC6, v6.0.12. The latest (and only supported) version of FSUIPC6 is v6.1.6 - please update. After updating, produce a short log file showing your issue: activate logging for Axes controls, load your aircraft and then move each brake through its full range, then exit FSUIPC/P3D and show me the FSUIPC6.log file. As you are also using Linda, it may be a good idea to disable Linda for this test. And your log shows that you have installed FSUIPC6 under your Windows Documents folder. This can cause issues - it is better to install in a non-protected folder and just have your add-on.xml file under the Documents\Prepar3D v5 Add-ons\FSUIPC6 folder. You should consider installing in a different folder when you update (and remember to move all your files across to the new installation folder afterwards). John

They are available once you have registered your FSUIPC license. You do this by tunning the installer - there is a dialog at the end of the installation process to register your license. Enter your registration details there and click the Register button to validate and generate your FSUIPC7.key file. John

No. Its just that the Pan controls are not working correctly in MSFS via SimConnect. For view controls, best to assign your buttons/switches to the default MSFS key bindings for such controls. If there is no binding for that in MSFS, you can assign a key binding to the control in MSFS, and then assign your button to that key binding in FSUIPC. Try that and let me know if thats ok, or I can look into this further for you but will take me a couple of days to get around to this (working through the support backlog!). Cheers, John

Hi Ron, Why don't you just create a profile-specific calibration for the Arrow and reverse it there? You don't need to use profiles for anything else if you don't want to. But there is no issue with creating profiles. In fact, its a good idea to use profiles for most MSFS aircraft, especially add-ons, as there are many controls that can only be accessed via lvars or hvars, and as these are profile specific it is always better to use these in a profile. I do have the JF Arrow but have not noticed this issue. I have assigned to the Bravo trim wheel, which uses buttons, so I have assigned to the trim offset for both fast/slow increments and decrements. I don't assign to the elevator trim axis so haven't noticed this issue. If interested, I shared my Bravo assignments (including trim wheel) in this post: Cheers, John

Hi Tom, Presume you mean WideFS7. That product is still with Pete. I don't think he provides trial licenses for WideFS7, but I can ask him if its ok for me to generate one for you (assuming that a time-limited license is possible with WideFS7, not 100% sure on this). You can actually now run FSUIPC7 in a client machine. This is experimental and undocumented, but allows a full copy of FSUIPC7 to be ran on the client machine. It is different to the WideFS solution in that it will maintain its own offset table, and doesn't communicate to FSUIPC7 on the FS machine. However, all offsets populated by the FS should be available and the same. I have been meaning to create a post on how to set this up and use FSUIPC7 on a client machine for a while but have not had time yet. I could do this soon (i.e. in the next few days) if you would like to try this. Regards, John

Hi Gary, ok, no problem - glad you have found the cause of your issue, and thanks for reporting back. Cheers, John

Could you also attach your FSUIPC7.JoyScan.csv file please...

Could you attach your Runways.txt file please, if that exists (you can zip it if its large). Also, if there is a MakeRwys_Scenery.cfg file produced in the P3D root folder, please ZIP it and also attach. Thanks, John

Hi Torsten, please try the attached version. Let me know how it goes, and check your FSUIPC7.log file for a message starting '*** Calling OpenHid with ...' and post that if you have issues. BUT, looking at your HIDScanner output, it seems as of the issue is with the Manufacturer, Product or Serial number (and/or GUID, which seems to be the same for both cards), which are all null/empty. Even though the VID is 0000 (which IS ok, as your USBKeys card IS recognised), there is still a unique product ID for both cards. Given that, I don't hold out much hope. Have you tried OpenCockpits support to see why these fields are not being populated? John