mjolner

Thanks for the tutorial RCN, very helpful. Some Rep for ya.

Does this occur when you run the game from Modman? Maybe try to restore all your files from the modman backup. Uninstall Modman and try from there? Hope you wont have to waste a deactivation.

First wanted to say thanks to Mitch for the excellent CDDS file ( Mitch3 ). Those of you who have been either not using EURO_Green or been living with the missing paint here is a quick fix. After reading the tutorial PDF from Lockonfiles and backward engineering the various "skin" releated files I figured this out. All because those missing pylons were bugging the crap out of me. Anyway, it turns out that in Mitch's CDDS file there is atleast one left out templates: the lines below come from the Ka-50.skins file located in bazar\world\shapes\, this file contains all the skins including new ones, with text that will associate parts of the Ka-50 with the proper template. 3.3 correlates to EURO_Green. } skin { value = 3.3; material = {"KA-50-lamp", "Standart", "KA-50-PAINT33-DEF-02.bmp"}; material = {"KA-50-PAINT1", "Standart", "KA-50-PAINT33-DEF-01.bmp"}; material = {"KA-50-PAINT1_M", "Standart", "KA-50-PAINT33-DEF-01.bmp"}; material = {"KA-50-PAINT2", "Standart", "KA-50-PAINT33-DEF-02.bmp"}; material = {"KA-50-PAINT3", "Standart", "KA-50-PAINT2-DEF-03.bmp"}; material = {"KA-50-PAINT4", "Standart", "KA-50-PAINT33-DEF-04.bmp"}; material = {"KA-50-PAINT5", "Standart", "KA-50-PAINT16-DEF-05.bmp"}; material = {"KA-50-PAINT6", "Standart", "KA-50-PAINT33-DEF-06.bmp"}; material = {"KA-50-Vtulka_met", "Standart", "KA-50-PAINT33-DEF-02.bmp"}; material = {"SOPLA_KA-50-PAINT3", "Standart", "KA-50-PAINT2-DEF-03.bmp"}; material = {"KA-50-gear-rubber", "Standart", "KA-50-PAINT16-DEF-05.bmp"}; material = {"KA-50_ST-rm_paint1", "Standart", "Ka-50_St_Paint2.bmp"}; material = {"KA-50_Lifting_rotor_mast", "Standart", "KA-50-LRM-34.bmp"}; material = {"KA-50_LRM_Part", "Standart", "KA-50-LRMpart-34.bmp"}; material = {"KA-50_LRM-CENTRE", "Standart", "KA-50-LRM_centre-34.bmp"}; material = {"KA-50-LRM_B", "Standart", "KA-50-LRM_B-2.bmp"}; material = {"KA-50_BORT_NUMBERs", "Standart", "KA-50_Numbers-mitch1.tga"}; material = {"KA-50_Turkey_Numbers", "Standart", "empty.tga"}; Notice this line from the above text: material = {"KA-50-PAINT4", "Standart", "KA-50-PAINT33-DEF-04.bmp"}; The file KA-50-PAINT33-DEF-04.bmp does not exsist in Mitch's CDDS. Simply change PAINT33 to PAINT34. Keep in mind that the paint is not a perfect match and I am sure not what Mitch intended, however, you now have a weapon mount, and its a slightly darker green, barely noticeable. Note: If you are using Mitch's CDDS file and are trying to get "Fictional Digital Camouflage scheme", and "Fictional DOSAAF scheme"), to work, realize that these are not included in his download and will not function. Sorry if this is old news, thought it might help the stragglers, like me.

Map trim button to your stick. I use a cougar and I have mine mapped to S3. Trim, and trim some more, and when you think you are trim, trim again. When you speed up or slow down, trim. Accelerate slowly and be sure to not over control and trim. Dont forget that when you are holding the trim button down and moving the pedals (or how ever you use rudder ) you will be trimming rudder as well. Things seem a little crazy, check that rudder trim. Use the axis display CTRL + ENTER. Dont even try high speed until you can trim like a pro. Dont drop fast when slow, watch that envelope or you will drop right out of the sky. So many others. Lots to learn. Have fun

Thanks for the info guys. Gonna try some masking tactics with the Bradleys, see how I fare. I have to admit at this point I have been testing different systems by approaching slow at 30 to 50mm seeing how long I live. I also downloaded Mitch's skin pack from Lockofiles and have been playing with a turkish Ka-50 against russian SAMs, lots o fun.

So watch out for T-72s got it. What about the TOW missile. Is it supposed to be so effective against air borne targets? I fear that more than a tank round. If you are side tracking you can dodge a round but not a TOW atleast less likely to avoid the missile.

