SOLVED (workaround): Varjo Aero locks IL-2 files, makes it impossible to map controls in VR.

[SvAF/F16_Goblin]

EDIT:
Moving to different display port solved the issue!
On the second move, changing both monitor and headset display port I was able to map the controls again.
Apparently the files don't really get locked. There seems to be some kind of erroneous signal sent in this scenario blocking the possibility to map controls. It's interesting however that it only affects IL-2. 

 

Any one else having this problem?

Can't map controllers since last upgrade, getting "null" input when trying to change mapping.

Files are market read-only but DCS don't have any problems. Just IL-2.

Edited October 31, 2023 by SvAF/F16_Goblin

[AEthelraedUnraed]

Unmark them as read-only?

[SvAF/F16_Goblin]

Don't work, I have concluded that it has nothing to do with the files being read-only marked.

This is a Varjo Aero software issue. It seems to lock the files in VR so it's not possible to edit or map controls.

DCS works perfectly in VR but not IL-2.

Confirmed this by starting in 2D and no problem with mapping of controls.

[AEthelraedUnraed]

14 hours ago, SvAF/F16_Goblin said:

Don't work, I have concluded that it has nothing to do with the files being read-only marked.

This is a Varjo Aero software issue. It seems to lock the files in VR so it's not possible to edit or map controls.

DCS works perfectly in VR but not IL-2.

Confirmed this by starting in 2D and no problem with mapping of controls.

I happened to change a key binding last Thursday evening, in VR (Quest 2), so that confirms there's no sudden changes in IL2 that prohibit adjusting key bindings. It also sounds very unlikely to me that this is something the Varjo Aero software would do, since Varjo has no way to know which actions it should disallow in which apps. Besides, it would be a lot of work to program such a thing, and to what gains?

 

It still sounds like some local issue on your machine. Are you on Steam? If so, could you verify the integrity of the game files? Also, please ensure no files and/or folders within the IL2 directory (especially the data\input folder) are still marked "read-only"; it may or may not be the only issue, but if those files are read-only, it wil certainly result in being unable to change your key bindings.

[Patricks]

16 hours ago, SvAF/F16_Goblin said:

Don't work, I have concluded that it has nothing to do with the files being read-only marked.

This is a Varjo Aero software issue. It seems to lock the files in VR so it's not possible to edit or map controls.

DCS works perfectly in VR but not IL-2.

Confirmed this by starting in 2D and no problem with mapping of controls.

 

Well, all I did was untick the read-only flag, no other changes, and it immediately worked.. Changing ports did nothing, and now it's back (on it's own) to Read-Only and it STILL works, so I would say it's still a total mystery...

[SvAF/F16_Goblin]

Right, so I was happy for a minute there ? 

It worked one time and the next it was back again, not being able to map controls. The only sim/game that is affected so far is IL-2 and therefore I have to conclude that it is a problem with how this software handles the files. Unfortunately, since I don't have a monitor in my simulator rig this means that have no way to handle this.

It will probably mean that I will shelf IL-2 indefinitely for now. 

[dburne]

21 hours ago, SvAF/F16_Goblin said:

Right, so I was happy for a minute there ? 

It worked one time and the next it was back again, not being able to map controls. The only sim/game that is affected so far is IL-2 and therefore I have to conclude that it is a problem with how this software handles the files. Unfortunately, since I don't have a monitor in my simulator rig this means that have no way to handle this.

It will probably mean that I will shelf IL-2 indefinitely for now. 

 

Don't give up yet, the experience  with the Aero is second to none. You can get this working trust me. Sometimes it is the simpler things. Computers, gotta love em. Sometimes those gremlins bite though lol.

 

Try posting a new thread on this in the VR forum, VR Aero subforum it will not be seen by many.

 

Don

[[CPT]Crunch]

Lemme guess, default install in program files Win 11?  Never do that, it wants complete control and will auto lock your files right back to read only especially if your not on the Pro version and have limited say.  Transfer your game to a folder you make anywhere else besides in a windows made and managed default folder.

[dburne]

44 minutes ago, [CPT]Crunch said:

Lemme guess, default install in program files Win 11?  Never do that, it wants complete control and will auto lock your files right back to read only especially if your not on the Pro version and have limited say.  Transfer your game to a folder you make anywhere else besides in a windows made and managed default folder.

 

That be some smart thinking there. This man knows his stuff!

I have not installed games to that default folder in years.

 

Don B.

Edited October 29, 2023 by dburne

[SvAF/F16_Goblin]

17 hours ago, [CPT]Crunch said:

Lemme guess, default install in program files Win 11?  Never do that, it wants complete control and will auto lock your files right back to read only especially if your not on the Pro version and have limited say.  Transfer your game to a folder you make anywhere else besides in a windows made and managed default folder.

Nope, I never install in windows program folders.
All my simulators reside on separate drives.

[firdimigdi]

On 10/27/2023 at 9:54 PM, SvAF/F16_Goblin said:

Apparently the files don't really get locked.

 

Out of curiosity: could you paste the contents of your data/input/devices.txt file here?

And when it happens next rename that file to _devices.txt and again check the contents of the newly created devices.txt?

 

What you describe sounds like something is registering your HMD as a directinput device that the sim picks up and inserts (in the wrong order) in the list of input devices it knows of. If it's even actually related to the HMD.

 

Edited October 30, 2023 by firdimigdi

[dburne]

25 minutes ago, firdimigdi said:

 

Out of curiosity: could you paste the contents of your data/input/devices.txt file here?

And when it happens next rename that file to _devices.txt and again check the contents of the newly created devices.txt?

 

