tsumikae

I'll try not to be too confusing. I might tell a few bulls, but nothing big, and I'm sure I'll stand corrected if required. Your main navigation and targeting system onboard is the prPNK. Its a combination of many systems that will help you to fly and kill stuff, to be short. You set it on with the K-041 switch on the target management panel on your left. Now, within the prPNK, the subsystem responsible for navigation is the PNK-800. It consists itself in a series of subsystems dedicated to navigation. Inertial Navigation Unit (INU), PVI-800, and to some extent the HSI are part of them. PVI-800 act as your command issuing interface to the PNK-800. It receives info from the INU, and gives instructions to other systems. You can enter, select, edit waypoints, and if a sequence of them is entered, you can fly the according track with the route mode. While it's not its sole purpose, the HSI will then display infos accordingly. The ABRIS, on the other hand, is not part of the PNK-800. As a late add-on, it can receive infos from it, but not send anything. So when you're flying a route, it will validate a passed steerpoint and illuminate the path to the next one, but it won't say anything to the HSI. The PVI-800 will. If you fly using the AP route mode, and your PVI waypoints are organised as a sequence, your helo will automatically turn to the next WP, and the HSI will display the new heading automatically (in auto mode). The ABRIS will have nothing to do with that.

Don't take it wrong, Skinnadoor, but I'm with Isegrim, here. You don't show much to help "understand how the KA50 operates". It's really cool of you to be willing to help beginners, but shouldn't you consider giving more insights? For example, a step by step start-up sequence including the systems descriptions, actions and relationships to each others would be nice. Still, thanks :) Bigfoot, I'll take that opportunity to say a huge thank you to you, man. Those interactive tutorials of yours are killers. My armor munching skillz own a great debt to you. They should definitely be included in the default BS2 package.

Actually, the BS2 module is more recent than the A10c module. And it was sold either as an upgrade, or as a full-price module. And I strongly agree with Shurugal, the only reason why I got to DCS was because of the Shark. It's still my fav, and will remain so for as long as it gets the attention it deserves. I bought the others for the sake of variety and to support ED. Learning the A10 is neat and all, but I'm really more of a rotor head. I would be really disappointed if the KA was left aside from now on. That said, ED is doing an incredible work on the whole DCS world and its maintenance. Maybe they have a lot of stuff on their hands and priorities on other departments?

In the same spirit, there is a mission in the "deployment" campaign, where the TIR roll axis is inverted.

I can understand. Why spend more money on air defense if your italian and french neighbours are doing the job for you ;) However, while as a friendly neighbour I'm glad we can be of service, as a french citizen i demand either a tax decrease, or an annual invitation for a week stay at a palace in Geneva :p

Basically, if you have waypoints pre-recorded in the PVI, you will be able to access them via the PVI 800 numpad. The HSI will point in the right direction accordingly. As Flanker said, the Abris and the PVI work separately. Actually the Abris is a late add on in the chopper. It won't communicate anything to the helo systems. Waypoints are generally pre-recorded prior to flight, in most missions. They will dispaly both on the PVI and the Abris.

By default, TrackIR should not interfere with external view anyway. Simply by entering an external view such as F2, you should be able to move around the framed object with the mouse, no matter the state of trackir. Just to be sure, the mouse movements are correctly assigned into the "Axis" department, right? (camera vertical/horizontal/zoom views). Are those the controls greyed out?

They are larger, actually. Albeit not by a huge difference.

So what was the reason, then? Just being curious, here, as I just saw the vid. I know they thought it was the pressurized vest, at some point, but pilots have been experiencing the same problems after the vest removal, from what I've found.

Exactly. May I ask, however, why you won't fly any Russian plane? I mean, they are pretty cool too. The Su27 is said to get a PFM upgrade soon, too.

That's a simple UI bug, specific to 1.2.8 and the introduction of the standalone F-15C. If you own FC3, you own the F15C as part of the whole module.

:D Man, I trust you so much!

