Scenery not moving fluently; what can I do?

Loek

I am using GIT for connecting a couple of aircraft and the GoFlight MCP Pro. When flying in X-Plane I experienced scenery was not moving fluently but with short 'hick-ups'. Investigating the issue, I removed all plugins. I had a very smooth and fluent flying experience. I placed the plugins back one by one and all was good until I enabled the GIT plugin. During flight with GIT enabled and the MCP Pro connected to an aircraft, I experience the scenery not moving fluently. With GIT enabled but without connection to the MCP Pro I experience the same problem. When I - mid-flight - disable the GIT plugin, scenery is moving fluently. Enabling GIT again brings back the hick-ups.
Does anybody have a suggestion what can be wrong or what I can do? Thank you for any help.

admin_pps

Does it do it with just the GIT plugin enabled and no others running?

Best wishes
Steve

Loek

Hi Steve, thanks for reacting. You are asking a good question. I will try out and get back to this place.

Loek

Steve, I tested. Fresh start-up of X-Plane 11.41r1 with all plugins enabled: scenery not moving fluently. In-flight disabling GIT: smooth. Fresh start with only the GIT plugin enabled: Scenery not moving fluently. In-flight disabling of GIT: everything smooth.
During these tests I am flying the default Cessna; MCP-Pro is not connected. I started my investigations after flying with the Toliss A319 and the TBM900 connected to the MCP-Pro (with of course GIT enabled) and noticing the disturbed moving of the scenery. At higher flying speeds the situations worsens and is really annoying.
[I have GIT 2.0.15.2.]

admin_pps

Do you have multiple screens as someone reported a similar issue in P3D and it was when GIT was located on a different screen.

The only other thing I can think off is that you could try increasing the polling time in the GIT settings tab.

Is there anything odd in the GIT Log tab?

Best wishes
Steve

Loek

Steve, thank you for helping.
Yes, I do have multiple (3 x 1920x1080) screens configured as one screen, wrapped around by NVIDIA settings. GIT is on that same screen.
A contributing factor is of course that when flying on one screen only, the field of view is smaller and when looking straight ahead the discontinuity is less pronounced. In my set-up the field of view is 120 degrees and especially looking out of the side windows the hick-ups are clearly visible and annoying.
I will play with the polling time and check the log tab. I also will see what happens when disabling the NVIDIA wrap-around and configure X-Plane for multi-screen (takes more capacity of the hardware causing lower FPS).
I may come back to this place after further investigation. Be assured I really appreciate the support from you!

Loek

Steve, I continued checking. With X-Plane configured for three separate displays everything looks OK, except that I have a too low frame rate. When using NVIDIA surround the scenery flow becomes inconsistent with slowing down and speeding-up. Without GIT plugin enabled scenery flow is OK. Polling time doesn't make a difference. Log tab has nothing.
I was hoping other people would have seen the same behavior and would know a way around it. Maybe you can come up with a good idea. Without improvement I cannot enjoy using GIT and the connected GF-MCP Pro.

admin_pps

Is it aircraft specific or does it do it with all aircraft?

Loek

Steve, I was on business trip and could not react earlier. It is with both Toliss and TBM. But it is also with other (default) aircraft and without starting GIT but with the X-Plane GIT plugin enabled.

admin_pps

The backend does it's dataref checking on the display thread. It didn't originally, but it had to moved there to stop major crashes with complex 3rd party aircraft using certain tech.

I will add an option to run the backend on its own thread so you can see if that helps and it doesn't crash the aircraft you want to fly. It will be a few weeks away as I'm alpha testing a new product at the moment.

Best wishes
Steve

Loek

Steve, Thanks. I am looking forward to the option. Can I assume you will communicate the availability in this forum? In the mean time: success testing the new product.

Loek

Steve, did you already make progress with this issue? You indicated that you would add an option. It would be great if this would be over. Thanks.

admin_pps

Not yet, I'm still working on alpha testing another product I've written. Once I reach a natural break in the testing, I'll focus on GIT and resolve any outstanding issues. Probably start on it next week.

Best wishes
Steve

admin_pps

Hi,

I have built a new version of GIT that will hopefully address this issue. The Polling Time on the settings tab was being ignored so I've fixed that, so now moving that slider will influence the impact GIT has in X-Plane.

If that doesn't help, I have created another way of updating GIT, but it may cause crashes with some aircraft. On the settings tab, enable Update On Flight Loop, then Save Settings and then restart GIT.

I will PM you a link now.

Let me know how you get on.

Best wishes
Steve

Loek

Good news: With Vulkan everything is moving fluently and my problem as reported to you has been solved. Thanks for all efforts.
Best wishes, Loek.