Jump to content

Ryan Mann

Members
  • Content Count

    10
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    Yes

Recent Profile Visitors

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

  1. found the error: parameters.xml installation was not my correct path for installation for some reason.
  2. I've read the quick start guide, I've also read the manual. Still when I start the flight sim and then start PSXT v 5.5.0, the "sim" is in red; 53: no liveries is found at bottom. I cannot even get the very first initial part to work. I've started over in the regular manual and followed it as well, but same result. I've added the license manually in the parameters.xml even though I already added it in the realtraffic program initially, and nothing. Where do I start to figure out my mistake? Currently at MK Studios KPHL w/ FSLTL models installed.
  3. Correction: C:\Users\<you>\AppData\ROAMING\PSXT\parameters.xml
  4. I'll try the deadzone tip. I am not using the PMDG SDK either.
  5. I appreciate all the time you have taken to help. I did not try the demo, I just purchased it. I'd say the rudder is a little bit "noisy"? I look at the data when it pulls to the left on takeoff and I see it jump a lil here and there, but to be fair, I've always had the pulling left issue even with an older joystick, which is the reason I purchased the new one. I will continue to test until I figure this puzzle out because I am very much interested in getting it to work. I am very thankful for these types of software and the amazing work and incredible amount of time that developers put into this hobby to make my pursuit of realism worth it in the end. Being that the common denominator is me and my setup b/c I do indeed know it's working great for everyone else, it will just take some patience on my end. I appreciate your response and will continue to support. 🙂
  6. I deleted all the button assignments, issue still happened. Targeted the axis assignments and got it working much better after I deleted my axis assignment for elevator and set that instead in MSFS Controller Settings for Elevator Axis. It was previously set under simulator axis event > elevator in AAO. On a side note: my MSFS "crashes" (gives warning on loading that something crashed) on loading. I only have pmdg 737 and aao installed. I temporarily moved 2 folders from community: lorbysi-content-fippanel lorbysi-content-hooks and it no longer crashes. not sure what they are specific too or why they are crashing.
  7. I did import a script for my SDXL from: https://flightsim.to/file/34382/pmdg-b737-700-streamdeck-xl-profile-need-lorby-s-axis-and-ohs I haven't used AAO w/ other aircraft yet. If I disconnect from AAO, does that "shutdown" any scripts imported through it? I will be trying everything from scratch today. I manually set up the axis and button assignments and the only script that I imported (from above link) was for that plugin on the streamdeck. I set up a new profile for the tca airbus joystick and throttle quadrant in MSFS Controller Settings and removed all assignments that matched up with any I was assigning in AAO (in real-time ie. as I was assigning each one, I immediately went into to delete the one in MSFS). After the issues, I disconnected from AAO only, went into MSFS controller settings, chose the default profile (instead of my new profile) with all the original assignments. Then I took off and tested the autopilot and everything worked again as was expected.
  8. I should've elaborated more, I apologize. I was manually clicking on the autopilot, heading, speed, FDs, AT, etc. The only actions that were bound to my airbus quadrant/joystick for autopilot were autopilot toggle, lnav, vnav, but I was not actually using them for this issue. I would take off and manually set these things with mouse clicks and they just didn't listen although they did "activate" and turn green for everything. As soon as I disconnected AAO completely and manually switch back to the default settings for the joystick, the autopilot acted properly. I guess what i'll have to do is maybe just add one assignment at a time until I figure it out and see which event is the cause. Is there a way to disable each button/axis assignment instead of deleting them to try different scenarios? I do have brakes set but nothing advanced or complicated (not sure if it is rotor_brake variable) but I will check. I think it was a different event I assigned and it seemed to work fine. I watched your YT video from few years ago and assigned things like that as well as continuing to read from the manual. The trim setting I've left alone b/c I'm just doing a freeflight in this testing, not using the FMC, therefore not setting up the actual trim, so whatever it is when the plane loads on the runway, I don't touch it. Maybe set at 0 by default. Appreciate the info and I'll see what I can come up with this weekend. I generally fly as realistic as possible and use the FMC, but I just wanna test the app first. The main reason I wanted to use AAO, and correct me if I'm wrong, was to capture the surface events when replaying or recording video. Any software that I've used kept saying it captured these events but every time I replayed, my gear never went up, flaps never went up, etc. etc. Also I recall someone asking why one would use your software, and you replied back with many different reasons, also one being voice recognition, which interested me as well but haven't even looked into that yet. One thing at a time. Thanks again!
  9. I am having an issue that I've possibly tied to AAO w/ pmdg 737. After takeoff, if I try to engage autopilot, it does but doesn't quite listen. Altitude assignments never work. Heading doesn't listen to bank angle and slowly turns no matter what and the autothrottle is all over the place. I'm not sure where to start as I'm pretty sure I've read the manual correctly on how to set up. It responds to my input and mapped buttons. I originally thought it to be a pmdg issue and saw others recently having issue w/ the AP. But I disconnected from simulator, went into controller settings in MSFS and switched back to default for my airbus joystick and tested and it listens and follows my autopilot instructions. I understand this could be tricky but I'm hoping someone could point me in the correct direction on where to start. I was also using the throttle quadrant. I also have been attempting to get the streamdeck plugins to work on my xl from lorby as well as chris_a320_pu plugins from flightsim.to but have put that to the side while I tried to figure this out. It is a clean install of the OS, clean install of MSFS, only using pmdg 737 and AAO at the moment. nothing else has been installed yet. thank you Ryan Mann
  10. I already spent a lot of money on flight simulation, most recently P3D. As I'm trying to get everything installed and tuned properly, I find myself getting very agitated with Prepar3d. It seems that when a new update comes out, I must constantly wait for compatibility updates to various amounts of software that I have purchased. So my question is if this happens in X-Plane. This is starting to get so frustrating that I am ready to abandon P3D altogether if I don't have to constantly go thru this. Then to make matters worse, I am sure they will jump to a new version altogether in due time, rendering everything basically useless unless I pay for more upgrades and new sim from LM. Thanks, Ryan Mann
×
×
  • Create New...