Maverick-X

I agree with you. I've got the X52 (whats the difference to the Pro version except from black/red to silver/blue design? ^^) and imho it's the best HOTAS you can get for that price. It's not that well manufactured, but in terms of available buttons... I love it. (I use 2 Modes with pinkie and clutch button as modifiers, so 3 layers for each mode)

I recommend to get some knowledge about navigating through the CDU menus, where to find things about INS Alignment and how to create waypoints from given coordinates, either lat/long or MGRS. Thats quite easy to learn with some repititions and very useful. Also look up the controls (my combination is l-ctrl + l-win + button, dunno if thats default), you can do input to the CDU directly vía keyboard. Saves a lot of time

Iglas are quite effective low altitude area denial weapons. Hard to spot, but hit hard ^^ I've got quite some trouble evading them aswell. Preventive flaring does quite a good job against them. If possible use terrain cover, especially with threats behind you. Important thing when flying low with manpad threats is being lightweight. Forget those 6 mav's + hundrets of GBU's and CBU's loadouts, you can't put them to use when you are shot down anyways!

I don't understand why you shouldn't use the FD, as it gives you a much smoother flight! If some people are able to fly the Shark in precision with FD disengaged, fine. But I don't see how this is possible when the AP constantly tries to get back to set attitude while you try to change it... And the FD is way more elegant than just holding the trim button while you do anything apart from straight flight.

thx Eno, so if there are any suggenstions where to tweak files to allow fixed wing aircraft rearming when near FARPS? EDIT: unitsclasses.lua located in ...\DCS World\MissionEditor\data\scripts contains this: -- FARP (Площадка базирования авиации) ["FARP"] = "P0091000022", -- Airport 2 class (Аэродром второго класса ) ["Novorossiysk"] = "P0091000032", ["Khersones"] = "P0091000032", ["Gelendzhik"] = "P0091000032", ["Tskhakaya"] = "P0091000032", ["Kobileti"] = "P0091000032", ["Batumi"] = "P0091000032", -- Airport 1 class (Аэродром первого класса ) ["Simferopol"] = "P0091000033", Perhaps you could declare a farp as an airport, I'll try that tomorrow when I find the time. But is this a solution regarding multiplayer (if it works)? PS: just read the first line: "-- Units - icons conformity table", so that seems to be for map icons? I should go to sleep now ^^

Hey, I had an idea for a mission, this involves rearming of fixed wing aircraft of a provisional strip. This would be a bigger road for example. I tried a FARP near a road big enough for safe landing, but all I get is a blackened Crew Option dialogue, which you seem to get if you land anywhere (except allied airfields). Rolling on the farp didn't get me any further ^^ Is it by any means possible to get this to work? If I don't have to include a FARP that would be fine, just thought it was the easiest way to somehow give fixed wing aircraft a permission to rearm there, as they are able to store the required weapons. Thx, Mav

I'm in, filling gaps as needed. A10C prefered

Why shouldn't you be able to? You can load stations 3-9, except #6, so 7-1 = 6. OFC its questionable if you want to load 2 JDAMS instead of 4 Mavericks. (Please ED, simulate burned tires from inner Mav's so these 6 Mav's + 1000 GBU12 loadouts disappear ^^)

Afaik Yurgon is right on this, the TGP uses elevation data, therefore lasing the target gives you higher accuracy in terms of target coordinates. But still, the GBU 38 is not that accurate. I can launch from steady flight with target perfectly aligned and SPI right on target, the Bomb still misses by ~2m, which is enough for a MBT to survive the attack. Everything else still gets busted w/o big problems, but if this behaviour is correct and I don't do something wrong it is not suited as an antitank weapon

Propably said by some1, but I'm to lazy to read the posts, so here are my 2 cents: the A10C is easier to fly, as it is a fixed wing aircraft. The Avionics although are more complex and take a lot of time to understand completely. The Shark is "easy" to fly once you know how, but that takes some time. Combat employment is quite easy, but being effective requires precission in flight. I personally like both very much as they are simulated in detail and are fun to fly. But on regards of battlefield survival the Shark is a bit tough to master. Your only warning system is the laserwarner, so you don't have a missile- or radarwarningsystem, and you don't have rear hemisphere visibility. In fact, fly the shark if you find Helos interesting or the A10 if fixed wing is what you like ^^

I don't think rockets are affected by set ripple intervals, which is kind of sad, as deployment of S13 rockets at a single pair is really not easy. I try to push as shortly as possible, but I usually get off 4 rockets at a time. The bigger rockets are limited to single fire, never tried to fire them rapidly, but I guess its about the same thing: if you are good enough to fire single pairs of S13, you'll get a pair of S24's off rapidly, too ^^ If I'm mistaken and there is a way to limit the amount of rockets launched per trigger squeeze, please enlighten me!

