Notso

Not sure if this is a known issue throughout DCS or just the F-16 module. But I hadn't noticed it with the A-10 or Hornet. I was flying the other night doing some training - takeoff from Creech, some practice weapons delivery on the NTTR and then hitting a tanker before doing some overheads and then a full stop, taxi back at Nellis. All good, no issues. 6 single LGB medium altitude deliveries, about a 69 mile transit to the AAR track, topoff on the tanker, transit back to Nellis to fly the full Hi-ILS 21L approach to a touch-n-go and then a few overhead patterns. Ended the mission and checked the log book..... 33 min total time. NFW!!! I was in the seat without interruption or sim pause for probably closer to 3 hours. 2.5 at a min. Is something wrong with the logbook flight time counter? Anyone else see this?

The CATM-9Ms are not working for me at all. They show in the inventory on the SMS but no functionality. It won't let me step between missiles and I get no seeker tone or any symbology. Do I have to do something to get them to work?

Great info, thanks! You likely just saved me a $900 headache.

I just bought a new computer with the following specs. I know most of the answers are floating around in various threads, but if someone could give me a good starting point for all the VR settings, I would really appreciate it. Its a bit overwhelming to try to sort through all the chaff. CPU: i9-9900K, 3.6ghz, 16MB cache (but seems to be running at 5ghz) GPU: MSI 11GB RTX-2080 Ti Trio RAM: 32GB 3200mhz MB: MSI Z390 GAMING PRO CARBON SSD: 970 Evo Plus 1TB Windows 10 Pro NVIDIA driver 441.41 Steam VR HTC Vive Pro HMD My questions are about the 3 different setting areas: 1. DCS in-game setting 2. Valve Steam VR settings 3. NVIDIA graphics settings I have a pretty decent idea of how to use the DCS in-game settings, but don't know how to set up the others to make sure they are all sync'd correctly. Note, I am NOT a PC genius by any stretch. Especially when it comes to getting into the weeds on digging in Windows directories or editing computer settings, Huge thanks in advance for any help :helpsmilie:

To answer the OP's question - once you go VR, you will never go back. To the further discussion on which headset..... I'm currently running a Vive Pro and it seems to be doing well, although the image quality is slightly lacking, although I don't really have anything to compare to. I just upgraded to a "supercomputer" set up specifically for DCS: i9-9900K, 11GB 2080-Ti, 32gb ram, etc, etc and I'm now looking to upgrade the HMD as well. Of course I would love to get the XTAL, but I'm not sure if I'm ready to spend $7K on it yet. The Reverb sounds interesting but how does it compare to the Pimax 5k or 8K? There doesn't seem to be a lot of Love for the Pimax here so far. Thanks in advance for any suggestions.

Hi all, sorry - very late to the thread. Any updates on the possibility of getting a Mudhen hi-fidelity module? Or is it still just vaporware at this point? TIA.

Great question, as I've been wanting to do the same. A Section or Division (2 or 4 ship) based training scenarios without the LFE type stuff. It would be great to fly on the wing of some seasoned guys or gals here and absorb some knowledge in a fairly controlled learning environment as a way to ease into MP.

Well, of the ones who are still alive, I would say 100% :music_whistling:

That makes sense.

Here is the track file attached this time. The vertical scan seemed to be behaving much better. And the HMCS Bore was working with the exception of if you looked away from the target, commanded bore with TMS fwd and then looked back over to the target with the helmet oval, it would not lock unless you then TMS'd fwd again. However, if it was already over the tgt, and TMS fwd it would lock right away. Not sure if this is a bug or how the viper is actually mechanized. HMCS Bore-vert scan.trk

There already is a rounds remaining counter on the SMS MFD. At least it is there in Strafe mode. I haven't looked closely yet in A/A guns.

I'm getting a very distinct pull to the right side of the runway always on takeoff. I do disengaged NWS steering around 50-60kts, but I find I still need quite a bit of rudder to keep the jet in the middle of the runway until liftoff. It almost like taking off with a big prop motor with lots of torque. A single engine centerline thrust jet should not be veering off the runway so quickly with no rudder inputs. I can't imagine the real F-16 behaves this way.

This is pretty much what I do as well..... gear+flaps while still in the turn to downwind once below 250Kts. Porpoising is fairly minimal at that point and then trim for on speed AOA. The finesse comes with throttle management when you enter the base turn and then roll out on final. I find I have to lead the turn with a little bit of throttle to maintain speed and AOA due to the bank angle and then pull throttle slightly before rolling out on final. I find if I don't lead both - I then chase the AOA all the way to the wire.

What I've seen from my very limited experience on DCS is that joining up with the tanker when its been set to an AAR task in the mission editor is key. It if it just flying between waypoints, I see it doing some pretty drastic turns when it gets to a turn point. But if its on an AAR task, it seems to settle down and never bank more than 10-20 deg or so. In fact, most of the time - it seems once i have made contact with the tanker to say I intend to refuel, it goes into a lazy 360 deg turn and stays in the constant turn until I'm done. Maybe I'm just not setting the AAR track up correctly.

