fitness88

For sure I'd be getting the controllers, I'm glad you mentioned it doesn't come with them.

What exactly is this? I started with Rift then went to Rift S like many but had difficulty with its IPD as it was only digital, non-mechanical. How is it on resources? I'm using 2080S, 64ram i7-10700K cpu variable to 5.1.

Surprised to hear about the setup, is it comfortable and do you have to purchase any accessories with it?

I've been noticing recently that when mapping UI Layer keystroke commands to my F/A-18 I've started to get conflict advisories for other aircraft other than the one I'm programming...for SU-33 MIG29 etc. I never used to get conflicts to other aircraft...yes I would in the one I'm programming. I take it the UI commands are global...never saw evidence of that before.

Hey dburne I've seen your critique of the Rift and Rift s, well done...what say you re: G2?

I take it this is a bug...as mentioned it's goes away if you enable MSAA.

Thank you for this info. I believe "D:\DCS World\bin\DCS.exe" --force_disable_VR needs to be a shortcut pointing to "D:\DCS World\bin\DCS.exe"

When I have MSAA on it doesn't appear...cheers.

Thanks for your response dburne. I have a 2080S, 64ram i7-10700K cpu variable to 5.1. I find PD1.2, MSAA 2 seems a sweet spot for me not sure what the others do, I'll read up on the net. One thing I noticed, without MSAA 2 I get a gold aura all around my canopy over water??

Do you use 1 only or a little of each and what improvements should you notice with each. I realize there will be a performance hit so I guess the question is how do you get the biggest bang for your buck? Also, I understood awhile ago there was little VR benefit from enabling any of the settings in the Nvidia Control Panel 'Manage 3D Settings'...is that still the case? Thank You

Like with other apps, file organization is important especially here with keeping individual exported diff.lua column files and DCS input device diff.lua files and any diff.lua backups

Thanks Tippis for that comprehensive explanation. To clarify your final point [last paragraph] if I accidentally import a throttle diff.lua into my joystick column the joystick will now have the bindings of the throttle. Also I guess it's a good idea to have both individually exported column binds as a back up making sure you logically name them for future reference and put them in a different folder other than input. Also to back up input folder! And yes I see the diff.lua file in input gets updated after I make changes to the controls in DCS controls window. Thanks again!

I would appreciate anyone knowing where I can download them from to please let me know where. Thank you.

I asked that question to make sure that only binds that were saved column by column can only be restored to their respective columns and that's when you start seeing lots of diff.lua files which by the way you need to uniquely name so you know where to restore it to. On the other hand the all inclusive device diff.lua file for each device that is automatically created by DCS can be used but if there is an ID name change it will have to be renamed. All of these files get put into the 1 input folder? This is what messed me up not understanding the difference between the 2 types of diff.lua files.

Thanks...what an interesting experience What would happen if you restored a complete device .diff.lua [with all columns axis UI] into 1 column through the controls tab?

So all that's needed is to just back up the input folder and change ID's when/where necessary unless you want individual columns replaced then do it through the DCS controls tab...correct?

Update: After spending time on remapping of my Logitech software and DCS controls I realized that the C:\Saved Games folder that was created before I changed its location to G:\ actually had the most recent device settings [input\.diff.lua] with the correct ID. I don't understand how that could happen I would have expected the input folder to be empty? Also can someone please explain the workings of saving and restoring the individual device settings profiles in the DCS control tab. Every time I make DCS mapping changes I've been clicking on each column, saving the individual devices and their respective columns one by one and doing this for axis and UI selections making for many .diff.lua files. When I restored these .diff.lua profiles yesterday I had to do it again one column at a time and this created many .diff.lua files in my input folder, one for each device for each column, axis & UI as well. Why not just back up the input folder and UI folder and use them to do a restore or does the possible change in device ID make it impossible to restore from these diff.lua files if the device ID changes for any reason? I do understand that sometimes only 1 column may need restoring so that may be an advantage to doing it one column at a time so if there is an ID change then just copy the old ID to the new .diff.lua...correct? Your thoughts please?

Yes I forgot to immediately change the location of the saved games folder and did an update first then realizing what happened I deleted the updated c:\ saved games folder then moved its location over to g:\. And yes I have also experienced the frustration of plugging some USB devices into another port by mistake so I now mark down where everything goes. OK I can try some things you guys enlightened me to and then worse comes to worse do a remap...thanks again!

Thanks gentlemen for your response about the ID changing. So should I work with what I have and change the settings where need be or start from scatch to avoid mapping conflicts? Also why would all my other options tabs change as well, such as on the audio and the system tabs? As for the shortcuts I guess I'll make myself but I can't find the 'repair file' in the bin directory in order to make a shortcut and I lost my no vr dcs shortcut. Yes I moved the Saved games location c:\ over to the DCS drive as like before the move. Thanks again for your help!

When opening DCS after moving the installation drive to my new computer all the settings tabs have change to what looks like a default installation. For example, in DCS options> 'controls' tab for some reason the device mapping in the device columns are not the same as before I moved the DCS drive? Why would I have this issue if all I did was move my installation drive? Are there any registry edits that may be needed. How do I get my start menu shortcuts back, after doing an update and repair still no shortcuts? Thank you.

Radar on right DDI, FLIR on left. Thanks for your input, I've got it figured out now. I have noticed however that when you try to move the FLIR once it's slaved to A/G radar sea tgt it jumps back to the original point. I suppose it's necessary to do a radar unlock and then slew the FLIR manually, hopefully it will stay on tgt for quick and easy re-acquisition.

Thanks for that... I find AG radar designation of a tgt needs to have the SCS moved to the right, won't work just pressing TDC/depress .

AH, right you are...as usual Just did some testing in A/A, what I wasn't doing consistently was making sure to be in A/A mode, I thought I could be in NAV as well but of course the RRSLV would not be available without being in A/A so that resolved the problem of slaving the FLIR to an A/A aircraft tgt. SEA [and I assume GMT] don't have RRSLV to slave FLIR to surface radar tgt. It seems I need to use instead of pressing designate tgt like I can do with A/A in this scenario, I need to move the sensor switch to the right. Anything you'd like to add would be appreciated...thanks.

I can't reproduce slaving a gmt or an air target to FLIR on a constant basis. I do the same thing but sometimes it works and sometimes not? Can someone please clarify the exact procedure for slaving gmt or air target to FLIR. Thank you.

Feed the end of spring loops first onto the zip tie then loosely secure the zip tie around the knurled plastic locking collar so that the springs can be moved enough to allow for proper equal distancing. The flange just underneath the locking collar will keep the zip tie from slipping off. Then you place the springs 1 by 1 onto your corner bolts and tighten, then do a final balance of the spring loops, then pull tight on the zip tie...finally do a stick calibration. Remember to first remove the stock centre spring the unit comes with. Also I was lucky on the first purchase to find the 3" springs with the amount of tension I wanted...very important that you have a slight bit of tension when stick is centred otherwise it will have looseness.