737PILOT2018 Posted 6 hours ago Posted 6 hours ago Hi, I’m currently flying the iniBuilds Lockheed TriStar using the PMS INS setup, and I’ve run into an issue related to simulation rate. The aircraft itself allows me to use sim rate x4 without any problem. However, the PMS INS does not seem to account for the increased simulation rate when performing its calculations. Specifically, the distance to Top of Descent decreases at the same rate regardless of whether I am at sim rate x1 or x4. As a result, during accelerated flight, the INS calculations become inaccurate, and the TOD prediction is no longer usable. It seems like the INS is calculating based on real-time rather than simulation time. Is this a known limitation of the PMS INS, or is there any workaround or fix available? I’d also like to report a major performance issue with the iniBuilds Lockheed TriStar. I am getting extremely low FPS with this aircraft. When I pan the camera, it stutters heavily, making it very uncomfortable to use. I’m also seeing very high VRAM usage. I have NVIDIA RTX 4070TI , Intel I5 13400F , 32GB ram so my setup shouldnt be a problem. What’s strange is that with other aircraft, I get literally around 7 times more FPS and far fewer stutters under the same conditions. So the issue seems specific to this aircraft. Would it be possible to introduce lower resolution texture options? For example: A “Low Resolution” texture pack An “Ultra Low Resolution” texture pack Even more aggressive options, like significantly reducing passenger cabin texture quality (e.g., very low-res / 360p-style cabin textures) I’d like to suggest a feature regarding GPS integration. Currently, the default GNS 530 in MSFS 2024 has several issues with flight plan sequencing. I’ve spent about a month testing and analyzing these bugs, and from what I’ve observed, the GPS sequencing logic in the default GNS 530 — and therefore also in the PMS GTN 750 (which relies on similar logic) — is not fully reliable. Because of this, complex flight plans can behave unpredictably, especially during waypoint sequencing and approach phases. Would it be possible to integrate support for the TDS GTN 750 NXi as an alternative option? For example, similar to what is done on the FSS 727, users could choose between: Default GNS 530 PMS GTN 750 TDS GTN 750 NXi This would give users more flexibility and allow those who need more reliable GPS sequencing to use the TDS solution. Thank you for your time.
IniJamir Posted 1 hour ago Posted 1 hour ago Hi, the performance issues are being actively worked on and reports from early testers on future builds have indicated a noticeable performance increase. As for the suggestions for the PMS/TDS, I will pass it along to the team albeit there are no guarantees there as the GNS530 was actually utilized on the L1011 in real world applications where as I cannot say for the later (guessing no based on the era but I could be wrong) the Calculation I will log and pass it to the team. Thank you
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now