I’ve been working with the team at PMS5 regarding their GTN750 for MSFS 2024. When using their product ( GPS for MSFS2020 ), I found that if you’re at KBOS and you select the LOGAN4 departure and using runway 33L, once you select the map it causes massive stuttering to the point the sim is not usable.
I attempted this using the stock Asobo nav data and didn’t have any issues. If you manage to deselect 33L and select another runway, it works fine.
I created a video showing the issue… I’ve tried it with a full route or just the SID and the issue happens regardless. When I reached out to the team at PMS5, they made it clear this is an issue being caused by Navigraph, which kinda makes sense because the stock data works fine. Appreciate the help to narrow this down. I tried other products like PMDG and inibuilds with the same SID/Runway combo and had no issue. Also, the stutter doesn’t start until you click the map.
Hi,
Do you see the stuttering in a default stock aircraft, too? Like the C172 with the G1000? I ask because PMS5 uses the sim data (as you have also discovered), which means that when this is really a data issue, it must have happened on every aircraft that uses the sim data.
PMDG and Inibuilds are bad examples because both use their own datasets (MSFS-independent), so you can´t really compare them. But when you try the same in a stock aircraft, you use the same dataset as the PMS5.
Can you check this, please? Because I don´t see any stuttering in the C172/G1000 when I select the LOGAN4 departure.
Thanks for the quick reply. I just tested the other stock aircraft and it works fine. The only thing that seems to be affected is KBOS on the LOGAN4 with 33L selected while using the GTN750 from PMS5.
Thanks for testing - as I have written, the stock aircrafts use the in-game BGLs which we offer. PMS5 also uses the in-game BGLs. So, here we have the same context. I also know that the stock aircraft uses the WT Framework in the background, and when PMS5 uses the SDK, I would assume the same results.
Have you ever seen this at any other airport? Because it could be a SIM issue with KBOS. I know they had made a handmade airport, possibly, so that the packages behind generate the stuttering.
It is very unlikely that this is a data issue at a single airport for a single procedure. A BGL contains the entire airport (so there is no splitting), with all facilities and all terminal procedures. Loading one BGL gives you the complete navdata for this airport in memory. No reloading of anything …
We (and also PMS5) don´t influence how the data will be loaded - I assume he loads it via the SDK, so this is also a component between the data and the aircraft. Not sure how I can help here, sorry.
Thanks again for the follow up. Maybe I should add that while the stock aircraft work with the G1000 and such, anything using the GTN750 from PMS5 has the problem… whether I put it in the 172, Black Square Caravan, etc…. and when I load the GTN750 without Navigraph data installed, the PMS5 GTN750 works fine. So I’m struggling to totally understand all of this myself.
**I guess what I’m saying is I’m not sure if I’m explaining it wrong or what here. Their product works with stock asobo nav data. It doesn’t work with that SID when Navigraph is installed.
I guess we speak exactly from the same, but here is a short comparison:
Stock aircraft with Navigraph = no stutter
Stock aircraft without Navigraph = no stutter
PMS5-equipped aircraft with Navigraph = stutter
PMS5-equipped aircraft without Navigraph = no stutter
What I mean is, you use it in all 4 scenarios exactly! The same BGL files, but get different results. When this is really a data issue, you should see the stutter in the stock aircraft (without the PMS5 addon) too, but you don´t—no stutter with our data in the stock aircraft.
So, it is completely unclear to me what I should do, where I should look … and, more importantly, why only ONE procedure produces these stutters. The LOGAN4 is a vector departure; possibly that is the reason… because it ends nowhere, I don´t really know… I´m sorry.
I think I understand some what better now. I appreciate the reply. I hope you understand obviously why I reached out here, since PMS5 is saying this is a Navigraph problem. A bit hard as the consumer with limited technical knowledge of how everything works as far as integrations for who to ask for help, especially when it’s unclear as to where the problem actually exists. Thanks for trying to help though.
No problem - I don´t want to blame PMS5; that was not my intention here. I know how you feel as a customer in such difficult phases between two chairs.
Possibly the SDK (that’s the third part in this game) is the culprit, especially given the vectors. I think aloud now: what, when any method in the SDK tries to calculate the next waypoint, compare it, or similar. All that needs CPU, memory, … I try to find an answer to all these question marks, but I must also accept that we don´t get all questions answered.
Anyway, whenever you find something out or identify any possible reason for this, let me know, please. The doors for such discussions are open
Sorry that I can´t help here or offer a professional answer. I wish I could …
Have a nice evening and enjoy your weekend
Richard