Gimbal is strictly mechanical, and if you throw that in the balance, we'll have to leave the strictly sensor-ish argumentation. Still, "vastly" is exagerated. That word would fit more in a comparison between a KA-50 and a D variant. Yes, that's a surprise, I haven't read anything like that yet. But I'll take your word for it, as your sources are without a doubt way more accurate that the even above average internet research results :D Indeed, and again, I'd rather have some in my plate, sitting in my desk chair in front of DCS, instead of actually testing the theories for myself in real life, no matter in which helo :P

The A variant TADS is more or less the same stuff as the SHKVAL, and indeed the PNVS allows for night operation, while the former SHKVAL does not. Ok. The A had no GPS and from what I read, no datalink either. So maybe telling that the AH 64 A has vastly superior sensors is a bit exagerated. But, I'm no specialist, maybe you are and I should know better than arguing with you. In the unlikely event of those two meeting each other (in the past), I would rather be in my couch, at a bazillion kilometers from the duel site than in any of them anyway. But considering that the KA is faster, more maneuvrable and the vikhrs are also faster than the hellfires and have slightly more range, I envy your confidence about chosing tha Apache over the Shark. I really think you'd rather stay in your couch as well :D

The AH64 A (the one OP was talking about)? And what would be those "vastly superior sensors", if you please?

I think that any #insert plane name# VS #insert plane name# or "is better than" video on Youtube should be seen with a small sarcastic grin on the mouth and a raised eyebrow. Not that they are all completely false 100% of the time, but they are generally very biased. They are either fan made edits with spartiat infos, or national propagandas. Most of those 5th generation planes actually never met in combat.

Thanks, that was very instructive :thumbup: I shall definitely do that experience.

I have exactly the same problem, in the release version. Geforce 580 GTX Game resolution 1920x1080, aspect ratio 16:9 Ingame screens resolution 1024, not forced. It does happen when the dispenser is empty, and you try to change its default settings.

I thought those yellow LEDs meant that the engines electronic protections (EEG) were currently active and automatically *limiting* RPM. Which makes me wonder, Capt Zeen, if you haven't forgotten the EEGs for your flight? (in the case this was not a scripted event).

Here are two M-2000 HUD footages. A near crash: And a demo: And another one, very nice, with a lot of low level flight along Morocco beaches, but do yourself a favor: cut the music :D

I tried really hard to use the HOTAS slew ultra-mini joystick when I was learning the weapon systems, but it never worked well. I ended up reproducing -to some extent- the KA settings and now, I have only joy in my heart and fast, total destruction capacity in my right hand. Which, for some reason, does not sound less awkward than "in my stick". Sorry for that. All of my Shkval controls are on my WH stick, along with HMS activation and Shkval uncaging, slew fonction being on the 8 dir hat. I thought the default keyboard speed was nicely done and it's exactly what I need since only the large zones swipes are performed with the HMS and TIR. The only function that stayed on the HOTAS slew thingy is the target acquisition, because I got use to it. Here's the layout, for the record: DMS up: HMS on/off DMS down: Uncage Shkval DMS right: Weapon mode DMS left: Firing rate TMS up/down: Shkval zoom in/out TMS left/right: increase/decrease target frame Trim/POV hat: 8 directions slew. It may be worth noting that I'm currently starting the A10C and think the TGP slew function can be downright infuriating, at time. But I try to get used to it the way it is intended.

I got sniped once by a F15 pilot coming right in front of me. Sniped as in "headshot". Pilot was dead, but my KA, on route mode, continued its route as if nothing happened, good as new.

Same problem here, it looks like the controls won't handle both TIR z axis and the warthog slider at the same time for the zoom function. But it does work in F15c, for instance: I can use both TIR and the slider to zoom in the cockpit. By the way, some cockpit options may confuse zoom and translation.

Count me in your protest march. The new one sounds like an asthmatic teenager taking a deep breath when started, and a fart coming from the oldest anus in the universe when shut off. Which is kind of a bummer. But as you said, if it is supposed to be that way, so be it.