Flyer626

Did a takeoff and landing with flaps configured with regular axis assignment and all the detents. No issues. Guess PMDG is perplexing software that needs somethings there way and others not, I did learn somethings that I didn't know before so this was not a wasted exercise. Thanks for your help and time.

I am aware of the power issue and it only affected the throttles and that is why they are calibrated according to PMDG requirements. Flaps did not have any issues when set it with regular calibrations on speed or power. I had to do a firmware update on my Intel chip due to it being unstable as informed by my computer maker Dell. I will try your suggestion first about rotor brakes before I revert back to regular flaps calibration.

contacted the throttle maker, they said they make the throttle with PMDG in mind. Not a hardware issue. I don't use LINDA. What were you referring to about roto brakes settings, don't understand or know anything about it. Since my flaps were working with the regular axis assignment I'll will try that again. They worked on the ground with engines running but not while I was flying or landing,, have to know why is that. Very puzzling.

for when you return, yes I can custom control a button. right now I can just turn it off have to figure out how to turn it on, it's a light button

I now assigned a button with the value 74702 for flaps one, no movement. I would have to presume by this that it will not work for me as an AXIS ASSIGNMENT as we have tried. If you know of something else that maybe is wrong and interfering in someway from making it operate let me know, thanks FSUIPC6.log

I saw nothing happen. I will now try to assign a button for a flap setting. I know I have a button set for flap incr and decr and it does work. FSUIPC6.ini FSUIPC6.log

I have made many attempts to configure this,, this is the last one, the numbers look right but no movement occurs. My throttles are set up for a PMDG 777 and they work fine. Curious thing my spoilers are set up the regular way and they work in the aircraft in the simulator fine. The buttons set up for incr and decr flaps also work fine. I use an add on util for voice control of my flaps and that works also. Just was trying to configure these in case support for voice control goes away with a windows update in the future as a back up. The add on voice control util is longer supported in P3D, so I don't expect an update when change occurs. Thanks for the help, just not sure what I else I can do to make it work. FSUIPC6.ini

6=2R,D,16383,16000,74703,0 -{ DIRECT: (Unused)Entering=Custom control: <74703> }- 7=2R,B,12159,11767,74704,0 -{ Entering=Custom control: <74704> }- 8=2R,B,7656,7272,74705,0 -{ Entering=Custom control: <74705> }- 9=2R,B,3183,2583,74706,0 -{ Entering=Custom control: <74706> }- 10=2R,B,-1762,-2162,74707,0 -{ Entering=Custom control: <74707> }- 11=2R,B,-5998,-6398,74708,0 -{ Entering=Custom control: <74708> }- 12=2R,U,-13117,-13517,74709,0 what I am really asking is how to enter the numbers on left side into the axis assignment boxes, if I leave them empty I get the current file. I am not able to manually enter anything into the boxes and if I manually change the file it will just get overwritten. FSUIPC6.ini

I did actually put those control numbers in correctly but the program changed them because I did something incorrectly. That is what I am trying to figure out. Please be patient, there are no step by step instructions for doing this like there is for buttons and keys. So excuse my frustration, I will get it corrected but there is no rush on my part. I am using sort of trial and error procedure on my part. FSUIPC6.ini

I'm doing something wrong but i don't what Prepar3D 2024.10.16 - 13.21.10.03.DVR.mp4 FSUIPC6.ini

another attempt, still no movement of flaps FSUIPC6.ini

Not working for me, what did I do wrong? FSUIPC6.ini

don't exactly know what I did but now I have all my detents working including 30. I did reset the flaps in joystick config and started setting them again. This time it worked but going flaps up sometimes I have to play with handle to make it work, can't figure that one out. My axis assignment is just flaps, not flaps set that wouldn't work. You can compare the difference that is why I sent an updated file. thanks. Any feedback is always welcomed. FSUIPC6.ini

unable to config flaps 30 but all others work on my throttles, up, 1,5,15,20,25. since this is a boeing 787 throttle could that be the issue. If it is I will use a button to get to flaps 30. FSUIPC6.ini

I did not know about the key file, sorry, my apologies. I also do not believe your software has anything to do with this event but I was pointed in your direction by the iflly forum by someone who had the same issue and they deleted the ini file to resolve it. I don't and won't do that. This btw is a Pre3D plane not msfs. Does the event log show anything of that might cause this. I will go back to the ifly forum for help if it really is there problem.

I'm hoping you can explain why at cruise altitude this happens, Starts climbing then recovers, yoke also goes forward as climb starts. Sending files from what happened with the rest. Hope you have Happy New Year. 7206657 EVENT Cntrl= 66124 (0x0001.txt FSUIPC6.ini

I do assign the rudder an axis assignment, then I go and do a configuration for calibration. This part is very unconventional, I reset the rudder and do not set them again. It seems to have a default setting, maybe the firmware does it, I don't know but it then works perfectly. Old adage don't fix it if it is not broken might apply. I go down the runway on takeoff and rudder is very smooth and makes small adjustments accordingly. I did make the other change you advised.

will do, btw under windows settings bluetooth the device does appear and the old rudders device is gone. FSUIPC6.JoyScan.csv

I just installed new turtle beach rudders to my system, I have calibrated them and they seem to be working fine. I had thrustmaster rudders before and they seem to be still in the profile not the new turtle beach. Why is this?FSUIPC6.iniFSUIPC6.iniFSUIPC6.iniFSUIPC6.ini FSUIPC6.log

I configured the settings for the model -9 manually and loaded a model 10 and that configured the settings automatically. I do have that line in my .ini file ShortAircraftNameOk=Substring. Guess I don't need your help but thanks.

why is it that my settings do not apply for different models of 787 when starting. This is what my config looks like but only the -8 model is working with right settings [Profile.787] 1=QualityWings 787 2=Boeing 787

thought you would say that, I just disagree.

I think this is now resolved, cleared the "V" axis from FSUIPC and the issue has gone away. I never saw this setting in FSUIPC until I looked after this button was pushed that extended the spoilers and it became visible in axis assignment without even scanning. The Hotas joystick has no V axis properties. Where it came from I have no idea since it has been there right from the start before I even assigned the spoilers to the X axis and finished the calibration. Mystery.

just a quick follow up after scanning on axis set up and I found a spoiler set on the V axis, ??? Have no idea where that came from or what is a V axis to begin with. I hope I cleared it, will let you know.

I have now checked again, I did notice on start up my controllers were enabled again, don't why this isn't saved once it is done once in P3D. Do I need to change it to Raw input or just leave it as Direct Input. The issue still exists with controller not enabled. If you need screen shots to show you this, I have to find another way then using V button to take the screen shot in P3D. Hotas joystick is allowing any and all buttons to deploy the spoilers on start up, I don't know where or who is making this setting. Like I said it only happens once and even without reenabling the settings it does not do it again. Is it the aircraft or Thrustmaster doing this setting I don't now know where it is coming from. The setting for my spoilers on my TQ6 quadrant is tricky but it works correctly to arm the speedbrakes right, don't know if I want to do anything since it works fine the way it is.