Sandman1330

Interesting Reddit thread (for what that source is worth) that indicates a first week in May release (I guess this week?)

Flying on NVG, we position the goggles such that we can see underneath them simply by moving the eye. They don’t sit right against the eyes, one can look around them. You then look through the goggles at the outside, and under/around them to see the instruments. Think of having 2 toilet paper tubes about an inch from your eyes, you can still see around them. DCS doesn’t allow this in VR, as the goggle takes up your entire field of view. It’s been requested before to have it only take the center of your view to allow us to look around them, but not yet implemented.

In the aircraft I fly, we have a small attachment that goes on the right tube of the NVG that provides a HUD in the NVG (it’s a little screen that goes in front of the tube). It’s not positionally tracked like the JHMCS, it just provides flight information, but it shows that you can display information in the NVG. I don’t imagine it to be too much of a stretch to make it positionally aware and provide the same functionality of a JHMCS. I have no real hornet specific info to back this up though.

The RWR can still get indications off of sidelobe, just at reduced ranges - much like the flashlight analogy. You won’t see him as far out if the flashlight is pointed away. Maybe consider it as one of those more focussed mag lights with a narrow strong beam... No analogy is perfect but this is pretty close.

It wasn’t as bad last time I tried it, in open beta. I also take less time than before to hook up, so not sure if it’s related to that...

Think of a radar as a flashlight in a dark room. If I’m hiding in the dark, I am going to see that dude’s flashlight long before he is close enough to see me with it. I am also going to see it from the side, when it is not even pointed towards me. Therefore, your radar alerts others to your presence well before you see them on your radar scope.

I asked yesterday at the Microsoft store about the Reverb... the salesperson had never heard of it. I know first gen WMR were sold there, so I’m left wondering if the business focus of this headset will make it hard to get ahold of.

I’m curious what the real life SOP is? A 2G level turn requires 60 degrees of bank. This seems rather extreme for a tanker, indeed I have to wonder if a KC135 could even maintain a 60 and 2 without bleeding speed and/or altitude? Maybe a bit faster could be called for, especially if no one is plugged in, but a 2G turn is probably a bit excessive :smilewink:

Crazy level of detail, eh?

This. Look at your G meter in the photo: your max G is pegged at 10, which is as high as the gauge goes so potentially even higher. The Tomcat is older tech, so aside from not having FBW to ensure you remain within the aircraft’s 7.5G safe limit (6.5 in peacetime), it also has mechanical spinning gyros rather than newer solid state sensors that provide the attitude data. At high G, these spinning gyros get damaged and provide incorrect attitude information. This is what you are seeing. The next step if you pull a bit more G is you lose your wings. I know, I’ve been there :)

Haha, I apologize but I don’t follow: are you agreeing or disagreeing with me? I myself have only used a CV1, and I know it compares very poorly with my small 1080 monitor, but no doubt the newer generation headsets like the 5K+ are a real boost

Haha I think the Tomcat happened....

Upon more thought and a review of the manual, I believe jester losing targets in TWS after missile launch is probably more related to the fact TWS Auto is not implemented yet. Auto mode is required after launch and is supposed to modify scan volume and azimuth to keep the targets illuminated. Without this system implemented yet, the RIO must do it manually, which isn’t realistic anyway and Jester isn’t up to the task (I think it would be tough for a human RIO to do while ownship and targets are both manoeuvring)

Hahaha that about sums it up

Yup. Phoenixes rarely hit for me because Jester loses track after I've fired them and the missile goes stupid. Tried the Kish Kat attack mission today and lost all my Phoenixes from well within optimal range (the thicker bar on the velocity vector on TID). Then you try sparrows, and they bite off on enemy chaff right away, leaving you dodging the AI missiles - oh, and those things don't seem fooled by any amount of chaff, you have to aerodynamically defeat them. AI wingmen are still useless... Very frustrating to try and play that mission alone and with one hand tied behind your back.

Are you disabling roll SAS for dogfighting? When on, it greatly increases instability at high AOA. Turn if off for dogfights.

You make solid points about DCS vs reality. However, I would argue that it’s not necessarily a valid comparison, as this is still a game of sorts and everything is relative. Right now as a CV1 user, I am at a spotting disadvantage against other players online who use higher resolution monitors, and we are all at a massive disadvantage against the all seeing AI. I can live with the disadvantage against monitor users, as the situational awareness in a dogfight using VR easily levels the field. However, if we are to accept spotting that is close to reality as you rightfully argue, our main enemy - the AI - needs to be brought to the same level.

Yeah, after more testing they work pretty good up close, within 3-5 miles. However, this is supposed to be a BVR missile, I’d expect decent performance at 10 miles at least in a head-on situation. Part of the problem may be that Jester seems to switch from P-STT to PD-STT while the missile is guiding, I think this trashes the missile. They also seem to be too sensitive to chaff.

Oh man, are they ever... They just don't track. Even if I keep lock throughout, range 5-10 miles in trail, they don't even guide, just go stupid.

Same. I can remote in from any computer, including the server computer, via the DCS webpage - but the local webgui index.html does not connect.

Brownout is a real thing and is extremely dangerous. 2 of 3 Canadian helicopters that crashed in Afghanistan were due to brownout rather than enemy fire. The DCS brownout effect is very under-simulated. In the desert maps it should be so thick as to block all visibility outside 10ft or so by the time you slow below TL on approach.

This is fixed in the current open beta.

Confirmed, and previously reported some time ago. The work around is to switch to guns, then back to Aim-9 or whatever other mode you are using. You can tell when it's not working because the PRF selection disappears from the left side of the radar DDI (when it works, you get the HI/MED/INTL option, but this option is missing when the bug is present)

+1

Sure! Because the cyclic has no centering force, you have to hold it -all the frickin time-! Otherwise it will literally flop to one side due to its own weight. Think of a joystick that has no spring, it will topple to one side. The force trim system IRL is simply a system of magnetic brakes (in most cases) that holds the stick in whatever position it is in. A button on the cyclic releases the brake, so whenever you move the cyclic, the button needs to be depressed. Releasing the button engages the brake and holds the cyclic in the new position. After long missions with lots of hovering, my thumb can literally get numb from holding the button down the whole mission (the system can be turned off, but we rarely do for safety reasons). For more stable regimes of flight such as cruise, with force trim engaged you can let go of the cyclic without it flopping over. Not all helos have a force trim system, but most of the medium to large ones do. I suppose calling it trim can cause confusion, as it doesn’t work like we would expect based on the fixed wing usage of the word...