RackMonkey

After years of being on team green I thought I would give team red a chance. A couple of months ago I got my hands on a new 6900 XT. I've been working with it but I just am not comfortable with it. There's nothing wrong with it, it's just that after running nVidia for years I'm more comfortable setting them up and running them. Instead of paying Ebay to sell it and then pay them again to buy nVidia I thought I would try an find somebody like my self, who went with nVidia and found they prefer AMD, to trade cards with. My GPU is an ASRock Phantom Gaming 6900 XT. I am looking of an AIO 3080 Ti or 3090. Post here if you have questions that others might find interesting. PM me if you want to discuss a trade.

I installed ReShade and a Moltar profile I had dated 4/12/21 and noting happened...at least in VR. I did see changes on the monitor but nothing in the HMD. Any thoughts?

I guess all we can do is help each other and keep pressing the industry to up their game. I'm pretty sure that with the price of VR coming down, that play time on the computer will be the predominant method and games will be written for VR first.

And there in lies the problem. There is no consistency. How do you track down problems when the target is always moving. One person may have great VR and another bad but there are so many cooks in the kitchen you don't know where to start looking.

I don't know who is letting us down. Is it ED? Is it the GPU manufactures with a lack of proper drivers. Could it be the VR hardware manufactures. I don't know because I don't understand the way VR is processed through the system before it gets to my eyes. You can see by my sig that I have new and top notch hardware. I run an FRS mod, a shader mod and Process Lasso. My CPU is OC'd to 5.0 and the GPU has been up'd to 2580 and yet I still have to balance between having stutters and a resolution that is usable. And there doesn't seem to be a happy medium. If I want to get enough FPS to get rid of the stutters, I have drop all the setting so low that I can't recognize the instruments that are right in front of my face. If I want to see the instruments, MFD's, or ground targets I have to up the resolution to a point where the FPS is in the teens. And I still can't see anything because of the aliasing. Does anybody really understand VR? I sure don't. You would think that if you had all default setting that you would, at the very least, have a useable sim if not a picture perfect one. Right now we have some very talented individuals coming up with a patch work of mods to try and fix what ED should be doing. These talented people should be working on making DCS better, not trying to fix it so that it just barely works at the most basic level.

That's my procedure when ever I try something new. Although in this case instead of the default setting in DCS I took them all down to low or off. I started FSR at the recommended .77 and increase the DCS setting. I found a really smooth setting but aliasing was so horrible it was unusable. When I tried correcting the aliasing and got that under control the FPS and frame rate tanked to an unusable level. I think I found a "useable" setting today. Not perfectly clear and some aliasing so it's a little hard to see the icon's in the MFD correctly. Hopefully I wont have a blue on blue shootdown.

I turned on "Force DX11". I'll see if it changes anything in a few minutes. The 6000x6000 is the upscaled super sampling done with an FSR mod. The log shows it's final produce at about 3400x3400. Great clarity and very little aliasing but a whole lot of stutters while setting still watching an acft taxi by. All my setting are low or off except for textures...I need to be able to read the switch and instruments. It to bad it's not like 2D where if you can't run 4K you can just drop your resolution to 1440 or 1920, but at least you still have a clear display. Maybe not as much in the way of eye candy but it's no where as bad as 3D if your trying to get a display that doesn't look like it's doing the stutter step.

That hit it right on the head. Until ED catches up with the rest of the world and implements multicore only a MAJOR CPU upgrade would be worth the money. I really think ED is doing the VR community a dis-service by not keeping their core code up to date. It seems like they want to keep putting band aids on instead of fixing the core problem. How long have we had multicore processors? It not like it's a new idea and it has proven itself to be the best solution since we seem to be topping out the speeds that we can get out of the CPU. Usually have a leap frog affair. New hardware comes out then software catches up and uses all that it can give and jumps ahead. Hardware then jumps again and the cycle continues. ED seems to be a couple of steps behind and unable or unwilling to catch up. I think the complaints will continue until an Elon Musk comes along and puts ED in the position that Jeff Bezos finds himself in now. Behind and looking to die.

I finally got a 6900 XT so my old 2070 is no longer the problem. But now I wonder about the CPU. You can see I have a I5-10600K. It's OC'd to 5.1. The GPU is OC'd to 2580 and will normally put 300 watts or more. My question is, with DCS being coded for single core, is it worth it to get a I9-10900? With any CPU topping out at around the 5GHz mark, is it really worth the money to upgrade. The I9 won't OC any higher than my I5. Sure there's a little more L3 memory. That might help a little. The extra cores won't do me any good the way that DCS is coded currently. Even when I use Process Lasso I don't see any signs that DCS is bottle necked by the CPU. Right now I have to run SteamVR up at a 6000x6000 super sample range in order to get rid of the aliasing but then my FPS is at the mid 20's and frame time bounces in the 40's and 50's. If I reduce the SS down to where the stuttering stops and I get usable FPS and FT the aliasing is so bad I can' even read the fin flash on the plane setting next to me. It gets even worse if I flying low level and looking any where but straight ahead. I'm interested in seeing the opinions of those that have a better handle on the way DCS is coded and the hardware it runs on.

Checked it again on the OpenVR setting page. It's disabled.

