frostycab

OK, I've got 2 tracks for you, one long one in the Apache, and a shorter on in the Huey for comparison. On the Apache track you can see that there's very little cyclic deflection needed to maintain stable flight at 40-60 knots, though the deflection require does increase significantly around 80 or 90. Above 100 the deflection required increases dramatically. At low speeds there was some pitch up motion when releasing the cyclic back to center, but nothing dramatic. At high speeds I got the expected "reach for the sky" effect, again as expected. Towards the end of the flight I tried a few more times with and without ATT hold mode engaged, as I don't normally use it right now and thought I'd see how it affected things. It did actually manage to correct the low-speed pitch increase within a couple of seconds of stick release, and returned pretty much to where I'd have wanted it. (I'm not sure if it's something you need to turn off and on again when you want to settle at a different speed/attitude, so best to check with one of the SMEs for that.) You On the Huey track you can see that it pretty much exhibits the same behaviour, being relatively stable below 70 knots, but if you push the speed up then you get a bigger reaction when you center the cyclic. How does this compare to what you're seeing when you fly? Can you maybe get us a track to look at? P.S. Please forgive the slovenly standard of direction control in my tracks. There was a cat that thought my rudder pedals looked particularly comfortable and decide to defend it's new-found napping zone. I do not own a cat, so this was very hard to get my head (and feet) around. pitch test UH-1H.trk pitch test.trk EDIT: Another thing just occurred to me. Taking your original post as an example, you say you get a huge pitching up motion if you return the cyclic to the center. What are you doing with your collective when this happens? I just did a quick flight and noticed something that I seem to do naturally. I start to dump collective just before I ease back on the cyclic. Not doing so does induce a massive pitch up motion, but if I start to drop the collective first and then ease back on the cyclic as a countermotion using the flight path vector as a reference then the pitching is fairly easy to control. Afraid it was about a 20 minute flight and you can only really notice it at the end so I didn't bother saving the track but next time out I'll try to do a short demo to see if that might be what's happening. I should add that everything I've said in this thread is stuff I'd say if advising someone who's not overly familiar with flying helis in DCS. For all I know you may be a total rotorhead, so forgive me if any of these suggestions sound condescending. I have no measure of your level of experience to go on, so I write as if I'm dealing with someone who's a bit new to it.

Give me 15 minutes and I'll do a flight and upload a track.

I can pretty much tick all the boxes on that list! Perhaps I'll try to catch you on Discord in the near future if you have time to walk an idiot through things. Have you got a pre-written walkthrough anywhere?

That looks much cleaner and a lot less "Atari 2600"

Already reported a few times. NineLine has confirmed tthat it has been fixed but didn't make it in time for the recent hotfix. Expect it to be in the next one. From NineLine: "Ok, it was fixed internally but didnt get merged for the hotfix. Sorry guys. Work around that works for me is that when you start engine two, slowly bring the throttles up as the engine spools and it seems to catch. "

Don't apologise. You asked for help and we're trying to give it, but to do that we need to understand the "why it's happening part." Without actually seeing it the problem is very hard to diagnose. I've done my best in the above post, but you're saying that's not the issue, so we just need to look at other possibilities. You say this is happening at in the 60-90 knot range. Is your stab trim in AUTO? I know it reverts to AUTO above 80 knots regardless, but if for some reason it's in a nose-up trim then that could be causing issues. EDIT: Had another though. Have you been into the axis bindings and confirmed that nothing went out of whack with the last update? I'm thinking a conflict on your pitch axis with another physical axis. It's a slim chance, but it's happened to me in the past.

I did find this yesterday, but I can't work out how to use it. Seems to read (some) of the data when I tried with the Hornet, but no idea how to make it output anything to the LEDs https://forum.virpil.com/index.php?/topic/2561-vpc-link-tool/ I just found this as well, so going to have a look in a bit. It'll probably be beyond my skill level though. I'm still struggling to make sense of how to get which button to light up when, let alone get external signals.

FLT page - SET. Ensure RAD ALT is on. (R5 I think) Is off by default in cold starts. Does not come on immediately, so give it 20 seconds or so to warm up. If that sorts it out for you then please remember to mark this as SOLVED so the guys at ED don't get snowed under.

I'm loving the throttle regardless, though the software makes TARGET look simple. Currently trying to work out if there's some way of changing the RGB on the button based on flags in DCS like you can do with the Streamdeck, but I don't really understand any of this stuff.

