Sandman1330

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)

Yeah, you will probably be GPU limited with those settings on a 1060. Are you using any MSAA or PD? The thing I noticed in my brief run with a 3900X was a massive increase in FPS at very low settings, but at my current highish settings, very little change except improved minimum FPS under heavy load. Before, in certain conditions I could not saturate my 1080ti as the CPU would hold me back, but now I can. If I ever get it working correctly, that is!

That’s Dubai :)

Nice idea! I’ve been trying to find something to insert into there, that might be the ticket. I’ll give it a go!

Thanks! I’ve added the 1080ti. Sorry man! I hope yours works, as I think we have the same revision of board based on when we both bought it. I’m taking my whole system back to the store today, when I had it built I bought the extended warranty. I’ve started to see people getting to the RMA stage for the mobo over this issue. With my extended warranty, the store will replace the board on the spot if they can’t get it working either. It might mean I end up with a Crosshair VII hero instead... Yep, with Rift S.

Hey guys, So, through much trial and error I've managed to finally get my 3900X to boot, though I'm not convinced my troubles are over yet. However, once I got a stable boot to Windows, I decided to take a break and do some benchmarking. For those who weren't following in the other thread, I've plugged a 3900X into a Crosshair VI Hero mobo, but cannot get it to boot the vast majority of times - I get a 07 post code. It is likely BIOS issues. However, occasionally I can get it to boot - just once - by removing the CMOS battery. Once it does boot, it runs solid as I could ever ask, but I cannot reboot lest I get a 07 code. I've decided to use one of those fleeting opportunities to send you guys some benchmarks. Old system: Ryzen 1600X OC@4.0Ghz RAM running at 3066mhz New system: Ryzen 3900X, no OC, no PBO, so far max boosting to 4.3ghz RAM running at 2133 Common to all: EVGA 1080ti FTW3 Crosshair VI Hero Bios 7201 (AGESA 1.0.0.2) Corsair H110i 280mm cooler 32Gb GSkill TridentZ 3200C16 Samsung 960 Evo 512Gb Oculus Rift S OK, the good stuff: Cinebench R15 (multi/single thread): 1600X: 1260 / 161 3900X: 3116(!) / 202(!) Cinebench R20 (multi/single): 1600X: 2759 / 380 (I think, it didn't save!) 3900X: 6952 / 497 Firestrike: 1600X: Graphics: 29482 Physics: 18041 3900X: Graphics: 27505 Physics: 28348 Note the MASSIVE improvement in Physics score. I find the lower graphics score interesting, I believe my previous result may have been running with an OC on my card, so take that one with a grain of salt. DCS (Finally!!) Tbilisi Free flight TF51D 1600X: Locked at 40 with high settings, MSAA 4x and MSAA2x 3900X: Locked at 40 with MSAA 4x, up to 65/70 with MSAA2x On low settings with the 3900X, locked at 80, no movement. F/A-18C Free Flight Dubai 1600X: locked at 40 early on, into the 20s down in the city. Not much change with MSAA 2x 3900X: 80 early on, dipping just below 40 in the city. On low settings with the 3900X, locked at 80, no movement. So, apologies for being very unscientific, but this is the best I could do with one good boot and only a bit of time. So, my conclusions: I am FINALLY able to fully utilize and saturate my GPU. Low settings before, I could never cap out at 80 - now I can easily hit 80FPS. Previously, I was CPU limited to 40ish, and would just heap on GPU heavy settings until the GPU came close to 100% - at those same settings, I still see 40ish FPS, but it's GPU limited now. I should note that all of this was done with 0 tweaking, RAM only at 2133, no attempt to activate precision boost overdrive, nothing. I think there's still plenty more on tap for me. The key conclusion is that I can now easily saturate an overclocked 1080ti. Yay!! Now back to trying to get it to boot properly... More to follow if/when I ever manage it!

Haha touché!

