Blackhawk163

Fine tune it in the control settings within DCS. I adjusted the Y value saturation a bit. In fact I just did that instead of messing with the ratio within simapp and did this to any module that has an issue.

When I upgraded to the 5080 I was still getting the micro stutters out the side. Then I decided to actually tax the you and not the cpu. First DLSS/DLAA had to go, and then my Pimax custom settings that I had used on the 4080 super (.85 resolution ) had to be increased to native. 120hz (no capping at half). I don’t mind QV, and FFR. All modules save for the F4 phantom (which cuts down to 32 fps for some reason) run smooth with no stutters at 60 capped in DCS and OPXRTK. I usually test this over The BFM mission over tarinkot (just shoot down the mig right away) and then fly circles over the airfield as the density of objects go from low to high and then low again.

Off the top of my head 9800x3d is at 5.25 -40 on the curve optimizer, 2200 on the memory. 1.20 mv cap (I’ll check it out later to confirm that) The Zotac OC card I have is running at +425, I dropped it down from 435 as Elite Dangerous didn’t like it, and memory at +2000. The only problem I’ve run into so far with this card (even then it may not be hardware related) is that the F4 module will only run at 32fps no matter what the settings are at. This is an issue that I didn’t have with the 4080 super. Not only that, but then DCS as a whole gets locked at 32fps requiring a quit to desktop to get back my performance.

So I take back my “meh” feelings from the 5080. What I attributed to mid performance is in fact a Nvidia driver problem. Which seems fixed on my end. Also I think I got a really good card as I was able to hit +435 on core and +2000 on memory and it is super stable in DCS @ 60fps with nearly all the bells and whistles turned on. Another thing that I was unable to do with my 4080 super was to keep the Pimax CL at its native resolution, I can now do that with the 5080. Lastly it seems that my 5080 wants to be used and setting the resolution multiplier to anything less than .9 brings the stutters when looking over the left and right sides. This is gone at .9 up to native. I’m still running OPXRTK with FFR and Quad views in tandem, and yeah, while not recommended at all, it continues to work FOR ME. DLSS is not implemented nor is any AA as the resolution more than makes up for it. overall, I’m very happy, and can’t wait until the 90s become more ubiquitous and affordable (lol)

Been bitten by this issue. All other modules (see signature) are fine locked at 60. Once I try the F4e the FPS drops to 30 and then DCS is stuck at 30fps regardless of module unless I reboot the program. The "solution" to this problem is anything but as this only happens with the f4e.

Pretty much what I read and saw reported on. Nvidia will love to sell to the data centers where that sweet sweet money is before hitting the main consumer market en mass. Are there 5090s out there? Absolutely, but not as ubiquitous as the 80s on down.

Just got my 5080 ahead of the tariffs and it’s a middling upgrade for me in VR. Pretty much the same as the 4080 super I have. Might just send it back and just wait for the 6000 series or if AMD decides to step back into the premium space again. Really wanted a 5090, but it seems that Nvidia just isn’t interested in selling any to us consumers atm.

I should have saved the track for this mission. I broke it by simply looking to see how the Tornado gets shot down. By observing the encounter, the manpad misses the Tornado, and after that you just fly around and nothing triggers.

Yes it is. Right click on the /users/savegame folder and then navigate to location and then move it to where you want. I.E. different dive etc. I have a dedicated M2 for DCS and the save games folder

This is on 1.38.01.01 btw

@Calvin.Pimax I confirm that this now happened to me. PCL failed to initialize during this morning's startup. I had to unplug the display port and then reconnect. Upon doing so Pimax play defaulted to a setting that I had not used. It went from 120hz to 90, went back to auto on the lighting frequency, and chaperone was enabled despite me never having done so. However unlike @Moxica, I was able to reset my settings to how I've had it before.

I was going to suggest optiscaler to get fsr4 on DCS but then realized that this only works on DX12 games, which sadly doesn't apply to DCS as it's dx11 only. Still some promising results. Any micro stuttering out the port and starboard sides when looking out in VR?

yeah figured as much. @Moxica any luck?

Updated Pimax software etc etc? Calvin is there a way to factory reset the HMDU or is there a config file that can be deleted? Otherwise I’d go for a full uninstall (delete anything and everything Pimax related etc…) of Pimax play and do not do a room config, and if you haven’t then that’s on the Pimax software team to figure out.

Are you talking about chaperone mode? Turn that off under the device-> advanced page under passthrough.

Saw that. Guess my 4080s will be sticking around much longer, maybe until the 6000 series as the prices on the 5090's are freaking insane especially given that the AIB's are in on scalping their own customers now it seems. What a pathetic launch. Imagine needing a new mid-upper range graphics cards these days.

That you even get that far is great. I sometimes will burn a whole lot of gas waiting for the eagles to do something. These eagles must be from TLOFR, because they are just on standby, say they are running in and . . . Sometimes they do on the first convoy. I usually have to do their work for them on 2-3, by that time I'm low on fuel, I hit the tanker when the next bug hits, I can't get back to the area. I hit an imaginary wall, jet stream, what have you. Waypoints 7-10 become inaccessible to me. Also, from missions 6 up to this one, radio chatter either works or doesn't (mostly doesn't) and being in VR I tend to miss some of the calls. I obviously like to campaign enough to keep trying as it's a near perfect amount of time to play when wanting some action, but these trigger bugs are getting really annoying.

Aapje at it again? You seem to be the main character of all these debates, and in internet logo, that's not a good thing. I'm sorry mate but if you're not arguing with kksnowbear then you're doing it again with someone else. Best to move on. And here I was hoping we had users with actual benchmarks. Sigh.

Yeah the non XT version price makes no sense, the $600 price tag, I think is still too high for team red. The AIB’s aren’t going to stick to that. Oh well. Given the market conditions with scarce supply with all the gpu’s, I’m sure these will sell out no problem, whether or not that’s to regular consumers and not scalpers, remains to be seen. Apparently AMD/Aib has been shipping these out to retailers since late last year. So supply should be good.

Tell that to them

Does re-enabling Pimax play openxr as the runtime allow you to deselect it? I’m not near my computer but I think options like that are essentially locked out when the runtime is changed

Back during the black friday sale I got three of the MFDs and table mounts to go with it, but since I'm center stick that occupies the middle I justy shelved the third one. I now want to add the third on the hotas desk t channel that houses the Control stick, but I haven't a clue as to how to actually do this as there is nothing on winwings site to buy. The manual section for my particular application is blank.

Meanwhile this is exactly what the thread is about. Too bad prices are going up with some of the partner cards.

Ah no worries. Conversely, I wanted it because I fly VR and find it easier to reach out and press what I need. I have the MFDs just needed the UFC gear. Great price for all, should go in a flash.

Would you split up the package? Just looking for the UFC and HUD