Complicated is relative, but regarding the engine type, and the design era, these engines aren't only inefficient at low altitude. They are simply inefficient! It's the same problem with the A10, a full loadout with every possible TER fully loaded and (hopefully not) full internal fuel, some guys really dare to wonder why they can't dodge a SAM... So Weaponload adds weight which adds to the fuel consumption, as more lift has to be produced. Produced lift creates drag: C_d = C_0 + k* C_a^2 (C_d is drag, C_0 is zero lift drag, k is a factor regarding wing layout (elliptical lift distributuion [spitfire] is ideal - k=1) and C_a is lift) And then there is the shape of the loadout on the hardpoints, which adds a lot of surface bathed in the air and therefore creates additional drag. So as you see, a heavy loadout extremely affects flight performance. It's not that noticable with the A10, as it has very fuel efficient engines and quite large tanks. I guess (as I don't know it for sure) that the Su25 is usually equiped with at last one pair of ext. tanks. In fact there are many combat aircraft that are usually flown with ext. tanks, as for example the Mirage family, the F15...

Or you just use your HSI for navigation while using the Radar... Always shows course, track and range to your current WP. The Su is in advantage over the F15 in many terms, the RWR can't show you exact contact type, but you can read range and relative elevation. AWACS contacts are shown on the Monitor, so you don't give away your Position by using your own radar and have a advantage in situational awareness. In addition, there is the IRST mentioned by Humbug, which enables completely silent tracking and engaging (with IR missiles), as long as the target is quite hot / you face the engines. Very useful! Sadly no active radar missiles for the Su, but I still favor it

It is sufficient to delete ...\savedgames\DCS\config\input\UH-1H

Perhaps reset the controls in DCS? If problems remain, create a profile from scratch. You could aswell use a profile available in the database or I could upload mine. But creating an own profile is useful because you know the button bindings and don't have to learn them as much

If Q is the Autoturn to target button (don't know the Keybindings), then it should, if: -autopilot system is undamaged -heading channel is engaged -flight director is NOT engaged (no steering by AP if on) Are you trying to use it while in motion? I only used it while hovering, so don't know about turn2target while moving.

sry, messed that up. you obviously turn the FD on to shut the AP-steeringauthority off... Rest should be accurate though ^^

Just watched the track, although trk files are inaccurate... (first time i watched "you" crashed into a hill ^^) You abuse the autohover: correct procedure is coming to a hover, retrim and then activate autohover. Consider it more of a hover-hold! I don't exactly know why you weren't able to fire the Vikhr as all systems are set accordingly. I recommend to review your controls. Firing goes as following: lock the target and select the Vikhrs, position the reticule over the target and hold the missile-release button for more than .5s? Some tips for the autopilot: autohover engages altitude hold channel, deactivate that when you stop hovering. also deactivate autohover while moving! For dynamic flight (meaning everything thats not flying in a straight line) try to turn off the flight director (5th button at the autopilot channels). This disables the control authority of the autopilot, it is otherwise able to control the Shark with 20% of the maximum input. Basically the autopilot tries to maintain the attitude of the moment trim is applied, so it will always try to steer back to that attitude. With FD disabled, you still have the input smoothing of the autopilot channel, which makes flying easier, but you get rid of the steering-interference of the autopilot. Same thing happens while holding down the trim button, so in order to change trim, hold the button so AP-Input is disabled. Then steer to the desired attitude and release the button. Otherwise the compensation of the autopilot will cause these bumbs experienced while just quickly pressing the Trim-button.

You should try to fly with flight director disabled. (5th button at the autopilot channels). This way the input correction of the AP still works, but it wont try to hold the trimmed attitude by itself, so it is really just a trim. Thats basically the same as holding the trim button down. But keep in mind that route following, alt hold and hover hold wont work wile FD is disengaged! With FD disengaged it is far easier to change attitude as the AP does not constantly interfere. For rocketruns it is imho essential to disengage it to get a steady aim.

Easiest way of spotting enemys is looking out of your Pit and using zoom. If you have an Idea where the enemy is, try to find some landmarks you can easily find. Once found a little black dot, point your shkval on it and identify them. Use the landmarks to quickly reaquire your targets for the next pass. Memorize your heading for the passes to make it easier.

Moving a throttle from cutoff position to idle in order to start the aircraft is always done with alt/Gr / ctrl + home, assigning an axis for this is not possible. Moving both throttles (idle and above) can be done with setting the "slider 1" or whatever you want to the axis "both throttles".

Thats an interesting topic, as I personally feel like "I got the rockets, why bring em home?" and on the other side "ok... you want to go in... but you'll get yourself killed!". How often do you get out of rocket runs without even the need to repair because something important was shot? I mean, ofc I will run in with rockets when there are 2 MTLBs or similar left... But if the number of units is bigger or there is something with a good autocannon like a BMP or a (by any means way too effectivy against air targets) BRDM? No Cannon, no attack for me...

I'm not able to watch trk files atm, but clipping rotorblades is possible at high speeds: The lower rotor turns counterclockwise, therefore the right side experiences a higher velocity while in forward movement. The resulting lift lets the forward moving blade bend up, leading to crossing the upper blade area if sudden/hard steering actions are made. In short: only very light manouvers at high airspeeds! The problem with AI landing seems to be a stop in collision avoidance. I tend to let the AI land first, as long as I don't know which pad is the AI's destination.

a bit off topic, but proactive flaring works as far as I can tell. I've been doing a bombrun against infantry (Bactria) and flared 1 flare each second. Got an Igla launched at me, and stupid as I sometimes am I continued my attackrun as I was short before release. After the drop I realised my stupid move and the fact I was still alive. SHORAD got immediatly distracted.

The speed indicator will be visible when caging the skhval again. All necessary information can be retrieved from the analogue instruments without much looking around. The laser won't overheat as long as you have engagement rules on auto. If you fire manually however, you can overstress the laser when continously firing vikhrs. This however is only based on my own experience, perhaps there still is a way to overheat the laser on auto-mode