Sprool

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.

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