Sandman1330

Interesting that you are hitting 498 CB20 single thread, mine is also 498-500 single thread, but I’m showing much lower single core boost. Maybe it’s just something to do with the reporting software, maybe I’m actually boosting the way I should? That being said, most reviews were in the 520-550 range...

Because of the density of the die, temp swings are massive. Starting an all core FFT on prime95, mine jumps immediately from 35 to 90, then holds around 90. There are just so many transistors in such a small package that there’s nowhere for the heat to go until the spreader and heat sink start to soak it up. I’m glad to hear you are single core boosting well, I’m still not getting past 4.2ghz. What bios are you using for your C6H?

Hasn’t been an issue since the first week. Either a firmware update fixed it or something else changed, but no issues now!

Mic still works with headphones plugged in.

I’ve got something similar set up to spawn different tasks from the F10 menu. For air to air, there are several of them to spawn, but in all cases once you run out, you run out. To solve this I’ve got the option to restart the mission in the F10 menu as well. Just use “run mission” and select the mission file, and it works nicely. This is my mission file, feel free to reverse engineer it: https://forums.eagle.ru/attachment.php?attachmentid=215710&d=1566089374

I think the magic number is 3800mhz, right? I’ve yet to get my ram higher than 3200, though I haven’t played with timings much. With first gen I never even got it to it’s rated 3200! I haven’t been too worried about my low boost, as DCS is now GPU limited at my settings so extra CPU tweaking will have minimal effect anyway.

There’s very little manual overclock room in 3000 series. They almost seem to operate more like GPUs, clocking themselves as high as possible within power and thermal limits. Indeed, mine actually runs at 4.1 all cores during stress testing, and that’s with all settings at auto. You don’t get better performance with manual overclocking on these chips. Now if my single core boost would start hitting somewhere near where it should (4.6ghz), that would be nice! Hopefully AGESA 1.0.0.4 will bring improvements. Low and medium settings are definitely CPU bound. I’m running 1.2 for PD in VR. What program do you use to benchmark? Does it create the fancy graph for you?

Thanks guys! Nice work Hardcard, what a great and easy to implement script! Edit - It's working great in single player, but when I try to run it on my multiplayer server, the planes blow up! Any ideas? My mission is attached: Edit again: I see it’s a known issue on dedicated servers. Hopefully you’ll find a fix! Sandman's Server - PG - V1.1.miz

Here's a super basic mission with just 2 A10Cs to try it out. SWAPR sees them when I go into spectators, but nothing spawns. Thanks! SWAPR Test.miz

Hi Hardcard, Thanks for all the hard work on this! I'm having trouble getting it working. I'm coming in cold to the plug and play version (never tried the previous version), and I'm a bit new at scripting and ME. I've added the _Client and _Plane suffixes to my pilot names, and I've modified the lua file to look for those 2 suffixes. When I load the mission and select spectators, SWAPR sees the 2 clients I've added the suffixes to (I get the SWAPR Count = 2). However, no statics spawn in their spots. Clearly I'm missing something, but I can't figure it out. I've watched the new video, but I'll admit I didn't watch the old one as it seemed to include a lot of stuff that's not needed anymore. What could I be doing wrong?

I hope so too, I'd hate to think I paid as much as I did to max out at 4.2Ghz when I could have paid less than half for a 3600 that boosts to the same single core frequency. Indeed, I may even consider starting an RMA process if the BIOS doesn't fix it.

I know some people are saying that, but I don’t think it’s true. It think immature BIOS is to blame and it will eventually get sorted. Mine doesn’t exhibit that behaviour, I never see 4.6ghz.

I got super lucky. On the morning of 7/7 I put in a pre-order for both the 3800X and 3900X with my local store, fully intending to actually get the 3800X but willing to take whichever showed up first. They got a small number of 3900X in the first week and I managed to get one, but they’ve had none since. The 3800X still hasn’t arrived there. Truthfully, until we get an updated AGESA BIOS 1.0.0.4, the chip is not performing as it should anyway. I’m only getting single core boosts of 4250, nowhere near the 4600 I should get. So, you’re not really missing THAT much, just the early adopter growing pains!

Sorry, still can't. I don't have SU25 or FC3.