Been up against manpads, Linebacker, Chap, Avenger, only the Bradley mounted TOW missile makes me sweat. Endless reload and no effective counter measure except stay away. The effectiveness of flares on the Black SHark makes infrared seekers worthless at any difficulty. Atleast my observation. Whats up with all the stingers hitting the ground? Known bug or bad AI? Anyone else have different story? Even so, still playing and having a blast. I can almost land anywhere I want now. Cheers

I will name one. Though not a military flight sim PMDG 747 Queen and the MD11 are extremely complex flight sims. They run through FSX but have independent flight models seperate from the lame fm that comes with FSX. In terms of systems modelling and avionics and cockpit clickability they are on par with the Ka-50. Each have heavy weight manuals and takes serious study to fully comprehend. Each can be flown following exact airline procedures. Anywho, off topic really because they are civilian, but very cool and worth a look if you want to know how a modern airliner operates.

"Fratricide" at least in the strategic world is the inadvertent destruction of warheads by other warheads, there by effecting total damage done to the target.

Some recommendations: Build a simple mission with the ship on the runway or on the pad (use LWIN+Home for fast start). 1. Practive hovering from from the ground WITHOUT Auto-hover. Spend some time doing this. 2. Hit LCTRL+Enter to bring up the Axis display tool. Very handy. 3. Dont forget the rudder when trimming, it will be trimmed when you think its centered, gets me everytime. CTRL+T to reset. 4. Dont forget that Auto pilot only has 20% authority, and too much trim will pop back. 5. Map your autopilot modes to simpler keys. I use P(pitch) B(bank), H(heading), and Altitdude(A). and F(Flight director) Auto hover on Stick (like Cyclic). Make it easy. 6. If you are drifting in Auto Hover either you are not trimmed or one of your modes is off. Check them and re-trim, use cyclic to fine tune, but very small input. 7. When hovering with Heading control off ship will rotate to the right naturally. 8. USE ALT HOLD Mode, adjust collective using collective brake (F or preferably HOTAS). 9. Dont forget to ensure Route follow is off and dont forget about Decent mode on the collective, works great. You should always perform a hover check just after take off so practive on the airfield, and practice, practice, practice. Additionally, when you build that mission to practice hover, reduce fuel load and leave the stows empty, makes a bit of difference but not huge.

I also run dual boot and switched from XP to Vista. Tried all options to try and get rid of the micro freezes and stuttering. Installed on Vista (russian version) used up an additional activation. My performance and stability went through the roof. One thing I really noticed is Track IR smoothness and fine control really improved. Not sure what was wrong with my XP. Could be some DirectX thing, driver related, not sure.

I want to clarify that I do not think Vista is better than XP, I have a dual boot system and I mostly run XP. But I did experience a significant performance increase and I do not know why and suspect that possibly a software related problem was effecting Black Shark on MY Xp install. Who knows? So I am not advocating that anyone switch to Vista but look into software conflicts that may exist in XP.

My system: Was on XP SP3, now running Vista 32 Both installs are less than 3 months old. Intel Core 2 Duo E6600 eVGA nForce 680i SLI 4GB XMS PC6400 GeForce 9800 GTX non SLI ( Latest WHQL ) Audigy X-Fi Was getting acceptable frame rate of about 30+ but framerate would jump around alot and would stutter really bad in external view. In addition with my Track IR3 I would get real sluggish performance and it was hard to point and click the cockpit switches. No matter what I tweaked, be it the lua water setting, or video card settings ( anti alias, filtering ) or simply going to full low settings I could not get rid of the problem. I even tried the affinity settings. Made no difference. When I switched to Vista 32 everything changed. Runs smoothe as silk. 40+ average frames. The cockpit performance with TrackIR was like night and day, I can actually click and reposition the right switch on the first try. My general test is going to external view and slewing around over a city, and rotating up to the horizon, with Vista this test was much smoother and frame rate did not jump around. I have pretty much everything set to high settings including, textures, scenes, visibility, shadows. heat blur on and I am running 4x antialiasing and 8x ansitropic filtering. Now I honestly think that my XP install was the culprit. I have no idea what. But if you are having problems like I had with XP and a comparable system look into the possibility of really evaluating your (OS) install and do a decent house cleaning or maybe think about a re-installing your OS. Cheers

Very true sir. In my op I was questioning why I lost the numerical speed display after firing weapons, and the 50kmh speed requirment was adding to my confusion.

