Herastean

Absolutely would be a great QOL improvement.

For heaven's sake... Yes. Please. I'd be okay with a little "dirt", not this. The MFD looks like no-one cleaned them in years. Give us an option if must be, but I'm sure a "real" aircraft would have cleaner screens than this. I mean if a flock of birds <profanity>s on the pilot's canopy, I don't expect the ground crew would be like "Eh, just take off that way, it'll be fine."

Seems like it! Can't wait to fly that thing... Too bad there's no JDAM yet! I guess we'll have to settle with GBU for a while! Going to go old school on those T80s!

Okay finally! Thanks to a post from 2015 (phew...) I had to go to device manager, uninstall the 3 Throttle plugins, remove the drivers, shut off the throttle, restart, replug and now I have perfect control over the throttle again. For some reason, it appears to be the drivers getting corrutped in some manner. I installed a new headset yesterday, that's what might have triggered the bug! Relieved... Now back to business!

It does so on every aircraft I own apparently. I've also been checking if my throttle axis wasn't bound to another key, apparently not. JOY X is only bound to thruster or collective on all these aircrafts unless I'm missing something.

Hello there folks. Yesterday I was playing, everything was just fine and superb. Today I log in, I notice that my throttle jumps from 0 to 50% in the axis tune panel. I check on my software, the throttle moves perfectly. I tried to calibrate under windows... No can do for some reason. Anyway I have no idea what the heck is going on, and since it moves properly on the software, I don't believe it to be an hardware related issue. Any fixes for that? The only ones I could find are rather old and they don't seem to work for me. Thanks people!

I am curious about this myself... Are we ever going to get an AI for the door gunner? I mean, this is implemented in the other helicopters, so its not going to be too much of a bother for the devs to implant it in this module I suppose. We definitely need this, so far the Gazelle has been a big dissapointment in the fact that, while its a superb platform, it lacks what the other helicopters have... I fly on a server where troops invade cities and what not, so we need helicopter patrols to circle towns and shoot down moving infantry, and I'd like to take this beast on patrol over there instead of having to rely on a Hip or Huey.

Thank you for your help!

Hey there. Been using the autostart since my RIO isn't familiar with startup procedures. Thing is that when JESTER does the startup, my heading seems to be off by atleast 20 degrees. Is it only since the last patch? Also, I'm starting from an aircraft carrier. Thanks for the input. Edit : If I set up a TACAN beacon, the alignment seems to be figuring itself out, so its a fix... But no idea if that's still normal or not.

Salut Flappie! Thanks for the input... I'm an idiot. I've been asking around and people apparently used 91XX without a problem, so I guess we were miscommunicating. I'll try that out next time! Also for the second problem, I am guessing its a new bug. Didn't happen before the latest patch. i'll try it again this evening if possible and see if it happens again.

Hello there. I find myself sometimes having to turn my engine off to repair, and by so, lose electricity. Due to the plane having to "float" above ground for the crew to repair, I can't have the ground power on. Is there a way to make the whole flight plan, including LS, L1 and all the waypoints from the F10 map? I know its possible for BX, MX and a few others, but can LS, L1 and L2 also be put into the cartridge that way? That'd allow me to restart and align at a new airfield rather than to have to go all the way back to my main base when our forces advance. Thanks!

Hello there. I happen to have two different problems : First : When I try to input a secondary airfield, I use the code 91XX. Thing is that it doesn't do anything. L1 and L2 stays the same. I can only change L1 by using 90XX. Any idea why is that? Second : Today I took off with a full complement of dragged bombs. Went to my target, bombed and turned back to rearm... Even though I put the trigger back to safe, I still had my CCIP bombing HUD on and overlapping with what ever I would use... ANF, LDG or anything. Tried to rearm and go on with my mission, this time with RB75... I couldn't use them. Scope wouldn't turn on and I'd only have bombing marks on the HUD, even if I were using the right dial on the ship. Anybody ever had that?

I keep L1 as my starting airport, as in a safe spot to go deep into my territory. If a closer airport is available, I input its number as L2 to go there and rearm quicker. I have already tried to switch to L2 without having me input it... It does nothing wrong, the computer just sticks to L1. I think that this was my problem. Been using the RB75 alot those days and it does seem to be a little tricky sometimes with it failing to "re-align" and so I end up hitting "TV FIX" too early or... Just that problem I've explained before. Changing waypoint before going "NAV" again.

