Neutrino

I think that's what I'm going to do but I'll need a 10 keyless keyboard to have room for the joystick on the right and a left-handed mouse for the left hand side, and then I'll have to swap everything around depending which game I'm playing. It's an annoying amount of trouble to have to go to just because there isn't an ambidextrious joystick with a decent throttle control though.

Once I've mastered the Stennis I'll definitely be getting the Super Carrier but I'm struggling a bit. I have a T16000M joystick and the throttle has about 2/3 of an inch of travel and is so oversensitive as to be almost useless for carrier landings, but as a lefty I don't have many stick and throttle options. Might have to try using the keyboard for throttle control or coming in with the airbrake out.

I tried the technique out doing crosswind landings and while I couldn't say whether it helped to slow the plane down, it did seem to me as if it made the plane easier to control and less liable to skid under braking.

Here is a video of a couple of Hornets landing. I notice that on touchdown once the airbrake comes out and the brakes come on the pilot uses full up elevator for the roll out. Thinking about it I can see a couple of reasons this might be useful. The extra downforce at the back will put more load on the wheels and reduce locking up under braking, and the turbulence will create drag and help slow the plane down too. I'm wondering is this a standard technique in airfield landings, I've never seen it before?

After dipping my toe in the DCS world a few times over the years, but ending up bouncing between it and other things, I finally decided I wanted one of the premium modules, and after another couple of months I decided which one I wanted and got the Hornet, and in the three weeks I've had it I've mostly been familiarizing myself with the systems and practising basic airmanship. Earlier tonight I'd finished some night flying practise in the Caususes, winter, 23:00, fine weather. After half an hour of circuits and bumps I taxed to the parking stand and shutdown. As the engine whine faded and the canopy opened I heard an owl and thought, is that in game or outside, (it was in game). Then I looked at the sky and noticed the stars were twinkling and I saw the headlights of a few cars (probably locals coming back from the pub). As I sat there listening to the breeze sighing in the trees I remembered all the hours I spent playing F16 Combat Pilot on my Amiga (which had a great dynamic campaign btw), and the thought occurred to me that in all the years since then I haven't got much of what I wanted, but God damn I've certainly got the flight sim that I always dreamed of. Thanks ED, this game is bloody fantastic. P.S. I'll still probably bitch about the odd thing that irritates me from time to time.

I'm trying to practise manual navigation, pilotage and dead reckoning in the Caucasus. But it seems to me the maps are not remotely correct which is making the exercise most unsatisfying. The moving map GPS display available in certain aircraft, and the high detail maps released by DCS display obstacles and points of interest using standard aeronautical chart symbology. These features include tall obstacles (typically smokestacks or antennas) of either 200ft plus, or 1000ft plus, and points of interest such as oil wells, quarries and mines etc. The correct placement of these objects is essential to any effective manual navigation, and in the case of obstacles also to flight safety planning. However what's shown on the map, and what's displayed in the world bear no relation to each other whatsoever. Obstacles and points of interest shown on the map are not present in the world, and those in the world are not on the map. Why is this? As a military sim accurate maps are fundamental to any kind of realistic mission planning. Pilots are expected to be able to be able to navigate effectively and complete their missions or at least return to base safely without electronic navigation aids. If it's genuinely the case that the maps are just all wrong it seems like it shouldn't be that difficult a job to fix. Just remove the antennas, oil wells and whatnot from their existing locations in the world and then place them at the positions shown on the map. Or instead update the map, depending on what DCS is using as the source of truth.

Is there any way to get the HUD to display the HSI heading bug? If there is I'm having trouble finding it. No nav mode, not using TACAN or waypoints. Just using the heading bug for manual dead reckoning navigation.

I have a Thrstmaster joystick with a throttle slider, however the throttle slider isn't very precise and stretching both hands over to one side the keyboard is very awkward anyway, so I'd like to be able to use numpad +/- t control the throttle. These keys can be bound, however a single press of the key moves the throttle by 3 or 4 percent making it so imprecise as to be utterly useless. Please either fix the existing throttle keyboard binding so that it can be used to actually control the throttle setting, or provide an addition fine throttle control binding for this purpose. Thanks.