Yes. In the PLT seat all you need to to is select TADS as your ACQ. TSD or WPN page, R6 (ACQ) and then B6 (TADS). The CLOSR on the IHADSS will then show George's locked target. If you want video of the target as well then open the VIDEO page and select TADS on the right (R1 if I remember correctly.) You can then press TADS at T6 to hide the menus and get the TADS video on that MFD.

Then I don't understand why you're hooning around at 135 knots. These pictures show my controls at speeds of 135kt (to compare with yours), 90kt and 60kt. All were in fairly stable level flight using the aircraft configuration from the Caucuses Runway Start instant action mission. As you can see, at lower speeds you need very little cyclic input to keep things stable, but cyclic deflection seems to increase exponentially at higher speeds. Even if I'm in a rush I won't push her past around 115 to 120kt. Also take note of the engine torque. At high speed you really have to rag it, but ease off a bit and it comes back to a comfortable low to mid range. If you want to jump into MP sometime and we can see what you're doing wrong in real time then let me know, but I suspect it's just a case of needing some more practice and perhaps a bit of guidance. Let me know.

Are you referring to the red 2-way toggles on the CM3 throttle? They're actually ON-ON switches as opposed to ON-OFF, so I've got them configured as 2 different logical buttons. I only got the throttle on Thursday, but I wish I'd known about your great solution when I was still using my Warthog. The ON-OFF configuration was so annoying when there was no way to easily circumvent it.

There's a thread about this in the Missions subsection already. The creator has said that the last 2 MGRS points are a mistake due to not clearing the kneeboard properly while he was editing. Also mentioned that kneeboard has been fixed so might have been pushed out in the recent hotfix if it made it in time. If not then I'd expect it in the next one.

I'm sure I read somewhere that LST was WIP and not implemented yet.

The VIDEO page doesn't allow you to set your ACQ. To the best of my knowledge it's merely a sight. ACQ, as far as I know, must be set on either the WPN or TSD pages in order for the Cued Line Of Sight reticule to show the desired ACQ point in the IHADSS.

UK here, so usually shop from Amazon or Scan. Amazon have been ok most of the time, but I did buy a hard drive from them last year, that was DOA. Returned for a replacement which sounded like a train when it spooled up. Despite trying to get a refund they forced me to go down the route of contacting Samsung directly first, and I'm so glad I did. Gave Samsung the serial number for the drive and it turned out it was out of warranty when I got it AND it turned out it was an OEM unit that had originally been sold in a games console. Got my refund from Amazon, but it left a bad taste. It was one of those "Fulfilled by Amazon" items, so not directly sold by them. Still dodgy though.

Quick question before I spend hours on this: Is anything in this thread relevant to owners of the Valve Index? WMR doesn't recognise it, so I'm guessing that it's probably futile if I try to use this OpenXR thingy. Am I right?

I've noticed this too, with the stored point usually being several meters in front of the actual target, though I can kind of rationalise it in my head if I try: The MGRS accuracy with 8 digits total gives you a square of 10m by 10m, so I would assume that when you lase and store a target point it's recorded in the database using that same level of accuracy. Thus, when you slave back to that target it's entirely feasible for the stored point to be anything up to 10m away from the actual point you lased. (Actually, up to 14m away if you allow for 10m in 2 directions.) That's fairly consistent with the offset I've seen when slaving back to a point, and that's not factoring in that the aircraft itself only knows where it is down to a few meters most of the time. If you compound the 2 then it all makes sense (to me.) In any case, slaving to a target point usually puts me pretty close to the intended target. Close enough to make adjustments and shoot, anyway. I'd be amazed if the real system was flawless.

Sorry, it might be the way I worded it. I regard conversion and installation the same way. To my way of thinking by converting you're effectively installing the other version over the top of the existing one.

In VR, the IHADSS monocle smoothly animates out of the way when you turn it off, but if you turn it back on it just snaps into place in front of your eye. Small detail that doesn't matter much, but thought I'd mention it.

Oh? When I installed OB I seem to remember it only asking for a new installation directory, not an option to swap over. Then again I'm getting old now and my memory is bad. I *think* for Steam you just right click on DCS, select properties and tell it to use the beta version, but not done it myself so best to check.

Thanks, but I'd say Raptor9 gave the best answer. Give him the credit.

I put a +10 curvature on both axes just to get slightly better fine control when hovering.

Ah, I should have mentioned that I only run the standalone version, not Steam, so unsure if Steam just changes one install into the other or not.

FLT page - SET - RAD ALT needs turning on. Happened in the hotfix. Be patient, as it takes around 20-30 seconds to work.