Sid6dot7

Wether the reflections in DCS are exaggerated or not... Regarding any of the here shown real pictures: Think about that most of semi-/professional photographers (obviously most of the pictures here are taken by those) have polarisation and some UV/IR-filters attached to the cameras objective lenses. Pol-filters will reduce any kind of reflection, some more or less, depending on the lights angle of incidence and type (polarized/non-polarized/natural lightning...). UV/IR-Filters changing the contrast in pictures and can dampen reflections to some degree. What I was driving at? You can't use photographs as comparision for reflections (as well many other topics), unless you know that no above mentioned filters were used!

No continous ones. Maximum were 4 not controllabe spins so far, when I tried "tail slide"/"hammerhead"-ish maneuvers. Had several engine hickups/stalls, sometimes flame outs in one engine, but no real self sustaining spins. :joystick: But great flight model, especially the engine model so far. Even it's WIP yet. :thumbup:

Flame out is an unstable condition, which is resulting in an extinguished combustion chamber flame. Obviously without the flame, one of the most important parts of the thermodynamic process (creating a large temperature gradient in the combustor) is broken and the whole gas generator can't provide any thrust. In short: Yes, the engine shuts off. There are varied operation conditions causing a flame out, but in most cases the flame can be reignited somehow, if the gas generator didn't take damage.

well said :thumbup:

High friction and/or a rotor with low mass/inertia looks like what I observed. Especially at unsteady or turbulent wind conditions, the fan reacts far too sensible to wind speed changes, when the engine is cold. Maybe WIP, but it catched my eye.

My cd version of FC works fine on Windows 7 Prof. x64. I changed from XP (x86) in the last days (search for some drivers was hard ;)). I installed LockOn, then FC; Patched it to 1.12b and copied a backup over, which I made under XP. Installed everything with admin rights and also the following I did with. When I started FC first time, Starforce was installed and it wanted to reboot. So I did it. After the reboot SF wanted to reboot over and over again to finish the driver installation, when I was trying to start FC. After applying the SF-update from post #5 (admin rights) and a new reboot, FC worked without any problems. And for the next week without the cd in the drive. :)

When you use an actual version of DCSMax you can choose your favourite skin at startup. It then will be used as standard for missions.

And it has a real moveable rudder at the tail booms end to additionally support the yaw momentum generated by the coaxial rotors at high speed. Not many helos have this, most have a fixed vertical stabilizer that automaticly compensates the yaw momentum with higher airspeed to a certain amount. But as said it isn't directly adjustable.

Besides LO/FC: BlackShark Download (russian+english) and russian DVD. In near future I will buy the printed manual and later all modules ED will offer. (hope so :joystick:)

Nah...not really. ;) What I meant are videos with the "foreground music only"-thing and nothing else AND absent cinematics. As long as movies partially have that "Glowing Amraam"-quality or are as funny as Waldo II's (which really has BACKGROUND music) I gladly watch them. Everything else not. That's what meant. :thumbup:

I absolutely need to agree you! I also want to hear the ingame sounds and especially the load-dependent engine and rotor sounds of the shark. Not music that if the worst comes to the worst isn't fitting to what you see (-> absent cinematics). Music only should act as support, not drowning everthing else.

You misunderstood me. I meant engineers who build inverted rudders into early aircrafts/copters, not pc-pilots. :D

Yep, nice one. It's an really easy explanation! But in the past there where people who thougt the other way round. Would be interesting why they abondoned their thoughts or rather had those thoughts.

After some looong thoughts about this topic a while ago (as I made plans to buy pedals, but now I better will design my own...more fun /more challenging ;)), I got to a specific point in my brain storming about the reason why the pedals will act as they do irl, that makes much sense I think. :idea: On our computer sims we don't feel any forces due to the helicopter movement itself, right. So it seems more natural for most people turning the whole pedals on that axis direction or twist the stick in that direction they want the helicopter rotate to: left stick-twist/counterclockwise pedal movement for turning the helo left/counterclockwise. (I hope that's somewhat understandable =)) In real life you have centrifugal/inertia forces that will move your body away from the direction the helicopter turns. Turn to the left and your body goes slightly to the right. With above pedal movement you don't have that much body tension (hope that's the right word) you need and really would have problems to counteract those forces. Because your right leg is more or less stretched, you can't really rest those forces and pressurizing the left pedal to counteract won't work. With the pedals movement behaviour like in real life you can rest the forces easier on the right pedal, when you perform more pressure on both pedals and so can reduce your bodies movement completely. Also that's an mechanical more natural countermoment to the forces induced into your body afaik. I know the pilot is good fixed in his helo, but I think he also will feel it. If you keep an eye of above description next time, when you make a fast left turn in your car, you need to slightly rest your body with your right knee at the center console (if you have an left-hand driven car and your seats won't rest you that good) or somewhere else to the right you can. :D So that was my approach and maybe that's why the pedals in real life act like they do...:smartass:

