Majik

Yep, that's how it works by default in both the Hornet and Viper now. It's one or the other, not both, and interchangable by asking the crew chief only (or setting in the mission editor).

You nailed it as far as I'm concerned, I really think that these would be the perfect steps. Although highly unlikely, a Block 50/52+ on the other side would also round out the lineup nicely.

I don't think trigger zoom works in vr, does it? At least I haven't been able to get it working in the past.. A global option for both zooms would be the absolute ideal, hence why I suggested H4 as it already works so perfectly in some modules. I can't stress enough how much both levels are essential to us. The way I have my UI layer bound, S3+H3U/D ends up being being used for both zoom options in the C-101 anyway. It isn't the most comfortable to reach for, but would certainly welcomed as a global binding if you could swing it. I did think for a moment vr zoom on 1st stage trigger and spyglass on S1 could work as another global option, but you wouldn't always want zoom at the first detent (eg Viper lasing, F-5 gun port doors, or every single guns shot), and having to fiddle with toggling trigger zoom on or off (as the only option for that level of zoom) wouldn't be ideal either. That's absolutlely fair, I can see exactly why you've set it as such, and why you're trying to stay away from shifted commands for it. Do you get many vr users asking for hold? (genuine question, not trying to be facetious) Personally, I have a very strong stomach for vr, and yet anything but a momentary binding that I could release in an instant for zoom could make me vr sick. It's why I never could use the trim hat zoom, aside from the binding being clunky to use for me. Again, that's fair. Any consideration for us vr users is appreciated, and apologies if I'm causing you any headaches trying work this around; your profile is the reason I'm into DCS, I don't think I'd be able to set or remember anything if I were left to my own devices. I put off flying the sim for the longest time because the complications of binding everything daunted me (didn't know what half the stuff was even for).

Great to hear NL. The real number definitely is out there in public, and doesn't seem classified. Can't remember which episode of the FPP (or FB livestream), but the Charlie Hornet's AOA number was given (I forget exactly, but somewhere around 35°, and controllable even higher with roll rate being affected). I remember being surprised by that more than the number distinctly because there was a moment of "wait, can we talk about this? Oh we can..", and how that was seemingly different to what the Wags' interview suggested. Edit: found it

