Calibration of instruments with config file does not work

[jeehell]

make sure you get enough FPS in P3D (ideally over 30fps).

[Seppl1209]

Hey JL,
thanks for the tip.
Your comment reminded me that I had changed the graphics settings. I didn't undo these later on.
Yesterday at least it worked on a round trip over Cologne, no wobbling, no crashing.
Thank you.
Greetings
Sebastian

[flambinet]

Dear Sebastian,
could you please explain what you changed back and forth related to the graphics.
I have a similar problem sometimes somewhere enroute where the plane gets out of
control. Sometimes it crashes, sometimes, I can recover by manual flight.
FPS are always above 30.
Thanks for sending your ideas.
Best Regards
Fritz

[balu69]

Hello Fritz
This happens to me from time to time too - unfortunately. I also have stable over 30fps.
I'm not sure if it's because of FSHud. Do you use it?
What strangely helps me is if I immediately activate the pause, wait a moment and deactivate the pause again. Then I can catch the plane and continue flying.

[flambinet]

Thnks Stephn for your quick reply. I do not use FSHud.
I will try your trick next time it hppens again.
Thanks, Fritz

[stefangr]

+1!

I am also having the problem that sometimes the plane is getting out of control: suddenly extreme banking while A/P had control, sometimes on CRZ LVL, sometimes on approach or even on ILS.

I have tried so many things now, starting with changing setup and even deacitivating Active Sky, up to replacing hardware joysticks. Last thing I have done is deactivating the hardware rudder in JL calibration (currently the Z axis of joystick is taking over role of rudder). Not made enough flights since then to check if that helped.

But as I am not alone obviously, it seems that there is a different reason. I am not using FSHud, and I don't think it has to do with fps. I will check the trick with the pause. Stephan, for how long do you remain in pause mode?

Having P3D 5.4.9.28482 with JL B61.10.1 and Skalarki hardware.

[balu69]

Hi stefangr
Yes, this was the case for me too. The problem is that it is not reproducible. It always appears at a different time and in a different place.
The pause helped me the last two times. I had it active for about 20 seconds each time.
It feels like something isn't working (like with YouTube and a bad internet connection) - but it's just a feeling...

[stefangr]

Thanks, Stephan. Do you also have this message when it happens? F/CTL DIRECT LAW (PROT LOST) - MAN PITCH TRIM



Afterwards the plane is always difficult to handle.

Thanks
Stefan

[balu69]

It has also happened to me that he switched to "Direct Law". The plane is very difficult to control then.
Most of the time, I don't know if it has anything to do with how quickly I press the pause button, he continued to fly in Normal Law

[stefangr]

Do we have any idea where this is coming from? More P3D software or JeeHell software or anything else?

[flambinet]

Dear all,
the number of this event has increased in the recent past.
I did 3 flights from EDSB to EDDN with VOXATC initiated and one flight from EDSB to EDDN
and back from EDDN to EDSB both without VOXATC initited
What I observed was that in the first three casess, after finish of descent to EDDN (FL70), the
engine sound started oscillating and soon after that the wobbling started. In one case the plane crashed and
in the other two cases, I was able to recover through manual flight.
I tried the trick and paused the simultor as soon as the instability started, but saw bank and pitch moving on the PFD
after the simulator was paused.
The two flights with VOXTC initiated, showed some slight engine sound oscillation, but no further instability.
I guess it is to early for conclusions, but the banking and pitching while the simulator was paused was strange, I thought.
Anybody with further observations or ideas?
Best Regards
Fritz

[jeehell]

it seems either P3D is "stalling" (P3D, not the aircraft), and has issues sending data to the network, or even has too low FPS.

[Seppl1209]

@Flambinet
Hey, you addressed me personally on the subject of graphics. Sorry for the late reply.
I have reset everything to default in the NVIDIA settings.

[balu69]

Hello everyone
I think I found a flight where I can reproduce this situation and I think it has something to do with the FPS, as JeanLuc writes.

