Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Everything posted by Twenty6

  1. Did you ever resolve this? AAO recognizes my yoke/throttle as VelocityOne Flight, not as a "gamepad." So I'm wondering if your input mode is set to Xbox, not PC. I switched my input mode to Xbox and AAO did not pickup any axes or buttons on the throttle quadrant. Switch back to PC mode and no problems. No problem setting up the default Baron. I'm also running the v1.40 firmware on the VelocityOne Flight and have the USB cable connected directly to the computer, not a USB hub (powered or otherwise.)
  2. DLSS anti-aliasing is much blurrier. Worse than before. Switched to TAA to avoid the headaches.
  3. Open Microsoft Store and go into your Library. "Get Updates." See if that solves your problem.
  4. Version 0.9.28+patch1 is the current version. Where do you come up with v0.9.02?
  5. Back a couple pages in this thread was a mention of a 787 mod interfering with the Duke's tablet.
  6. Question for the one person that actually got onto the JustFlight website and bought the plane(s). What's the price of each and bundle???
  7. I uninstalled their KGSP. Did they ever get runways 4 and 22 pointing in the correct direction?
  8. Nirvana! Stop coding and go enjoy your work.
  9. Yes, it was a beta update. Forgot what thread I was in.
  10. Anyone else get an update to v1.37.9 earlier today (Friday)?? It fixed the starting in windowed mode snafu, updated WT instruments, Wright glider and Hughes Hercules. Some other minor updates went by too fast to notice.
  11. I start TrackIR and immediately switch into precision mode for the rest of the flight. Been doing this for 12+ years without issue in FSX, P3D and MSFS. To the OP ... did you try cleaning the camera and receptors?
  12. Where I currently live in NE Tennessee I have a data cap so I try to save 1s and 0s wherever possible. That said, I do use the cache built into the Map Enhancement program and have since this program came out. Without issues. I can't see any advantage to not using a caching option, but to each his/her own.
  13. Never heard of that. I've used it since it first came out. It's a small utility that just works.
  14. https://flightsim.to/file/15033/toolbar-pushback might be what you're looking for. You can go forward and backward manually or by plotting out a route, turning this way and that way.
  15. https://www.inibuilds.com/
  16. Should have explained it that way when you first posted the picture. I'm not smart enough to figure that out without explanations.
  17. Probably the same Artificial Intelligence that thinks driving fuel trucks down taxiways and runways is a good idea. Sorry, I don't have your answer. I disable crash detection and run them over when (not if) they get in the way. They always seem to come back healthy.
  18. Love this livery color. I'll be looking for the registration update. Thx
  19. Don't know if you want to rollback from the 1.40 firmware. There were a lot of refinements between 1.33 and 1.40. You might lose more than Slider 0 by going to an older firmware. I avoid their discord channel but maybe they're talking about a newer firmware or have some insight into the Slider 0 axis.
  20. It used to before Turtle Beach updated the firmware to v1.40. Item in question is this: https://www.amazon.com/Turtle-VelocityOne-Universal-Control-Windows-x/dp/B09JM8SX8G/ref=sr_1_1?crid=24D2KLH1RKD8B&dib=eyJ2IjoiMSJ9.crqSJalR9q1y937om4pv7lv_4Hk1HZQfVfLKnfJYgG3ggHWUZMXh3aArkRv9pGIBiAs8WaMnfO5eVuMXhu_f7g.D1cAJylQ9nVX9Syf392gzvJiZBzpjxW42vy03cZkJV4&dib_tag=se&keywords=velocity%2Bone%2Bflight&qid=1704930238&sprefix=velocity%2Bone%2Caps%2C156&sr=8-1&th=1 Because at one time AAO was able to pickup Slider 0 I never considered it a bug in your program. Anyways the workaround is easy enough to do The trim wheel is on the Throttle Quadrant and works really well for GA aircraft once setup in AAO.
  21. Here's a workaround that involves editing the XML file Axis and Ohs creates. If you don't want to do that then ignore this post. Create a new profile for the aircraft involved. Remember the name of the profile. Add one axis to the profile using the lever right next to the trim wheel which should come up as "Slider 1". Set it up for Elevator Trim and save the profile. Go into "ConfigDatabase_MSFS.xml", find the profile you just created and change "Slider 1" to "Slider 0". Make double sure you're changing the correct aircraft noted in the "AircraftId" parameter. Save the file. Go back to Axis and Ohs and add the rest of your axes and buttons. "ConfigDatabase_MSFS.xml" is located here: %localappdata%\LORBY_SI\LorbyAxisAndOhsMSFS. Backup the file even though there are other backups there. they could be old and outdated. If you're not comfortable doing this .... don't. Here's the pertinent info for the Asobo Baron 58 as an example. Your joystickGUID will be different than mine: <AircraftConfiguration> <aircraftId>Asobo Baron G58</aircraftId> <airFileId>SimObjects\Airplanes\Asobo_Baron_G58\aircraft.CFG</airFileId> <loadFromMaster>false</loadFromMaster> <buttons /> <axis> <GlobalAxis> <joystickStateProperty>Slider 0</joystickStateProperty> <joystickGuid>16752120-c8ee-11ed-8009-444553540000</joystickGuid> <joystickName>VelocityOne Flight</joystickName> <midiDeviceId>-1</midiDeviceId> <midiChannel>-1</midiChannel> <midiEvent>-1</midiEvent> <filterValue>1</filterValue> <assignedAxis> <Label>Elevator Trim</Label> <SimulatorEventName>AXIS_ELEV_TRIM_SET</SimulatorEventName> <MinValue>-16383</MinValue> <MaxValue>16383</MaxValue> <DefMinValue>-16383</DefMinValue> <DefMaxValue>16383</DefMaxValue> <curve>false</curve> <isSlider>false</isSlider> <Response>0</Response> <deviceMin>0</deviceMin> <deviceMax>65535</deviceMax> <deviceCenter>32767</deviceCenter> <leftMargin>0</leftMargin> <rightMargin>-0</rightMargin> <deadzone>0</deadzone> <nonlineardeadzone>false</nonlineardeadzone> <reversed>true</reversed> <progressive>false</progressive> <momentary>true</momentary> <onChangeOnly>true</onChangeOnly> <triggerDir>NONE</triggerDir> <triggerRepeat>NONE</triggerRepeat> <outputType>FLOAT</outputType> <vkModifiers /> <vkKeys /> </assignedAxis> <detents /> <Action>Elevator Trim</Action> <ControlLayer>0</ControlLayer> </GlobalAxis>
  22. Really? Your posts seem to indicate otherwise. You're all wound up about which doesn't make sense unless any written documents are copied verbatim. Including actual examples would help your argument. If there's any theft of intellectual property why not let the devs at A Pilot's Life handle it.
  • Create New...