Baldrick33

Could try stopping and starting the windows installer service edit: start run services.msc Yes it should appear after you have run it with the Apache

I use VR and use the CMS hat on the Warthog stick as mouse clicks, so I look at a switch and press the hat switch for left or right buttons. I find it works pretty well. I also use Joy2Key to centre the mouse cursor again using the same hat.

The Wags video linked above is very comprehensive - although at over 30 minutes long is a bit too much for my limited attention span The problem is although we are trying to replicate the real thing it can come down to personal choice as mapping everything you might need can lead to complicated setups with lots of modifiers and loads of combinations to memorise. Here are my settings so far if it helps: AH-64D CPG.pdf AH-64D PILOT.pdf AH-64D AI.pdf

I think it may be because there are two WAS hats in the CPG Cockpit - on the HOCAS and the TEDAC LHG. If you bind WAS Up to the HOCAS keybind the tutorial doesn’t proceed awaiting a press on the TEDAC WAS Up.

To the OP, yes this is a complex one to setup. I think it will take people some while to find their perfect setup as they find what is needed to have mapped in action. To use both cockpits you need to map both PILOT and CPG cockpits separately (plus the few controls for the George AI) To get going though you can just focus on the PILOT cockpit. To be able to fly and shoot stuff you need to map the WAS hat to select weapons. I mapped this to the TMS hat (left hand below weapon release button) on my Warthog stick. I then mapped trigger safety to my stick paddle and fire to the trigger. I used the TRIM HAT for the trimmer commands AND the George AI. The button top right of the stick I use to select George. Once selected the TRIM controls work for AI, when not selected they are trimmer controls. I use the pinky switch on the throttle to switch between sights (HMD & TADS) There is a ton more to map but that gets you shooting stuff on the range

There are two WAS hats in the CPG cockpit. Cyclic and TEDAC left hand grip. The tutorial requires the TEDAC one to be pressed and ignores it if you have it mapped to the cyclic. I had the same cyclic WAS controls mapped to PILOT and CPG, I needed to click on the TEDAC WAS hat using my mouse to proceed with the tutorial.

Firstly any new module needs to be added to SSA by @f4l0 As he doesn't get the modules for free or in advance he needs to purchase it and then map the telemetry to his free program. Hence the suggestions to donate. The second issue is that there are limitations with some modules to be able to extract the telemetry depending upon what gauges etc. the aircraft has to extract the data from for inputs or something like that! Making it hard or impossible to extract RPM or torque for example.

Also reported here:

I have this too. The blue cursor just freezes in the position it would have disappeared in previous builds. It is a bit annoying!

I might just add a modifier (button on a button box) as this should only need to be used at start up. Alternatively I might map the 3 position WH Throttle ENG OPER L & R switches as off/idle/step up.

Some good troubleshooting there Mr_B! As frustrating as it seems that is kind of what open beta is about. If this didn't happen to anyone in the closed beta testing then the next step in the bug discovery is open beta. Having worked in Corporate IT where we have standard PC builds and do not allow users to install their own stuff I do have some sympathy for PC games developers where every PC is different and all sorts of mods are installed. Let's hope the next one is less work to install for you though!

Not sure if this link covers your model but it maybe worth looking at the software and firmware available https://semiconductor.samsung.com/consumer-storage/support/tools/

Does the drive come with any software? If so is it running? Is there a firmware update available for it? it feels like the drive is running at 100% unpacking and times out the DCS installer.

My only suggestion is to copy your installation to another drive if you have enough space and update it and then move the installation to your SSD.

Controls such as collective, cyclic and rudder are mapped to double or multiple controllers. By default it seems any controllers with axes get mapped, I needed to remove several binds so I had just cyclic pitch and roll to my stick, collective to my throttle and rudder to my pedals. Then I had to reverse the throttle axis bind and make it a slider.

It is maxing out my 100Mbps connection here in the UK

You can also do it using the DCS_Updater.exe command line. Instructions are in the first post here (just scroll down to the section switch between versions)

Ok to spell it out. They couldn't run the Apache they had pre-ordered using the stable version they had installed and didn't wish to install the beta version. They hadn't realised the Apache would not be available on the stable version at initial release. Some have helped the poster to explain how to get the beta version loaded without downloading loads and using lot of disk space. Some people don't realise a module isn't immediately available on both versions so we are trying to help and repeatedly saying that modules aren't specific to versions really isn't helping them, when that is exactly the case for the Apache which this thread is about.

You laughed at someone because they said they couldn't have the Apache they pre-ordered on the stable version. Yet that is exactly the case which we have tried to explain why. No you don't have to purchase modules for both versions as you rightly state but that was never the question!

If you bought the Viper when it was released it would have been on OB only. It is always the way, initial release is only available on OB and when considered suitably stable gets promoted to stable version. It is exactly what the names beta and stable imply. So no, if you are on stable the module you have pre-purchased will not be initially available. So they are absolutely bound by versions. Fortunately as others have mentioned the GUI updater can quickly transfer between versions and only download the deltas.

They are very much version bound!

Might be worth clearing the environment data in WMR and resetting the seating position? I read that the recentre works a bit weird you have to look (not move) the opposite way to where you want it to shift to or something like that. Sat in the Spit I got centred in the right place but whenever I looked left I got the out of cockpit wind sound so it is a bit buggy.

My experience performance wise so far isn't great, however, I find DCS using SteamVR with my Reverb G1 is much smoother (with motion reprojection on) than MSFS so that maybe be down to my PC config (I run a 8600K at 4.9GHz which seems pretty good for DCS in VR, maybe that isn't so good for OpenXR?) Running DCS in OpenXR works fine but unless I achieve 90fps it isn't smooth at all, so this must be down to motion reprojection. I have tried enabling it in OpenXR tools but seem to have little or no effect. My initial reaction is that this isn't the boost some have suggested it might be but it is early days of tweaking!

This is what i did to get it to work: Download the file OCXR_WMR_ACC_v0.4.zip from here: https://gitlab.com/Jabbah/open-composite-acc/-/releases From the zip file copy the files to your DCS installation bin folder (backup existing files first): opencomposite.ini openvr_api.dll D3DCompiler_47.dll Note that I already had OpenXR Tools installed on my PC, you can get it from here https://www.microsoft.com/en-us/p/openxr-tools-for-windows-mixed-reality/9n5cvvl23qbt#activetab=pivot:overviewtab Note that having the display timing overlay on will stop DCS from starting I just started DCS in VR mode normally - some people say you need to keep DCS in the foreground when loading by clicking on the icon in the status bar, I didn't seem to need to do this but if you get a blank screen try this.