Here are my requirements:
- SimBrief Flightplan: LSZH/28 N0326F140 VEBI1X VEBIT T50 ROTOS Z669 ULMES ULME2R LSGG/22
- ActiveSky Weather from 25.02.2025 19:45UTC
- ActiveSky Settings: Maximum Cloud Layers: 10
- SIM-Time: Real Date and 07:10local time
- FS-Hud: AI-Traffic (AIG) on and 20/10Traffic
- Aerosoft Geneva Professional and Mega Airport Zuerich V4

When I fly away from Zurich, I get about 35 - 38fps with my settings. The weather is cloudy there too. In the Swiss midlands the weather gets better and the closer I get to LSGG the worse the weather gets. When I enter the clouds my fps drops to 20 - 25 and I had the problem with the plane staggering during two flights. The problem did not always occur in exactly the same place, but always in or below the clouds

On a third flight I reduced the cloud layer settings to 3, reduced the cloud display to 60 miles and turned off the AI ​​traffic and no longer had the strange behavior and was able to land without any problems

[dkreiskott]

Hi all,

maybe I can help a little here. I've struggled with similar problems over the last year. To find a solution, I must have done the same flight about 50 times. Always with different settings. I started with the basic settings of Prepar3d.

What can I say, JL is right when he assumes that the frames are the problem, that's what happened to me in the end.

I used a tool to evaluate the frames in Excel, because I didn't want to monitor every flight live and automatically put P3D into pause mode when the problem occurred. The article about this can be found here: https://a320-simulator.de/homecockpit/f ... nd-loggen/

The tool can also be downloaded.

However, the settings were ones where I wouldn't have suspected the problem. I had the problem you described, especially on longer flights. To make a long story short, for me it was the settings for the terrain. I have the following settings (in P3d v5) with which the problem no longer occurs:

Level of detail: Ultra
Tesselation factor: low
Mesh: 19m
Texture resolution: 1m

Since I reduced the settings here, the problem has completely disappeared. And since I'm mostly flying at FL300 and higher, it doesn't bother me. You can give it a try.

[balu69]

Hello Dieter
Thank you for your advice. Do you have limited or unlimited FPS?
I had the same problem again yesterday (ActiveSky Weather 10.03.2025 19:35Z) on my flight from LSZH to LSGG (VEBIT1T VEBIT T50 ROTOS Z669 ULMES ULMES2R) shortly after takeoff and before BREGO and I wasn't in the clouds and I'm sure I had enough FPS.
What I noticed was that my Elgato StreamDeck was briefly without a display and then, I was able to "save" the flight, FSUIPC no longer recognized my Thrustmaster TCA stick and the Leo Bodnar board. However, they were still there via joy.cpl and the buttons worked.

[balu69]

Okay, I have a suspicion... I recently optimized my cockpit and connected my TCA Airbus Stick and Elgato StreamDesk to a other USB hub. I didn't plug in the power connector because it's not practical.
My suspicion is that either the USB hub is temporarily shutting down because it doesn't have enough power, or it has a fundamental problem.
I just took a short flight, and when I briefly unplug the hub, the exact same problem occurs as the day before yesterday in LSZH.
I'm now powering it up and doing a few test flights - I really hope I'm on the right track!

[balu69]

it's not the USB hub for me

[balu69]

Hello Dieter
I have a fundamental question about your solution. Is it simply about keeping the FPS stable above 30, and could this also be achieved with a different setting (e.g., setting the scenery complexity to low)?
In any case, thank you very much for your input! I adopted the settings as they are – except for the mesh, which I'm keeping at 2m for better representation of the Alps – and was able to complete two problem-free flights!

Hallo Dieter
Ich habe eine grundsätzliche Frage zu deiner Lösung. Geht es einfach darum, die FPS stabil über 30 zu halten und dies könnte auch mit einer anderen Einstellung (z.B. Szenerie Komplexität auf sparsam stellen) zum Erfolg führen?
Auf alle Fälle danke ich sehr, für deinen Input! Ich habe die Einstellungen - ausser beim Mesh, diese belasse ich wegen der besseren Alpendarstellung auf 2m - so übernommen und konnte zwei problemlose Flüge durchführen!

[dkreiskott]

Hi Stephan,

