Jalava

And Marshal and LSO act like you are CQ because they call Charlie on everyone and you have to call the ball. I believe normal cyclic operations are ZIPLIP with signal charlie only given to one breaking the deck.

Going into ACM will swap the radar axis and also if your radar elevation isn't centered in the middle the VACQ mode will be biased and won't work either. Interesting to see that coming back to BVR doesn't reswap the axis. Try going back to ACS, undesignate and then for BVR. That would confirm axis are always swapped when going ACM but not swapped when going BVR

All JDAM stores and missions seem share elevation unit and changing from Meters to Feet will not convert elevation in other stores. How to reproduce: - Load two GBU-38s - Create waypoint in HSI with Elevation 177 feet. - Set one GBU-38 as TOO and set that waypoint as TGT. The waypoint is now copied into JDAM TOO mission with Feet elevation automatically converted to meters as indicated by line "53 MTR WGS" - Now setup second GBU-38s in PP1 so that it uses any elevation but set unit to feets. - STEP to first GBU-38 store. - Elevation for TOO is now shown as "53 FT WGS" even though it is still bound to TGT at 177 feet. - Setting the waypoint again does not fix this but the unit shown is stuck. I haven't verified if actualy waypoint elevation in JDAM TOO mission is actually correct due to just small error in height, but I can attest at least to unit indication being incorrect and should be unique for each PP and TOO mission?

But for non-CQ opeations, shouldn't the "charlie" be called just for the first one in stack (the deck breaker) and rest will then follow the traffic in stack and move down as planes leave the stack (two planes in 180 degree phase per altitude)?

With my 32:9 Samsung CRG9 screen mounted pretty close, TrackIr5 with Track Clip Pro works perfectly after I adjusted sideways curves to match my preferences from a track ir profile I found on DCS User Files. I view 180 rearwards on when my head is turned so that I watch about 20% of screen width in front of me. On 16:9 this would be already outside the screen. I watch directly up when I look to about top 10% of screen and then my downward curve from center is pretty damped you rarerly need to watch directly down so I need to watch much lower than screen edge to watch directly down but only a bit downwards to take a quick look at MFDs when I'm zoomed in so that I can only see HUD and tops of my MFDs. I don't use pause at all but TI5 needs regular recentering when you adjust your seating position, headset moves around etc. I use Warthog HOTAS with CTS script, so it is mapped to S3+S4 in all my planes and works great. It also maps pause to S3+H2D but I feel that if I need to pause, I'm probably spending too much time head down anyway instead of scanning. Main tip I can give is: If you have head position that feels wrong or uncomfortable, adjust the curves to have your head pointing to a comfortable position when camera points at direction you want to.

Just a note tower give QFE, not QNH. QFE is relevant when referring to AGL levels like pattern altitudes etc. Normally when AGL is relevant, I'll just fly on radar altimeter and visual. In IFR conditions, you should set altimeter to QFE for approach to ensure you have alternative altimeter indication.

I found out that extending my Warthog Hotas stick by 75mm using extension from MFG, everything just came so much smoother. Without extension, regardless of non-linear curves I just could not keep up with the corrections required around the center. Also make sure that you angle the stick so that when you are pulling towards you, the joystick actually moves towards you and not side. It doesn't take much to cause circular oscillation as pulling back may cause right bank and correcting back then introduces left bank if your "force vector" and joystick are not aligned.

On mission 5, the downed MI-8 seems like that if you don't get direct hit with GBU-38 but try to take out other targets, it will turn nigh invulnerable. You'd think heli with blazes flaming out of the engines in ground would be considered destroyed, but even additional 6 rockets and 500 rounds of CM didn't explode it :) Having a option in F10 for reporting it destroyed would move the mission forwards instead of just requiring abort.

Currently for some reason OSB20 and Right MFD Gain does not send correct kb commands on A-10C. Looking at event tester i can see that NVG gain is sent as LShift+RWin+Pgup / Pgdn, pressing S3 and NVG Toggle doesn't send any kb events but does seem to flash DX24 and DX32 on release. On my DCS A-10C Sim, NVG Toggle is set as JOY_BTN30 + JOY_BTN32 + JOY_BTN20 and gains are 30 + 32 + 28/27. Is this correct?