Think about: In a real helicopter you have most of your controls/displays within 70cm in your field of view. To speak for myself, I don't need to move my head forward to any labels/instruments I want to recognize within a near 1m radius. Just focus with the eyes and I can read it (without any eyeglasses). I guess the resolution of the Ka-50s displays themself are quite decent. In the sim, I need to zoom in because some instruments, especially the ABRIS, hud and sometimes the shkval are hardly readable from my seat when I had zoomed out to see more what happens outside the helicopter, because of the low resolution of my screen (1280x1024, even with 4x supersampling) and general limitations of any visual display unit. Thats the point where a second monitor with ABRIS/Shkval come into play, it simple gives you instruments, that you anytime can read fine like in reality (apart from some bad lightning conditions), independent from your zoom factor/fov. Thats without skidding your butt on your chair or constantly changing the zoom/fov (with some odd "jittering" behaviour on X52-axis). 2 pics for illustrating. The first shows my normal view for flying, where I have all relevant instruments in my field of view, but some are hardly to read (hud; abris is more guess work; Shkval when targets far away are locked) - besides some jpeg artifacts, ignore it ;). But it gives me the best feel of flying the Shark. The Second one shows another view I use often. Mostly for going into hover and some other situations where hud informations are important; but my field of view is insufficient, so I need to constantly move my head with TIR. In reality the hud lines will not appear like in the first shot and the ABRIS won't getting unsharp/jaggy. In reality they are readable anyway, because you won't have an limited resolution of your own view. Rather your eyes resolution is high enough (should be ;)) and your brain is interpoling eventually missing information better, than any anti aliasing algorithm.

The pilot's face absolutely fits the situation. :disgust::megalol:

@Husko If you don't change your hardware and only want to change/reinstall your operating system, you can Blackshark leave activated. You won't lose activations, when nothing is changed on hardware, rather you don't exceed the 12 points needed for an activation (counting points). Simply save following registry key to a .reg file: HKEY_CURRENT_USER\Software\Eagle Dynamics\Black Shark After you reinstalled your os and blackshark, simply doubleclick that .reg file and readd the key to your registry. Worked for me so far.

Ok, such an overview would be hard to find. Back to the pdf-manual...One Note: You can copy any of the pictures in there into your clipboard. The descriptions/arrows won't be copied. So You have a clear picture of any dash/switch/panel you want.

Isn't the manual enough? There are all panels and the location where they are described.

It doesn't sound unrealistic. Helicopters are mainly controlled by variations of the main and tail rotor blades angles of attack. With different techniques on actuating the blades you can roll, pitch (cyclic control), yaw and change height (collective control). In "normal" helicopters you yaw via the tail rotor, in the KA-50 via the main rotors (variation of torsional moment [torque] between the upper and lower disc; should also be collective control here (?)). So thats why it is possible to fly without the tail section, because its for stabilising the heli in forward flight only. What you will experience if you fly faster without your tail. ;)

Well said! :thumbsup: The smile from the uprunning APU is still there in my face. Even after nearly 4 months of sharking around.

Simple problem is that some features are not meant to be in the patch for sure. There's always the possibility that some of them can be removed in short or added behind schedule. But explain some of this decisions to the customer will be more complicated, than simple not tell him that this or that fix/feature was planned. It seems not about trying, if new features are working. It's more like... will they work together? Will arise more problems when they are implemented? Thats what I think. And like everytime surely there would be someone who says "But ED had said...". ;)

The bottom one looks to be similar to the "Werewolf" Demo Paint of Blackshark. Look: For the other skin. Why don't ask brewber19 directly? --> DCS: Black Shark User Screenshots Dedicated Thread

Maybe you can make a good use of this. It is a decalset from a AH-1Z scale model.

I don't know if it's the right way to do it, but it works. For changing lat./long. default settings: Open your ...\Scripts\Aircrafts\Ka-50\Cockpit\ABRIS\Options.lua with Notepad++ Goto line 442, there you will see following opt.Options.measurements.latitude = { data = { [color=blue]{"%02.f°%02.f\'%.s%02.f\""..LOCALIZE("C")," __°__\'__\""..LOCALIZE("C/Ю")}[/color], [color=red]{"%02.f°%02.f.%s\'" ..LOCALIZE("C")," __°__.__\'" ..LOCALIZE("C/Ю")}[/color], } } opt.Options.measurements.longitude = { data = { [color=blue]{"%03.f°%02.f\'%.s%02.f\""..LOCALIZE("В"),"___°__\'__\""..LOCALIZE("В/З")}[/color], [color=red]{"%03.f°%02.f.%s\'" ..LOCALIZE("В"),"___°__.__\'" ..LOCALIZE("В/З")}[/color], } } The blue values seems to be the default one. Simply swap the blue with red values to: opt.Options.measurements.latitude = { data = { [color=red]{"%02.f°%02.f.%s\'" ..LOCALIZE("C")," __°__.__\'" ..LOCALIZE("C/Ю")}[/color], [color=blue]{"%02.f°%02.f\'%.s%02.f\""..LOCALIZE("C")," __°__\'__\""..LOCALIZE("C/Ю")}[/color], } } opt.Options.measurements.longitude = { data = { [color=red]{"%03.f°%02.f.%s\'" ..LOCALIZE("В"),"___°__.__\'" ..LOCALIZE("В/З")}[/color], [color=blue]{"%03.f°%02.f\'%.s%02.f\""..LOCALIZE("В"),"___°__\'__\""..LOCALIZE("В/З")}[/color], } } There you go.