Luigi Gorgonzola

This description by EtherealN is at least one clue in understanding the Sharks lift off behaviour: I briefly tested it and found the way I handle Collective does indeed make a difference. Being too gentle with Collective inevitably leads to strong nose-up behaviour, the faster I pull Collective, the less this nose-up behaviour seems to be. however, I don't think it's linear, so raising Collective abruptly would probably result in yet another "strange" behaviour ;)

Thanks for the links :) Of course, the "G940 Guide" is a must-read and it was the first I followed once I connected all the devices to my PC :) However, I'll check the other links more thoroughly when I'm back home and in the pit. I still hope it's a software/configuration issue (FW 1.42 and latest Logi Software) and not a hardware issue. I'd hate to return the device...

As I happened to notice it for the second time, I just wanted to see if I'm alone with the issue or if it is know already: In BS2 multiplayer - may it be a remote server or a self-hosted mission on my PC - I sometimes encounter an extremely unsteady rudder (according to the Shark's behaviour and the control indicator window - rudder is just moving by approx. 10% of its range in both directions) even though I keep my feet steady. I cannot reproduce this symptom nor force it to appear. All that I can surely say is that it happens when I apply just a little input - strong input works fine and as expected. And it only seems to happen in multiplayer mode. Any ideas?

Ah, so I'm too shy with Collective ;) Thanks for the hint, I'll give it a try :) However, this nose up attitude is far from being uncontrollable.

See here: http://forums.eagle.ru/showthread.php?t=83127&highlight=Molnia Sounds as pretty much the same issue to me.

Oh, that's weird, I always see the very behaviour as shown in EagleEye's videos as long as I don't touch Cyclic, including the tail touching the ground.

It's normal and usual in this business to build full scale models for in-studio usage. This most definately is the case with the Shark's nose in the studio clips. The lights of this model don't necessarily have to be red in reality. Check your mobile phone cams or other digital cams you own, most of them have a setting labelled "White Balance" that compensates (or is supposed to) colour discrepancies caused by the temperature of the "source" of the light - the so called colour temperature. Traditional light bulbs usually produce light at a very low temperature (ca. 2200 °K), the light of the sun that reaches mother earth on a sunny day has a higher temperature (ca. 5500 °K) and is considered "white" by the human eye. Colour temperatures lower than 5500 °K are being experienced as red. Analog film material as well as most digital photo receptors (processors, chips, name it as you'd like to) is configured to behave the same way as the human eye. Studio lightning is usually calibrated at 3200 °K or 3400 °K and so are the cameras (white balance). As a result, light sources emitting light with a colour temperature below this temperature - e.g. a conventional light buld in the Shark's nose - is rendered red, every source emitting a higher colour temperature becomes blue.

Loads. Just search for "root server hosting". Monthly fees start at about 100,- €/month (plus/minus) for a WinDoze server. Depending on the hardware and the service level you choose, costs can easily reach four digits ;) However, an average "DCS Only" server capable to feed 32 pilots shouldn't harm your wallet for more than said 100,- € a month. If it works, technically spoken. These servers are usually headless ones (i.e. without GPU). I wouldn't be surprised to see DCS not being able to run on these, although I never took care about this topic. At least in BS2 it's the "Options" button of the Multiplayer "startup screen". It allows you to be "Player 1" as well as to choose your network speed ;)

LA1, as a starter you could download (and read) the BS1 Flight Manual from the DCS website. There are no changes in BS2 that would render the BS1 manual useless.

Recce and attack, they're usually way better in that than I am ;)

You forgot to list printers, Xerox' etc. All applicable to additional tax since last Millenium, e.g. in DE. This is really cold coffee being boiled up once more.

Why should FPS increase by turning off XFire? Doesn't sound plausible to me as this would leave all the rendering stuff at a single card. At least with a single monitor configuration, that is. Multiple monitors plugged in to different cards might do a difference. Dual 5770, single monitor configuration here, XFire on and no real issues at all (I don't count in the white flashes as these seem to be related to the driver and not XFire).

