Hoirtel

We are all focusing on the F15E development and well, maybe ED want to get the core engine all nice. This is a huge release for the platform and I would fully respect a decision to get everything working well for this module. Just wish they could have waited a bit to light the hype fire...

Seems a lot of hype for July release, there is only so many videos I can watch. What good is five cold start videos two months before release? I hope they were trolling us but seems an odd troll. They should say two weeks, when it is actually two weeks away. That would be funny and honestly what I thought they were doing last time....

So after quite a while I have some benchmarks to post. Nice little improvement all benchmarks done with the same 3090. Old system is i9 9900KS 64Gb DDR4 3600 C18, new system is 7800X3D with 64GB of Kingston fury, this is rated to 6000 C36 but for below tests it is running without expo. Expo is making no difference at the moment due to GPU bottleneck. Shame capframe X doesn't let you make these bar charts with the average frametimes rather than FPS. The individual analysis tabs show a decent lower and more consistent frametime on new system. I can also feel this at all stages of flight, the whole thing just feels more fluid and responsive. Didn't expect that. Tests done with plasma torture track, high preset, 2D, 1440p. Tested ST and MT on both systems.

You will be very very GPU bound. I've gone from a i9 9900KS OC'd at 5.1, to 7800X3D using the same 3090. The 7800 is very very GPU bound now whereas the 9900 managed to load it to between 80-98%. EXPO makes no difference for me here, due to GPU bounding. I have some stats to post later.

Somebody else pointed it out in this thread couple of months ago. I watched it back and saw. He also says he gets asus's "refurbished" or returned boards. Not a good move.. might explain some problems? Maybe not.

Dunno if it fixes it or not yet, but I expect that setting the SOC low enough would half fix it anyway, and dont think any of the bios updates fix the borked OCP unless they just left that out of the change notes.... Doubt it will get tested aside from the user base, but we got nothing else to do but try it and be vigilant. He did put the ram in the wrong sockets. It was in the video.... Just saying...

Asus Strix X670E-F has new stable bios posted today, so I would assume all current Asus boards have one.

Not disagreeing, but the warranty voiding disclaimer has been removed from the bios downloads - some of the attention is getting through.

I'm in similar position, will post my results soon. Much less improvement from a OC 9900ks than I was expecting, but it is improved. No expo, I was hoping that it would add a bit but maybe not. I have seen videos that memory of makes no difference for X3D so if that's the case then it might be best off considering. 5800x3d didn't need it I think. What bios are you running @Fakum

It's a DCS simple and heavy track file that allows us all to run the same gameplay to compare hardware. The track file is linked in this thread in the earlier posts. Scroll back through and you will find it.

Yeah it's crazy. For the x670 there is two betas in a row and last "stable" is long enough ago at the moment to not be correct. They were taking the old ones down but now I have a choice of three betas and and out of date stable. Nice. Build on hold.. still.

Interesting... and a bit of a blow along with the current X3D issues... To be really sure what's happening it would be nice to see a proper benchmark that has additional load on it. I don't think flying round an empty Caucasus map is the best test, however I wouldn't expect big leads either way. I would prefer to see it over a big city on Syria or over Marianas with some added units. What is a bit more unknown for me is that all the tests are really at the frame lock of the headset so not really unconstrained, it does look like the 12900 has more to give and the 7800 doesn't, but the constraining behaviour could just be different. There is terrible aliasing so I would assume the resolution is low which is how they test 2D games, but for a headset with an FPS lock this doesn't really work. Other thing to consider is the recording itself, intel may be better at multitasking like this. Having said the above, can't see there would be a be massive difference rather than trading blows at best. Anyone wanna buy a unused x3d...

Yeah, maybe. One of those things that would need to try to see how it works. Just needs the integration of comms options and VoIP to be a bit better. For your example, it would be good if they could install two radios in jets to they could do these types of things easily....

My X3D has been totally fine and cool, but then it is still in the box...

Yeah literally just finished watching it. So glad they are doing this... but what a crazy mess. Feels like this is a bad result of competition to intel, with AMD just pushing tech to the point of it almost not being suitable for mass market.

