martinistripes

Perhaps aerodynamics was the wrong word. I wasn't refering to weight, but more airflow over the surfaces. I only fly the regular 25. The big ugly Shkval screen in the 'T' was enough to put me off alone. It's nicely integrated in the Ka-50s design, but in the toad it's just bodged in there like a messy after thought.

In FC2 is the regular 25 AFM or just the T? I keep seeing people specifically mentioning the T when they talk about AFM. For some reason I had it in my head both were AFM. Aren't both aircraft the same in terms of aerodynamics? The FC2 Upgrade FAQ suggests both are AFM. If only the T is AFM, it makes more sense why it was exclusively chosen for DCS World.

Voted :D

I like the Frogfoot, so provinding there are significant tweaks, bugfixes, improvements etc. I will buy.

I can't imagine choosing to play P-51D over IL2 1946. I would be curious to see it flying low over a modern battlefield, but that's about it. I was hoping the first Legends aircraft might have been a Vietnam bird. Still could and probably will happen given enough time. When Black Shark was first released, I suspected EDs priority would be getting equal opposites and likely rivals into the same arena to maximize multiplayer appeal. Now I see there is no pattern or limit to what they'll create. They're like a box of chocolates... :D

I can confirm my UV-26 is the same. Clearly a bug. Thanks for posting your fix.

I've seen this glitch before also, but not noticed it recently. I'll check again today.

Interesting repsonses. Never would have considered using an R/C controller before. I will take a closer look. Thanks.

Then, it seems I've just been educated. Interesting to know. I never would have guessed the blades to be so fragile.

So what you're basically saying is, it's normal for a 6 m/s wind (moderate breeze by the Beaufort Scale) to snap a rotor blade in two if someone were to leave the rotor brake off?

Sorry AlphaOneSix. I was not being ignorant to your post. I understand that using the rotorbrake will avoid the situation. But I don't understand the mechanics of what's happening, and why it's happening. To me, it still appears bugged. Would my wind speed of 6 m/s begin to turn the blades like that? Perhaps so. But would the blades really snap, just from being turned by the wind? :huh: I'm assuming they would withstand much greater forces under normal use.

The only mod I'm using (and have used with this particular install) is the one that converts the EKRAN voice to Russian. Otherwise, it's clean.

Ok, here's a track. I realise I didn't start-up as per the book by the way, but I'm still not sure that accounts for my blades snapping the way they are. You can see the blades begin turning at some speed and all I did was start up the APU. :huh: Rotor Failure.trk

I'm really liking black shark 2. My dilemma is that work requires me to travel. Until now I've been using CH kit at home. It's obviously to big to travel with so I throw an old thrust master game pad in my hold luggage when working. It has 2 analog sticks. One acts as the cyclic and the other doubles as collective and rudder. Problem is collective is at 50% when the analog stick is centered. So it's far from ideal. Does anyone have a solution? A way to get around the collective issue, or perhaps a recommendation for another control system that is compact and robust enough to throw in my hold luggage?

Thanks Pyroflash, but I'm sure it's the blades. The aircraft begins to wobble then I switch to the external view and see some blades are half length with the debris on the floor. I'll repeat and record of course. Now, I'm going to look for a cold beer in Sri Lanka. :smilewink:

6 m/s 12 m/s 18 m/s

Not sure what's causing this at all. Maybe random failures setting. I created a mission starting cold on the pad at Batumi. I start the APU and the blades start turning (yes, before even starting an engine) and then snap. It's happened on several occasions consecutively. Not sure if I'm doing something wrong or it's a bug. I'll post a track later (I'm away from home now). I set the temperature to -15. Is it something to do with ice on the blades maybe, but still I don't understand how they would turn or snap after starting the APU. It could be a random failure, but it dosn't seem likely when it occurs 3 times in a row.

Awesome post SilverOne. These are the kind of step-by-step guides we need. Is anyone using FaceTrackNoir v1.6 with BS2? The software is tracking, and in BS2 control options it is showing a headtracker. But I'm getting no response when in game.

So perhaps we are experiencing the same thing. To me, it looks like no HDR is applied until I alt tab. But you say this IS HDR in normal mode? Either way, the rendering is altered by alt tabbing, which of course, should not be happening.

I have normal colours selected. I didn't even realise the HDR effect was missing until I alt tabbed the first time.

I'm guessing this will be an AMD issue rather than a program bug but wanted to mention it here anyway. I have a new laptop with the Radeon HD 6990M. When running BS2 HDR is not applied, even though I have the option checked. However, if I alt tab back to desktop, then back into the game, it is.

Fixed the first problem. Just trying to get it to track in BS2 now.

I just installed FaceTrackNoir v1.60. When I launch the program it seems to run fine. But when I press 'Start' in the 'Tracker Source' box no webcam image is displayed. I just see the green X,Y,Z etc. numbers appear and they are all stuck on 0.0. I have BisonCam, NB Pro on Windows 7 x64 bit operating system. To the right of the X,Y,Z box it says BisonCam, NB Pro so I'm guessing it's detected the camera. Any suggestions?

Hey, I just got round to playing BS2 (1.1.1.1). Great work on the update! I noticed the EKRAN is speaking English now. Any reason why?

I really hope it's not WWII.