Baldrick33

My cheap and cheerful solution was to modify an old joystick as an analog brake, recalibrating it to just the back half of the range . A bit low end compared with the solution above but a quick fix for now

Frankly it isn't. Flying through solid buildings is something that under no circumstances can be considered a simulation. Easy to agree on. A bug if it occurs. Moving through a virtual cockpit in VR needs some careful thought about. You can't restrict the player's physical movement so have to make choices as to what happens should it occur. Those solutions are compromises, hence the debate about how best to deal with it. The hard limits option (stop positional tracking at limits) as used in other sims is the worst of those compromises In my experience. Now as long as I don't have it forced upon me I don't really care but being told over and over this is a fix to a bug is in my view not grasping how VR works for many people.

The point is that any VR implementation of simulating physical limits is going to be a compromise. It is determining which suits individuals the best and comparing the solutions with flying through buildings is irrelevant.

It is impossible IRL to continue moving your head once it is pressed against a glass cockpit. This is the issue we face as short of building physical constraints we can keep moving our head. Either the world magically shifts with our head or we magically move beyond the glass. Maybe it could fade out as we move outside or becomes lower res. None are great choices in immersion terms but the world suddenly shifting with us is the worst of those choices in my view. It is a tricky one to crack and not the simple analogy to flying through buildings you suggest. The only true to life simulation is a physical constraint. Period.

Curious as I see loads of key commands for this aircraft?

Without some physical limit on our head movement it is always going to be immersion breaking. 1/ I stick my through the virtual glass and get a whooshing sound as I move outside the cockpit. 2/ The tracking suddenly switches from 6dof to 3dof and the world moves with me. From a VR immersion perspective both aren't nice. The latter is worse as it feels like my VR has lost tracking and for some this can be quite an uncomfortable experience. Either way from an immersion perspective I quickly learn the boundaries and don't do it again. Personally I prefer the whooshing alarm than breaking my tracking but that is preference. Once learnt it seldom if ever happens so I have no real need for a fix, if people genuinely use it to emulate plastic man in multiplayer to cheat then I guess it needs addressing. Perhaps simply allowing a small amount of whooshing space as the first warning for those who don't want the boundary to be tracking breaking followed by a hard limit where positional tracking stops. So people won't be able to cheat more by sticking their head right out but those who accidentally push the boundary can back off without the nausea inducing tracking stop.

My speculation would be around priority of applications. Windows 11 changes how it prioritises to give greater priority to foreground apps. The more things you need running as a package the greater the risk of something being pushed back down the list that needs to be prioritised. Early versions of Windows 10 game mode badly impacted VR because the game was given too much priority over the VR compositor which was treated as a background app. Maybe the Vive software is being treated in the same way, I am making a wild assumption that WMR and SteamVR are recognised as being more than background apps by Windows. Are you running Game Mode in Windows 11? I currently have it on and seems fine with a Reverb but your Reverb is fine anyway so that proves nothing other than maybe worth trying on and off if you haven't already.

I should add that when I had the Index that refused to be recognised on one PC I had a Reverb G1 working perfectly. Had I not had the other PC to prove the Index worked I would have returned it as faulty. I still have no idea why the PC didn’t recognise is as the same hardware with same applications worked with a fresh install of windows. Nothing in device manager suggested any issue and the Reverb plugged into the same ports worked fine. Darn finicky these Windows PCs!

Oh I am not giving excuses for support, I try to avoid as much as possible! I just think it can be hard to pinpoint issues with PCs which are different and even on similar setups the OS can get screwed over time. Whether the issue here is with Win11 per se or the installation of Win11 over Win10 which could just as easily have happened with Win10 still installed is hard to say. The only proof would be a fresh install of Win11 but that comes at the cost of re-installing everything. Given unlimited time fresh installs are the best way to clear out underlying issues but it can be a daunting task.

The manual way Download the zip file from here: https://github.com/fholger/reshade/releases/tag/openvr_alpha2 Extract the zip file to your DCS installation\bin folder (not the Saved Games one) To tweak it edit the reshade.ini file in the DCS installation\bin folder Not sure if you can use OvGME or other tools to install and uninstall it but otherwise to remove just find the files and folders in the zip file and delete them manually from the bin folder.

