simnutzer1962 Posted January 3 Report Posted January 3 I am programming the FSSUIPC5 for my PMDG NGX for P3D. And I have a problem. I wanted to control the flaps by a Joystickaxis. For this I did following things: Opened the PMDG SDK, where I found the following infos about the Flapslever: #define EVT_CONTROL_STAND_FLAPS_LEVER (THIRD_PARTY_EVENT_ID_MIN + 714) #define EVT_CONTROL_STAND_FLAPS_LEVER_0 (THIRD_PARTY_EVENT_ID_MIN + 7141) #define EVT_CONTROL_STAND_FLAPS_LEVER_1 (THIRD_PARTY_EVENT_ID_MIN + 7142) #define EVT_CONTROL_STAND_FLAPS_LEVER_2 (THIRD_PARTY_EVENT_ID_MIN + 7143) #define EVT_CONTROL_STAND_FLAPS_LEVER_5 (THIRD_PARTY_EVENT_ID_MIN + 7144) #define EVT_CONTROL_STAND_FLAPS_LEVER_10 (THIRD_PARTY_EVENT_ID_MIN + 7145) #define EVT_CONTROL_STAND_FLAPS_LEVER_15 (THIRD_PARTY_EVENT_ID_MIN + 7146) #define EVT_CONTROL_STAND_FLAPS_LEVER_25 (THIRD_PARTY_EVENT_ID_MIN + 7147) #define EVT_CONTROL_STAND_FLAPS_LEVER_30 (THIRD_PARTY_EVENT_ID_MIN + 7148) #define EVT_CONTROL_STAND_FLAPS_LEVER_40 (THIRD_PARTY_EVENT_ID_MIN + 7149) In case of these values I calculated the Custom Control values by adding the basicvalue 69632 Then I started FSUIPC and opened the axis assignment. I moved the Lever on the joystick and began to create Step 1 by setting the numbers for "from" and "to" via moving the lever to different values. So I clicked "from", moved it to the second value and clicked "to". In the first case the values were from 16383 to 16180. After that, I used the function "Custom Control" to put in the value, I calculated für the "Flaps 0" Position. In this case it was the value 76773. I did not write any value in to the Parameterline. The 0 are the defaultvalue inside the Parameterline. Then I repeated all the things, I did for further 8 steps. Here ist the Code, I found in the FSUIPC.ini, after i programmed FSUIPC in this way. The Pollinterva ans the RangeRepeatRate were automated set from FSUIPC. [Axes] PollInterval=10 RangeRepeatRate=10 0=1R,256 1=1R,B,16383,16180,76773,0 -{ Entering=Custom control: <76773> }- 2=1R,B,11663,13316,76774,0 -{ Entering=Custom control: <76774> }- 3=1R,B,5702,8593,76775,0 -{ Entering=Custom control: <76775> }- 4=1R,B,2386,4604,76776,0 -{ Entering=Custom control: <76776> }- 5=1R,B,-247,1601,76777,0 -{ Entering=Custom control: <76777> }- 6=1R,B,-3306,-1068,76778,0 -{ Entering=Custom control: <76778> }- 7=1R,B,-7128,-4410,76779,0 -{ Entering=Custom control: <76779> }- 8=1R,B,-13081,-9721,76780,0 -{ Entering=Custom control: <76780> }- 9=1R,B,-16384,-15748,76781,0 -{ Entering=Custom control: <76781> }- The problem is now, that the Flapslever in the Sim does not move to the Flaps 40 position as ist should move, programmed in number 9 of the steps and it does not move to the Position Flaps 0 (what means Flaps up, I think) and stops at the Flaps 1 Position. It seems so, that Step 9 and Step 1 will be ignored. The Lever stops at Flaps 30 and at Flaps 1. Where is my mistake? Thanks a lot.
John Dowson Posted January 3 Report Posted January 3 Those assignments look ok, except that the ranges for flaps 0 and 40 look rather small, try increasing them, and the lower range should be Down only, and the upper range Up only (although not strictly necessary). So try: [Axes] PollInterval=10 RangeRepeatRate=10 0=1R,256 1=1R,U,16383,14580,76773,0 -{ Entering=Custom control: <76773> }- 2=1R,B,11663,13316,76774,0 -{ Entering=Custom control: <76774> }- 3=1R,B,5702,8593,76775,0 -{ Entering=Custom control: <76775> }- 4=1R,B,2386,4604,76776,0 -{ Entering=Custom control: <76776> }- 5=1R,B,-247,1601,76777,0 -{ Entering=Custom control: <76777> }- 6=1R,B,-3306,-1068,76778,0 -{ Entering=Custom control: <76778> }- 7=1R,B,-7128,-4410,76779,0 -{ Entering=Custom control: <76779> }- 8=1R,B,-13081,-9721,76780,0 -{ Entering=Custom control: <76780> }- 9=1R,D,-16384,-14748,76781,0 -{ Entering=Custom control: <76781> }- If you get the same issue with that, activate logging for Axes Controls and Events and see what he log says. Best to do this with the logging console window open so you can see the log in real-time. You can also post/attach it here along with your ini if you can't see the issue and I will take a look. John
simnutzer1962 Posted January 3 Author Report Posted January 3 It did not help. Problem still exists. I attached the inifile and the logfile. This logfile is full of confusing lines and I have no idea, why are so many lines with the terminus "Rotor Brake" is in that file. FSUIPC5.ini FSUIPC5.zip
John Dowson Posted January 3 Report Posted January 3 2 minutes ago, simnutzer1962 said: I attached the inifile and the logfile. This logfile is full of confusing lines and I have no idea, why are so many lines with the terminus "Rotor Brake" is in that file. The ini file you attached is a continuation log file and contains no useful information relating to your issue. Please attach a full log file - do NOT start a new log file. The Rotor Brake control is what the PMDG aircraft use for many custom controls (internally) - the ones in your log have a parameter of 67803 and 67903 which are a 'mouse move' (03) over the control stand trim wheel and speed brake lever: #define EVT_CONTROL_STAND_TRIM_WHEEL (THIRD_PARTY_EVENT_ID_MIN + 678) #define EVT_CONTROL_STAND_SPEED_BRAKE_LEVER (THIRD_PARTY_EVENT_ID_MIN + 679) You can ignore such events by using the DontLogThese ini parameter - see the Advanced User guide for details.
simnutzer1962 Posted January 3 Author Report Posted January 3 Ok, I will do that later, cause I have to do some sports now. My doctor tells me that 🙂. What do you mean with a "full" logfile?
John Dowson Posted January 3 Report Posted January 3 Just now, simnutzer1962 said: What do you mean with a "full" logfile? I mean exactly what i said - do NOT start/request a new/continuation log file - take a look at the log file you attached: Quote ********* FSUIPC5, Version 5.157 (26th June 2020) by Pete & John Dowson ********* User Name="Robert Hammer" User Addr="flightsimmer@marteau.de" FSUIPC5 Key is provided WIDEFS7 not user registered, or expired 23954187 System time = 03/01/2025 15:47:19, Simulator time = 12:59:59 (11:59Z) 23954187 FLT path = "C:\Users\offic\Documents\Prepar3D v4 Files\" [Continuation log requested by user] Running inside Prepar3D v4 on Windows 10 Module base=7FFB97290000 ... John
simnutzer1962 Posted January 3 Author Report Posted January 3 Hi John, this time I just switched on the logfunctions you mentioned and began to operate the lever. I erased the rotor brakes by hand, cause the "Don`tLogThese" did not work in case of the fact, that I did something wrong. But I can not upload the file, cause the compressed file is still more than 6 Mb and it is only allowed for me to upload files till a maximum size of 4.88 Mb.
John Dowson Posted January 3 Report Posted January 3 50 minutes ago, simnutzer1962 said: I erased the rotor brakes by hand, cause the "Don`tLogThese" did not work in case of the fact, that I did something wrong. Its DontLogThese. i.e. under [General] section: DontLogThese=66485,69000-70999,66503,66504,66587 If it didn't work, you did do something wrong - did you check the Advanced User guide on this parameter? 56 minutes ago, simnutzer1962 said: But I can not upload the file, cause the compressed file is still more than 6 Mb and it is only allowed for me to upload files till a maximum size of 4.88 Mb. It shouldn't be that large. Turn off all logging in FSUIPC and restart P3D so FSUIPC starts with no specific logging. Select and load your aircraft on the runway and ready-to-fly. Then, open FSUIPC and set the logging for Axes Controls and Events. Then move your flaps leaver through the ranges and back again, then exit P3D/FSUIPC and attach the log (compress if still too big). If its too large to attach compressed (oy shouldn't be!), you can transfer using one of the free file transfer services (e.g. https://filetransfer.io/ or https://wetransfer.com/)
simnutzer1962 Posted January 3 Author Report Posted January 3 Hi John, thanks for answering. I will do that tomorrow, cause it`s 11 o clock in the evening here, now and I shut down the computer. But one question: In the case of a to big datafile: On which mailadress should I send the datafile? Wetransfer or filetransfer need a mailadress. I can send it also directly to a mailadress, cause a regular mail size could be up to 30 Mbytes and the file has in the moment roundabout 6 Mbytes. But we will see tomorrow, wheather your tips let shrink the size of the datafile. However. I have to go to bed now. Sincerely Robert
John Dowson Posted January 4 Report Posted January 4 11 hours ago, simnutzer1962 said: Wetransfer or filetransfer need a mailadress. I can send it also directly to a mailadress, cause a regular mail size could be up to 30 Mbytes and the file has in the moment roundabout 6 Mbytes. You shouldn't need an email with https://filetransfer.io/ - select the 'share as link' option and post the link.
John Dowson Posted January 4 Report Posted January 4 (edited) You have controllers set to on in P3D: Quote 453 Controllers are set to ON, using RawInput within P3D If assigning in P3D, you should disable controllers in P3D. Your log file only shows FLAPS_SET and AXIS_FLAPS_SET controls (and custom control 85637) - it does not show any of the PMDG flaps custom controls. And the parameters to these controls look to be setting different positions.... So, please disable controllers in P3D (or at least remove any assignments to your flaps lever/axis) and try again, and attach the new log as well as your latest FSUIPC5.ini file. The one you posted before doesn't look quite right - most of the JoystickCalibration ini parameters are missing for some reason.... Can you also please set logging for Buttons & Keys - maybe be necessary to see the range controls being sent... Edited January 4 by John Dowson Further info added
simnutzer1962 Posted January 5 Author Report Posted January 5 Hi John, sorry for the circumstances. Indeed, I forgot to switch off the controllers inner P3D settings. I switched them for the axis on all existing hardware to off, now. So the throttlequadrant levers are controlled only by FSIUPC, now. But they do not move at all. I proofed all my calculations for the values belonging to the Flapslever and I can not find any wrong calculations. And in the SDK for the PMDG 737 I couldn't find any other values than the ones I calculated with. For your information and to check my calculations, written down in the FSUIPC ini file by setting them via FSUIPC. Here is an extract of the values from the sdk file: // Control Events #ifndef THIRD_PARTY_EVENT_ID_MIN #define THIRD_PARTY_EVENT_ID_MIN 0x00011000 // equals to 69632 #endif #define EVT_CONTROL_STAND_FLAPS_LEVER (THIRD_PARTY_EVENT_ID_MIN + 714) #define EVT_CONTROL_STAND_FLAPS_LEVER_0 (THIRD_PARTY_EVENT_ID_MIN + 7141) #define EVT_CONTROL_STAND_FLAPS_LEVER_1 (THIRD_PARTY_EVENT_ID_MIN + 7142) #define EVT_CONTROL_STAND_FLAPS_LEVER_2 (THIRD_PARTY_EVENT_ID_MIN + 7143) #define EVT_CONTROL_STAND_FLAPS_LEVER_5 (THIRD_PARTY_EVENT_ID_MIN + 7144) #define EVT_CONTROL_STAND_FLAPS_LEVER_10 (THIRD_PARTY_EVENT_ID_MIN + 7145) #define EVT_CONTROL_STAND_FLAPS_LEVER_15 (THIRD_PARTY_EVENT_ID_MIN + 7146) #define EVT_CONTROL_STAND_FLAPS_LEVER_25 (THIRD_PARTY_EVENT_ID_MIN + 7147) #define EVT_CONTROL_STAND_FLAPS_LEVER_30 (THIRD_PARTY_EVENT_ID_MIN + 7148) #define EVT_CONTROL_STAND_FLAPS_LEVER_40 (THIRD_PARTY_EVENT_ID_MIN + 7149) If needed, I can send a screenshot of my FSIUPC Windows from the axis settings by wetransfer. Dear John, I am so sorry for my lack of knowledge to get everything working properly. And I am very grateful for your patient help. Best wishes Robert FSUIPC5.ini FSUIPC5.log
John Dowson Posted January 6 Report Posted January 6 Your log shows the flaps lever is sending the correct controls when you move it through its range: Quote 124719 *** EVENT: Cntrl= 76774 (0x00012be6), Param= 0 (0x00000000) <76774> EVT_CONTROL_STAND_FLAPS_LEVER_1 124719 FS Control Sent: Ctrl=76774, Param=0 <76774> 124891 *** EVENT: Cntrl= 76775 (0x00012be7), Param= 0 (0x00000000) <76775> EVT_CONTROL_STAND_FLAPS_LEVER_2 124891 FS Control Sent: Ctrl=76775, Param=0 <76775> 124984 *** EVENT: Cntrl= 76776 (0x00012be8), Param= 0 (0x00000000) <76776> EVT_CONTROL_STAND_FLAPS_LEVER_5 124984 FS Control Sent: Ctrl=76776, Param=0 <76776> 125078 *** EVENT: Cntrl= 76777 (0x00012be9), Param= 0 (0x00000000) <76777> EVT_CONTROL_STAND_FLAPS_LEVER_10 125078 FS Control Sent: Ctrl=76777, Param=0 <76777> 125156 *** EVENT: Cntrl= 76778 (0x00012bea), Param= 0 (0x00000000) <76778> EVT_CONTROL_STAND_FLAPS_LEVER_15 125156 FS Control Sent: Ctrl=76778, Param=0 <76778> 125250 *** EVENT: Cntrl= 76779 (0x00012beb), Param= 0 (0x00000000) <76779> EVT_CONTROL_STAND_FLAPS_LEVER_25 125250 FS Control Sent: Ctrl=76779, Param=0 <76779> 125344 *** EVENT: Cntrl= 76780 (0x00012bec), Param= 0 (0x00000000) <76780> EVT_CONTROL_STAND_FLAPS_LEVER_30 125344 FS Control Sent: Ctrl=76780, Param=0 <76780> 125484 *** EVENT: Cntrl= 76781 (0x00012bed), Param= 0 (0x00000000) <76781> EVT_CONTROL_STAND_FLAPS_LEVER_40 125484 FS Control Sent: Ctrl=76781, Param=0 <76781> 128625 *** EVENT: Cntrl= 76780 (0x00012bec), Param= 0 (0x00000000) <76780> EVT_CONTROL_STAND_FLAPS_LEVER_30 128625 FS Control Sent: Ctrl=76780, Param=0 <76780> 128750 *** EVENT: Cntrl= 76779 (0x00012beb), Param= 0 (0x00000000) <76779> EVT_CONTROL_STAND_FLAPS_LEVER_25 128750 FS Control Sent: Ctrl=76779, Param=0 <76779> 128844 *** EVENT: Cntrl= 76778 (0x00012bea), Param= 0 (0x00000000) <76778> EVT_CONTROL_STAND_FLAPS_LEVER_15 128844 FS Control Sent: Ctrl=76778, Param=0 <76778> 128984 *** EVENT: Cntrl= 76777 (0x00012be9), Param= 0 (0x00000000) <76777> EVT_CONTROL_STAND_FLAPS_LEVER_10 128984 FS Control Sent: Ctrl=76777, Param=0 <76777> 129109 *** EVENT: Cntrl= 76776 (0x00012be8), Param= 0 (0x00000000) <76776> EVT_CONTROL_STAND_FLAPS_LEVER_5 129109 FS Control Sent: Ctrl=76776, Param=0 <76776> 129297 *** EVENT: Cntrl= 76775 (0x00012be7), Param= 0 (0x00000000) <76775> EVT_CONTROL_STAND_FLAPS_LEVER_2 129297 FS Control Sent: Ctrl=76775, Param=0 <76775> 129469 *** EVENT: Cntrl= 76774 (0x00012be6), Param= 0 (0x00000000) <76774> EVT_CONTROL_STAND_FLAPS_LEVER_1 129469 FS Control Sent: Ctrl=76774, Param=0 <76774> 129703 *** EVENT: Cntrl= 76773 (0x00012be5), Param= 0 (0x00000000) <76773> EVT_CONTROL_STAND_FLAPS_LEVER_0 129703 FS Control Sent: Ctrl=76773, Param=0 <76773> So FSUIPC is sending the controls as expected, but if it is not going into the 0 or 40 position, then it looks like those controls are not working as expected (although they are being sent and applied in the FS). I am not sure why. To test this, can you assign a spare button or key (or key combination) to the flaps 0 and flaps 40 custom controls (76773 and 76781) to see if they actually work. If not, then it should be reported to PMDG, You could also try assigning the flaps 0 and flaps 40 range positions to the EVT_CONTROL_STAND_FLAPS_LEVER custom control instead (70346). I am unsure of the parameter needed though - try either 0 or -16384 for flaps 0, and either 16383 or 32767 for flaps 40. And you could also try assigning the 0 and 40 ranges to the Axis Flaps Set control, with a parameter of -16384 for flaps 0 and +16383 for flaps 40.
simnutzer1962 Posted January 7 Author Report Posted January 7 21 hours ago, John Dowson said: 16383 Hi John, unfortunately nothing from your suggested procedures works. Though I put the function of the Flapssetting to a button, it does not work, too. I thought, that the thrustmaster could be defect. I tried another Joystick and the result was the same. No Button and no axis let move the Flaps in the sim. So it can not be the Thrustmaster itself, I think. What`s interesting is, that only the thrustlever works fine in FSUIPC. If I switch on the controls in the P3D controlsection, the Spoilerlever works fine, and the Flapslever does work for Flaps 1 to 30, but does not work for Flaps 0 and Flaps 40. This is all strange. I think, I have to contact PMDG for Support.
John Dowson Posted January 7 Report Posted January 7 2 minutes ago, simnutzer1962 said: nothing from your suggested procedures works. Ok, although that is strange - I would expect the EVT_CONTROL_STAND_FLAPS_LEVER and Axis Flaps Set controls to do something... You can also try assigning to Flaps Decr when entering the lower range, and Flaps Incr when entering the upper range (may be vica-versa). Does assigning the flaps lever directly to the Flaps control (Send direct to FSUIPC calibration), Flaps Set or Axis Flaps Set controls (both 'Send to FS as normal axis) work? If so, and your flaps lever has detents, then toy can use one of those and then set the detents as shown in the user guide (section CALIBRATING FLAPS WITH SPECIFIC DÉTENTES). It was reported that assigning to Flaps (direct) and calibrating with detents works fine for the PMDG737 in this post (although this is with FSUIPC6 and the Bravi, that should make no difference): 3 minutes ago, simnutzer1962 said: Though I put the function of the Flapssetting to a button, it does not work, too. I thought, that the thrustmaster could be defect. I tried another Joystick and the result was the same. No Button and no axis let move the Flaps in the sim. So it can not be the Thrustmaster itself, I think. It is certainly an issue with the controls, and not the thrustmaster, but this should certainly be possible... 13 minutes ago, simnutzer1962 said: This is all strange. I think, I have to contact PMDG for Support. Seems like you had this issue before and got it working in September 2023: ? Why did you not report this in the same topic? Is this a new throttle quadrant - were the flaps previously working correctly (as it says in that post), and if so, how did you assign then?
John Dowson Posted January 7 Report Posted January 7 In the ini you just posted in the other open topic you have, you have the flaps lever axis assigned to Flaps Set, AND are assigning to the custom controls in ranges - that will always be problematic. For now, please assign the axis to Unused, and just use the custom controls. Do you get the same issue? If so, try what I said above, i.e. assign to Flaps (direct) and calibrate with detents.
simnutzer1962 Posted January 7 Author Report Posted January 7 Man, you made my day in case of the levers. With your suggestion to send directly to the FSUIPC calibration, it works perfect. I reversed the levers in the cali9brationsection of FSUIPC and the levers work also in the right directions, now. THANK YOU SO MUCH!!!!!
simnutzer1962 Posted January 7 Author Report Posted January 7 I was testing something. But I erased the control sets in P3D. As I mentioned, it works now very well.
John Dowson Posted January 7 Report Posted January 7 2 minutes ago, simnutzer1962 said: With your suggestion to send directly to the FSUIPC calibration, it works perfect. Did you remove the custom controls being sent in ranges then? 1 minute ago, simnutzer1962 said: I was testing something. But I erased the control sets in P3D. As I mentioned, it works now very well. Ok, glad its working. Could you attach your working ini file here please.
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