Those numbers seem freakishly high for an older and non-OC processor. Was that running the track I posted? Was the viewpoint on the track looking straight ahead the whole time? It should also be noted that BIOS for 3000 series is still very immature. My chip is only boosting to 4.2-4.3ghz right now, 4.4 is achievable in game mode. It should boost at least to 4.6, up to 4.8 with good cooling and power delivery. I think there will be more performance to be had as BIOS improves.

Thanks, I’ll give it a look! I really lost the silicon lottery on this RAM. With first gen Ryzen, I was stuck at 2933, and eventually got it up to 3066 on later BIOS. I’ve had no problem with 3200C16 on my 3900X, though it does occasionally fail to POST. I tried going higher, but any higher than 3200 immediately fails to POST. maybe with more tweaking, but I think it’s already near max.

OK guys, as requested, here it is: -Using the attached track file (free flight over Tbilisi), -all non-VR benchmarks at 1080p (sorry, I don't have a 1440p monitor like Dackster, so I cannot duplicate his settings). -FPS measured with FRAPS. -Computer specs in sig, 1080ti slightly overclocked. -3900X is set to game mode in Ryzen master (disables one of the CCX for higher single core boost). Low preset: Min: 1 Max: 189 Avg: 177 (I don't know where the 1 min comes from...) Med preset: Min: 1 Max: 200 Avg: 179 High preset: Min: 88 Max: 188 Avg: 126 (High preset, plus 4 x MSAA, 16 x AF, all sliders maxed) Rift S, VR preset: Min: 0 Max: 81 Avg: 79 Rift S, High preset (as above): Min: 1 Max: 81 Avg: 45 (ASW was off, but it still seems to like to hang around 40 or 80, though occasionally it will hit FPS between 80 and 40) So, at 1080p low/medium settings (where we are CPU limited), frames are high enough for even the highest refresh rate monitors, if that's your thing. If eye candy is your thing, you'll be GPU limited, as you can see the numbers going down due to GPU maxing out at higher settings. In short, this CPU will not hold your GPU back at all. Indeed, you may even be better off saving a few hundred and getting a 3800X or 3700X and putting the rest into your GPU, as I don't think the performance of those chips will be far behind this one. tbilisi benchmark.trk

It sounds to me like you are still processor limited. The way windows scheduler bounces the thread between cores, it happens so fast that you never get a reading of 100% on any core. Try this experiment: lower all settings to minimum and note your FPS. With your proc, it will probably max at 90, your HMD max refresh rate. Then add eye candy settings one at a time (textures, MSAA, PD) and note your FPS. At some point (probably with lots of eye candy in your case), your FPS will start to drop. This will be your GPU maxing out. Slightly back off from that point, and you will have a good balance (both CPU and GPU running full). This is more pertinent to those with weaker processors (like when I had my 1600X), but may still work in your case.

Weird, looks like he has 2 different LUA files for each stick and throttle. In DCS control bindings, select any space in the stick column and import one of the lua labelled stick. Do the same for throttle and you should be done.

There should be a separate LUA for each aircraft, and one each for stick and throttle. I’m not sure why you’d have 5, but for each aircraft you should have 2.

I believe the pr0 file is opened in the Logitech software, and the lua is opened in DCS. For the pr0, simply open the profile using the standard open icon from within the Logitech software. In DCS, go to control bindings, select the mirage, then open profile.

When I first published the benchmarks, I only had the ram up to 2133. It’s now up to 3200, but the observed difference isn’t massive. I haven’t quantified it by running benchmarks yet. Sorry guys, off on family vacation for the week. I’ll try and do it when I get home, but you can be assured that 1080p non-VR will likely be triple digit frames with this system.

Well, got it working finally. It took a beta of a beta BIOS (I guess more like an alpha BIOS), but she finally boots up every time. I can actually get my RAM up to the rated speeds and timings now, so the new IMC is much more friendly as well. A brief session in DCS seems to confirm my earlier observations, instead of being CPU limited I am now GPU limited. I’ve actually reduced MSAA to x2, since I can now get close to 80fps. The only problem now is it doesn’t seem to boost to rated or advertised frequencies. Running Cinebench single thread, I should see it boosting to 4.6ghz single core, but the best I’m seeing is 4.2-4.3. I’ve tweaked most of what I can in BIOS, turning on AutoOC and precision boost 2, but still no luck. Hopefully more mature BIOS will help down the road.

From AMD on Reddit:

The version I posted also moved most of the units out of the trees. A couple of the scenarios are still tough, but most of them are fixed (in addition to fixing the sound to country)