Galinette

Hi, Just received my G2. Is there any way to enable motion smoothing without the controllers? I found somewhere that it's in the steamVR settings, but apparently this was moved out at some update. I saw elsewhere that you can do it in the SteamVR dashboard (in-VR) where there is a WMR button, but I can't do anything in steamVR since I have no controller. Any idea?

Do you mean the throttle "STOP" detent, unlocked with the little red button besides the throttle, which stops the engine?

I recently did a night patrol. All lights were set to full. It was very hard to follow wingmen at more than 100-200m as we couldn't see navigation lights (or any other light) When RTB, there was a patrol of F/A-18 close to us. They are as visible as a lighthouse. I believe this is because their lights generate a halo which is easy to see, while the 2000 visible light size is sub-pixel from 100m or so.

I've seen your track, the small shift between asterisk and FPM is a long known bug, the HUD markers are all slightly mis-aligned on the 2000 (this includes bomb designator and ILS). This is not an autopilot bug, if you need perfect altitude hold, then you should use the ALT HOLD mode (second AP button) which normally keeps you perfectly at level. Otherwise you can't place your asterisk exactly at 0° angle.

Yes, I have 'Use Mouse' checked in VR tab. And when moving the mouse AND the cursor at the same time, the cursor moves as a sum of both moves. So for instance small inevitable head movements always shake the cursor even while moving the mouse. I'm using an Oculus Quest with Link. G2 ordered, I don't know if this is an Oculus vs Steam/WMR thing. I will do a video tonight. Yes, I have 'Use Mouse' checked in VR tab. And when moving the mouse AND the cursor at the same time, the cursor moves as a sum of both moves. So for instance small inevitable head movements always shake the cursor even while moving the mouse. I'm using an Oculus Quest with Link. G2 ordered, I don't know if this is an Oculus vs Steam/WMR thing.

Nice! Thanks For exporting all your settings for all your modules, I guess copying the whole Saved Games Input folder is faster.

DCS stutters because it's mostly single thread. Any operation (such as network I/O, loading textures on the fly, computing game physics, etc...) is blocking others. It's possible that more VRAM causes less frequent textures loads in-flight, thus less stutters.

Hi, On my system, the mouse cursor moves with my head. This makes turning a knob while looking somewhere else almost impossible. Some users (such as @imacken) have reported that mouse cursor stays still with head movement. Is that something we can configure somewhere?

Has the new throttle engine stop detents as well? @imacken : that's interesting, my mouse cursor always moves with the head movement... could we discuss this in the VR channel?

That's personnal preference I guess. I have played several many-player events where communications were very important, and we had to switch channels and set volumes a lot in a busy environment. Changing channels fast is very important, and it was really painful with the clickable cockpit. Now with dedicated encoders, this is super easy. I find the DCS clickable cockpit UI really painful for high workloads, since you have to keep your eyes pointed at the control the whole time. It's nearly impossible to turn a knob while looking at something else, there should be a "mouse lock" mechanism. For instance, in the Mirage 2000-C, the UHF channel knob is has a channel indicator just besides it, but the frequency is at a totally different place close to the hud. Turning the knob with the mouse in VR, while looking head up to the frequency, is nearly impossible. So if you know the freq you are looking for, but not the channel number, you're really inefficient.

I fly the Mirage 2000 mostly, and the panel is very handy in VR, where you need clear and simple command placement. I use the pots for radio volumes, encoders for channels, guarded switches for master arm and jettison, buttons for PCA and external views, etc... There could be some way to do this on the HOTAS only but it would certainly be less intuitive, especially when you need to reach everything blindly in VR with muscle memory and touch only.

Yes, this is the VIRPIL approach. I'm not a fan of this one, the switch spring fights the cover spring, and it feels wobbly and unrobust.

Most guitar pots are logarithmic, not a good idea for us.

Same case here... Unfortunately they had to increase slightly the shaft length to accomodate the detents. Changing the shafts with all the cables passing through is beyond a retrofit kit I guess.

I experienced this yesterday. And I'm 100% sure it's not an old bug, or at least it wasn't there 2 month ago.

Ah, I have open a new one before your post : Can we merge them?

