moggel

Unfortunately, no. I'll be sure to do that when/if I see this next time

Was training with the HTS today and noticed my TGP had gone in to some unknown mode I hadn't seen before. Apparently it was slaved by the HTS, as expected, but all symbology was gone and in the lower half I saw the word "RATES". I could not slew it at all. I tried undesignating the HTS but TGP didn't change at all. Anyone else seen this?

I have only tested this with the F-16C but overall I get the same result when I lock moving targets: The weapon locks but does not track after being fired. I first noticed this when testing it against ships. I also noticed that if I slowed the ship down considerable (7 kt or less) the weapon would track but not when moving faster. I tested the same against some BTRs lately and found the same behavior. Can anyone else confirm or explain this behavior?

I get this too, occasionally, and I don't even own a pair of controllers. I get other types of dialog popups as well. Today I got one saying "Your IP is: " (not showing an IP number). There was a "Close" action button but I have no clue as to click it. I do have WIN+Y set to manual to set focus to WMR but that didn't help. Is WMR hogging certain keybinds to popup stuff like this? If so; is there some settings somewhere I can deactivate that?

I'm using TARGET to emulate some extra axis, as well as assigning one key to SHIFT, allowing several buttons to have double functionality etc. If I understand your advice correctly I need to create "keyboard" assignments for all MFD buttons? If so, what are their "script names"? The lower left switch on the throttle, for example, is called "EACON" / "EACOFF" so I can use those names in the TARGET sript. But I haven't found any such names for the MFD buttons in the TARGET manual.

Finally got myself a pair of Cougar MFDs but can't figure out out how to use them with the TARGET scripting software. I went into the keybindings (F-16C Sim) and bound all the MFD keybinds to the virtual controller's "Joystick buttons". But, apparently, the same "Joystick button" is found both on the MFDs and on the HOTAS. How do you create keybinds for the Cougars that does not interfere with the HOTAS? I found nothing in the TARGET manual for this, or am I just blind?

Might be that I initiated the alignment before INS alignment was done. I will make sure I do and see if it happens anyway. Thanks

Every now and then when I align the HMCS during a cold start the procedure fails. At the first step, when I go M-SEL and align my head/eyes with the large cross, I get a "FAIL" message at the end. When this happens it seems there's nothing I can do to fix it. I have tried turning off the HMCS and start over but I always get the "FAIL" message in the end, which then prevents me from continuing to the other two alignment steps. Does anyone know what might be causing this? I suspected it could happen if I'm aligning during rearming but I have also seen this when the jet is completely undisturbed so I haven't really found a correlation to what else I'm doing during the cold start.

In my tests I've been doing low level ripples, not dives. Did you try with a lower spacing, like 250ft or so? I'll give the .trk a look. Thanks!

Ok, that's also how I thought it worked but if I set a spacing of about 300ft my full load seems to be distributed over aproximately that length. Am I the only one seeing this?

How I remember it used to work is if you wanted to distribute, say, four ballutes over 1000 feet you'd set the separation to about 250 (1000 / 4 = 250). But now, it seems if I set that separation I'd be covering only about 250 ft in total. Did this change at some point or do I just remember it wrong? The problem is, with the current mechanic, it's not possible to distribute one's whole bomb load over a long (say 3000 feet) runway as the max "FT" setting for ripple is 999.

No idea why but I have major problems getting the FCR to lock, RWS/TWS doesn't matter. As an example: azimuth 6, antenna elevation correct. Track is hot, at 25-40nm, filled in (own radar and others paint it) and very often I even have a filled in white track underneath. But I keep pressing TMS up and it take a lot of them before the FCR actually locks up, and by then I'm way too close for comfort. Is the FCR bugged or is it really that crappy in the real Bk50?

Thanks guys. This is what I was looking for

Some time ago I considered replacing my Warthog flight stick base with a mod that makes it work like in the real Viper; fixed to the center and just reading the pressure applied by the pilot. I'd like to look into that again but I can't find it anywhere. Has anyone got that mod? Any hints on how to find it, or recommendations why I should/shouldn't?

Was practicing buddy lasing yesterday with two squad buddies and I flew a FAC. About 20 mins in, after having lased four or five attacks for the others, the "L" indication on the TGP format page looked a bit "dimmed" and it no longer flashed when I pulled the trigger. Could it be that I had overheated the laser? If so, what's best practice to avoid that? Somewhat related: It seems I can lase through clouds. Is the cloud modelling not blocking lasers yet?

I actually wasn't aware I could go full screen with VR but I'll see if I can figure it out. Thanks!

(I have only seen this in VR so I assume it's not a thing in pancake.) What happens, quite often, is I realize DCS no longer responds to physical buttons (HOTAS and other devices). Axis seems to work fine though. I have a TM Warthog HOTAS and also a SIM GEARS ICP (I'm pretty dedicated to the Viper) and both devices become "numb" when this happens, so it's probably not relating to the hardware itself. What I need to do is quickly ALT+TAB to a different app and then back to DCS. That usually fixes it. Very annoying, especially when you realize nothing's happening when you try engage NWS after landing and the plane becomes unresponsive to rudder input and is starting to skid off to one side, or when you quickly need to work your switchology flow, running in for a ground attack while AAA is whizzing by on all sides. Worth noting is that the "Window is out of focus" message, that usually appears when another window have obtained focus, does not appear in this case (until I actively ALT+TAB, of course). Has anyone else seen this: Is it a bug in DCS or Windows? Any known workarounds (other than ALT+TAB)?

I have managed to resolve my issues. I am no longer running OpenVR/SteamVR at all and it works great!

Agree. Would love some RED cruise missiles, other than the rusty old SCUD.

+1 !!!

If I indeed have a connectivity issue, shouldn't that also affect it when I turn ON Varjo's OpenVR option?

Ok, I must be misunderstanding something. I turned off Varjo's OpenVR support and started DCS with the --force_steam_VR flag. When I started DCS I got this from SteamVR:

No, the cross-eye issue was resolved by --force_steam_VR it seems. Without that flag I had that problem but the debug tool also didn't have any effect. I'll turn off OpenVR in Varjo now and try again. Thanks for helping out! Much appreciated!

Re-read your guide and realized the --force_steam_VR should've been added in the first place. So, re-enabled OpenVR in Varjo Base and reset the DCS binaries to disable OpenComposite's OpenXR support and tried again. The stutters are much better and the double cursors phenomenon is fixed. But I get a very pronounced distortion effect, making the whole experience feel like I'm looking through some fish eye lense. Also, it's still pretty laggy, compared to my G2 experience. Moving my head quickly from side to side produces significant lag. i9-11900K @ 3.50GHz, 32Gb RAM, RTX3080

Ok, disabling OpenVR in Varjo Base and adding "--force_steam_VR" seems to allow me to run in OpenXR (although a bit non-intuitive considering the "--force_steam_VR" flag). This fixes the double cursor problem and the stutters but the overall experience is so laggy I can't play the game at all. Specs: i9-11900K @ 3.50GHz, 32Gb RAM, RTX3080