I am hitting the targeting system reset (backspace) key to reset everything. Chapter 7 clearly states that different weapons have different HUD display info. Maybe not very different but it is covered. SO RTFM does apply here. Air speed was always there it just changed to a speed tape vice a numerical display. I think I was just concentrating so closely to flying smoothly and never really looked hard at the HUD. Never realized that the 0 500 scale was a speed display. I think when I expended all my vikhrs the system auto switches to the inboard stow. Is this correct? I have yet to deliberately select and fire rockets or the cannon. I have one small lessoned learned I would like to share with others like me struggling to fly this thing: Use the rudder to full deflection when you think you need it. It has tons of authority and gives you tons of control. Gotta re-train rudder useage if you ve been flying jets or GA.

Before you give me a big RTFM slap on the back of the head, I did search for this problem before I decided to post. Also I have actually printed that beast of a PDF and cant seem to find this one. Now, that doesnt mean I have been completely thorough, after all this chopper sim is very complex. Alibi aside here is my issue. After I uncage my Shkval (love sayin that) and fire weapons and so forth I have been hitting the reset button to turn the HUD back to "normal" which also turns off the monitor. The button I am refering to is right next the laser standby switch to the left of the collective. I am at work so I cant be more specific. However on my HUD I lose my air speed indication. This doesnt always happen though. So I am pretty sure my procedure is wrong. Now you can hit me with a RTFM and I will certainly do more of that. But since I am at work and on company time thought I would post and what see others might say about this. Thanks

LWIn + End... I do this and then watch the blades stop. By the time I am done flying a mission and manage to land where I take aim for, I am ready to do a fast shut down. Otherwise, I would start the APU, put the fuel levers down, and turn everything off.

Dont forget Ebay, you can find a pair on sale there every now and then. And they dont have to be USB. The older game pad style connector works just fine and they connect right up to the cougar. I use non-USB ones and modified them per the instructions at Cougar World for the brake pedals to be recognized. Works great and have had them for years. Good luck to you.

Well that screenshot says it all. If you are still having problems realize that you will not see your purchased product or the serial number on the english side of the site. On the english side, log in your account, then select: FILEs, then: Products, then select russian language. Your serial number will apppear like magic.

Damn, some of you guys are actually firing weapons already. Skillz I say Skillz. I'm not even out of ground school yet.

The level of detail is staggering and intimidating to say the least. Comparable to PMDG 747 and similar add on flight sim packages, no small feat. Even though I will spend years mastering the Ka-50, I am gleefully anticipating a falcon, Frog, or Warthog module with the same level of detail. Heres for hoping. Cheers

My apologies if my previous post seemed to imply that you lacked a fundamental knowledge of the games mechanics. I really need to remember to thoroughly read all posts in a thread before posting. I am always passionate about fixing problems when I think that someone is missing out on a great simming experience. I get a little overzealous. Anyway, thanks for clarifying. Honestly, I do not use an FF2; several of my friends do and they never mentioned this issue. I personnally use a Cougar, frought with problems of its own but I could never go back to plastic.

This is where I am not understanding. You say your "( Trimming all the time anyway ) " With the 25T advanced ACS ( w/ AFM ) and the vanilla frog without ACS they have very stable airframes as long as loads are balanced, and even if you release some iron and wings start banking use the ACS (25T) to balance yourself out then turn ACS off, its simple and brilliant. Read the manual on the ACS and map some keys, its a must if you fly the T. If you are banking left or right just after you hit the S key, your stick is giving inadvertant control inputs that need to be addressed not trimmed out. I really wish I could trouble shoot your sticks myself. Oh well.

So, if I may, to clarify your stick problem and "solution", your wings bank left ( only in the 25T ), because of some FF2 anomaly. This only occurs in the 25T correct? And your fix is to create a large dead zone in the center neutral area and create an excessive response curve which is contrary to even the devs recommendation for AFM planes quote from 1.1 readme: "A dead zone would create a “flat” response area (local control insensitivity zone) when balancing the dependencies in the mid-angle of attack range (5 - 10°). This would make angle of attack and G-loading control difficult." But all in all you are happy with this fix and will continue smartly. Hey if it works for you run with it. I just think something simple is amiss with your configuration or drivers. Happy flying

Whoah..... With those curves you lose about 75% of your control authority. That stick must be extremely sensitive. Lets say your on a gun run, diving with combat flaps, as you accelerate your nose wants to rise so you increase pressure however your stick settings are way too sensitive and you would over compensate. If you can dive on a tank and hit him greater than 1K with those stick settings you are the man. You could of course use your ACS but that comes with its own problems particularly when you are pulling out from your attack. There must be another solution for you.