Swift.

Cooperative launches, please ED. SLAM-ER is marked as completed on the roadmap, yet this fundamental feature is still missing.

Can we at least in the short term have the ability to better control this behaviour through a lua? Just so that the user can adjust the behaviour to suit their needs, in lieu of the ability to match it closer to RL.

Just to put this thread back on track. The issue being seen is not a PC performance issue. I'm still maintaining very high FPS throughout and the game is not lagging outside of the PNVS view. Additionally, as said in the OP, TADS is silky smooth, which is effectively the same rendering effect. What is going on here is a stutter with specifically the PNVS, no stuttering anywhere else during this event.

Would be a nice to have, especially once we get the Afghan theatre.

Ah, so Sight Select Switch wont change the IHADSS symbology. Sight Select is used to select the Sight, ie HMD, TADS, FCR, LINK. What you are looking for is the Symbology Select Switch. Which is used to change the IHADSS symbology.

The Bob-Up box should represent a displacement of 6ft from the centre(where it was dropped) to the edge of the box. As the box itself is a 12x12ft box. In DCS however, it looks like it might be about half this size. With a centre to edge displacement of about 3ft. Edit: The Flags in the track are 6ft apart. NB. I'm not sure if my attached track includes mod objects as I used some flag markers to show the distance. BobupBox.trk

When using the toe brakes to release the parking brake (by depressing them), the parking brake seems to correctly release. However the handle remains out. The expected behaviour here is for the handle to pop back in when the brake is released in this manner. ApacheParkBrake.trk

There are more ways to report a bug than just the bug forums. The problem is a lot of the people who once cared and reported these things have since moved on now that it's become clear ED aren't going to fix these issues.

Maybe a little late to this, but the way I've had to reason it to make it make sense in my mind is that the ball isnt showing centred when the airflow is perfectly inline with the fuselage. But rather centred means it in the optimum aerodynamic condition, which for reasons described above, is slightly angled to the right. So whilst you could have a more streamlined fuselage position, it wouldnt necessarily be a better position for the aerodynamics of the airframe.

Ed Macy has a couple of good books: "Hellfire" and "Apache". Its about British Apaches, if that matters to you.

I see, well its difficult to know what's going on without an accurate reproduction of the issue I guess. Apache is known for being a bit tippy afaik, and the track you did provide shows it being surprisingly stable on what amounts to not very stable ground at all.

You landing was stable until you pressed on the left pedal whilst on the ground. You don't need to land with the tail wheel unlocked, just don't try and turn with it locked.

Is that a universal thing or unit specific? I see these apache supposedly from 1-25 ARB have 3 digit numbers in white, but other units have 5 digits in black: Could have sworn you can enter more than 3 numbers. I was playing around the other day, plugging in 5 digits. It wasn't doing anything, because as you said the skins don't have those numbers yet, but it wasn't stopping me from entering them.

So this doesn't look like any issue with tire interaction or anything like that. Its as BN said, you still had a heft chunk of torque being pulled and you stomped on the left pedal. This rolling moment is because the apaches tail rotor is so high up, that as you push the left pedal, you are making that tail rotor push to the right. Simultaneously it will try to make the tail tip over to the right. On smooth ground this can be accounted for with a little bit of left cyclic, but on a soft desert like you landed on, that rolling moment will be the only motion produced by the tail rotor. So your massive left pedal input is doing only one thing and thats tipping the heli to the right, which is exactly what we saw. So lesson learned. Don't ground taxi when you land off field in the desert.

Not sure tbh, I imagine its not a regime of flight that's known much about. Especially if pilots are being trained specifically to avoid it.

It could probably just be an extra slot in the rearming menu?

They work just fine in A-10. I've only logged 30 hours of A-10 flight, but already experienced at least 1 failure (broken Left MFD). I've also seen a couple of stuck buttons.

Yeah, that's what I wanted to test. In other modules, the HUD slews smoothly and continuously and I wanted to see if, in the Hornet, it's only a matter of sensitivity or a matter of the designation slewing in increments instead of continuously. I mean give it a go, I'd be curious to hear your take on it. I do remember that 1 month when they fixed the slew rate for the HUD, and then it broke again the next update. What a glorious month that was.

In my experience there is no failure modelling of any systems in hornet. There is a brief suggestion that we might have an MC1 failure mode modelled, but it doesn't show the correct indications for that failure and recent peer experience has led me to believe its just a bug (unreproducable so unreportable). Having said that, I have no idea how deep the simulation goes. All I know is whatever system might or might not be modelled below the surface, are perfect and cannot fail. Leading to there currently being no requirement to learn any EPs. Source: 5.3K combined logged hornet flight hours in our group, random failures on. Never had a proper Hornet failure, just those odd MC1 things I said above

It's a known fact that pulling too fast will outpace the FCS's ability to limit the G. That's why IRL pilots are trained to not pull too fast. Having said that, snapping the wings during these excursions is likely a bit too far, as you said. Probably due to the interim damage model we currently have on hornet. Once we get a proper DM then I hope we will start seeing things like specific control failures, wing fold issues, etc etc at these G excursions. And not just binary broken or not.

Are you saying that you cant have the G only on 1 radio in SRS? Because I'm most certain you can (as its what I do every time I fly)

Worth isolating there, the HUD HMD slew is still too sensitive, regardless of the jumpiness of it. You can turn down the TDC sensitivity and the HUD slews nicely (obviously at the expense of the ability to slew anything else)

That is a bug, and its been reported

I think this is another report of the issue that everyone is seeing here. Uncorrectable INU velocity errors.

Very very valid point. Same for the ATFLIR on hornet, in 2005 there were only ~3 pods available for Legacy Hornets. It seems the precedence is for adding features even if IRL they were one offs.