S1 doesn't easily allow for zoom during/just before pulling the trigger. Often some zoom is needed when using the gun to see what you're shooting at (especially ground targets) even on a monitor, let alone VR. Thumb is already on/near H4, so quickly using zoom, even momentarily, is easy as can be, and trigger finger stays where it is ready past the first detent. I understand that this is similar to the VR trim 0 mouse issue though, and may be an individual case. Personally, I've never used the trim hat mouse or zoom options; both are/were too unwieldy for me. Secondly, and this is entriely an opinion; I believe if something is mapped to a hotas is the real jet, then it is an important control, and should be accessible without a shifted function whenever possible. It's true they don't usually require much manipulation or sustained hold, but having say, the MSL step button on the Viper actually step stations or change between fox2 and fox3s in DGFT mode, often under a stressful situation, is important without the extra step. This is also why VR Trim is set non-shifted for me; trim is very important and constant on some planes. Thirdly, and this is the single most important reason, which isn't an opinion; a hat allows both VR and Spyglass zoom to be used independently. Having both levels accessible is essential for inside and outside cockpit. S1 alone is not sufficient. Using a single hat for both vr zooms as well as rudder trim, as is the case on the Jeff and Hornet (and as I've modded onto other modules) keeps things easily accessible and neatly contained also.

Is there anything I can do to convince you to continue with with S3+H4U/D as the standard VR zoom for 3.0? :cry: Personally, I've been remapping S1 back to normal in the last few updates, and going with the above as my default (or S3+CSU/D depending on module, eg Viper). It works for now, but am concerned 3.0 might change all this...

I've not noticed any problems/disparity with aircraft lod in stereo culling; have been spotting near and far with zero problems so far. Perhaps it's something I've overlooked (:smartass:), I'll keep an eye out for any issue though, and see if I can replicate what you're seeing.

Even though it's a WIP, I've been using the stero-parser/frustrum culling option for a good few weeks now, and it has completely solved this issue for me. Shadows, clouds, and smoke etc appear in both eyes. The option does have its downsides though; flood lights currently appear in right eye only, clouds can pop in and out at the edges (much, much better than popping in the middle of the screen in one eye though), and water has some glitches occassionally. ED do seem to be working through these issues, as the carrier crew no longer appears in one eye only with this turned on. The trade-off has been more than worth it for me, and performance is improved also. Might not work for you, but worth a shot.

Can confirm, also experiencing this. I've had the F10 crash happen a few times now, including once tonight. Also had two crashes mid air tonight. All on Syria in busy MP servers.

I wouldn't say the adjustment is in the wrong direction for VR; it definitely helps with low light conditions. That being said, the upper end definitely needs to be able go much brighter. A wider range is the best solution for all conditions and setups.

After I had issues with the steerpoints with Mavericks, I switched to a CAP loadout and didn't notice any issues with the TGP in A-A mode. Haven't yet tried TGP in A-G without Mavericks since the patch dropped though, so still could very well be a TGP issue. Powering off the Mavericks did fix the issue for me though, and I didn't store the TGP.

Confimed same issue on Syria TTI. Powering off mavs on the SMS page eventually returned correct steerpoint info.

Have had this happen with Mavs powered on. HSD shows correct steerpoints, but the hud sherm is pointing nowhere near where it should, and the distance to waypoint information looks like I'm being hacked. Powering off all mavs eventually returned the sherm to where it should be pointing.

DMS up makes HUD SOI

Absolutely agree. It's a work around I discovered by accident, but a useful one sometimes :smilewink: Wish we had the newer EGI

Very helpful, thank you for making this!

If you do a stored align, switch to nav, then back to norm, you can get down to / 6 (much, much quicker)

If a reasonably effective representation of the AN/ALQ-184 can be made, then this conversation will become moot.

Opposite of keybinds; Can we get clickable mirrors please? Not easy to reach for the keyboard key in VR

Okay, so going to stable and then back the open beta has completely fixed this issue, as well as a few others. Looks like the Syria update last week was somehow corrupted for me.

It's all good brother.

Perfect, found them. Thanks! Huh, I could have sworn it was MSD in the Viper, and S3+MSD in the Hornet. I must be getting old. :joystick: Anyway they work fine so no big deal, thought I'd screwed up something digging around somewhere I shouldn't have been. Digging around did get me to figure out that AI RIO was set to 0 in values for some unknown reason though, and now that I have it back on, all is well. Looking forward to you working you magic in CTS 3.0!! Ah yes, sorry, should have stated; yes I'm using a Warthog Throttle. I have both VAICOM and SRS running for MP, and VAICOM for all SP. Single PTT appears in both scenarios, with the MAP dial set to NORM (my usual setting) or SNGL, and no PTTs appear on MULTI or INV. Easy Communications are off.

Is S1 the first stage trigger? I had a brief play with the F-14 to test out, and couldn't figure out the new zoom. Is there somewhere in the references that lists the names of the buttons as you use them? I've had a look, but couldn't find anything. What little I know is from the profile JPGs, and has been inferred from other parts of the references. BTW, S3+ H4U and H4D mapped still work great for VR zoom in the F-14 (but I've already made my opinion clear on that :D) For me, H1U zoom wasn't practical in the slightest, so no problems seeing it go. Also, I don't know how others feel, but I'm not sure a hold function is needed, or even a good idea in VR because it may cause motion sickness. If it doesn't affect the dx limit, then by all means keep it in. Secondly, I'm not sure if it's something on my end, or on Vaicom, but the bindings seem to have changed. On the F-16 and F/A-18, intercom is now S3+MSU. MSD in the F-14 hot toggles the Jester squelch sound, but he doesn't hear commands (they work fine on S3+MSD though). Don't have discrete ICS on. I think this might have always been the case, but for the JF-17, Vaicom only sees comm 1 on any mode. I understand that comm 2 is largely used for D/L so no huge loss, but not having an intercom isn't ideal for MP. Also the dobber switch doesn't seem to work in the jet (enabled in values). BTW, thanks for the F-5 updates! :beer:

There's a link to a track in the first post

I appreciate you taking the time to have a look, thanks! :beer: The mystery continues. Agree on the Viper flow being much nicer to work with for me also! I dropped some more GBUs today, hoping it was computer gremlins or something... I don't know why I expected any different. I also tested unguided CCRP, which works as expected, but did have a couple of odd things happen; on one drop the cue didn't fall, but at zero seconds, jumped straight to the FPM, and another was that the bomb dropped as soon as I pressed the pickle button at about seven seconds as the cue was falling. The latter happened to me yesterday in the JF-17 also.