Sprool

sorted, was switching tads/fcr on the display but not on the grip button. Remapped a couple of controls.

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.