Regarding your first question, I use unlimited frames. But only since I've done all the testing. Regarding the mesh, in my tests, that was exactly the setting that caused P3D to crash or freeze for a few seconds.
We both know that every system is different, but I think the mesh reloading is causing more problems than the scenery. As I described in my blog.
And at cruising altitude, the Alps don't really look any different with my attitude.

Hallo Stephan,

zu Deiner ersten Frage, ich nutze unbegrenzte Frames. Das aber auch erst, seit ich die vielen Tests gemacht habe. Was nun das Mesh angeht, bei meinen Test war das genau die Einstellung weshalb der P3D abstürzte oder kurzzeitig für wenige Sekunden stockte.
Wir wissen beide, das jedes System anders ist, aber ich glaube, das dass nachladen des Mesh eher Probleme verursacht als die Scenerien. So wie ich es auch in meinem Blog beschrieben habe.
Und auf Reiseflughöhe sehen die Alpen mit meiner Einstellung nicht wirklich anders aus.

[balu69]

Hi Dieter
You're absolutely right, every system is different, and all settings probably need to be checked and reviewed.
I finally had success and was able to noticeably improve my frames by switching AA from 8xMSAA to 2xSSAA.
Clouds also have a strong impact on me—which is probably why I experience more dropouts in this bad weather. That's why, when I'm flying in clouds, I reduce the "Cloud Draw Distance" to the minimum of 60 miles.

Hallo Dieter
du hast völlig recht, jedes System ist unterschiedlich und wahrscheinlich müssen alle Einstellungen überprüft und kontrolliert werden
Bei mir hatte ich endlich Erfolg und konnte meine Frames spürbar verbessern, indem ich AA von 8xMSAA auf 2xSSAA gewechselt hab.
Was bei mir auch einen starken Einfluss hat, sind die Wolken - daher habe ich bei diesem schlechten Wetter wohl auch mehr Ausfälle. Deshalb reduziere ich, wenn ich in den Wolken fliege, die "Cloud draw distance" auf das Minimum von 60Mi.

[balu69]

Hi
I'll give up (for now) and just have to accept this strange spin behavior.
For me, it's definitely not the FPS issue. I've tested (LSZH/28 and DEGE1X) with "clear skies" and thick clouds, and I sometimes get over 70 FPS, and it happens there too.
What I know now is that when this happens, the CPU (AMD Ryzen 9 5950X) is at 100% capacity and the PC is generally slowed down. When I dig deeper into the Task Manager, P3D is primarily responsible.
For me, it often happens when FSHud issues a command or I repeat it – but according to support, it's not FSHud's fault.
Since the problem doesn't always occur, troubleshooting is very time-consuming, and I've already lost a lot of time.
Has anyone found a solution?

Ich gebe (vorerst) auf und muss mich wohl mit diesem seltsamen Trudelverhalten abfinden.
Bei mir liegt es definitiv nicht an den FPS. Ich habe (LSZH/28 und DEGE1X) mit "Clear skies" getestet und dicken Wolken und habe dabei zum Teil über 70FPS und es geschieht auch da.
Was ich inzwischen weiss ist, dass wenn dies passiert, die CPU 100% ausgelastet ist und der PC grundsätzlich verlangsamt ist. Wenn ich im TaskManager in die Details gehe, ist P3D hauptsächlich dafür verantwortlich.
Bei mir passiert es vielfach, wenn FSHud ein Anweisung gibt oder ich diese wiederhole - gemäss Support liegt es aber nicht an FSHud.
Da das Problem nicht immer auftaucht ist die Fehlersuche sehr aufwendig und ich habe schon sehr viel Zeit verloren.
Hat jemand eine Lösung gefunden?

[dkreiskott]

Hi Stephan,

Could you make a video of the "spin"? Or explain in more detail what's happening? Otherwise, here are a few tips:
Always based on whether you have a flight where this is reproducible.

1. Disable FSHUD; you can see in the P3D forum that others have problems with it.

2. Use the Windows Resource Monitor instead of the Task Manager. This is more complex but more accurate, as you can control what you want to monitor.

