potneros

I use the custom presets in the DCS system options menu to toggle between my preferred 2D and VR presets. I would love if DCS itself could be launched with a flag (e.g. "--custom2-preset") to apply the desired profile from a Windows shortcut. That way, I could combine it with the "--force-enable-VR" flag to create direct-launching DCS 2D and DCS VR shortcuts which pre-load the relevant settings profiles. No mess, no fuss. There are a handful of extremely useful DCS launcher utilities already in existence which variously get close to this. I've tried a few and found them chockful of features, but haven't found that any provides a way to do exactly what I want (at least, not that I've figured out!). So I knocked up my own, which works exactly like I wanted, and figured I'd share it. Usage: dcs_launch.exe [OPTIONS] [ARGS] Arguments: ARGS Arguments to pass to DCS executable [optional] Options: --dcs-bin PATH [required] --dcs-saved-games PATH [required] --profile-id INTEGER [required] --help Show this message and exit. Simply create a shortcut to this launcher, and set the --dcs-bin, --dcs-saved-games, and --profile-id options in the shortcut target. You can add any additional arguments as well, which will be forwarded on to DCS. The launcher will pick up the custom profile options in your saved games folder and integrate them into the options.lua file before launching DCS. By allowing you to specify the DCS bin directory, you can create separate shortcuts to ST and MT as you wish. Example shortcut target: C:\Users\<username>\Downloads\dcs_launch.exe --dcs-bin "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt" --dcs-saved-games "C:\Users\<username>\Saved Games\DCS.openbeta" --profile-id 2 --force_enable_VR Why is it 8-freaking-MB!? Because I knocked it up in Python, and so the .exe includes an entire Python DLL (I used Nuitka for packaging). I'll include the extremely short Python script for anyone who wants a look-see. Just - please - if you want to try this SAVE A COPY OF YOUR OPTIONS.LUA FIRST. This script rewrites the file, and while it hasn't been a problem in my extremely limited 5-minutes of testing, consider yourself warned. dcs_launch.exe dcs_launch.py

Interesting. And I'm glad it's not just me. Are you saying that setting the impact angle in the weapon profile has no effect? I might try that next.

I'm at wits end. I can use the laser JDAM perfectly well on moving targets in the training missions, but when flying the stranded kilo mission...nada. I've checked and rechecked that the laser codes match, that I'm lasing before drop (and not IR pointing - did that once before), that TGP is providing SPI. I've got a wonderful point track which stays perfect and unobscured throughout the bomb's fall. Time and again, the bomb impacts 300 yards behind the ship - where the SPI was at release. What else could I be messing up? If it's nothing obvious I guess I'll capture a track file and call it a bug?

I only really tweak the up and down (seat height)f. In the A-10 - I find in the default the gun reticle is too high in the HUD so I lower the seat a bit. The viper takes more tweaking fore and aft, but I also like to sit lower on landing so I can see the gun cross relative to the 15 deg pitch ladder so as to not drag the tail...

Are they even the same name? I remember somewhere saying it's "data management switch" in the A-10 and "display management switch" in the viper. Same acronym, different name. I use the 4-way on the MMS for cockpit view - seat up/down and camera forward/aft. I find myself needing to move around, especially in the A-10, to keep everything in sight. I play in VR so zoom isn't really an option.

This isn't really a question, just a thought to share. I alternate between the Viper and Hog and have the WinWing Orion2 F-16EX HOTAS. My challenge is that the Viper uses DMS for selecting MFD screens and SOI, where the A-10 uses the coolie switch. My muscle memory is stronger than my brain and I end up doing strange things in the A-10 under pressure, like turning on the HMCS MFD repeater when I'm trying to bring up the TAD. This isn't really any fault of the HOTAS mapping, which (amazingly) works pretty seamlessly layering the A-10 on top of the WW F-16 throttle (use the IFF IN/OUT for China switch, DGFT/MSL ORIDE for boat switch, 4-way MAN CAGE for coolie). Instead it's a result of rapidly alternating between two cockpits, which isn't something that happens all that often in real life (and definitely not in combat). My solution is to simply swap the coolie and DMS for the A-10. Sacrilege to some, but it functionally aligns with the Viper layout and it doesn't require brute force realigning my brain. Just leaving this here for any who might need a spark of inspiration when struggling with the same.

Roger that. That all makes sense - the only thing that I question is whether in Block 50 the VHF radio was on the DC emergency bus as you say. There's indication on the internet that it wasn't until later variants, but if it's modeled intentionally on DC emergency bus then it's working as intended. I'm in no position to say what is exactly accurate and what isn't.

My understanding of the block 50 electrical system is that the VHF radio is powered by the DC non-essential bus (main gen only), whereas UHF is on batt bus #1 (EPU powered). When I cause the engine to flameout in flight and the EPU kicks on, then select Com 2, the DED still shows VHF ON. Can anyone speak to whether that's accurate? Talk about niggling though

I second (third? fourth? millionth?) the need for this tool and correction support in MT w/ native OpenXR. I have substantial vertical alignment issues in DCS with my Reverb G2 which can be corrected using the debug tool under ST w/ OpenVR -> OpenCompsite-> WMR, but not with MT w/ native OpenXR. Here's an example - with head completely level (recenter to be sure), hold one eye shut, then alternate to the other, rapidly back and forth. Presumably there should be no vertical shift, but without the correction in place I see a significant vertical displacement (effectively introducing vertical heterophoria). Without the correction in place VR is very uncomfortable, but as soon as I applied it in ST w/ OpenCompsite everything was so much improved. Unfortunately the ST performance isn't as great. Please please please @BIGNEWY convince who you can to bring back support for this in MT OpenXR!