AFAIK Radio Maykop seized its operations in 1.0.2 due to new audio handling and has yet to become oprational.

1) and 2) are exactly how I use the collective brake now, plus loosing altitude as well (not really necessary as I could also use the descent mode, I know). The effect of doing so - and this is, at least to me, the most important and enjoyable fact - is a smoother flight and I don't have to keep the state of the altitude channel in mind. No necessity, I know, but I enjoy it. :)

Continuously whiile changing altitude, as far as I understand the concept. See AlphaOneSix' earlier explanation. IRL as well as in DCS there seems to be no "must" in using the collective brake, technically spoken. Hence, you may safely omit it. I still may be wrong, though. However, and this is what I actually do, if you want to enjoy all of the AP channels, you always should use the collective brake. Not doing so would leave you dealing with the AP limits. As long as you combine the collective brake with the "Altitude" AP channel, yes. One of the reasons, I use the brake :) But be aware of what type of altitude you're using, Radar or Barometric (applies more to flight than to hover)! I just see yellow arrows... There's a small yellow arrow on the right side of the ADI (the upper instrument / "virtual horizon"). This arrow displays the current deviation from the assigned altitude, so - according to your description - it is serving its purpose perfectly fine. According to your description, you're trying to hover with the brake engaged. While it may work, it's probably not the best approach ;) Engaging the brake - pressing "F" - disengages the AP Altitude channel. You'd have to disengage the brake - let go the "F" key - in order to assign a new altitude value to the AP. That should do the trick. Engage brake -> set/approach new altitude -> disengage the brake -> enjoy.

Ah, I used to expect the collective to keep its current position anyway. Reading your explanation, I understand that without the brake or the friction, the collective would return to its down position as soon as the pilot takes off his hand. That's interesting, thanks a lot :) What kind of bike do you own? Neither of my bikes throttle grips ever kept its position when I took off my hand. All returned to their "closed" position, some faster, some slower, depending on the amount of dirt collected and applied during earlier rides ;) I know of some aftermarket accessories that keep your throttle grip at a fixed position (either by friction or by a pin locking the grip), but I wouldn't like to see any of these on my bike (don't even know if they're legal in my country at all).

That was exactly the same I encountered once. It was just my description that didn't catch your attention ;) See also the track I attached in this post: http://forums.eagle.ru/showpost.php?p=1360964&postcount=8 However, I neither saw it befor nor after this single event...

Oh, just leave those fixed-wingers enjoying their superiority. That way, they become careless too soon... ;) :D Sharks otoh should always be aware of their weaknesses - serves both fun and survival ;)

So it's "just" friction? I remember reading of similar brakes in different helicopters when browsing the web for more information, but as it didn't seem to be something common to all helicopters, my confusion started. Some have it, others don't? Anywa, thank you very much for your explanation! :) Oh, and by the way - yes, it's "F".

It's a pretty faint sound. The first time, I took it as some noise from outside (sort of traffic noise), but then I realised that it occurred most of the time when I felt the gusts tipping the Shark.

Anyone noticed the sound of the gusts when "dynamic weather" is set? I like it very much :)

Sorry, it's been obviously too early for my brain replacement device to work properly :poster_oops: Of Course, I intended to refer to the Collective Brake, trying to fix this in the OP...

Reading the Black Shark Flight Manual (both), I used to be a little confused by the Collective Brake. Having found some additional description of different helicopters in the web, I understand that one is supposed (if not obliged) to press the lever, thus disengaging the brake, prior to any Collective movement. IRL, as far as I understand, it would be impossible to move the Collective while the brake is engaged. Is that correct? Apart from that, I briefly tried it in DCS - with all four AP/AH buttons pressed - and found keeping altitude quite easier,, so I think, I'll keep this habit :)

Always Black Shark - Черная акула also sounds nicer ;)

Maybe a DX issue. Happened to experience this as well (out of the blue) and since resinstalling the VC redistributables didn't do the trick, I completely reinstalled BS2 out of lazyness. During the installation, I checked both the "install VC redist" and the "install DX" checkboxes. Having done so, everything worked as expected. Win7 x64 here...