Sprool

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.

while the pilot mic switch is now sorted - ie: turns on automatically with hotstart, the WSO mic switch remains off. Not a biggie but would be nice to have consistency.

I tried twice redesignating target a couple of times and it never worked, I didnt try more than twice as I'm just not patient enough

I made a shortcut to DCS multithread which force-loads VR and the OpenXR toolkit, which is great for a performance boost. "E:\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe" --force_enable_VR --force_OpenXR Works fine as long as the Quest 2 is fired up and ready to go, I run DCS from within the Quest app, dcs appears in my games library.

Got round the issue - didnt know it was possible to set custom snap views in VR, but it is so I have allocated one each for the L, R and lower MFD's at mid-zoom level which is fine for reading the font on the displays. Sorted.

New to VR, I have both zoom and 'spyglass' zoom mapped to hotas buttons but I find the zoom level is too high for me to comfortably read the mfd's in the jets. Its like my nose is pressed against the MFD. There must be a lua file somewhere or setting you can edit to get the zoom just a bit further back? Has anyone looked into this?

I'm getting an issue with mixed GBU drops in the F-15e: loading up some GBU12's and some GBU10's along with T-pod. Both configured as Auto/Step/N-T. First lot drops fine, laser guides onto designated target via T-pod. If I switch to other types, designate target with t-pod, the laser fires but doesnt guide the bombs onto target. Sometimes the vertical aim line is way off where the target was designated. Both types are set up identically in the armament page and have same 1688 laser code. It seems to happen when I switch from GBU12's to GBU10's, and not vice-versa. I'm hot starting in the air from the mission editor. But I get same problem in the 2nd part of the Operation Goliath campaign in downloads section.

So it looks like this may be a bug rather than operator error...?I made a hot start mission in the ME but only had to set up the GBU10's in the PACS menu.

I'm getting a problem when I have different GBU's in a loadout and laser bombing using the T-pod to designate. If I designate a target, drop a GBU12 then switch to designating a new target to drop a GBU10 the fall line goes way off so either the bomb doesnt release ot it doesnt track the laser. Maybe I'm missing a vital step somewhere but I dont get he same issue switching from a GBU 12 to a CBU97. Its just the GBU10 that seems to cause an issue?

Any tutorials , guides or hints for conrol mapping and workflow for the poor guy that sits behind the pilot?

Can I map the gain and level of the T-pod to an axis or buttons from the WSO position?

Not a biggie but if you hide the joystick, then switch the wso position, then back to pilot position, the joystick appears again as a default.

That makes me happy

Such a great tool for F-16 missions, I'm wondering if you will be working on a version for the newly released F-15e?

Aided by my fellow expert i found the bug disappears when you press L Ctrl and Num + , or L Ctrl and Num - to switch fom fwd to aft radio comms. It brings up the comms menu again.

Same issue here, in MP servers you can only contact the ground crew once, then the comms menu fails to come up. This is regardless of if the plane is running or cold, cnopy open or closed, radios on any frequency. Just since the last update. In SP or quickstart its not an issue, which may point the problem towards having easy comms switched off in most MP servers?

you'll have to wait till they sort it out and put it back in

Really not getting on with the new Gazelle FM, it oscillates wildly trying to self-correct when turning/banking, Im finding it almost impossible to take off with reduced weight, it feels like one of the poor msfs helicopters

As a work-round I can program the location of the targets then switch to FLIR and use TOO mode but then I lose the ability to ripple off up to 4 JDAM's on 4 close targets.

I'm having trouble getting Jdams to drop in pp mode in the Hornet when using TheWay. Any steo-by-step tutorials available?

Brilliant tool - big thanks! Works so easily in the F-16. Struggling wiht the F-18 Jdams (J82) to get it to work properly. Is there a step-by-step tutorial somewhere on how to use in the Hornet? I cannot get the bombs to ready for release? I'm sure its pilot error as I've not flown n the Hornet for ages. I can get the co-ord data transferred over correctly and get the Jdams on countdown to ready but the pp1 mission remains crossed out. I have jdams set to pp mode, instant fuse. I checked the data was in precise and correct co-ord mode selected before data transfer.

Would be nice if they finished off the K-4 with wing cannon and rocket options

Solved for me - dcs_volanta.lua file had never installed, nor the corersponding entry in the export.lua file. Now both in place Volanta connects perfectly in sp or mp, im running Openbeta_MT

It cant be dead as my friend is usuing it, i cant get volanta to recognise dcs at all though. I have no volanta entry in my export lua file. Is thee a volanta plugin i need for dcs, or alternatively a dcs plugin for volanta? Volanta shows a msfs plugin in the user settings > simulators screen but nothing for dcs

about 18 months - one of them was a start/taxi/takeoff tutorial from Reflected, he mentioned the fuel pump slider and no im not asking him for a track file