frostycab

You can just hit IDENT(L1) on the TSD to clear what you've already entered and accepted, then start over. Alternatively, below ADD there is an edit function, so you can just complete the point with the error and then edit it to be right afterwards. The sequence is ADD(L2) - HZ(L4) - IDENT(L1). EDIT: I just re-read what you said and was wondering if you typed "HZ" into the KEU when it first asked for the identifier. If so then it probably flashed twice when you hit ENTER and didn't progress to the FREE entry page, since HZ is point type and not an identifier. Check the manual pages 347-348 for the valid HZ identifiers. They're the ones in yellow. You can also look up all the identifiers by pressing ABR at T4 on the main TSD page. By default, not all point types show up in the TSD. To enable them, Go to SHOW(T3) and then on the left side you will see various options boxed. Also, once you're in SHOW, you can select THREAT SHOW(T5) and COORD SHOW(T6) for even more options. In the COORD SHOW it's normally the "Enemy Units" that hides most of the points that people are expecting to see. Don't forget the TSD has 2 modes too, NAV and ATK. To swap them over hit PHASE(B2). You can have different points visible in each phase, so set them up however you like. Being lazy, for now I just enable them all in the NAV phase to save swapping. When you're finished, hit SHOW again to exit back to the normal TSD.

Just sent you a PM

100% agree! Just look at the Viper. It just recently had an update to it's flight model that radically changed the way it performs and how you can best use it tactically, and it's been out for how long now?

Glad you're feeling more confident with it today. My offer is always open, and don't worry about talking much. I'm not exactly much of a chatterbox with new people myself. I also fly much, much worse when I know somebody is watching! LOL

I've flown airliners in flight sims for many years, and I've heard of many company SOPs stating that the downwind engine would normally be started first. If memory serves me, on aircraft such as the 737 it's also common to alternate which igniters are used.

Casmo has talked about this on his streams. AUX tank is off by default, and there's no hard-and-fast rule that anyone he knew stuck to regarding when to turn it on. He said a lot of the guys would turn on their AUX tanks after about 30 minutes of flight.

Do you know which mission it was? I can have a quick look and see if it's one I recognise. I know the kneeboard for the SCUD Hunt mission had a couple of extra points on it that the creator just forgot to erase. It was reported and acknowledged, so might have been sorted in the hotfix. EDIT: Just a little "good practice" thing that I do is always compare the KEU altitude entry that pops up to the one on the kneeboard. If it doesn't match then it's a good sign that you've got the wrong grid and need to check.

Yep. The ground effect seems to increase very rapidly from 10ft down to 0, much more noticably than in the other helis. If I leave the collective alone she'll yo-yo from 2ft and go back up to around 15 before dropping again, so you definitely need to learn how to finesse it. You need a good feel for the collective in this lady..

Do me a favour if you've got DCS running. Load up the Caucuses cold start mission from the instant action menu and look at the kneeboard points. You'll see that most of the grids start with GG, but a couple start with KM. The fact that there's such a big difference in these codes is a massive clue that your flight is going to cross into the next 1000km grid, which could explain your problem. Open the F10 map and make sure you have MGRS as your coordinate system. (LeftALT-Y in case you don't know how to cycle it.) Now put the cursor over your heli and look at the grid reference. It should start with "38T KM." 38T is the 1000km grid square. Now point the cursor at the coast West of you and read the coordinates. It should now say "37T GG" which is in the next grid. If you then enter the coordinates into your TSD using the appropriate major grid at the start you should hopefully get the right results. It's purely down to the kneeboards only giving you most, but not all, of the full MGRS data. It's something you need to watch out for, and familiarity with the local area will help you to recognise it in the future. Let me know if that solves your issue or if I've misunderstood..

OK. Break it down a bit for me. Is this on one of the included missions? if so, which one? There are numerous errors on some of the kneeboards.

This could be referring to the range that's displayed to the left of the Field Of Regard display, which I think shows "NX.X" when you have a point set as your ACQ. Could well be wrong about this, as it's late and I need to sleep soon.

Short answer: It's done by setting the appropriate ACQ source. *I think* that from the CPG seat Laser would apply when using the TADS as your sight AND firing the laser. Navigation would be ACQ - ?00 for a TSD point. AUTO and Manual apply when aiming the gun using the HMD. *I think...* I've got both, tried both. I just prefer VR. It doesn't help much in terms of keeping your LOS on the target. Maybe I need medical attention or something, but when trying to make adjustments for just a few pixels left or right it's as though the muscles in my neck all lock up and I find my view juddering slightly as I try to get the fine control I need. It's a bit like trying to move your eyes slowly, in that it just can't be done. You always end up snapping a bit too far one way and then snapping back to correct.

