Everything posted by noahharget
-
SimConnect request ac within range fails
I updated PSXT to v12.5.5 yesterday, 04JAN and have been getting InvalidParameter in the MSFS Crash log. I have not had any issues with GSX and have ran everything the same. The only change was PSXT update. This is using 2020. Though, It seems it could be linked to GSX based on a forum post. However, I am able to inject for quite some time before the CTD occurs.
-
RealTraffic not registering some Aircraft Properly
Those were just hand-picked. I'm flying into SFO now, and there's tons of missing regs. Definitely think it may be a RT issue given all models are installed and this just started to become an issue. However, it does seem to be better now! Will reply to this thread if it does become an issue again!
-
RealTraffic not registering some Aircraft Properly
I am using PT Only
-
RealTraffic not registering some Aircraft Properly
Ok lots to reply to haha I was checking FR24, which did show that B738 should have been a -700. I'm getting lots of incorrect matching as of recent, which could be due to the AIG-regcodes I assume. I have all liveries installed through AIG along with the updates. I used to get pretty spot on matching when it came to special livery tail numbers (SWA or AA) too, but that has changed. Today's post was obviously in MCO. Looking at little navmap, I have an Envoy E175 labeled as 175, a United B38M labeled as 737. It's missing the type designator for the incorrect planes. I know this isn't an issue with PSXT per se, but wanted to bring it up! I've attached my settings of PSXT just to ask for suggestions of what I could change 🙂 https://photos.app.goo.gl/kTsZiZaRKjNzEM597
-
RealTraffic not registering some Aircraft Properly
I believe there may be a bug in how traffic is being read. Looking at the log I noticed some information missing JBU395 N629JB HPN->MCO JBU A320 =c= AIGAIM_jetBlue Airbus A320-200SL - jetBlue for Good SWA2590_ SWA B738 =2= AIGAIM_Southwest Airlines Boeing 737-800SSW - SN ETOPS SWA2590 is actually a B737-700, however it is obviously showing as a B737-800. More examples include - NKS203 NKS A320 =2= AIGAIM_Spirit Airlines Airbus A320-200 - Wifi NKS1475 NKS A320 =2= AIGAIM_Spirit Airlines Airbus A320-200 - OC Wifi new engine titles SWA1980_ SWA B738 =2= AIGAIM_Southwest Airlines Boeing 737-800SSW - SN AAL3017_ AAL A320 =2= AIGAIM_American Airlines Airbus A320-200 - CFM As you can see, each entry is not only missing a city pair, but also a tail number. This also seems to be happening with A319/A321's. I don't believe this is an issue with my setup, as the models do show on Vatsim and have showed up until a few days ago. I just am usure how to check or communicate with RT to inquire about this.