I cannot seem to pass the illumination flares mission no matter what I do. I've now visually verificably flown this mission for at least 10 times through. First I noticed that I have to fly over IP quite exactly, so that is solved. However, I'm very unclear on how should I do the drop of the flares. Parameters say that within 1Nm and under 6000AGL, so I tried doing that at altitude lower than initial 8000AGL (Mission could have note about that too). Also for fast target management, I've tried both setting initial mark points beforehand to WP areas and also sestting EL of target WP:s to 0, so I can slave my TGP to ground level immediately. I've tried to do this by dropping those flares in multiple different altitudes like 5250, 4000, even almost point blank at just 500 feet by practically divebombing the flares in place over trucks. Most of the time I do get 2 AWAY message, but not even that always? I noticed that there are two lines of visible trucks at Target 1 WP, one bit further from the WP itself, maybe this is the issue? In addition, should I drop flares on top of WP or on top of units? I haven't received notification about hit on any other waypoints either, except flying over last waypoint I get message that says basically well done, head for egress. After landing though, I keep getting rating U. Having message to tell which objectives you failed on mission would help me debug my flight. Now there is no way to know if mission decided to fail due to bad illumination or for example me doing shutdown procedure in non-kosher order (like turning off MFCDs while still in motion near parking)

It should work when set as keystroke assigment. Have you the latest gamepanel software installed, just noticed myself that there were update for mine. I use similar setup with RALT+Arrow Keys for china hat -> G16, G17, G18 (I have the old model of G15 which is basically G11 with flip out LCD screen, not the black+orange model) I'll include my keyboard profile for reference, works for me. (It might be that there is issue with sending F-keys with modifiers on G-software?) DCS A-10C.zip

MSFFB2 is very accurate, though throttle slider is way to small. However, it's discontinued few years back so you might have trouble finding them in new condition. Also see: http://forums.eagle.ru/showthread.php?t=35243

I currently own MSFFB2 but I'm afraid that one day it will break and what then? Is there any other precise, sturdy and fullrange ff joysticks in the market currently as FFB2 is discontinued? I'd prefer to have more buttons and perhaps HOTAS setup also, but currently I don't know if there are any FF+HOTAS products in the market.

Getting MSFFB2 might be bit tricky considering it came available 2001 and they discontinued it over 5 years ago or so.. I'm just so hoping that Logitech would come up with G-series replacement for this, the G25 wheel and G15 keyboard has been top notch for me, especially the wheel and pedals.

There is no reset trim in real KA-50, it's just in sim because beta testers really felt it was necessary. Btw, with proper ff joysticks (MSFFB2, is there other good ones left?), zore-force position is actually where you press the trim. However, I feel there is some bug in trim because clicking trim while position is set causes strange fluctuation in pitch unless you keep trim pressed for while and stabilize the position again before release.

Ah, I see, that's exactly what I did when couldn't get tracking. Slew to target, range check, fire and correcting los on shkval while moving sideways and yawing nose towards target :) Pretty easy from <4km ranges... though that's when they start firing back at you :)

I think you are thinking different mission, in dusk you fly over the border and mountain range and then descent to destroy a camp near lake. You have lots of BMP-2, BTR-80, T-72 to destroy, air-support helps initially with air-defenses but after that they just leave. And it's not really that dark in there, almost normal day-light conditions. http://jalava.stc.cx/dcs/dusk_complete.jpg Thing is, from certain directions, I can't get lock even from 4km, from some directions I can get lock from 8km. Any idea what that ЧД means in hud when attempting to lock. Because I do get range measured properly, but no TA lock, it just skhval screen just keeps at TГ while hud says ЧД and counter counts down for cool down. Can I improve the locking by adjusting the skhval contrast and brightness settings?

I know, but low-light conditions shouldn't affect laser-lock, as the laser is reflected in enhanced manner in low-light conditions, right?

What I hate most is AT-5 Konkurs (ironically, in Finnish Konkurs is bankcrupcy in english :P) fired from those BMP-2s. No warning and damn they hit well for a anti-tank missile. Not sure if they are actually used for that because in reality, as they are mean for ground targets only?

I was wondering that when flying the mission Dusk in first campaign, I had severe problems locking to targets. After pressing lock, the hud just said ЧД and i just couldn't find that from my manual anywhere. Then I thought that perhaps smoke and heat rising from wrecks in front of me might block proper laser lock and circled to the side of target area and suddenly everything worked. However, I'm interested in undestanding different HUD states while targeting that might occur and if my hypothesis was right. Man that mission was hard to do, I alway ran into trouble when out of missiles and had to close in for rockets :)