I don't have anything that would be an FPS limiter, like motion smoothing, turn on. I selected preset-VR with DCS PD at 1 and SteamVR at %100/%100. Neither the GPU or CPU were any where near running at %100. I then went through the DCS menu, and set to high anything that said it was a high user of the GPU. I was trying to stress it and get it up toward %100. It failed, continually bouncing between about %25 and %75. The GPU never does settle down, it's always doing a %50 bounce. I then tried pushing it by increasing SteamVR up through %300 and the only thing that changed through all this was that FPS dropped and frametime would jump to the mid 20's up into the 30's. The GPU and CPU numbers stayed the same. It just seems to me that there is a lot of performance being left on the table if I can't figure out why DCS can't push the GPU to %100.

I think I have a bottleneck someplace but, I can't spot it. Assume that my DCS settings are "normal" as suggested by most helpful post here. My CPU is OC'd to 5.1 and Project Lasso sets DCS priority to a single CPU. The GPU has 300 watts available. Memory is set to 2150 and the GPU is at 2570. When I'm running DCS the FPS stays at @45, frametime at 24. The single CPU bounces around but averages @60% and after loading I've not seen it go to %100. What I don't understand is that the GPU averages %75. The full potential is not being used..Like an engine that's not getting all the gas it could turn into horse power. I have tried moving my setting much higher but the GPU always hover around the %75. Please ask question and make suggestion as I would really like to think that I did not waste my money on a 6900 XT.

Mines turned off. I just transitioned from a 2070. I would have stayed team green if I could have found a 3090 that I didn't have to take a mortgage to get. I just really want to see what my G2 can do but the 2070 couldn't push it hard enough. @Lange_666, just got it and don't have all my sig's changed yet.

Add me as having the exact same problem. The only difference is I'm using VR. I can get rid of most of the stutters but resolution has to be so low as to negate having the top AMD card. I also need a bunch of AA that really drags the FPS into the toilet.

Expanded on you advice and got rid of both beta versions of StreamVR and WMR. Flew all day on a server with 15 blue pilots and an unknown number of red's with out a crash. It may not be the fix for all but it worked for me. Now if I could just find a 3090 that won't cost me my first child.

Me to, me to. I don't even get past DCS's splash screen before SteamVR dies from a "critical error". DCS continues to load but like all the others...the HMD is a black screen. I've run Window system file checker and it found a few files that needed to be replaced. I've unistalled and reinstalled SteamVR. I've run DCS repair a dozen times but nothing helps any more.

I've tried the RC2 version and it's killed something. When I start DCS SteamVR ALWAYS shuts down with a critical error. No information so your left holding your joystick wandering what happened. I tried reverting to the original DLL and deleted the RC2 files. Same thing. I'm still tring to figure out how to get DCS back to just SteamVR and DCS. I've tried uninstalling and reinstalling SteamVR and running a full on repair of DCS but it doesn't seem to do any good. X-Plane seem to run fine under SteamVR and DCS runs fine when not in VR mode but there is something screwed up when I try to run DCS in VR mode. I also noticed that NeckSafer is also screwed up but I havent gotten to trouble shooting that one yet.

I don't doubt that you use them for that but it is a strange use of a rotary encoder jut to do on/off task that any normal switch could do. I wouldn't even know where to start to program a rotary to do something like that.

What program are you using them in. I'd like to determine if it's just my flight sim's that are causing a problem.

There are 4 encoders on the CM2 throttle and I can't get any of them to work correctly. Testing with the A-10's HSI heading and course, I have tried almost every combination of setting that I can think of. In VPC's joystick testing software I'm seeing "ON" numbers between 0 and 8 million MS...if it registers at all. I try to turn the knob at a constant rate of about 500MS per click. I get the same results if I test with X-Plane 11 also, so I am assuming that the problem is either with Virpil's hardware of software. Since Vipil uses very good hardware I believe it's the software that's not reading the hardware correctly. Just in case, I've also tested Joystick Grimlin to see if the problem might be between Virpil's software signal output and the way that DCS and X-Plane interpret it. The result is the same. The question is, does anybody have the encoders working correctly? Are all of Virpils encoders worthless? What can we do to get Virpil to look at the software to make them useable?

I'm the opposite, I'm on the grid and can't find a way to get the Steam house back.

I would imagine that in DCS the push of the encoder has been set as the "shift" function for the CCW and CW turn of the encoder.

I must be insane because I keep trying to do the same thing with the same results. I started a ticket with Virpil support for the encoders that are basically useless. I got " that's the way it is". Probably some poor slob making $5.00 an hour. Not given access to any database that would do him any good in trying to answer questions and no authority to do anything any way. My last contact I asked what should be a simple question. What is the difference between "encoder scroll" and "encoder dial". I WAS GHOSTED. I haven't heard a peep out of them in a week. They make a hell of a HOTAS physically, it will probably outlast me but their software and support system really needs help.

I'm afraid your on your own here. Since the buttons and switches are not even close to matching any aircraft in DCS it all come down to what's comfortable and memorable to you. I will say that the word "ergonomics" is NOT in Virpil dictionary. You've got switches that are hard to reach in a position that doesn't make any sense. There are only two encoders that don't work. I dare you to set radio freq's or set heading or course with them. Don't plan on using these for anything, their useless and Virpil doesn't seem to want to answer any questions about them. Find the common switch's for the acft you fly, like gear and flaps, and map the same switch across the board so you don't have to worry about not getting you gear down before hitting the deck.

Twillis When your setting in SteamVR and looking at the grid does NSVR operate correctly?