Sprool

thanks that was useful, you confirmed my suspicions about wiping memory when starting a new scan, at least i know its not me missing a trick.

Either seat, i can switch from SAL to RF but not RF to SAL, im trying to disengage fcr and get the tads display up again but cant select SAL. Im not engaging HMD in the front seat, just the centre screen/TADS

Now the FCR is with us, I found I can change from SAL to RF but not back again, I'm assuming pilot error here...?

I'm still waiting for the corsair

VR is a bit fickle but if MSFS can implement an easy switching system to and from VR->flat screen and do it consistently and predictably (which it does on my setup) then I would hope same can be implemented in DCS. It takes a lot of tweaking to get the balance of performance and quality but when it is there it is fantastically immersive. DCS runs at over twice the frame rate of msfs in VR, but it drives me mad every time I remove the headset the game freezes and crashes.

3) targets might have moved - it can already distinguish moving targets and changes symbology accordingly, and the FCR still marks them with an X once they've been fired on.

OK, but if it's clever enough to put an X on the screen where you already fired a missile why would it allow a second one to be fired there? Regarding the scan area slew, can you do it whilst scanning?

On the FCR it already marks an 'X' on targets you've launched missiles at, to have to mark it manually as well with a target point seems a bit of a pain - if it knows you already shot at it, it should not reset with a new scan should it? I'm suspecting this is not a feature but something that's not yet fully implemented, I hope. I dont like wasting Hellfires on targets already killed. The whole point of the FCR is to release a load of Hellfires on a group of enemy positions in a short as possible time with minimal effort.

this bug has already been reported

2 issues I'm finding with the Apache FCR; first the manual slew L & R for the scan area, only moves when you stop scanning. When you stop scanning it re-centres anyway so is there any point in having the scan slewable? Should I be able to slew it left and right when its actively scanning? Second, if I stop then re-start a scan it picks up a target I have previously hit and destroyed, and will send another hellfire to hit it again. Its like the scan restarting wipes any memory of previously targeted and destroyed units, and the scan is picking up destroyed ones as still live.

Not sure I can agre with this, I've not sat in an F-16 cockpit or F-18 irl but in game vr the F-16 feels really tiny compared tot he F-18, and the Huey feels huge with really big gauges in comparison, as does the Mi-8. Not sure I can agre with this, I've not sat in an F-16 cockpit or F-18 irl but in game vr the F-16 feels really tiny compared tot he F-18, and the Huey feels huge with really big gauges in comparison, as does the Mi-8.

Id like to piggy-back onto this thread and askf ro the mouse scroll wheel button (3) to be made active and mappable; I have this set in all other modules to toggle mose-clickable cockpit on and off, but the viggen module has no setting for mouse buttons other than the main L & R-clicks [edit] i just read you can activate this by double-clicking scroll wheel - sorted.

I followed a hunch last night to test further - I think I found my problem. In mission editor I have a sandbox rtainiing mission where I add aircraft & different payloads to learn weapon delivery. If I change loadout before flying the mission there seems some interference from the original loadout I entererd when I created then saved the mission. For example, originally I have an F-15e with GBU12's and CBU97's. I then went into the mission and changed loadout to GBU12's and GBU10's, removing the CBU97's but when flying, the aircraft armament still thinks CBU97's are loaded in and when I switch the the prog I set up with GBU10's the drop line is way way off target. GBU12's seemed ok - the mission was originally set up with them anyway. If I delete the aircraft and set up a new one with mixed GBU loadout, the problem seems to be cured - when switching between GBU10 and GBU12 the drop line remains on designated target.

totally agree, msfs is so easy to switch between the 2 modes - i just have a button on the hotas assigned to do the switch

This is easier for what I'm after: https://www.digitalcombatsimulator.com/en/files/3319775/

thanks! I think I get the idea, creating a vr and a 2d folder, but how to create the custom configs needed in each one if I just want graphics settings preserved? Do I just run it it VR, then save & exit and copy the config folder, then rinse and repeat for 2d?

Is it possible to set up 2 separate shortcuts for dcs.exe (MT) - one that recalls all my settings for VR flight and one for 2D flat screen flight?

Manual? I have to read the manual?!?

im looking for a bit more info/training/how-to videos for the WSO - radar, t-pod, target designation, all the usual stuff

When I create a new shortcut by dragging existing one to my desktop for example, I just add the extra text to the properties that already exist, and in Target there are already speech marks there around the text so you just add the --force_enable_VR and so on. You just add a space and 2 dashes or minus signs then the rest of the text. If you are still struggling then can you launch DCS from within your VR headset in 'my apps' or 'Library'? Thats what I end up doing most of the time.

strange, works ok on my pc

you should have speech marks after .exe and not after OpenXR "E:\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe" --force_enable_VR --force_OpenXR

Your work-round doesnt work for me. I think you just got lucky. The bug is not consistent, I'd say 70-80% of the time I get an issue. I tried different combinations if slewing and designating. If you can get it to function correctly as a work around till they get the bug fixed then you are more fortunate than me! I also noticed in a self-made mission with an F-15e already configured with GBU10's and GBU12's, the 10's consistently fail to show up in the armament screen, but all the other ordnance shows up correctly. So you have to go back into A/G and identify the GBU10's that the pylon hasnt recognised. Not a big problem but it identifies that something is not working consistently re loadout and it points again to the GBU10's.

I agree with Bosun, I think WizzRD is barking up the wrong tree. The fall-line problem is specifically when switching to the GBU10's whether or not you redesignate. It has to be a bug - the other GBU's work fine with no problem, totally predictable behaviour. With GBU10's the fall line can be 1/4 mile off even when the HUD cursor is sitting on the target. No wonder they dont pick up on the laser.