Yeah this happens with me too every now and then after flying few attempts in campaign mission Dusk. My setup: X2 6000+ 4GB DDR2 800Mhz ATI HD 4870 with normal clocks Microsoft Sidewinder Mouse (installed as regular mouse to prevent crashing with newinput.dll) Logitech G15 keyboard SB Audigy Platinum Ex Powered with 600W Zalman Heatpipe Here is my system.log from that run: SoundManager: Starting... SoundManager: DirectSoundEnumerate DXMixer Primary Sound Driver : Starting... DXMixer Primary Sound Driver : Start succeeded DXMixer SB Audigy Audio [9C00] : Starting... DXMixer SB Audigy Audio [9C00] : Start succeeded SoundManager: DirectSoundCaptureEnumerate DXCapturer Primary Sound Capture Driver : Starting... DXCapturer Primary Sound Capture Driver : Start succeeded DXCapturer SB Audigy Audio [9C00] : Starting... DXCapturer SB Audigy Audio [9C00] : Start succeeded SoundManager: Start succeeded Sound Card Information: 4000 Minimum sample rate specifications that are supported by this device's hardware secondary sound buffers. 191999 Maximum sample rate specifications that are supported by this device's hardware secondary sound buffers. 64 Number of buffers that can be mixed in hardware. This member can be less than the sum of dwMaxHwMixingStaticBuffers and dwMaxHwMixingStreamingBuffers. Resource tradeoffs frequently occur. 64 Maximum number of static buffers. 64 Maximum number of streaming sound buffers. 62 Number of unallocated buffers. On WDM drivers, this includes dwFreeHw3DAllBuffers. 62 Number of unallocated static buffers. 62 Number of unallocated streaming buffers. 64 Maximum number of 3-D buffers. 64 Maximum number of static 3-D buffers. 64 Maximum number of streaming 3-D buffers. 62 Number of unallocated 3-D buffers. 62 Number of unallocated static 3-D buffers. 62 Number of unallocated streaming 3-D buffers. 0 Size, in bytes, of the amount of memory on the sound card that stores static sound buffers. 0 Size, in bytes, of the free memory on the sound card. 0 Size, in bytes, of the largest contiguous block of free memory on the sound card. Loading error: bleeper is zero - class wHumanHel Creating error: bleeper is zero - WarningTone1 Creating error: bleeper is zero - A10_AutopilotEngage Creating error: bleeper is zero - A10_StallWarnSteady Creating error: bleeper is zero - A10_StallWarnChopped Loading error: bleeper is zero - class wHumanHel Loading error: bleeper is zero - class wHumanHel Loading error: bleeper is zero - class wHumanHel Loading error: bleeper is zero - class wHumanHel ObjectSounder-Play() error: bleeper zero pointer - class wHumanHel ObjectSounder-Stop() error: bleeper zero pointer - class woAIHelicopter ObjectSounder-Stop() error: bleeper zero pointer - class woAIHelicopter ObjectSounder-Stop() error: bleeper zero pointer - class woAIHelicopter And error log: 12/17/2008 22:55 warning: no weapon sensor for host 17661002 warning: no weapon sensor for host 17661002 not sure if this helps, no crash file was generated as audio was still running but 3d graphics was just stuck and could only move mouse pointer (which rendered itself as yellow cross)

can you actually send coordinates from ABRIS to PVI? Or do you need to do this by hand? Btw, was ABRIS added to KA-50 late-on, or why it is so separated from everything with all input and no other outputs than screen?

Principles of Helicopter Flight is quite expensive book, over £100 in amazon.co.uk :o I think also this one might be good one: Without Parachutes: How I Survived 1,000 Attack Helicopter Combat Missions In Vietnam by Jerry Childers Includes 13 rules of Helicopter Combat Missions, which are still in use, though modified.

+1 DCS:BS is most enjoyful combat simulator for me in long times. Heck, it's the best any simulator i've every played combat, GA, racing or otherwise. The attention to detail and handling is so great that even with bit lacking ground graphics and AI, it's very immersive and has huge playability. Last helicopter simulation I really enjoyed was THX and Gunship2000, after that for some reason I switched out of combat simulations for a long time. Though I did play Comanche vs Hokum but I found it bit repetitive gamewise. Any news on which DCS modules are coming next? I really really would like to see Tornado make re-entry to simulation market, the tactics with Tornado (low-riding, lobbing bombs across hills etc) would fit well against Hokum in combat simulations. Jalava

Yes, thats the mouse.