j9murphy

under "VR Interface Settings" I cannot change the Rendering Driver? It's Stuck on Rift and I'm using WMR.

have you tried running the windows task manager to see what might be interrupting the cpu? sort the list by cpu time and then look to disable/kill whatever processes are getting cpu while you are playing DCS - or better yet uninstall them completely if they are something you dont use. Could also be that windows defender scanning dcs. I typically exclude the DCS path from security scans. you can google for instructions on excluding directories.

I'll try anything lol. My current settings are Steam resolution per eye: 150%, Steam per app for dcs: 142% Motion Smoothing enabled DCS PD: 1.0 Which looks pretty good, but still not sharp on the MFD's. If I could run at a PD of 1.2 with everything else the same that would look great, but I jut dont have the horse power to get there and for everything to still be smooth.

Thanks, I'll have to try a higher renderScale, .77 was worse than not using it at all. What value do you use for your reshade sharpen?

Does anyone know if there is a good Mod to make the text appear more clearly on the MFD's in VR?

so is this complementary to or does it replace this... https://github.com/fholger/reshade/releases/tag/openvr_alpha2 from the thread

are you saying that essentially 2 and 3 above are done in one pass by the gpu?

This will probably be a few posts as try and dig deeper into understanding how to "tune" VR settings, but I want to try and understand what's going on so hopefully a few of you are guru's in this area... Question 1.... As I understand it, simplified of course... 1) PD in DCS VR settings together with the DCS graphics options determines the resolution and quality with which DCS renders a frame. The amount of CPU time and GPU time to do this is tied to the complexity of the scene and the specific graphical options selected. 2) the frame is then passed off to the GPU to scale the frame (in this case through steam) based on the value specified in supersampling (could scale up or down) 3) finally the frame is scaled again by the GPU based on the actual resolution of your VR headset and displayed is this correct? is there a way to see what the contribution of CPU/GPU at each step is to the overall frame time?

Figured out by resetting the keyword database and starting over:)

For whatever reason when I enter keyword training mode now, the Voice Attack window no longer shows the confidence % when I try and train a word and the windows speech engine seems to always have no idea what I'm saying.... however in game many things are recognized. Any ideas what could be breaking the training mode?

Thanks for posting that link about removing the deadzone.. that definitely goes on my todo list:)

When using mmjoy2 with the virpil stick the hand brake looks like a button rather than an axis, but it works. For setting up mmjoy2 the following two videos are a great start.. of course the pinout for the thrustmaster is a help... along with this...

Are you looking for just how to get mmjoy2 to work with a thrustmaster compatible stick and an arduino pro micro? That I can certainly help with. If your asking about the overall deign and modification of the FFB2 base then I'm not quite there yet:)

Thanks for that, I went down the mmjoy2 path only because I already a pro micro that I could use. Was easy to get it working. I agree though, freejoy is the better approach. Thanks for the links, you can certainly go down the rabbit hole with this one:)

Great Thread! I do plan on doing the resistor mod. The problem with the resolution of the pots and the throw of the stick is something I havnt grappled with yet. I'm hoping to keep the extension short enough where that wont be a huge problem, but we'll see!

I have a Virpil T50-CM2 Grip that I am planning to put on a MS FFB2 base to go with my Virpil Collective that I preordered. Thus far, I have... - Acquired one of these to connect the grip to an Ardunio Pro Micro - https://www.digikey.com/en/products/detail/MD-50PL100/CP-2950-ND/500828 - Flashed the ProMicro with MMjoy2 in order to be the joystick controller so that I can configure the stick and have it recognized by windows and DCS - Prototyped and printed new extension in fusion360 with threads on one end (to connect to the stick) and the appropriate hole in the other end to attach to the FFB2. - Verified MMjoy2 will allow me to control the Virpil Grip. What I havnt done yet... - Finished designing the extension to house the pro micro controller, or modified the FFB2 base to accommodate it. - Done the resistor mod to the FFB2 in order to strengthen the FFB for the heavier stick and extension. I've validated all of this will work - in fact, this approach should work with any thrustmaster stick or compatible stick. This approach is much cheaper than salvaging the electronics out of a virpil base.. MMJoy2 is free and a pro micro is just a few dollars. I'm happy to collaborate if anyone else is going down this path as well.

That looks like a winner! I have a drawer of pro micros already on my bench so that works quite nicely:) Thanks!

I would like to interface the buttons on a warthog stick (not the axis) to a usb connection that would recognize the button presses as joystick button input in windows. Essentially I'm looking for a pcb or schematic design of how to interface the 5-pin din output on the bottom of the stick with the necessary electronics to attach it to a usb connection. Anyone have a link or pointer for how to do that?

that made my day! I thought I was going to have design one for my own frankenstick project.

+1

Where in the WMR Settings do I "set it to SteamVR Managed"? I'm looking in the settings window that appears from the Mixed Reality Portal but no joy.

Thanks, I figured it out... didn't have the ALE selected in the EW page... doh!

I can select targets with the HARM/FLIR button but pressing cage/uncage doesnt free up the harm and I cant fire it? Using release version and TOO mode in the STORES Page. Any hints as to what I'm missing or is this a bug? Sensor select is on also on the correct DDI.

Is a grip required for this to work? Seems like the collective and throttle would still work with one?

I ordered a 9V adapter and tried it out last night and I found it to solve the problem for me. The lower end of the effects (Values less than 10 or 20) are much more subtle but they can still be cranked up to be strong enough to thump you. Solves the issue for me. I ordered this one from Amazon US if anyone else is interested in going this route. Cord is a little shorter than I would have liked, but at under $10 was worth a go: https://www.amazon.com/gp/product/B01ASX6RBO