That’s strange, because I preordered both the 3800X and 3900X, the plan being to take whichever came in first and cancel the other. 3800X still hasn’t come in yet, but I’ve had 3900X since Wednesday. It’s backordered again, so it must have been a small shipment. It also could be that 3900X gives more flexibility on binning, since each chiplet has 2 cores disabled, they only need 6/8 cores on each chiplet to bin well. Either way, I have it but can’t use it, which is a shame as I know many are waiting on this chip. Here’s hoping for updated BIOS later this week. Incidentally, not sure if I posted this, but I bought super cheap 4GB 1.2v RAM, and got the same Q code, so not sure if it’s RAM related, or maybe the chips memory controller. Also had my GSkill RAM tested, it passed. Hoping it’s just BIOS!

Sorry guys, the few times I’ve gotten it to boot, all I’ve done is basic cinebench runs. I’m more focussed on getting it to boot consistently for the time being. As soon as I get it running smoothly, I’ll do some DCS specific VR tests. I’ve put my 1600X back in for the time being, waiting on a newer BIOS before trying again. Pilotasso, have you got it up and running yet?

Woke up this morning, ran Cinebench R15 for a single core of 199(!), but my AIO cooler wasn't being detected by it's software so I ran an update of the AIO software which required a reboot and.... Code 07. Won't boot again. :mad: At least I know it all works, I think it's crap Asus BIOS. They've fallen behind all the other vendors in releasing AGESA 1.0.0.3.AB. Last time I buy an Asus board.

Up and running! Managed to get it to boot into BIOS once (again, removing CMOS battery, though it took 2 tries of that). Upped memory voltage to 1.35v, and I'm up and into Windows. I'm afraid to try and get the memory up to speed, as if it fails, I may not get it booted again... But at least I know everything works and is compatible!

So it booted once after removing CMOS batt for the day. Recognized the 3900X no problem, but went back to its old ways (code 07) on subsequent boot. I’ve removed the batt again and am waiting. If it boots again, I will up RAM voltage manually and see if it fixes it. I think it’s my crap RAM, which never ran to spec 3200 from the get go. I think it’s failing RAM training due to low voltage induced by BIOS bugs.

Ummm... thx guys but I’m not an idiot. Crosshair VI Hero, latest BiOS (flashed several times to be sure), supposed to be compatible with this BIOS and board (albeit “unofficial” compatability”). I’ll also note that AMD advertised forward comparability years ago. Yes they may have said AM4 and not X370, but that’s greasy if it was their plan all along. There is a bug in the AMD AGESA BIOS right now that causes it to undervolt high speed RAM. My Q Code is calling it a RAM problem. I’ve had issues with this RAM all along, so I’m sure this is the issue. The problem is I can’t even get it to boot once to manually up the voltage. :doh: Edit: I also blame Asus, who have not released proper AGESA 1.0.0.3AB BIOS yet, even for those boards that do have “official” support. 1.0.0.2.B isn’t fully compatible. Droves of people having issues, though many have 3900X working in a C6H at lower RAM speeds. I think my RAM is crap.

Forget everything I’ve said, buy Intel. 3900X won’t even post in my board, RAM training fails of all things. FFS.

You won’t get PCIe 4.0, which unless you are running a PCIe 4.0 SSD, won’t matter. There are no 4.0 graphics cards yet, and 3.0 isn’t even saturated. Memory speed I’m unsure, but as the Ryzen has the memory controller on die, I’m hoping the memory support will be improved.

Lagging behind in single digit percentages is hardly significant. In real terms, a 5% difference on 50fps is only 2.5fps; even 10%, which is about worst case, is only 5fps. The difference I will gain by dropping a 3000 series into my 2 yr old motherboard to replace my first gen chip will be on the order of 30+%, or 15fps. The ability to upgrade down the road is worth the 5%, at least to me.

Haha I noticed - had to happen after I’d already put in all the work! :doh:

Still no availability in Canada. Newegg had them for about 30mins and ran out of stock just as I was doing checkout. C’mon, I’ve been waiting for this for 2 years!! :D