JeeHell FMGS forums

Dieter,
Thanks for the additional information. You can see in the video linked above that I had no issues with the left turn at DL013 (2:45 into the video).

Hi all,

@Thierry, interesting, that in your case it works. Hopefully it helps us to find out, what the difference is. Can you link your video please?

Here's my video with shaking at DL013: https://www.dropbox.com/s/sn990tnf4n2ky ... g.mp4?dl=0

Comments:
- it looks like even before and after the shaking I have a lot of stuttering. But in reality it's all smooth. Must have something to do with the recording...
- forgot to record the sound

I guess I should have made the hyperlink in my original message above more obvious. Sorry about that.
Here is the full link:
https://www.youtube.com/watch?v=Y2FB0LWxHd8

This is my video:

thierryd wrote: ↑Sun Apr 23, 2023 6:49 pm Dieter,
Thanks for the additional information. You can see in the video linked above that I had no issues with the left turn at DL013 (2:45 into the video).

I find that interesting, I can reproduce the stuttering at waypoint DL013 at any time.
Do you use ORBX Open LC Europe, Vector and GES?

Can you try to use this 2 files in the FMGS Server folder:
https://www.jeehell.org/FBW.exe
https://www.jeehell.org/rudderFilter.txt

Hi JL,

the link to the txt file is corrupt.

No it works it's probably opened as is in your web browser and since it's empty it shows all white.
You can just create an empty rudderFilter.txt file along the FBW.exe

Aaahhh ,okay

I jsut uploaded a new FBW again, so if you downlaoded before seeing this mesage, download again here:
https://www.jeehell.org/FBW.exe

jeehell wrote: ↑Mon Apr 24, 2023 12:02 pm I jsut uploaded a new FBW again, so if you downlaoded before seeing this mesage, download again here:
https://www.jeehell.org/FBW.exe

I have loaded you last FBW, but nothing has changed for me.

Hey folks,
same here... Last working FMGS was B56. Did an Update to 57, that caused CTD after some minutes. Now, with B58.0.2, it works fine, but I've also "the shaker".
3 PC-Setup:
1)World (P3D V5.3 + FMGS Server, Skalarki-Profiler and Hardware, CPFlight FCU, and all theater thinks like Pro-ATC, ASN, AiG, ...)
2)A320 (Software-OVHD, PFD/ND)
3)MCDU (MCDU CPT and FO)
By the way: in my case it also came up at EDDL. Did not try any other Location...
I also did an Update to Windows (Win10 pro), usual security things and such stuff coming up regularly. What I noticed after that: Can't see the others PCs inside the network anymore. So maybe Windows and its networksettings could be a part of the failure?

cheers
Joe

I did change again some settings if you can test:
https://www.jeehell.org/FBW.exe

bluevision83 wrote: ↑Mon Apr 24, 2023 2:01 pm I also did an Update to Windows (Win10 pro), usual security things and such stuff coming up regularly. What I noticed after that: Can't see the others PCs inside the network anymore. So maybe Windows and its networksettings could be a part of the failure?

cheers
Joe

no, a service does not have an auto start.
in German „Funktionssuchanbieter-Host“ und „Funktionssuche-Ressourcenveröffentlichung“ "Function Search Provider Host" and "Function Search Resource Publication". Look into your services and set this to auto start.
If these two are activated, you will also find your computers again.
But that has nothing to do with performance.

jeehell wrote: ↑Mon Apr 24, 2023 2:26 pm I did change again some settings if you can test:
https://www.jeehell.org/FBW.exe

Yes I can, but not until tomorrow.

JL, while watching the Video from Dieter following raised my mind. Could it be an issue with the flightdirector?
Because, if you watch the lateral FD-Bar very carefully, you can see, that the bar is mostly placed on the right side of the PFD aircraft nose, but the filgtpath is left from the aircraft on the ND. Maybe the FBW struggles within the computations getting data which don´t make sense. Especial when the aicraft has passed the second Waypoint on the ND, there is another longframe where it is very obvious that the FD-bar is right from nosedirection but the path is left from the ac. That seems very wrong, as the lateral FD shows into the direction where the path is located relative to actual position of the ac.
Even the strong oscillation of the FD bar doesn´t make sense at all, because in fact the aircraft is NOT change it´s direction that much, that the deviation from the path is that big. It´s just shaking, while stay on the direction in general.
Just an Idea.

