eV1Te

Take a look at Metacritic (they list all major reviews of games and the average of these when there are enough reviews to average) there are so far only 2 reviews with very different score... http://www.metacritic.com/games/platforms/pc/dcsblackshark?q=black%20shark

Even depleted uranium is radioactive but in extremely small amounts... To be exposed to radiation from uranium, you have to eat, drink, or breathe it, or get it on your skin. The aerosol produced during impact and combustion of depleted uranium munitions can potentially contaminate wide areas around the impact sites or can be inhaled by civilians and military personnel. // Wiki

That's true, and the best thing about it is, that they landed in a minefield so they couldn't leave the aircraft without being picked up by a fire truck :thumbup: It was the 2:nd episode of the 3:d season of the Air Crash Investigation documentary series.

I do not agree... The features Cichlidash refereed to, the lack of multi-core support etc. I think should have the same priority as upgrading AI etc, since many people have near unacceptable frame rates due to bad CPU utilization (including myself). But I can agree with the fact of adding new visual effects that doesn't improve performance should have a lower priority.

They will probably upgrade the graphics in time as well... Just look at IL-2 Sturmovik, it's 8 years old now and after a few patches and new releases of modules it looks like this

I've had a few BSOD myself, but very random and usually during the loading sequence of missions. Maybe the game is sensitive to drivers and what input devices are connected at the moment etc.

The quick answer is for DCS BS; No you don't need to cut anything... but the story is probably different in real life... :music_whistling: Unless someone know the correct procedure, we have to wait for the new manual which is supposed to contain checklists.

Does that include aerodynamics for the helicopter as well?:) Now it's time to read about ballistics so I can post more questions for you to answer :thumbup:

Thanks for your answers they have been helpful! Now I can go on and actually fly the damn thing :thumbup: By the way... Since you tend to answer many questions covering the aerodynamics of the Ka-50 on the forums, have you had any involvement in the creation of the physics engine in DCS? :music_whistling:

Is it possible to extract more information from the track file than just watching the track file..? For example can I somehow extract the information why the engine turned off (due to Ice or Dust etc.)... Or after an enemy hit's me and some systems turns off, I would like to afterward see exactly what that enemy hit on my Ka-50.. (generators, batteries weapon system etc. which overlap each other in some cases)?

Start APU Start Engine :music_whistling:

I've had similar problems before as well.. and the feature I'm missing in DCS which would answer many of these kind of questions is a detailed log over the last flight, which would show exactly what systems have been disabled and why...

I see (I noticed that the image file name had Ka-32 in it after you mentioned it :music_whistling:), what is the gearbox ratio for the Ka-50 then? When you say nominal RPM do you mean the RPM at 100%? (there is no mentioning of what the scale is of the rotor RPM indicator in the manual, as there is for the engine RPM indicator) That is true, I simplified this some what since the airspeed was zero etc. But you mean that it is not possible, even with full collective and the wind coming from below and with rotor RPM at 50%; for the stall region to cover the majority of the rotor on the Ka-50? (when i say stall I mean when the horizontal components of the drag vector is larger than the lift vector so that without changing the collective the rotor RPM will not stop decaying) How do you stall the rotors in DCS during autorotation in such a way that you can't recover from it? (I haven't succeeded in entering any kind of unrecoverable state during autorotation) I believe have stalled the engines at least one time during my flight in DCS... :music_whistling:

If we say 1 USD will you sell the game for that amount then? :music_whistling:

For me and my friends windowed mode gives us 10-20 lower fps than full screen even though windowed mode is at lower resolution. I use alt-tabbing a lot and the game isn't playable in windowed mode due to the performance drop. I hope this issue is resolved in the patch.

Thank you for a good explanation; First, the gear ratio I found in this print posted somewhere else and since the the ratio also matched the value i found by slowing down the simulation and counting the number of turns each second, I assumed it was approximately correct. :) The reason I tried to make some calculations was to only for me to try and understand the subject better. I couldn't find any information about what happens when you increase the pitch drastically, so that the entire blade has an AoA that is higher than the stall AoA. The only thing I knew was that real pilots on other forums and web pages said that depending on the helicopter. You only have a matter of seconds to reduce collective, from it's normal flight position (so increasing collective would be worse) when engine failure happens, until large portions of the blade stalls and the rotor RPM reduces below an unrecoverable limit. Some even mentioning that helicopters have crashed with their rotors almost completely still. But of course one can not trust what you read on the internet therefore I asked here... Edit: The phenomena I'm referring to seems to be called Low-RPM-Rotor stall. Reports from for example US Academy of Aviationsays that it is the cause of many helicopter crashes. One example from a report about the R-22 said: The rotorblades of the R22 have a maximum angle of attack of about 15 degrees. If that angle of attack is exceeded the rotor blades stall, lift is cancelled, and the aircraft falls out of the sky. It is also mentioned that not even the engine at full throttle can give the required thrust to increase the RPM if that threshold is reached (below 80% of operational RPM) How come the Ka-50 is not affected by this Low-RPM-Rotor stall in the same extend as other helicopters?

There have been many reads of this thread but no responces lately, maybe I killed the thread with the last post.. :music_whistling: Is there someone that have the knowledge of how autorotation works in reality; If the pilot fails to lower the collective or even worse increases collective after an engine malfunction what would happen? (In Ka-50 nothing more happens than that the rotor RPM goes down a bit but is easily increased by lowering the collective again, even though logics tells me that the rotor would stall...)

I'm not so sure that MP would use more CPU than SP... I have also noticed that in windowed mode in SP i get about the same FPS as in MP (in MP windowed/full screen doesn't matter much) so there seems to be differences in how the MP and SP engines runs even on other levels...

I have also noticed lower frame rates in MP... but probably not more than a 20-30% difference...

As someones said: Check the files so they aren't corrupted, this is the first thing you should do with every file you download from the internet that isn't working! File name: setup.exe File size: 1.31 GB MD5: b097066f30001c596f576d3f3c850cc1 File name: data1.cab File size: 897.4 MB MD5: dc721fc2d8730c1bdd5621bcaf8d92e3 A quick google search found this poplar free MD5 checker: http://www.download.com/MD5-Checker/3000-2092_4-10410639.html?tag=mncol

I found another "secret" accessory on the Ka-50 :music_whistling:

It would be nice to have some kind of Mod that enables the use of the R-73 for example. Even if they aren't used in real life today one might want to create a mission where one is playing as a test pilot for Kamov and evaluating the effectiveness of A2A missiles on the Ka-50. Which would be a realistic mission since they have probably in some way some time tested this i would guess...

Keep in mind that are some bugs in the Editor right now that will be fixed in the next version I guess (Mainly covering multiplayer). There are also incorrect information in the manual on how one should set up some target points (for example carpet-bombing where the manual says that the target points should have different names but in fact should have the same name)

Look in the GUI manual that comes with the game, there you have 80 pages covering the Mission Editor :thumbup:

That explains why Coop missions I made sometime bugs if the client and host doesn't fly together... Will this be fixed in upcoming patches so one can make better MP missions then?