I agree. Got my first Virpil unit 2 days ago, a shiny new CM3 throttle. It takes some getting used to after 5 years of using a Warthog, but the extra buttons/hats/etc make it much more versatile for a variety of aircraft. I used to struggle to work out how best to bind things for some planes on the 'Hog. Still using the Warthog base and grip, though when money allows I'll probably make a Virpil base then next purchase. As for pedals, I replaced my very old Saitek Pro Flight rudder pedals last year with a lovely Thrustmaster TPR Pendular system. It's so hard to describe the difference though. The pendular design feels so much nicer than the old "slide" action, and they're smooth as butter with customisation for resistance and ergonomics and a huge range of motion from stop to stop. Bloody expensive, but then I thought the same about my Warthog when I got it. Worth every penny though. It'd be interesting to compare our bindings sometime!

It shouldn't. Doppler systems rely on changes in frequency in the signals they emit relative to what they send out. If the aircraft is stationary then there would be no doppler shift. I was told that it's used to aid in making corrections for INU drift over time/distance. (That's my recollection anyway, but I'm getting sleepy now. LOL)

Interesting. What map was that on? I timed it on the Caucuses map and got 3:55 from APU ON light. I wonder if they've modelled the Earth's rotation into the alignment, as I understand that it can take longer depending on your latitude in some civilian aircraft.

Shouldn't need any translation in most cases if you've set your units to MGRS in the map view. It's a nice idea, but not sure how they'd implement it in practice. The F10 coordinates would have to be truncated to conform to the 8 digit format in the Apache. Perhaps they might bring a data cartridge system like the Viggen has, where you can have a "personal" cartridge loaded with points from dropping markers in F10.

Having flown GA planes for years in FSX I’m glad I have them. I couldn’t ever go back to flying with a twist grip stick. Everything going wonky every time I need to let go to use the mouse would drive me nuts. IMO they’re a must have for helicopter immersion.

I agree, the PNVS is nowhere near as smooth as the image you see when switching over to NVGs. I don't know if this is accurate to the real thing or not, as it could conceivably just be a limitation within the real hardware/software. (I'd be surprised if it was though. It's not like the US military is scared of spending money to get rid of issues like this. )

No problem. My offer of a multiplayer flight still stands. It might be the simplest way to sort things out.

I've struggled with flickering due to props and rotors interacting with things like projected gunsights in warbirds (and the IHADSS in the Apache) for ages, even since the supposed fixed were made. I finally managed to sort it out today. If your using Steam VR, go into your settings and on the General page check to see if Motion Smoothing is on. Mine was, and as soon as I turned it off all the flickering in DCS disappeared. It's completely changed my VR experience, so worth checking.

And did you?

If you're firing the gun to the left or the right of the aircraft while flying forward then you do need to adjust your aim slightly aft of the target as the rounds already have some forward inertia as they leave the gun. More forward speed means + more angle off your direction of flight means you need to compensate more. I fly almost exclusively in VR, and appreciate there are differences between that and using TrackIR. What helped me though was to do my best to ignore the I-Beam as much as possible and keep focussed on the target. At first I found myself "chasing" the I-Beam with my head, then realising what I was doing before doing it wrong again and again and again. Now I try to keep my LOS on the target and just try to be aware of which side the I-Beam is on. I then fly the helicopter in the other direction until it I-Beam crosses my LOS. It's totally counter-intuitive, and your brain tries to force you to move your view to get them to line up. You just need to get over that and force yourself to do it the other way, rather like flying with the PNVS and trying to ignore the wrong visual cues your other eye might give you.

On the TSD, go to UTIL at T6. You will see the 2 INUs in the top box. They start out white, but turn green when confidence is high enough.

Thanks. I think I will start a thread on that later today or tomorrow. Your picture helped me with a test using the mcp_CanopyOpen flag. I didn't realise that you needed 2 entries for each flag, though I'm not sure why yet. LOL Defo going to need help though, as my parameters list on the left panel looks nothing like yours and bears very little resemblance to anything on the aircraft. I'll @ you in the thread when I've written something meaningful.