I've been trying all day today to find stuttering through GES. I think I found a way to reduce the stuttering.
GES and GEN can be configured. I unchecked almost all of the boxes on both, so I was able to reduce the stuttering of the scenery a bit.
Maybe someone with the same problem can try this.
After at least 20 test flights, I don't feel like it anymore.
I'll do it again tomorrow.

dkreiskott wrote: ↑Mon Apr 24, 2023 4:09 pm I've been trying all day today to find stuttering through GES. I think I found a way to reduce the stuttering.

That’s a good thought. However if there are GES/GEN related issues, they appear very local. For example, I have no issues at all, when taking off EDDL23L. Only 05R.

I will test tomorrow the latest file from JL, and also test from EDDL 05L.

dkreiskott wrote: ↑Mon Apr 24, 2023 8:58 am

thierryd wrote: ↑Sun Apr 23, 2023 6:49 pm Dieter,
Thanks for the additional information. You can see in the video linked above that I had no issues with the left turn at DL013 (2:45 into the video).

I find that interesting, I can reproduce the stuttering at waypoint DL013 at any time.
Do you use ORBX Open LC Europe, Vector and GES?

I do have ORBX Open LC Europe, Vector, and GES.
I did another test flight today, with the full "pattern" to make sure I had the exact same waypoints, and thus turns. I did not run into any "shaking" despite having a few "long pauses" here and there.

thierryd wrote: ↑Mon Apr 24, 2023 8:43 pm I did another test flight today, with the full "pattern" to make sure I had the exact same waypoints, and thus turns. I did not run into any "shaking" despite having a few "long pauses" here and there.

Hi Thierry,
yes, that's what i mean. Those long pauses are the real problem. Without these pauses, the wobble of the aircraft probably wouldn't happen. Unfortunately, we will never be able to completely solve the problem of stutters caused by scenery.
The FBW system only wobbles when it happens in turns, which seems logical to me.
What surprises me is that it doesn't happen with you at this point.

One question at all,

did any of you turn on hyperthreading in the bios?

Today I primarily tried to track down the stuttering of GES. It's a pretty stupid thing to do the same flight over and over again to find a problem.

In fact, I was able to improve my result significantly, I was actually able to fix these long breaks. However, I have changed my complete settings in P3D. I turned off the building shadows and locked it to 60fps instead of 30fps. In the next attempt I increased my autogen settings and checked all the boxes for GEN and GES again.

As a result, I now fly with only very short jerks, without the Airbus starting to wobble. The only exception is when Active Sky is active. But even then, the swing is now considerably less.

Posting my settings here does not belong in the forum, so you can find them in a blog post on my homepage:
https://a320-simulator.de/software/stot ... n-beseits/

Here is a video of the situation as it is now. Taken from the original FBW.EXE from B58.0.2. As you can see, the CPU, graphics and SSD loads on the computer are not really high.


I will later test the latest FBW.EXE with Active Sky and report back.

so gentlemen

my last test for today before i go crazy
I quickly downloaded the latest FBW.EXE from Jean Luc. This time I wanted to make it as real as possible and switched on both Active Sky and the AI Traffic, which is not generated by the P3D but by VOXATC.
Even that works with the last FBW. I had done the same test before, but with the original
FBW.EXE, it didn't work there. Of course, the wind may have changed over time. There was approximately 1.5 hours between the tests.
p3d is stretched across all three televisions in full HD so that the performance is realistic

I loaded new FBW, still got Wobblies, Active Sky on and off. Manual flying no problems.
Barry

Barrykensett wrote: ↑Tue Apr 25, 2023 8:14 pm I loaded new FBW, still got Wobblies, Active Sky on and off. Manual flying no problems.
Barry

Barry did you put the rudderFilter.txt in the FMGS Server folder?