February 11, 20206 yr After a year or so of not using the GTN's I installed them again (and the Garmin Aviation Trainers obviously). For some reason all of the avionics trainers run super slow. I have tried compatibility mode windows 8/7, disabling full screen optimizations, and forcing it to run as an administrator (for the garmin main app and the gtn trainer exe). I have a decent system that should not be the issue since others with less capable hardware are able to run this fine (i7-8700K, 32GB RAM and a GTX 1080ti. Garmin thing is on a Samsung 970 EVO Plus M.2 SSD). Windows version is 10.0.19559 build 19559 (latest insider fast ring) and version 442.19 for the nvidia drivers (latest ones available). The linked video is now on the v2.6.0.0 I have tried v2.5.0.0 and v2.4.0.0 and some other random ones and they all have this issue. Just to clarify they run slow in sim through RealityXP and standalone with nothing else running on the system (of course Windows stuff and other background drivers etc. are still running). Video showing this: https://youtu.be/s_0gAV4VEL0
February 12, 20206 yr Hi, The metrics in the video are not showing any particular CPU or GPU limitation and the process impact is marginal. I'd recommend you first try using an official Win10 release to get started, because the one you're using is a 'work in progress/beta' version with bugs. Do you have 2 GPUs in your system (like integrated Intel and discrete Nvidia)? If so you might want to review the RXP GTN User's Manual troubleshooting section about integrated vs discrete and what to do about this. Edited February 12, 20206 yr by RXP
February 12, 20206 yr Author Yeah I was expecting that, I guess I'll wait and see for the time being if the the fault is with the insiders builds. Its more of a Garmin issue anyway and maybe I'll try to report this to them. I would test on release versions of Windows but I dont have a spare computer and I need the insider functionalities (WSL 2 mainly). Yes the i7-8700K has integrated graphics but that is disabled since im running a discrete graphics card. I was hoping to not be the only one with this issue. Thanks anyways for the help.
February 12, 20206 yr I had this problem when running the "other" GTN's. I resolved it by using an affinity mask. If you run multiple GTN's place each one on its own core or logical processor. Greg
February 12, 20206 yr 14 minutes ago, lownslo said: If you run multiple GTN's place each one on its own core or logical processor. As long as you let the default RXP GTN setting CpuAffinity = -1 (meaning 'automatic') you won't have to 'play' with this because our implementation does this automatically for you! If you experiment with CpuAffinity = -2 though (only with the latest GTN Trainer 6.62) it will run on all cores 'intelligently'. NB: running the latest trainer 6.62 standalone via the 'Garmin Launcher' should already make it run on all cores. NB2: the issue you're having is not related to the CPU cores at all. It is related to the internal clock in the Garmin Trainer (most likely). Something must be affecting the Windows timing API somehow. If you're knowledgeable about Windows API, think about timeBeginPeriod(10) (timer precision 10ms - roughly your video) vs timeBeginPeriod(1) (timer precision 1ms).
Archived
This topic is now archived and is closed to further replies.