Sometimes it is nigh on impossible to get to the bottom of an issue. In the Corporate world the quick fix for a playing up PC is to reimage it - i.e. reload the standard image of OS and applications. With corporate tools it takes a small amount of time, user data is generally stored centrally and any local files are stored in a given place and easy to backup and restore. Windows sometimes just gets itself tied up in knots and poring over logs and replacing drivers and DLLs takes too long or simply never resolves it. Last year I had and Index for a while and two PCs with Win 10. The Index worked fine on my old PC though it wasn't really powerful enough for DCS it would run it well enough to see it was working ok. On my gaming PC it wasn't recognised at all. I purchased a PCI-E USB card to no avail, tried numerous Windows fixes and spent days before concluding it must be the motherboard. I finally bit the bullet and reinstalled the OS from scratch. The thought of reinstalling all my utilities and drivers for my sim gear including and older direct drive wheel with a fairly complex setup with Granity and MMOS drivers filled me with horror! A few hours later everything was installed and working - including the Index. I didn't even need the PCI-E card.

I come from a corporate IT management background with standard builds and OS patch testing and deployment regimes. A Windows OS upgrade is a massive deal and takes months, sometimes years before adoption of a new version. My gaming PC on the other hand is my chance to rebel and contains all sorts of beta, early access. latest drivers and latest OS. I think it comes with the territory of games/sims enthusiasts to be early adopters. Not everyone of course, to some DCS is more mission critical than their work PC apps and certainly back in my league sim racing days I wouldn't dare mess around with my gaming PC during a season! Now I enjoy the bleeding edge aspect

Alexa understands me more than my wife I just used some cheapish Unicom remote control sockets from Amazon. Have the remote attached to my rig. Use it for fans, my powered direct drive steering wheel, amp for buttkickers and for base stations when I had them. Very useful.

When I had base stations I also used smart plugs with a little remote control to turn them on and off. They used to whine a little so I only turned them on when needed.

I upgraded and found no issues nor degradation in performance so I took the view there was no reason not to Given this is where the focus will be on development going forward and hopefully some benefits. Not without some risk of a dodgy update of course but life on the edge and all that.

It needs to go in your Saved Games\[DCS]\Mods\Aircraft folder rather than the DCS installation folders. This may be the issue?

My interpretation is that is it is just a change to naming of Actions rather than changing the bindings. So what was undercarriage down is now something like input.spitfireLFMkIX.uc1. The bindings are still there, just harder to find!

2.7.8.16140 Open Beta Several aircraft now have strange names appearing in the Action column in the controls setup These have the form Input.aircraftname.xxxxx In some cases these can be aircraft other than the one being setup (presumably copied from other aircraft controls) So far I have identified the following aircraft that are impacted: Spitfire Mosquito BF109 FW190-D9 FW190-A8 Yak-52 P-47 An example of the Mosquito entries are shown below:

Will do

I just found this and searched for any posts referring to it, yours was the only one I found, so I think we should raise it as a general controller bug as it seems to effect several aircraft. So far I have found it impacts the following: Spitfire Mosquito BF109 FW190-D9 FW190-A8 Yak-52 P-47

Mosquito Example:

Yes I am seeing that, the same for the Mosquito and BF109 from what I have checked so far The Mosquito also has references to Input.Spitfire and Input.YAK controls!

I recently got a new cable for my G1 whist it was still under its 2 year warranty in the UK. The G1 Pro was supported by the business side and the workstation team when phoning up. Not sure how the G2 is supported. The cable turned up a couple of days later. I found HP to be very helpful, they also replaced the headset three times in that two years. Fragile product with great support in my experience.

I think it is because the Mosquito seems the most sensitive on the brakes for aircraft that use a joystick lever rudder braking system and the least progressive of the applications, hence the tweaks to make it more progressive using Joystick Gremlin etc. or much better adding an analog brake. It just feels nicer than tap tapping the lever to taxi. Whilst not essential an analog brake lever for these aircraft is a missing feature for Warthog owners and other sticks the Mosquito has really bought that to our attention!

I lost an engine soon after take off with a cold start and that was exactly the reason why.