I can confirm that changing: {pressed = iCommandAltimeterPressureIncrease, up = iCommandAltimeterPressureStop, name = _('Alt Pressure INCREASE'), category = _('Autopilot, Navigation, & INS')}, {pressed = iCommandAltimeterPressureDecrease, up = iCommandAltimeterPressureStop, name = _('Alt Pressure DECREASE'), category = _('Autopilot, Navigation, & INS')}, To: {down = iCommandAltimeterPressureIncrease, name = _('Alt Pressure INCREASE'), category = _('Autopilot, Navigation, & INS')}, {down = iCommandAltimeterPressureDecrease, name = _('Alt Pressure DECREASE'), category = _('Autopilot, Navigation, & INS')}, Does fix the crazy ALT pressure control issue. Regarding the missing V/UHF numpad binds, this does solve it: {down = 3952, up = 3952, cockpit_device_id = devices.VHF, value_down = 1, value_up = 0, name = _('VHF MEM/CLR'), category = _('Radio')}, {down = 3953, up = 3953, cockpit_device_id = devices.VHF, value_down = 1, value_up = 0, name = _('VHF VLD/XFR'), category = _('Radio')}, {down = 3954, up = 3954, cockpit_device_id = devices.VHF, value_down = 1, value_up = 0, name = _('VHF 1/READ'), category = _('Radio')}, {down = 3955, up = 3955, cockpit_device_id = devices.VHF, value_down = 1, value_up = 0, name = _('VHF 2/SQL'), category = _('Radio')}, {down = 3956, up = 3956, cockpit_device_id = devices.VHF, value_down = 1, value_up = 0, name = _('VHF 3/GR'), category = _('Radio')}, {down = 3957, up = 3957, cockpit_device_id = devices.VHF, value_down = 1, value_up = 0, name = _('VHF 4'), category = _('Radio')}, {down = 3958, up = 3958, cockpit_device_id = devices.VHF, value_down = 1, value_up = 0, name = _('VHF 5/20/LOW'), category = _('Radio')}, {down = 3959, up = 3959, cockpit_device_id = devices.VHF, value_down = 1, value_up = 0, name = _('VHF 6/TONE'), category = _('Radio')}, {down = 3960, up = 3960, cockpit_device_id = devices.VHF, value_down = 1, value_up = 0, name = _('VHF 7'), category = _('Radio')}, {down = 3961, up = 3961, cockpit_device_id = devices.VHF, value_down = 1, value_up = 0, name = _('VHF 8/TOD'), category = _('Radio')}, {down = 3962, up = 3962, cockpit_device_id = devices.VHF, value_down = 1, value_up = 0, name = _('VHF 9/ZERO'), category = _('Radio')}, {down = 3963, up = 3963, cockpit_device_id = devices.VHF, value_down = 1, value_up = 0, name = _('VHF 0'), category = _('Radio')}, {down = 3964, up = 3964, cockpit_device_id = devices.VHF, value_down = 1, value_up = 0, name = _('VHF CONF'), category = _('Radio')},

I can confirm this looks okay now. Just to confirm, is this normal if the FPM is horizontally caged in A/A modes, and uncaged only in NAV mode?

Here is list all the stuff in the mirage that you can control properly by clicking in the cockpit, but can't via binds. It's not just a lack of features, it makes the module very hard to use in challenging, multiplayer, radio intensive situations. My first take: Most multiposition knobs lack increase/decrease commands and we can't bind an encoder. HOTAS and panels have lots of encoders we would like to use with. UHF Channel preset V/UHF Channel preset TACAN 10 digit TACAN 1 digit PCN Mode The ALT pressure has increase/decrease binds but these are using "pressed" action, which makes the pressure change by a bunch of millibars for the slightest input. It's unusable, changing them to "down" would allow millibar input. Missing V/UHF numpad binds. Entering manual frequencies on the tiny buttons in VR is a real, real pain

+1, the first crank is already super bright. Light dimming should never be linear, but at least quadratic (light amount = input value ²) in order to provide smooth dimming for the human eye.

+1, but there are so much control binds to be improved on the 2000, I propose to add a wishlist for this...

Hi, Just for the record, after having printed the Bourns dual concentric pot knobs, I also found some here: https://www.ebay.com/c/18025109092 The pots : https://www.mouser.fr/Search/Refine?Keyword=dual+concentric&No=50&FS=True

By the way, how do you detect cover opening? I have seen the Virpil Approach, it's a good idea for a cheap&quick implementation, but it's not fully convincing as you replace a permanent switch by a temporary switch, and the two springs fighting together seem a not so robust option. I have thought adding a small push button on the rear, but maybe you have some recommendations? Thanks again!

Hi, Thanks for replies! @molevitch Do you have an example of ebay stuff? I tried looking for "guarded switch" but couldn't find anything interesting besides usual cheap plastic stuff. @PickleMonster Thanks, I'll definitely have a look! (Edit : ah yes, mouser have them, 51€...) (Re-edit : thanks for the microhelis tip, I didn't know that website! They seem to have a lot of interesting stuff!)

Hi, I looked in DCS yesterday... Where do you import/export device profiles? I could not find the feature. Thanks!