No, in theory - all you're doing is flying formation with the tanker. No different than if you're flying fingertip formation with someone else. A flight lead is not going to call every turn. As long as the turn is smooth and relatively slow (i.e. std rate) - should be no issue. I do find the AI DCS KC-135s do tend to turn a bit abruptly at times. But so far, I've not had any trouble staying on the boom in a turn.

That would actually be really cool!

Nope, most turns are comm out usually. A good tanker pilot MAY give a courtesy call prior to a turn, especially if turning at a non-standard time such as to deviate to avoid weather or if IMC in the clouds to help out the guy on the boom. But turn calls are not SOP or required.

Yeah, that would be a REALLY LONG and REALLY high altitude runway. 7842 m would be almost a 26,000ft runway at 5000ft MSL.

Its not so much that the GBU-12s can't see through the clouds (they can't) but its that the laser won't penetrate the clouds and therefore the bomb won't see the laser spot once they are below the clouds. The main principle that a lot of people don't understand about LGBs is that the bomb is NOT following the laser beam itself. It is only seeing the reflected spot on the ground and guides to that spot. The beam itself is irrelevant to the bomb. But if the A/C is above the clouds, even thin wispy clouds, the laser will not penetrate that and instead will be reflecting off the top fo the clouds. Or more importantly is being diffused by the clouds. In any case, the laser will never be on target on the ground, so therefore your GBU-12 will never see it and therefore never guide. The only way to fix this is to (A): release below the clouds (B): Have someone on the ground designate the target with a laser (i.e. a JTAC) © or have a wingman below the clouds to buddy lase the bomb. A GBU12/10 can be released above a cloud deck with no problem as long as it has sufficient lase time once it pops through the bottom of the cloud deck (usually 8-10 sec) and there is a laser spot on the correct code illuminating the target for it to see once it pops out of the clouds. It just takes some extra coordination. As someone said, better to use JDAM / GBU-38s instead if you know there is a cloud deck and you can't operate below the clouds due to terrain or threats.

I was not able to get the 26R ILS to work at McCarran (LAS) either - I was using the info from the kneeboard approach plate. It works fine at Nellis (LVS) though.

[MISSING TRACKS] STT & ACM Boresight and Vertical Scan acting strange So I was playing with some of the Radar modes last night and ran across a few weird things. Not sure if they are bugs or user error. See attached track. 1. I was doing a stern conversion intercept on an IL-76 from below. I got a radar lock on him in the beam at about 10nm lookup. The radar was having trouble keeping lock and kept drifting off in the stern and sometimes losing the lock or going back and forth behind. The radar shouldn't have had any trouble keeping lock in the beam or in a stern chase from a lookup at close range. 2. I was experimenting with the ACM modes using both Boresight and Vertical scan. The boresight mode initially seemed to work OK, but the vertical scan would not lock the target hardly ever and I should have been well within parameters. I was at 6 oclock to the target at about 2-3nm. It was intermittent at best. And at other times it would lock in Vert scan when the lift vector was NOT on the target -which is the opposite of what should happen. 3. I then switched the HMCS on and tried the same test. Vert scan was still very intermittent still. But occasionally even Bore would not lock when the nose was pointed at the aircraft -i.e. I was not looking off boresight. When I would use the HMCS Bore to lock the target when it was off the nose, it worked fine. I was also still seeing the vert scan and boresight mode lock the target when I was not in what I would consider the correct parameters such as the lift vector was not on the target in vert scan or I was not looking at the target with the HMCS circle and sometimes it would lock anyway. 4. Another final thing I wondered about the mechanization of the ACM modes...... If I had a lock and then TMS'd aft to break lock.... shouldn't the radar lock the target again if it sees it, or do I have to always go TMS forward to relock each time? Also when using the HMCS, If I was looking off to the side of the nose at the target in ACM boresight and put the oval over the target, the radar would lock. If I TMS'd aft to break lock, it would relock if I was still looking at it. However, if I broke lock, looked away and then put the oval back over it, it would not automatically lock the target again unless I TMS'd fwd to command the lock. Is this all normal behavior?? Thanks. Edit: Doh, the track file is too big. I'll have to rerun it and shorted the time down. Sorry, standby for that track file..

Yep. I could never go backwards after having flown with VR. I can live with the slightly degraded graphics quality for the HUGE leap forward in immersive quality. And VR is just going to keep getting better. I have the Vive Pro and Warthog stick and throttle and it's an awesome setup. I'm thinking about adding MPDs as well now.

100% concur! There's far too many variables to staying on the boom (or in the basket) for a single speed to be set. And all of that is even assuming the tanker itself is able to maintain an absolute precise airspeed. Maybe in DCS it can and does because its an AI entity. But IRL, that's rarely the case. If formation flying was a strictly 1-dimensional event (i.e. Fwd/aft), then ATC might work. But the up/down - L/R thing also usually involves small speed changes when one of the other parameters needs adjusting. Especially if the tanker enters a turn while hooked up.

True, but the Nav pod did have its uses when the Low Light vis or other factors made the NODs less effective. The NODs were far superior in most cases, but there were a few scenarios where the NAV/FLIR pod good to have.

The brakes and stopping distance seem fine to me.