Sandman1330

Yet it has been the far more reliable of the 2 lately, at least when employed on the Tomcat. I never use it on the hornet.

I think it has to do with the missile guidance aerodynamics. Right now, both the AIM120 and AIM54 run out of energy well before they should based on their respective aircraft’s radar cues. If you watch the missile in F6 view with the data bar on, you will see that the missile executes max performance turns in response to every small movement of the target, and each one of these turns bleeds massive amounts of energy. The missile should be guiding much more smoothly than this, retaining its energy. There’s hope though. I remember an update a while back fixed this for the sparrow, and doing some testing last night I could see the sparrow guiding much more smoothly and retaining its energy. ED may be working on redoing the AMRAAM (and hopefully Phoenix) guidance algorithms, after which perhaps we will see the Rne cues become more realistic? Of course, the hole in my theory is the F15 and why it’s numbers are different...:dunno:

This is totally in the realm of the possible. Star Trek Bridge Crew has had this for years, and it is super immersive. You can hold your arm/hand out in front of your face and it just feels real. Here’s hoping we see it in DCS eventually!

I love it for everything else, much more comfy than my first chair. I’m adjusting my seating position such that I sit leaned a bit forward for BFM, getting used to it...

Just had this happen to me too. No log file was written, straight to desktop. I'd been playing for a while, then turned the music on, tried to switch sides (it didn't switch), so I hit stop, then switch sides and it CTD.

As a heads up, be careful buying a high-backed gaming chair. Dburne, I know you are a VR guy, and I've just bought myself one and found that the high back makes it very difficult to look up and behind, as my head keeps hitting the headrest. Fine still for most things, but for BFM (which I do a lot of), it's a major disadvantage. I may return the chair, I'm undecided if I can get used to working around it...

I’m wondering about the board myself. PBO is on (though PBO is the all core boost, PB2 is the single core boost) I’ve tried several combinations of BIOS settings...

New AGESA in 2 weeks https://www.tomshardware.com/news/amd-ryzen-3000-boost-frequency-fix-bios-agesa-1.0.0.3abba-longevity-reliability,40368.html 25-50 more MHz planned... mine is still 200+MHz below spec on single core load. Maybe now if I’m lucky I will only be 150mhz slower than advertised.

Have you kept the oculus software and your device firmware up to date? Maybe try the public test channel (beta). I haven’t had the problem for a while now, it appears to have been rectified in firmware somewhere along the line.

Haha, this. Using collective to slow the rotor is strictly forbidden in the B412 I fly. In fact, it’s exactly the opposite of Fri13s statement - the rotor slows quickly on its own to about 40%, which is our brake limit. At 40% we pop that sucker on and the blades slow down quickly. If the rotor brake is MEL’d, it takes forever to fully stop! The rotor brake is 100% designed for slowing down the rotor on shutdown, we don’t leave it on afterwards to secure the rotor as it puts stress on the hydraulic system that powers the brake. We have tie downs for that. It also does not wear the mast down, as it is all connected to a disk brake just like in your car. It doesn’t put friction on the mast at all, but rather on the attached disk brake.

My 3900X has very good all core boost, I see 4.1-4.2 under small FFT stress testing and just about any other all core load I throw at it. This is well above the advertised 3.8ghz all core base clock. However, single core, I get nowhere near the advertised 4.6ghz. With the latest BIOS I only get 4.2, and almost 4.4 if I use game mode (disable a CCX and go down to 6 cores). There is hope though. I have been unable to run the older BIOS with AGESA 1.0.0.2 due to a POST problem with those BIOS, but it has better boost behaviour. This weekend I found a user modified BIOS that took the latest Asus BIOS but reverted it back to 1.0.0.2, and it works in my system. The end result is I now get 4.4 consistently single core, with both CCX enabled. I still have hope that AGESA 1.0.0.4 will rectify the issues... some hope.

I know you’ve got it figured out, but I’m going to throw one more into the ring: any time you plan on flying above 15 units of AoA (ie dogfight), turn off roll SAS. At those high AoA due to roll reversal it will actually cause greater instability and departure from controlled flight.

Corner speed is misused on these forums, Corner speed is literally the “corner” of the EM diagram where load factor and max AoA meet. Basically it is the point where the aircraft can reach its max load factor without first stalling the wing. Any lower speed and the wing will stall before reaching max G, any faster and you are limited by max G. This is where the aircraft will achieve best turn performance. However, it’s instantaneous turn; the aircraft may not have the power to maintain that speed at that load factor. Best sustained turn rate is usually achieved at a lower speed and much lower load factor, but it is the point where the aircraft achieves best turn rate that it can sustain. At least that’s how I remember it from my military aerodynamics classes many years go... But to answer your question, from trial and error in DCS I find the Tomcats max sustained to be somewhere around 275-325, depending on weight. Edit: seems my memory served me well! http://navyflightmanuals.tpub.com/P-821/Corner-Speed-200.htm

I’ve had the same problem as him. The thing is, I am 100% certain that ASW turns off (I’ve used ctrl+1, OTT and the debug tool). I’m sure it’s off because the obvious artefacting that occurs with it on disappears, like the squigglies that appear on the Spitfire gunsight. It’s a weird bug that’s been around for years. ASW disables but Oculus still locks to 40 (and it was 45 on my CV1).

OK, I wasn’t sure but thought I’d try it. Thx!

Nice work Hardcard! I’ll give it a go on my server too. I was considering asking you if we could do statics vice AI, as I’m seeing a significant performance hit that maybe going to statics will alleviate.

I’m going to give them some time to sort out BIOS, but if I don’t get better boost frequencies within my 1 year warranty I will be RMAing.

https://www.digitalcombatsimulator.com/en/files/3304447/ It’s for the hornet, but he intends on converting it to the Viper when it releases. I found it to be a very entertaining mini-campaign, as I too am a big kid!

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?