What will be interesting is the integration with the Comms menu, I think it would be interesting to block VoIP on frequencies that are set to airfields, tankers etc so that they are distinguished. One big problem with SRS at the moment is needing two bindings for each transmit button, so that you still access the Comms menus (not entirely avoidable) and also have another for talk. From looking at the button map it looks like two bindings are still required but maybe this will change.

The current status as as far as I was aware remains unchanged and that it is not available for use in DCS even if enabled manually. This is because Nvidia has locked it to compatible titles or whatever the commercial agreement is. Prior to lockdown it did improve smoothness for me in VR, no FPS increase but good reduction in ground stuttering. I could literally switch it off and on with completely repeatable results. This was on a much older version of DCS, maybe an early 2.7. Then one Nvidia driver locked it, and on or off performed just like off. Rolled back to old driver and it was smooth again. I have since moved on to the many GPU driver updates since then and DCS has had a lot of change in this time too. I continue to run with rebar enabled and see no difference in DCS with it on or off, suggesting it is still locked.

2017? Errr.

It seem the root cause of the issue lies in RAM overclocking and not directly CPU overclocking. Some ram expos require SOC voltage over 1.3 (which is on CPU) which seems to be the danger zone over extended periods. This is still early information so I am sure there will be more detail to come, the safe position at the moment is not not run any expo settings. This could be problematic as if the fix involves a hard lock on SOC voltage then it may make a whole load of EXPO settings invalid for life and the only way will be manual tuning or standard timings. Considering vcache is supposed to be less sensitive to memory I would be interested how much this reduces performance. I will be building my machine soon and will not run EXPO at this time, coming from my old PC I still expect better performance and I will see what happens. Bit annoyed at this whole EXPO/XMP thing, they all advertise it but when it goes wrong they say that it shouldn't be done. When I build my new machine and it asks for a name, it will be "shouldhaveboughtintel" Source: Update: Just noticed that yesterday (25/4) another new ASUS bios has been released and all the last ones have been removed. This is a beta for now, info included is: SoC voltage for Ryzen 7000X3D series limited to a maximum of 1.30V to protect the CPU and motherboard. Before running the USB BIOS Flashback tool, please rename the BIOS file (SX670EF.CAP) using BIOSRenamer. Please note that this is a beta BIOS version of the motherboard which is still undergoing final testing before its official release. The UEFI, its firmware and all content found on it are provided on an “as is” and “as available” basis. ASUS does not give any warranties, whether express or limited, as to the suitability, compatibility, or usability of the UEFI, its firmware or any of its content. Except as provided in the Product warranty and to the maximum extent permitted by law, ASUS is not responsible for direct, special, incidental or consequential damages resulting from using this beta BIOS. This includes a nice little note about using a beta BIOS which is currently the only option... Seems I won't be building at all now.

Ah new adopter blues. Maybe my case being out of stock has been a good thing. Now thinking it should all stay in the boxes! Not watched this yet but should also be a good point if view.

Great thank you. I wasn't quite sure for a while. That's good there is a workaround, and a fix.

Thanks for posting. What motherboard is that?

Reports have specifically mentioned x670E boards.

Just been reading about this. First time I decide to go Asus and they seem to be having a lot of problems!! Kinda glad my case has been out of stock as I haven't built the PC yet. Did see the latest bios is dated 21/4/23 so hopefully this one is ok, may leave it all in the boxes for a while until this has been worked out.

Hi I am assuming that this is a bug, but I am brand new to this aircraft and so may have got something wrong. It appears that the rudder starts deflecting randomly when there is wind and turbulence set in the mission. This also appears to be more pronounced on airfields that have a higher elevation. I have included two tracks, with and without wind and turbulence. The conditions are not unflyable so its not a crazy weather type of scenario. I have checked all bindings and it does not affect nosewheel steering and it does not appear on the controls indicator. I have checked the rudder trim too. F1EE Nevada - Wind and Turbulance.trk F1EE Nevada - No Weather.trk I have also made a short video to show the problem, and how it persisted down the runway and into take-off where it was really bad. I did notice that after take-off, a full deflection of the rudder pedals seem to completely stop it, however this was not the case on the ground. All testing was done with hot start aircraft. I have also probably done many things wrong as this is one of my first few attempts at flying so it wouldn't have been pretty even without this! Sound is quiet until the external shots, turn sound down.