Logite

I'm still mystified as to why this is happening, like a few of you. Could it be that the engineers forgot to put air in the tires? :P I don't have any failures set afaik. Failures are set in the triggers window no?

I apologize in advance for the headbanging. client-20100522-164041.miz.trk

I made a custom mission and whenever I start to take off or fly this happens (in order) ELEC ON ACCUM COMMON HYDRO HI VIBR LEFT ENG Then the rotors stop and the engines start to catch fire. What might be causing this? What steps can I take to diagnose these problems myself in the future?

fixed

Huh. You guys are the moderators for a reason :) Alright gents. Now that I realize people care more about turning things into arguments than helping the fellow user out, I made sure all my posts are shining examples on perfection of the English language. In criticizing what was a major public release, I truly had no insight into what importance was placed on precise spelling and grammer on an internet forUM. To give everybody an insight on how relevant things stay on topic on this forum, here are the stats. 27 posts were made. 5 of those were relevant solving the solution presented in the topic. That's 82% of the posts made in this thread that contributed into making this forum one step closer to an ugly place. If you choose to blame me, analyze first if you were one of those posts that were a part of that 82%. A mere 18% were relevant to the topic.

Okay!- Well hey, since you have zero regard whatsoever for other player's feelings and opinions, there is perhaps no chance you will hear this at all. Let alone care enough about your fellow players (to which there are very few in this genre). But I digress! Let me state there have been MULTIPLE, and I mean MULTIPLE examples (that are much more inhibiting than "petty" as you so inaccurately state. This is the lack of polish that tarnish Black Shark's name. Errors, such as complete inaccuracies along with small misspellings in not only the Pilots Manual, but the GUI Manual as well. Providing reference screenshots as well as dedicating sections to things that aren't even THERE in your game's manual it's more notable than you seem to realize. It's something that is inhibiting enough to block learning. Don't try to say learning in this game isn't important because when you do I will call you out on it flat. I won't say that I haven't got a fantastic value for the $40 I spent on this. It was worth my money. Yet, when you fail to spend money for someone to spell-check the manual for the price of "a couple of pizzas", how can you expect someone to not state that flaw? Even misspelling "astounding" wouldn't be meritorious enough to garner criticism from me - it is the simple failure to remove a few paragraphs here and there that describe objects or elements that _do not exist_ anymore. Your criticism falls flat on it's face when you analyze both the fact that: You're using excuses of "difficulty" to cover up a developer's fault (I'm sorry boss, but I didn't do the job you're paying me for because it was just a little bit too hard for me). Not to mention the ridiculous idea that I garner some sort of prejudice against Russians makes me wonder why you're so touchy about that notion. Could you point out please what part of my discussion made you come to that conclusion? Right. You can't. Because it doesn't exist. Don't get on your high horse by thinking you're doing some sort of justice to the "Eagle Dynamics" or "Black Shark" name by defending things that make the game and developers look bad. What you seem intent on doing has the opposite effect. You not only make yourself and the person you're defending look incompetent but prevent progress of the contributing parties as a whole. I'm utterly stupefied to actually see this sort of knee-jerk defense reaction from anybody on these forums. To Eagle Dynamics: I would gladly spend some of my free time editing out those portions of your manual and spell-checking it if you would be willing to distribute it.

Sorry, I don't want to fumble around in the dark to try to start up the KA-50. I guess now would be a good time to complain about how dumb it was to leave such an obvious feature out...that on top of the numerous spelling errors and the horrible lack of fluidity in the manual really make it hard to enjoy this.

I'm trying to concoct a mission of grand proportions here, and I'm set back by that all too annoying thing of matter called "light". I'm on a FARP in the middle of nowhere. Is there some sort of building or other object in the editor I could possibly use to be able to see my cockpit?

I just thought everyone would like to know me and a few friends came up with a way for all the English (please) speaking Black Shark users to coordinate games with each other. It's preferable for users to have a microphone to use with the VOIP information provided. We coordinate matches around 10PM and onwards each night. Hopefully we all will see this turn into a way for all users across the globe to find each other and enjoy the amazingness of Black Shark together :joystick:. Yours and our IRC server is irc.synirc.net in the channel #dcsgoons

How are you supposed to do this? I tried loading controls from the control menu - that gave me an error.

Unfortunately not. I've included a picture though to better illustrate what I'm trying to do-

I'm trying to use an axis based POV hat on my G940 to look around the cockpit as you would with the mouse. Unfortunately, a big chunk of controls in the Axis Controls portion of options are reserved only for the mouse. Is there some sort of alternative that will achieve the same end or am I going to be forced to use crappy Absolute controls with my joystick? I've included a picture of where I'm trying to place my Hat's Axes: