Daniel M

x2 I used to only use mouse input to the abris, but started using the FSK keys on the keyboard, and it's much quicker now. My tip would be to learn to navigate abris via the keyboard.

My two cents, I'm a press and hold trimmer, so i'll land while holding the trim button down, brakes only as needed, but usually just joystick input until everything has settled. After i'm at a stop i'll release trim and good to go(or apply parking break/shutdown). I've had issues with resetting trim after touchdown, she always seems to want to move after I do that. So I don't reset :D

What's your approx range and altitude? I usually "refuse" to fly above 100 m for more than a few seconds, and really like to stay below 30 if possible. Engage targets starting from 7km (been getting better at engaging above 7.5 k after lots of practice...). My basic sop is fly to foward edge of battle. If enemy units are known(fog of war and all taken into consideration), get within that radius, then start search from a low hover. Edit: Maybe I should ask first; can you still identify targets in the shkval at that resolution? (I would assume yes...)

Long short of it is (imho) ED/DCS needs security clearance before releasing to the general public....no(not enough) declassified info for the apache (again all speculation on my part)

Looks like my current attempts at taking off from farps in multi :juggle:

I wouldn't mind and would take the blame if it was my fault, the problem comes when someone else lands on "your" pad. You click "fly" and get an instant team kill, and in a couple of instances I got kicked from servers for "to many tk's". It's not a deal breaker, just frustrating; something that I think would be nice to clean up. Unless I"m missing something? Is there a way to check if the pad is unoccupied before spawn?