3. Save your configuration and create a new Prepar3d.cfg. Then try the flight with the automatically generated values ​​and see if the problem occurs.

4. If you have an Intel CPU and Hyper Threading enabled, disable it in the BIOS!
I wrote a blog post about this topic and the resulting problems: https://a320-simulator.de/software/wind ... threading/

Next time I'm in the cockpit, I'll find something for you. I've changed the thread in my Prepar3d.cfg file where P3D primarily runs, as many other programs (FSHUD) often place a strain on the first core.

Regards, Dieter



Hi Stephan,

könntest Du von dem "Trudeln" mal ein Video machen? Oder mal genauer erklären was passiert?. Ansonsten mal ein paar Tipps:
Immer bezogen darauf, dass Du einen Flug hast auf dem das reproduzierbar ist.

1. FSHUD deaktivieren, da kann man im P3D Forum sehen, dass auch andere Probleme damit haben.

2. Nutze statt dem Task Manager den Ressourcen Monitor von Windows, das ist aufwendiger aber genauer, da du steuern kannst was Du beobachten möchtest.

3. Sichere Deine Konfiguration und erstelle eine neue Prepar3d.cfg. Versuche dann mal mit den automatisch generierten Werten den Flug zu machen und schau ob das Problem dann auch auftritt.

4. Hast Du eine Intel CPU und Hyper Threading eingeschaltet, schalte es im Bios ab!
Zu dem Thema und dem daraus resultierenden Problemen habe ich einen Blogbeitrag geschrieben: https://a320-simulator.de/software/wind ... threading/

Wenn ich das nächste mal im Cockpit bin werde ich etwas für Dich heraussuchen. Ich habe bei mir in der Prepar3d.cfg den Thread auf dem der P3D hauptsächlich läuft geändert, da viele andere Programme (FSHUD) oft den ersten Kern belasten.

Grüße Dieter

[balu69]

Hi Dieter
Hi
The spin is such that the left and right control commands are suddenly delayed or not implemented at all, and the aircraft enters an oversteered state. As far as I can tell, the aircraft also (automatically) goes into a dive.
If I manage to press pause (which sometimes also happens with a delay) and wait a moment until the CPU is no longer at 100%, the aircraft functions normally again.
Thanks for the tips. I've been looking into the current ATCs again (PF3, Pilot2ATC, VoxATC, Pro-ATC SP) and I find that FSHud is the best product for me.
Reproducing it is sometimes difficult; I can do 2-3 identical flights, and it happens again on the 4th.
I have an AMD, and I disabled SMT, and I'll enable the resource monitor next time.
Do you mean the [JobScheduler] entry in the Prepar3d.cfg? I'll adjust this one http://izn-flightsim.s3-website-us-east ... esetAnchor

Hallo Dieter
Das trudeln ist so, dass plötzlich die Steuerbefehle links und rechts verzögert oder gar nicht umgesetzt werden und das Flugzeug in einen übersteuerten Zustand gerät. So wie ich feststellen kann, geht der Flieger auch (automatisch) in einen Sturzflug über.
Wenn ich es schaffe, die Pause zu drücke (die geht manchmal auch verzögert) und einen Moment warte, bis die CPU nicht mehr auf 100% ist, funktioniert der Flieger wieder normal.
Vielen Dank für die Tipps. Habe mich wieder einmal mit den aktuellen ATC's auseinandergesetzt (PF3, Pilot2ATC, VoxATC, Pro-ATC SP) und finde halt, dass FSHud das für mich beste Produkt ist.
Das mit dem reproduzieren ist manchmal schwierig, da kann ich 2 - 3 gleiche Flüge machen und beim 4 passiert es wieder.
Habe ein AMD und da habe ich SMT ausgeschaltet und den Ressourcenmonitor werde ich beim nächsten mal aktivieren.
Meinst du den [JobScheduler] Eintrag in der Prepar3d.cfg? Werde diesen mal anpassen http://izn-flightsim.s3-website-us-east ... esetAnchor

[dkreiskott]

Yes,I mean the Jobscheduler, but only the Main thread. I set it from 0 to 6. Nothing else!