Hoirtel
-
Posts
1299 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Hoirtel
-
-
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.
-
3
-
-
10 hours ago, Jonay said:
When I'm in 2D it states GPU bound, so it does have some purpose.
I know I'm only on a 2080S 8GB card, but I would have expected at a tiny improvement from my previous CPU, considering I've also bumped up from some medicore 32GB DD4-3600, to 64GBs of DDR5-6000
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.
-
34 minutes ago, SkateZilla said:
missed that, but doesnt explain the problem he continues to have.
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.
-
2 minutes ago, BitMaster said:
That's not enough to remedy the damage.
AMD and Intel need to respond to the XMP/Expo vs. Warranty issue as well. You shouldn't be allowed to advertise a feature but using it voids your warranty.
Anyway, does the new Bios really fix the issue, I thought I read otherwise today but I might be wrong and the Bios is newer than that article I flew over.
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.
Just now, SkateZilla said:Expo on ASUS has been a problem since day 1.
JayTC went thru like 3 mainboards already.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.
-
2 minutes ago, SkateZilla said:
Was about to say,
We've been following this closely on the "overclocking" forums/discords.
ASRock seems to have the least amount of AM5 problems,
But ASUS' Build Quality and Support have gone in the toilet, they literally email you back with a beta bios, that voids the warranty if you email their support.Not disagreeing, but the warranty voiding disclaimer has been removed from the bios downloads - some of the attention is getting through.
-
1 hour ago, Fakum said:
I still basically have BIOS at default settings. I ran benchmarks for Cinebench, Heaven and DCS Torture test, then I set BIOS to EXPO 1, ran tests, then EXPO 2. if an7ything, there was very slight degradation with each change. I havnt done anything with Overclocking. Im not going to start putting the hours in to do all of that right now. My intent was to simply set the BIOS to do something to take advantage of the horsepower on its own. I see mentions of turning PBO on, and walking away. I have also seen some comments relative to this that indicate that in doing so, it cranks up the CPU voltage most of the time, perhaps a bit unhealthy? I am willing to flip a switch and check it out. I ran into some confusion though, there seems to be at least 3 switches in the BIOS that could be fiddle with and Im not sure which one I should be toying with. And the explanations I have found in my search are a bit convoluted. Can someone please give me some advise in this area? Thank you.
null
null
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
-
1 minute ago, Fakum said:
@Jive_68 I am trying to figure out what this " plazma torture map" is? I presumed it to be some sort of benchmarking software so I searched for info. Basically the only thing I have come across are some uTube vids that show guys running some tests in some different games. I have seen 2 that show them using DCS. Can you point me in the direction that I can get some info about this so i can educate myself? I would rather use DCS as a benchmarking tool than Heaven or Cinebench exclusively. Thanks
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.
-
16 hours ago, Cavemanhead said:
Just checked Asus website for the new bios and there is a new 1602 version released... And it's still a beta! Wow, this is so ridiculous.
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...
-
50 minutes ago, rob10 said:
Can't agree with taking that away. Yes it's a bit of a pain, but reality is that in MP in many cases you're going to want to both be able to use the COMMS menu options AND communicate with other players on voice on the same frequency (i.e. landing on the carrier we use the COMMS menu mainly to get BRC, but voice call the rest).
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....
-
1
-
-
48 minutes ago, LucShep said:
Indeed, excelent work as always by the GN Team.
I just feel manufacturers are borderline scamming the customers/users.
Realizing how motherboards got increasingly ubber expensive (double the price compared to older iterations) and yet, bugs aside, they still lack protections.
With Intel, I recall dozens of systems built where I'd need to lock the vCore, and especially the VCCIO and VCCSA, to "normal" levels, as some motherboards would have those placed at sky high values once XMP was loaded, not just with "load optimized defaults" (and temps going crazy). Most users would be unaware of this, it's just not right.
Now it's bugs with AM5 motherboards...
I think I'll refrain from recommending an AM5 system (X3D mostly) to friends and customers until this is fixed.
Feels like a friggin "early acess game"!
Meanwhile, how are you guys countering this issue? Any good "safe" solutions so far?My X3D has been totally fine and cool, but then it is still in the box...
-
1 minute ago, some1 said:
Solid investigation about the recent issues.
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.
-
1
-
-
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.
-
2
-
-
On 4/19/2023 at 9:29 PM, Fakum said:
Im in the process of a new build and stumbled across some comments about this Resizing BAR, so I did some digging to get educated. The shorter version of my findings are that I learned alot just from this video. A few things that I got out of it were:
-You can manually turn it on for DCS
-It does take a bit of the load off of the CPU when enabled
-Reading through the comments though, it may have a negative impact in DCS and although it MAY increase your FPS slightly, it may also be creating more latency between frames resulting in more FPS, but more stuttering.
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.
-
1 hour ago, LucShep said:
From Igorlab's website (still one of the most rock solid sources of info on PC tech):
https://www.igorslab.de/en/neues-asus-am5-bios-beinhaltet-einen-unerlaesslichen-mechanismus-um-schaeden-an-amd-ryzen-7000-cpus-zu-vermeiden/
quoting:
"The creator of the Hydra tool for AMD Ryzen CPU tuning and optimization recently made a shocking revelation. He claims that AMD and board partners knew about a CPU power supply issue before Ryzen processors were launched in 2017. Despite this, AMD asked board partners to keep it a secret. The problem is that the voltage supplied to the Ryzen processors is not constant. As a result, the CPUs do not run stably and often crash or are unstable. The only solution that the Hydra tool creator has found is to overclock the CPU to stabilize the voltage supply.The revelation that AMD and board partners knew about this problem before the processors hit the market is very worrying. Customers who purchased Ryzen CPUs may have received inferior product performance and may have paid for problems and inconveniences that could have been avoided. It’s unclear why AMD decided to keep the problem a secret. However, it is possible that the company feared that revealing the problem would lead to a loss of customer confidence. However, AMD is feverishly working on a solution to the problem."
2017? Errr.
-
1
-
-
7 hours ago, dugite57 said:
A bit of a response from AMD; "We are aware of a limited number of reports online claiming that excess voltage while overclocking may have damaged the motherboard socket and pin pads. We are actively investigating the situation and are working with our ODM partners to ensure voltages applied to Ryzen 7000X3D CPUs via motherboard BIOS settings are within product specifications. Anyone whose CPU may have been impacted by this issue should contact AMD customer support." -- AMD Spokesperson to Tom's Hardware.
I conject that there will be a fix via bios coming soon, In the meantime I'll be letting mine just run at stock until this is sorted. These CPU's are IMO pretty much overclocked by default. There's not much headroom like we saw in our old unlocked intel cpu's like my 4770k etc. So for me the gains by overclocking offer a poor risk vs reward result. The cache chips siting on top of the cpus compromise the cooling and it doesn't take muich of a voltage tweek to fry it.
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.
-
12 hours ago, fausete said:
Hello,
This is a known bug introduced in the last update. We have an internal fix for it that will be made available in the next update. In the meantime, turning off and on again the yaw damper (3 position switch in the front left panel, close to the gear lever) ends the oscillation events. Sorry for the inconvenience.
Great thank you. I wasn't quite sure for a while. That's good there is a workaround, and a fix.
-
1
-
-
7 minutes ago, some1 said:
My 7800X3D arrived earlier than expected, so I've been able to install all the components yesterday and ran some DCS benchmarks myself. Compared to my previous 5800X3D with 4x16GB 3600 CL16 RAM, the new setup has 7800X3D with 2x32GB 6000MHz CL36 DDR5 RAM. Which I set to CL32 optimized secondary timings using Buildzoid's settings from the video posted above.
Overall, I see around 20% more FPS in DCS on 7800X3D vs 5800X3D, tweaking the memory timings and -20 Curve Optimizer adds another 2% on the Plazma test track. Most of that 2% is thanks to the timings, CO-20 is within the margin of error, even though the CPU boosts noticeably higher.
Likewise, CPU frametimes in VR are around 15% better, but that's harder to measure reliably.
Here's my old 5800X3D on Plasma test track, 1080p, no mirrors, clean DCS on High preset. Blue line is GPU usage:
Here's 7800X3D, same setup, all settings stock, with memory on EXPO profile (6000MHz CL36):
And here's after I added -20CO and tweaked memory timings.
20% increase in CPU performance is a substantial difference between CPU generations, but not really worth the upgrade from 5800X3D unless you have the money to burn. Also for those using older AM4 CPUs, 5800X3D is still a very good value upgrade compared to the cost of the whole new AM5/Intel platform.
Thanks for posting. What motherboard is that?
-
3 minutes ago, EightyDuce said:
I haven't had any issues on my B650E-F (currently on v.1410), but I may roll back to the 4/21 v1409 just to be safe.
Reports have specifically mentioned x670E boards.
-
1
-
1
-
-
22 hours ago, BitMaster said:
I don't want to hold you guys back tuning the X3D chips, it sounds like some fun but there is this serious risc of burning it out.
https://www.tomshardware.com/news/amd-ryzen-7000x3d-burnout-reports
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
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.
-
5 minutes ago, RSharpe said:
You will have to make sure you're getting Hynix and not Samsung. He did it on M-die, but A-die works as well. My kit is A-die. Trident Z5 Neo kits at (2x32GB) 64GB 6000 CL30 are likely all A-die for the moment.
Yeah it is, should have mentioned that! I did a lot of looking and searching for RAM. Its Kington Fury Beast. Just could not get any Gskill over here and the only other kingston was renegade which says XMP only. Didn't want to risk it.. seen the jaystwocent video...
-
1
-
F-15E WIP Update Discussion
in F-15E
Posted
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....