Jump to content
The simFlight Network Forums

Flyer626

Members
  • Posts

    31
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    United States

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Flyer626's Achievements

Apprentice

Apprentice (3/14)

  • One Year In Rare
  • One Month Later Rare
  • Collaborator Rare
  • Week One Done Rare
  • Dedicated Rare

Recent Badges

0

Reputation

  1. 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.
  2. 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
  3. 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.
  4. will do, btw under windows settings bluetooth the device does appear and the old rudders device is gone. FSUIPC6.JoyScan.csv
  5. 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
  6. 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.
  7. 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
  8. 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.
  9. 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.
  10. 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.
  11. interesting since my controllers in P3D are not enabled and I will have to look where in my Hotas joystick that assignment since I don't see it and I have checked, but I can see now why this is happening.
  12. hope this helps, it shows what happens. I included the text file to highlight the action consolelog.txt FSUIPC6.log
  13. I know this wayward signal is only coming from my Thrustmaster T-Flight Hotas 4 joystick. It's only on the initialization of the aircraft and never happens again once setting is reinstated. I will have to figure out how to do open log while sim is open and see what is happening. I will also check the autobrake settings but I only do it manually by actually turning knob in aircraft. No buttons are set up for that. Thanks for trying.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.