FFS wouldn't it be a good idea to update the first post to indicate that this software doesn't work anymore? I've been sat here for three quarters of an hour waiting for it to create a damn snapshot. And unsticky the blasted post while you're at it!

Thanks, I suspected something like that would be the solution but couldn't find any specifics.

That seems counter intuitive, I'd have thought that bombing at a steeper angle would be _more_ accurate, you're releasing your bombs at a higher speed so they will be less effected by wind. If this weren't the case why would dive bombing ever have been a useful technique? I think I'm not explaining myself clearly. When you are approaching the target, flying straight and level at altitude 4km, you know where the target is but you can't see it because it's under your plane and you can't see through the fuselage, so looking at your attitude indicator doesn't tell you anything about your vertical angle to the target so you know when to dive. Similarly what instrument gives you a precise measurement of your range to the target when you can't see it, to enable you to calculate the point at which to dive using trigonometry?

What's the best way to line up a CCIP bombing run? The tutorial has you entering a steep -60 degree dive from about 4000m when hitting a nav marker. At this point the targets are nearly directly below you therefore you cannot see them beause they are obstructed by your fuselage, you only know when to dive because of the nav marker. In the absence of such a training marker, and ideally with labels off, how in a 'real' mission would you be able to set up a similar bombing run? How can you tell when you are at the right angle over the target?

To stop me from making the same mistake again How do you tell from the mission editor which aircraft are compatible with which airfields?

Thanks, I guessed it would be something like that.

Here's my mission. Su-25T ramp start at Kobuleti. Active runway is 07, I take off, turn left traffic back to the B3B waypoint, intercept NOC and the screenshot shows me on final, on the glideslope, no ILS. FreeFlight.miz

Probably worth noting that if I set the winds to 0kts ATC sets the active runway to 250 (which is the runway without ILS) so that seems different from what some of the last posters have said about how they got it to work.

I've always had issues with 7zip and rar files, it regularly fails to decompress properly. I've installed OvGME and the activated the Starways textures. It looks awesome, thanks very much for the hard work.

So I downloaded WinRar to unzip it, which works and unzips to a 1.7GB directory, but winRar is payware so it really sucks to be expected to buy payware utilities just to unzip a file. Also JSGME (which is what the OP says to use to install the mod) doesn't work in latest DCS, creating initial program snapshot fails with a steam read error, the JSGME thread is full of similar reports https://forums.eagle.ru/showthread.php?t=98607 I appreciate the hard work but I do wish people would keep their documentation up to date. Already spent an hour trying to install this, have to leave it to another time now.

What would you recommend I open this with? I normally use 7zip for archive stuff, but after downloading and running test on the archive it reports uncompressed size 25MB, compressed size 1.6GB and there are only a dozen files in it.

Is this now broken in a different way? I'm setting a 7 knot headwind on runway 07 (wind direction blowing towards 250 in the mission editor), I fly a circuit and hit the B3B (RTN) waypoint dead on, and no ILS. P.S. Tried it with 0kt wind too and that didn't work either.

Shouldn't the advert for the F14 module at least make that clear in the requirements then?

Hi. I'm contemplating getting the F14, it's still in early access but promises to eventually have two campaigns, one in the Caucuses and one in the Persian Gulf. My question is will purchasing the module include the terrain required for the Persian Gulf campaign or will users be expected to pay for that separately, taking the real cost of the F14 module to an eyewatering $130.

Has anyone yet worked out how to configure a usable external view in Flaming Cliffs 2 please? By which I mean an external view that you can rotate to look at your plane from any selected angle, and the view angle is fixed relative to your plane so that you always look at your plane from that angle irrespective of how you manouver. Or in short the standard external view that every single flight simulator has had in the history of flight simulators. The only external plane views I've found are these two: 1. Aircraft view. Where you look at your plane and can rotate the view, but the view is not fixed relative to the plane, so as you manover one minute you are looking in the direction you are travelling from behind your plane, and the next minute you are looking at the front of your plane in the opposite direction. Not remotely useful! 2. Chase View. Which looks at the rear of your plane but the view cannot be rotated. Instead if you move the mouse the view 'slews' away from the camera's origin such that you are no longer even looking at your plane at all. In fact once you slew away from a position where you can see your plane it can be hard to even find your plane in this view again at all. Even less useful! Anyone have a solution to this, pretty please?