TZeer

But I don't understand why they push unfinished FM changes to the live build, if it's a regression in overall FM quality. If the change improves the HOLD function, but the overall feeling and quality of the FM is worse. Then the FM change is not suitable to be pushed to live build. Quite simple really.

The insane part here as well is the premium they are charging for it...

Doesn't matter what cable they use. The problem is that there is no monitoring or any system in place to let you know if one wire starts to draw more current than the others. I think there are a few partner cards that have possibility to monitor if there is uneven distribution, but that's it. From the info and reports that have come so far it seems that it's so small safety margins that even doing everything correct will not guarantee you not getting hit by the problems. This was demonstrated by a guy where he plugged in the card 2 times with the same equipment, one where everything was within spec, and one where the the current in the wires where out of spec. Nothing physically changed in the setup. And with the small amount of 5090 cards that have even hit the market it's worrisome.

In general: 1: No, the cable is similar. The cable is nothing high-tech. Problem in the video is an extremely uneven distribution of power through the different wires. Some of the 3rd party cards has monitoring to check for these problems. But Nvidia founders card has not. But regardless, it's a <profanity>ty design and extremely poor QA from Nvidia's side. 2: It depends how much load there is on the GPU.

Seems the 5090 is even worse than the 4090 when it comes to potentially melting cables. 130-150 degrees celcius on the actual connection. Uneven powerdistribution through the cable. Does not look good.

I have seen the same behavior when flying low. Specially when flying helicopters. If I look straight ahead, it sometimes goes ok. But as soon as I turn my head and look into the trees my frames take a dump. It's not as noticeable on desert maps. But very easy to trigger it if flying low on the Caucasus maps over larger areas with trees. I also get it every time I fly low on Syria in clusters of vineyards. At a certain distance the frame time spikes.

I'm mostly a rotorhead, but I was surprised (in positive way) on the announcement for the F-35. No one is forcing anyone to buy or do anything with it. Servers can restrict the use of modules based on what kind of gameplay they want. This can be an interesting module to play with

To bad, I've had my eye on this for a while. Just been waiting on it to "mature". Guess I'll hold on to my money for a while longer...

I did some testing now, and it seems the CAS still give some input to the YAW while on the ground.

Do you have the latest version of DCS installed? I know it had that behaviour before. But should be greatly improved (fixed?) in the latest version.

Changed to the Huey to see if that helped. But still get the occasional drop in performance. It ssems to be correlated to bushes/trees/vineyards. When I get to close, the performance drops enough for my CPU to become a bottleneck. Get some distance or look the other way and the FPS goes back to 72 FPS...

I will upgrade to 9800X3D when they come into stock. But as it is now, everything is sold out until February in my country. Anyway, I upgraded my old 5800X to an AM5 platform and snagged a used 7900X CPU as a temporary solution. I use a Quest Pro, and I was surprised that my 7900X was the bottleneck when flying in somewhat isolated part on the Syria map in the Apache. I do use the Foveated Rendering, so I guess that might put an extra load on the CPU. But was hoping I could hold 72 FPS flying around in a sparsely populated area on the map. When using the 5800X I used Nevada mainly, due to how easy it was on the system getting 72FPS. My GPU is the 6900XT, and I have dialed in the settings so I'm getting up to around 90% utilization, before the CPU get bottle necked and cuts my FPS in half. I have 72 FPS while taking off and 90% of flight. I have already closed out all useless background apps. I have a optimized win 11 installation done with a custom ISO file made with winutil from christitus. https://christitus.com/winutil-install/ Any specific settings in DCS that heavily goes on the CPU that I can optimize? Or is it just wait until I get hold of an 9800X3D? Or keep flying on Nevada map?

Did some testing now, and I must say I'm very happy with the improvements. Feels much more controlled on the yaw. Very noticable while taxing. I have a Virpil pedal with a dampener-mod, and even with that setup the tail had a tendency to violently kick out when trying to do a turn while taxing. Now I'm able to do a much more controlled turn. I also noticed the constant oscillating behavior of the yaw is gone while flying straight. And the much more controlled behaviour of the helicopter when going into hover from forward flight. Before the change there was like a rug getting pulled out beneath you when getting below a certain speed, now it's actually somewhat predictable. Great work @Raptor9 and the rest of the team. Looking forward to the next improvements in the FM

Is the excessive sideways slip fixed as well?

Good news. Meta decided to do a full unit replacement