JozMk.II

Fantastic job, it looks great. I especially like the paint job.

Looks nice, but will the addition of these higher-poly models affect the frame rate at all? Frankly I wouldn't care if they left the current ground models the way they are; it's not like I'll notice their amount of detail in combat, anyway. Their detail is good enough for one to be able to tell what they are through plain sight or through the Shkval, so why worry about it?

Air-Force-One, My keyboard has the same type of configuration, but Undo doesn't cause the problem on my end; its function is to increase the game's running speed. I will try your method of fixing this problem if I encounter it again, though. If that doesn't work, I guess I'll try unplugging and plugging my joystick back in on the fly as Yskonyn suggested. I hope one of these methods works if this ever happens again. As for your question MTFDarkEagle, I've only encountered the problem once so far. Thanks for your feedback so far, everyone. If anyone else has any suggestions they are much appreciated.

I second Yskonyn and Polecat. This brings to mind a particular limited-edition flight stick and throttle set for Ace Combat 6 that had a not-so-convenient paddle on the throttle for rudder rather than a twist feature in the stick. I suspect that it was designed this way since many felt twisting the stick for rudder wasn't realistic. But then again using a less convenient paddle on the throttle instead isn't any more realistic; all it does is make things more difficult than they have to be! Certainly counter-intuitive. So yeah, like Yskonyn said, the question on the realism of these quirks is how you use them, not whether you use them.

Hi, I was playing Black Shark a few minutes ago when I encountered a strange problem. I was hovering with the laser rangefinder, helmet sight, and Shkval on, with an armored target locked on the Shkval screen. Autopilot Pitch, Autopilot Bank, Autopilot Altitude, Autopilot Heading, and Autohover were engaged. I then paused the game for a bit. When I unpaused, the game registered the left pedal as fully depressed, causing my chopper to spin. Hitting the trim and reset-trim keys didn't fix this; all either key would do is cause the pedals to recenter for half a second, but then the left pedal would fully depress again. Twisting the stick all the way to the right would recenter the pedals, but only as long as I kept it twisted to the right; I basically had no right rotational control. I tried auto-calibrating my stick's twist axis by running it through its extremes, but the left pedal still stayed fully depressed. I see a possibility that I hit a key on my keyboard that caused this problem, for I accidentally pressed an extra key or two as I hit the pause key. If this is the case, the key would be located near the pause key, but I simply can't recreate the problem no matter which key I press. If it isn't a key that caused this problem, I wonder if unplugging and replugging my stick into the USB port would have fixed the problem, something I didn't think of doing before ending the mission. Whatever caused the problem, it was no longer there when I started a new mission, and I haven't been able to recreate the problem. My stick is a Saitek Cyborg Evo Force. I have force feedback disabled in the Black Shark config file. Does anyone know what was going on here? Is there a key that that could have caused this or is it my stick? I'd like to know in case this ever happens again so I can fix it without having to restart the mission.

Aww, too bad. You don't have it either?

Ahh, must be nice to know someone who makes music like that personally. Overall I think he did a nice job on the version you used in your video. The version on that site you provided a link to is also nice, though the original is my favorite. I hate to ask, but do you know if Daniel would mind if you shared the original with us?

Glowing Amraam, where did you get the song yourself? Was it off a CD? If so, which CD?

Oh, whoops. Yeah, that makes a lot more sense than what I thought I saw, heh. I guess I'll start setting the throttles to auto after shutting down the APU from now on. Thanks for your feedback.

Thanks a lot, turning on WCS worked like a charm. As for the throttles, however, I'm pretty sure you're supposed to set the throttles to auto, not max; I recall at least one instance of an ED member mentioning on these forums that the max throttle setting is is mainly for emergencies, such as if one of your engines is shot out. For leaving it on too long isn't exactly healthy for your engines. Besides, it seems to start up fine when I use the auto setting. I will, however, try starting the Black Shark with ground power and see if that makes any sort of difference. Yeah, I doubt my startup process would be satisfactory in real life. I've only recently learned to do the full startup of the Ka-50, so my method at the moment is simplified to be easier to remember; I like to get as many of the switches on a single pass as possible. Truth be told I'm still learning all of the Black Shark's functions, so getting the startup sequence perfect isn't my prime concern at the moment. I'll likely perfect it later on, however. Thanks everyone

I've just recently learned to do the full startup of the Ka-50. Or so it seems. When I start up the Ka-50 on my own, the green and black buttons on the left cockpit panel(auto-turn to target, for example) don't work, whether I click them or hit the appropriate keystroke. They don't even light up when pressed. I've noticed that this problem is also present when the instructor starts up the chopper in the training video for helicopter start-up. However, the buttons work as they should when I use the cheat command to execute the full start-up sequence. I simply can't figure out what I'm doing wrong when I start it up myself. I've checked the start-up checklist in that stickied thread and tried to figure out what I'm doing wrong by watching when using the automated start-up cheat. Can someone look at my lastmission track and tell me what I'm doing wrong? That would be much appreciated. Edit- Okay, the buttons are actually black with green rectangular lights on them, not blue. LastMissionTrack.trk

I'm encountering this problem myself. Has anyone found a solution? If not, I sure hope ED addresses this in the first patch.