evensis

Runs fine for me on my 7900X so definitely not all AMD users, buttery silk smooth with the most consistent frame times I have ever seen. Very impressed so far, well done ED! No change to the base FPS, but there's a noticeable fluidity that wasn't there before, and I haven't had a single stutter, micro or longer. Just to point that if you have a 5900X and up (it may affect lower core count models or older gen but I have no point of reference) if you turn on 'game mode' in Ryzen Master, it will turn off one of your CCD's, and halve your core/thread count. I suspect many don't notice or even realise this happens, it took me a while to work out when I randomly found my CPU cores halved in Window's task manager after running with it for over a month. May or may not make any difference, but there might be some performance there you didn't know you had.

Moore's Law is Dead sources have stated that the 7900XTX has at least 10% rasterisation performance across the board in the pipeline with driver improvements. Unfortunately no mention of VR performance in his videos and source leaks but they do expect to eek further performance out of RDNA3 beyond that 10%, but will be a wait and see. The 7900XTX is not performing anywhere near its design goals at the moment, and needs a significant amount of further driver work of which AMD sources are 'confident' that they will fix the issues with the drivers. Ultimately if this comes to fruition, then the 4080 really will be exceptionally poor value for money at it's current MSRP (even more beyond its poor value at this point) - buyers remorse will be a big thing. Although just to chuck this out there, going from a 5900X to 7900X boosted my frame-rate average quite nicely, 75fps on the 5900X over Caucasus to 92fps avg on the 7900X (in the pit with a 3080); so certainly another route to consider if you are looking to improve performance. Ultimately i'm a developer so the 24 threads is useful to me and shaves enough time off for me where single generational jumps are economically viable, but for others who don't use the cores, the 7700X or the 5800X3D would be a good choice. Intel have brute forced their way to the top of the leader boards this year by rinsing your utility bills more so than the war is already doing, so factor the electricity average (another 100 watts during high load over the lifetime of the product) into the cost of the product. AMD on the other hand, forcing DDR5, makes the platform a high cost to move to. So it's swings and roundabouts. I would wait a quarter and revisit, the GPU market is a mess at the moment.

Hi, Been playing with the new throttle response on the F18. I noticed that the external model is not syncronised with the internal model, the most noticeable impact is the sound of the bang as the afterburner ignites, its almost immediate, if one is above 80% throttle in the cockpit, however, as soon as you look externally and do the same test, its taking seconds for the afterburner to ignite, certainly not matching with the bang internally. Or perhaps the ignition bang is timed wrong, or, the bang isn't actually the afterburner, who knows, but definately something not right there! Short track attached with demonstration. Thanks external-model-sync-issue.trk

I can reproduce this every now and again, when triggering AMRAAM on weapon select, when on the ground. The HUD goes into navigation mode, the instant the aircraft starts moving. If you weapon select in this small zone of initial inertia, the HUD makes a small change but you cannot select a weapon. By looks of it the A/A mode is disengaged, selecting a weapon will not engage A/A mode. This effect gets canceled out once the velocity goes above 20 knots as far as I can tell on SP (not sure why, you're still on the ground), however, on occasion, it sticks. I was noticing it on MP, single player interestingly, regardless of what I did, I could not reproduce the effect. Flicking a/a mode on and off does resolve it when it happens though. However at the very minimum, being able to select A/A on the ground was a recent bug fix, if the initial movement of the aircraft turns it off, seems it would add to pilot workload if in real life and counterintuitive. I do have a track but its from a rather extended gameplay session on MP and I imagine a bit of a nightmare to navigate. I will try next time I am playing MP.

Serial #: 99234 Location: East Sussex, UK

Click on taskbar, find the sound icon, right click it and select "Playback Devices". Find "Headphones Rift Audio", click on it and press the 'set default' button near the bottom of the window. All should work. Just plugged my GTX1080 in today for my CV1, didn't make a blind bit of difference to FPS :) DCS is the king of CPU bottlenecks!