What you describe sounds like something is registering your HMD as a directinput device that the sim picks up and inserts (in the wrong order) in the list of input devices it knows of. If it's even actually related to the HMD.

 

 

Listen to what this man speaks. He knows very well what he is talking about.  Best advice you can get.

Edited October 30, 2023 by dburne

[SvAF/F16_Goblin]

@firdimigdi

That sounds plausible, when I go in to edit the mapping it sends "null" immediately so the HMD must register as a control and send that input.

It happens all the time when I try to edit in VR mode, not in 2D mode.

 

However no change is made to devices.txt

Before VR
configId,guid,model|
0,%22c20e3a40-74e1-11ee-0000545345441180%22,Joystick%20V2.04|
1,%22c20e1330-74e1-11ee-0000545345440f80%22,VPC%20Panel%202|
2,%22c20e6150-74e1-11ee-0000545345441780%22,Total%20Controls%20MFBB|
3,%22c20e6150-74e1-11ee-0000545345441680%22,MFG%20Crosswind%20V2%2F3|
4,%22c20e3a40-74e1-11ee-0000545345441480%22,VPC%20Stick|
5,%22c20e6150-74e1-11ee-0000545345441980%22,VPC%20Panel%201|
6,%22c20e3a40-74e1-11ee-0000545345441280%22,VPC%20Throttle|
7,%22c20e6150-74e1-11ee-0000545345441880%22,Joystick%20V2.04

 

After VR

configId,guid,model|
0,%22c20e3a40-74e1-11ee-0000545345441180%22,Joystick%20V2.04|
1,%22c20e1330-74e1-11ee-0000545345440f80%22,VPC%20Panel%202|
2,%22c20e6150-74e1-11ee-0000545345441780%22,Total%20Controls%20MFBB|
3,%22c20e6150-74e1-11ee-0000545345441680%22,MFG%20Crosswind%20V2%2F3|
4,%22c20e3a40-74e1-11ee-0000545345441480%22,VPC%20Stick|
5,%22c20e6150-74e1-11ee-0000545345441980%22,VPC%20Panel%201|
6,%22c20e3a40-74e1-11ee-0000545345441280%22,VPC%20Throttle|
7,%22c20e6150-74e1-11ee-0000545345441880%22,Joystick%20V2.04

 

It seems to register as an input device but not edit itself into the devices.txt file.

Edited October 30, 2023 by SvAF/F16_Goblin

[SvAF/F16_Goblin]

However, there is something I could try. I can disable the HMD buttons in Varjo Base software. Perhaps that is what sends the "null" command?

Will test and report back.

 

EDIT:

No that didn't work. I've checked the devices.txt file during running of the game in VR as well and no change there.
The "null" input is fast but not so fast that a quick press of another button shouldn't register but it doesn't.
The HMD (or Varjo Base software) seems to disable new mapping only because mapping done in 2D works in game.

 

I'm not a newbie with computers and software but I don't understand this

Edited October 30, 2023 by SvAF/F16_Goblin

[firdimigdi]

So, just to be clear, even if you rename devices.txt and have the game recreate it with the HMD connected the result is the same?

 

Does any extra device show up in Windows' game controllers list when you hook up the Aero? Or in any program that can enumerate such devices, like DIView for example.

[Patricks]

I was just forced to do a complete reinstall of Win11 Pro from scratch, and all applications. Fresh install of Varjo, IL-2, Steam/SteamVR, et all. Saw immediately the VR keybinding "Null" bug was back, unticked the "Read-Only" flag.. still no good and it re-sets to Read-only with every IL-2 start anyway. Re-read some previous answers and one was running IL-2 in Admin mode fixed it, so I tried that.. It worked! I "think" the last time I did this I set it to Admin mode AND unticked the flag, and forgot I set it to Run as Admin. Got in\out of IL-2 several times, still works fine. Can't say for 100%, but this seems to do it (today anyway)...

Edited October 30, 2023 by Patricks

[SvAF/F16_Goblin]

@Patricks I think that it's You and I that have had the conversation in Varjo Discord ? Yes it worked but not happy with software running as admin. Will map controls and then revert back. Find it disturbing that only IL-2 requires this workaround. DCS, Falcon BMS and Cliffs of Dover works perfectly fine without admin rights.

 

 

34 minutes ago, firdimigdi said:

So, just to be clear, even if you rename devices.txt and have the game recreate it with the HMD connected the result is the same?

 

Does any extra device show up in Windows' game controllers list when you hook up the Aero? Or in any program that can enumerate such devices, like DIView for example.

Yes, the same result. However as per the post above admin rights seem to be a workaround.

Edited October 30, 2023 by SvAF/F16_Goblin

[firdimigdi]

Interesting, perhaps more info can be found by using Sysinternal's Procmon - set it to only show entries for the data/input directory and then you can narrow it down as to which process is setting it to read-only.

[SvAF/F16_Goblin]

@firdimigdi

I don't know if I want to go down that rabbit-hole.
The interesting thing is that it doesn't set read-only as far as I can see checking the files during a VR session, but still blocks the mapping.

In Aero discord I read a post where someone stated that instead of setting admin rights, they had managed to map controls using the virtual Varjo desktop as a workaround.

Will test that some day and see if it works for me as well.

Edited October 31, 2023 by SvAF/F16_Goblin

[SvAF/F16_Goblin]

I can confirm that mapping the controls via Varjo Base software virtual workspace works!

Use the button on headset to go in to the workspace and do the mapping of controls there and there is no need to give admin rights.

 

Very peculiar workaround but I'm happy ?