The problem occurs when someone else lands on your/ the pad(though i'm guilty of it as well). Plus sometimes a farp is 30 minutes closer than your original spawn point. Maybe have atc say "you're not allowed to land" :D How would this work in RL? Would ATC say land on pad x? Granted RL you don't have magically spawning helicopters It's more the no message warning of impending doom that would be nice to say "you can spawn here, but you may blow up" A tiny detail that hopefully will eventually get updated/cleaned up more than anything Maybe something like "flight 1-1 through 1-4 is assigned farp 1" and at moment of spawn pick an unoccupied pad. It's "working as designed", doesn't that make it a "feature" :D

Not sure if this should go under the wish list section: Don't allow spawn if pad is occupied

Did Hello Kitty Adventure Island really deserve the NC17 rating?

works thanks zmey

BS1 and 2? Not working for me in bs2? (may be me?) either --purposes = {render_purpose.GENERAL,render_purpose.HUD_ONLY_VIEW} --purposes = {render_purpose.HUD_ONLY_VIEW} purposes = {} my attempts

I usually leave alt-hold off when moving to/from areas*. If i need to enter hover hold it automatically comes on. Then say I'm trying to look over an obstruction, trees, building, etc. You can press and hold (f) the collective brake until you reach the desired altitude you want. At that point the alt-hold channel will set it self to that altitude datum, rather than your original height (auto hover engaged moment). Had you not reset the altitude datum, you of course would have sunk back down. You could also apply the tap methodology *Exception being if i'm going heads down and the general area is relatively flat. I won't stay in it long though...sneaky power lines....

fixed :D I guess that's always the hot topic. People know these classified systems exist. Does the military tell ED "you can't model this system at all" or "you can model this system but don't use the real world performance statistics"? I'm sure its shades of grey depending on the system/aircraft in question... Playing devils advocate... Does using these "adjusted" systems then make them fictional? How do we know the modeled 50 in game isn't adjusted for "public consumption" :book: I"m sure some people would argue that everything in game is adjusted because its "simulating" and hence not 100% real life match But see we're already getting into "who determines what is acceptable realism". I guess that answer is/will always be ED

Appreciated Accipiter. Part of me is with you, wishes we had something to defend ourselves. But I also understand why it's not being added; if you add this, what about other "possible" weapons. How do you draw the line? IMHO fixing the f5 "cheat"* would be enough for me to think that it wouldn't be as much of an issue. If that's fixed, and a pilot happens to stumble upon me, or actively searches and finds me, then kudos to them they deserve the kill. <hypothetical section and will probably pull this thread completely off topic> With the announcement of the "dcs core" in the april newsletter: What if ED starts adding these "100% not accurate to the model they, pardon my austin powers reference, modeled as chargeable mods. My initial reaction is "no", but at the same time would it be so bad to have AA on the ka50? Could Ed then have a "new" revenue stream, of creating almost 100% accurate aircraft and handling. I know they can't breach security and information to a certain extent, but what about creating their own "version" of say the ka-50sh. Again, I don't know what is top secret that they are not allowed to add, but they then could add in their own "device" that "improves night attack". It then jumps to, why stop there? Now they could start creating all aircraft without "needing" security clearance. Then it jumps to, who determines what numbers are "realistic"..and goes on in infinite. So while I would love to have AA, and would love to see ED have more and more profit (they are one of a few that I greatly appreciate have not "consolized" their efforts.) the purest in me isn't quite sure if I would like the end result. But I would love an AH1z :joystick:, as I'm sure others would want <insert aircraft that wouldn't be declassified enough to develop for 25 years>. </end hypothetical section> *not implying/nor "dis"-implying that the pilot that shot me down in the above screens used/didn't use f5

I see your point. Thanks for the insight (I must have just gotten so into the habit of automatically removing it :weight_lift_2:)

A little OT, but I would have thought the majority of controllers would be non-ffb. So I was/am a little surprised that the default was on. (not a big deal since ED does such a great job of making config so easy)

I usually experience this when I select the "wrong" trimming method in options, or if I forget to remove force feedback (I think, but could be wrong, that in 1.02 or lower you had to edit a lua file to remove ffb=on) Get bs2 the dynamic shadows alone are worth it :D edit: i had been running x52+logitech g27 without any issues so in theory mixing and matching shouldn't be a problem. Assuming you follow EtherealN's advise of course.

Are you referring to ai, or that humans pick up movement with their eyes? Or both? :pilotfly:

I'm def guilty of not looking outside the cockpit enough. This particular area that I was operating in was pretty flat, and the only concealment were trees. I assume the graphic engine would have me hidden behind those trees, say while s/he was tgp searching? Regardless of the a10's pilots tree draw distance? (In this instance I had not fired a shot yet, and was 15km away from closest wingman)

Appreciated. I guess I need to spend more time planning flight path before heading out.

Ah, that's weak sauce. Is that disable-able server side?

TLDR: Just wondering if anyone has any tips to avoid getting hit by human a10s. In west Philadelphia born and raised On the playground is where I spent most of my days Chillin out, maxin, relaxing all cool, And all shooting some b-ball outside of the school When a couple of guys who were up to no good Started making trouble in my neighborhood I got my revenge though (completely on purpose :)) Sorry for not cropping So, I know we are SOL if we are spotted. But does anyone have any tips for not getting spotted? I feel like these guys were finding me way to fast, but I have no idea what systems they can utilize. I was below 50p almost the entire flight. I did notice, at least on trk replay, that if you zoom out (like you are 15k above) the shadow of the chopper really stands out against the ground. Specifically against non-green fields. Just wondering if anyone has any tips?

Losing out to diablo 3 next month.... I told him i'd play diablo 3 if he gave bs 2 weeks...

Perfect thank you!

Bs2 Win 7 64 bit, logitech g15 but also applies to laptop built in keyboard I installed bs2, US is my default (ime) keyboard, en default language. But it appears the game picked up my keyboard as japanese. At the time of the install I had english and japanese installed. For instance if I hit the ~ key, the controls try to map it as "kanji" button. I wouldn't have a problem remapping, but I am not going to be able to replicate that key press in my hotas software. Any suggestions? I'm hoping there's an option in one of the lua's to switch from en-jp to en-us or something like that? I have tried removing japanese from the ime, but the game still picks up the keyboard as jp. Thanks