Just happenned again, here is what happenned : I was in ANF mode for a bombing run. I deliver my weapons and select "L2" so I can go toward my landing spot. I align with that position and now I select "NAV" and immediatly my waypoints jump around. I think this is whay may be causing it. I should probably switch to "NAV" before changing my waypoint. I believe that this is what have been causing my TERNAV errors. Also... How do I get you this file you wanted? First time I post about technical difficulties regarding the planes rather than the program.

Hello there. Been picking up the viggen again lately. I'm having troubles with the TERNAF. Quite alot of times, after flying for a little bit, I'll start having some drift, which is OK because I can just realign the radar poisition myself. My main problem is that sometimes my waypoints remain OK, but my landing airport simply flies off the map. Any idea whay might be causing such a massive drift? Thanks

Thank you so much for your help. I'll give that a try ASAP.

That sounds very plausible. I am always keeping very straight attitude, but I might be way too low. So the second bar appearing might be the pull-up queue. I always fly my viggen super low. And in my attacks I rarely pass the 100 meters altitude. I like my attacks to be way under radar's capability. I'll give it a try, being higher when trying to fire. So the "second bar" appearing to the side has nothing to do with accuracy? As the firing queue flashes, I still have to fire within 2 seconds to be almost certain to hit? Not wait for the pull-up and the line to flash once more to indicate fire?

Hello there. Been picking up the F18 after a very long break and everything works fine... Except the countermeasures. First, can someone pinpoint me to the file to modify to save my programm? I tried, and it did save, but its not loading in game and its annoying to input it everytime. Also. I have tried to set the CMS in AUTO. It does absolutely nothing. At all. Not a chaff, not a flare. Nothing ever, even when I have a radar missile on my tail. In SA, I have another problem. If I press the Chaff dispense... It just starts dispensing chaffs and flares like a madman. I mean, I am getting locked by a FOX1/3. Shouldn't it just dispense chaffs? And dispense flares when I'm not being locked by anything but I press the dispense button? I really need some help with that. I've been looking at the manual and I don't see what's I'm doing wrong.

I'll try to make a recording when I figure out how to do that. In the meantime, I'll just get screen shots to try to explain, or find existing ones and post them. But basicly. Yes. The firing order blinks 2 seconds before... But it does that 2 times. Once, there are 1 bar on each side of the targeting dot. It blinks for 2 seconds. A second bar appear on the side, and the firing queue starts blinking again. Very hard to explain, I guess a video or pictures would be easier, but that's why its confusing me. Everything on the viggen is super simple to understand but I'm really having trouble with that part.

I would sell my soul to the devil to be able to fly the F117.

Hey there. Been experimenting with a few weapons. Bombs, rockets, etc. I find myself rather accurate with bombs (then again, no need to be perfectly accurante for those.) And much less with rockets. I'm always falling too short or too long. This is that my "firing order" blinking comes... Well, at weird moments. Logicly, when you're between the "wings", it should blink and you should be able to fire precisely, right? It sometimes blinks way before its in the "wings", sometimes much later and... Some other times, I have no idea why. I get the signal, then it shifts and instead of having 2 bar on each side of the dot, I have 4 after, and then it starts blinking again. Been trying to find an explanation for all that, but I can't find any and I'm totally confused about all this. Anybody mind helping me out? Thanks

Works for me on hot start or cold start. I'm guessing you should repair the game. Or maybe something on start up you do wrong or so. No real idea on that one mate.

I'm mostly on 4YA or Fraternity. Sometimes IRAF server too. And yeah, finding other Viggen pilots is very rare! I actually do like to coordinate strikes. The Viggen carries so little next to the A10 or Harrier, it requires to be teamworking. I can't wait for the maverick to be fixed. Nothing like a flight of Viggens raining death at 1000km/h. Do chat me up if you see me in game, I have the same nickname there.

I know! I've missed my super-fast attacks when the A10 lags behind! Heatblur has my total trust. The Viggen is amazing, so is the F14. I'm guessing the problem here is the new DCS version... Which caused more problems than it solved.

Nah. Its still broken after the patch. I would have expected it to be. I'm guessing the recent update, which has broken alot of things, broke things so much it makes Heatblur struggling to fix it. I've never been dissapointed by the studio before. All the things they were late on were due to limitations of the game, like BK90 back in the first months of the module. Guessing its another of those new versions bugs.