iFoxRomeo

@Gadreel attach a track please. I fly the Dora since release and I never had an engine failure out of the blue

Nineline sagte im discord was dazu: Sinngemäß: Da es nur mit Nvidia Grakas funktioniert und ED nicht die Manpower dafür über hat, wird es erstmal kein DLSS in DCS geben

Sobald Tacview installiert ist, sollte es mit der options.lua auch klappen Fox

Wenn du Tacview auch auf dem Server installiert, kannst du das Delay einstellen. Ansonsten macht Tacview auf dem Client standardmäßig 10minuten, da es erkennt, dass Tacview auf dem Server nicht installiert ist. Fox

Tracks are automatically saved in MP. Just check your track folder.

Please attach a track

Try PD 1.0 in DCS and in the oculus tool. Then increase the PD in the Oculus tool only, till you get a good compromise. But keep DCS PD at 1.0

Do you know what data ED used? I have no idea.

You can use what you want. But I prefer real testflights as they show the real aircraft and not a calculated one. A single report contains several flights by several pilots. That's how its is still done today. Calculations are a good "estimate" what to expect from the projected aircraft. The errors can go in both directions. Flight tests remain the real thing, for several reasons: Engines perhaps don't deliver the promised power, airframes create more drag than thought due to big tolerances during the building process etc..

For example: www.wwiiaircraftperformance.org/fw190/Fw_190_A8_733705_Rep2.pdf A Flugbericht contains information like when, who, what, how etc,; it has a little bit more than only one graph. At least there should be some measurement points on the graph that are then connected to a line. At first I also thought that these graphs are taken from testflights, but these are calculations. It doesn't matter if WE know how they transformed values. They knew better than WE(majority here in the forums) do now. Yes they changed the engine. I wouldn't consider this as "little". Obviously that previous engine was faulty. I made some comparisons to the linked testflight with the DCS:FW-190A8. And it did compare quite well with Startleistung. Kampfleistung was a little bit too low. Fox

Really nice!

@Blackbird12 All these diagrams are calculated values. They are higher than what the real aircraft could achieve. You are correct with MW50. It was tested; no significant gain was the result and little cracks in the engine appeared during the testphase. I have to look for the source for this, will post it when I find it. Instead increased boost pressure was used and provided a significant power increase. 1.65ATA was used for the "JABOREI" case with additional C3 injection and only for the "bodenlader" (1st stage of the booster). In the fighter configuration 1.58ATA 1st stage, 1.65ATA 2nd stage. Fox

I was wrong. My memory made me believe the stick forces where weaker when the K4 was released. I installed DCS 1.2.16. Well I only tried to break the wings. But it behaves similar to the current version. Stick forces seem to be the same. And it is still possible to break the wings. Probably with time I got a more smooth flightstyle, hence I never broke a wing on the K4 in the last years.

Show it, or it didn't happen:pilotfly:

When it was in EA, there was not force limiter like we have it now. It was possible to break off one or both wings, if you forced it. Unfortunately I didn't record any videos about this.

What are your ingame settings? PD in game, in Oculus?

Hast du Hardwarebeschleunigte GPU Planung in Windows 10 aktiviert? Das verursachte bei mir diesen Effekt. Fox

Had that happen too... log out and in worked...

The point is, that the flight manual says to keep this CB off, unless you use a drop tank. I never experienced this sudden engine death in the dora, never. And I bought it the day it was available. Last weekend I made two testflights (time accellerated) that lasted 1.5h each. One with 2400 and the other with 2200rpm. Nothing happened. A few weeks ago I also did a online testflight on SoW with the dora a high power setting. Also, nothing happend. You seem to have this problem very often. Just fly with the mentioned CB off, just to rule it out as possible source.

Meine Vermutung wär, dass dein Prozessor hier der Flaschenhals ist. Kannst du die Frametimes anzeigen lassen? Bei WMR for Steam kann man anzeigen, ob CPU oder GPU schuld daran sind, dass nicht die vollen FPS erreicht werden, plus eine Frametime Anzeige. Da ists bei mir meistens so, dass die 1080ti nicht mehr hinterher kommt, um 45fps zu halten. Will mir ne 6900xt holen, werd dann berichten, wie es bei mir läuft, mit nem ryzen 3900x. Nicht, dass deine 3080 sich langweilt, weil der Prozessor nicht genug füttert. Fox

Thanks Nineline. That is at least some positive info for the (nearly) 5th birthday of this thread. Maybe, just maybe, you have a picture for the 23.November?:cheer3nc: Fox

I don't know how deep the fuelsystem simulations is. But could you do the test once again, but keep CB E85 on the fuel panel off? Unless you have a droptank attached, and only as long as there is fuel in the drop tank. I'm not at my gaming pc right now, so I can't run your trk. Will do that at the weekend. Fox

Top. Freut mir

Da hab ich auch was, aber nicht ganz so kurz. Mir gefällt es auch sehr. Fox

Probier mal forgendes: In C:\Users"enter your name"\Saved Games\DCS(.openbeta)\Config\ packst du ne autoexec.cfg, falls du nicht schon eine angelegt hast. Dort kommt dann diese Zeile rein: no_device_hotplug = true Wenn du noch keine Autoexec.cfg hast, kannst auch die hier angehängte nehmen Dann sucht DCS keine neuen USB-Geräte und diese Meldung und die dazugehörigen Probleme sollten verschwinden. Aber, wenn du während des Spiels ein USB Gerät(Joystick) entfernst, wird DCS es erst nach einem Programm-neustart wiedererkennen. Fox autoexec.cfg