Cruiser18

I completely agree, both the F-14 and Viggen are amazing modules and sets the bar really high for others to follow. Please keep doing what you are doing Heatblur. ^^

Have you tried using Right CTRL + Enter and having a look at what kind of inputs is being made as you take off? Might have some weird trim settings or other periphials making changes.

I tried out the dynamic deadzone filter, but it hasn't worked for me. I still get plenty of jitters with my rotary on the throttle.

Isn't Jester capable of punching in a target coordinate in the flight computer? A JTAC doing a 9-line should have provided you with a coordinate of the target he wants you to hit. Just have Jester add that to the computer and fly towards it.

Can't you just switch off the Intercom? ^^

A tip for how to do it on the ground: While parked on the ground, open the F10 map and locate yourself. Note the exact LAT-LONG position of your plane. Create a waypoint using that position. Switch your current waypoint to be that new waypoint. Do the nav INS update (no radar). Since you are right on top of the waypoint, you should get a pinpoint precise INS alignment.

Have you tried pressing Right CTRL + Enter and check what the control inputs are showing?

I noticed that you unsafe your trigger way ahead of seeing the target. From what I gather from the manual, and personal experience, when attacking a target using the ANF mode, whatever you have the target reticule on when you unsafe the trigger, will become your target by radar ranging. Therefore it is important that when you do the runin on the target, you visually aquire it, place the dot over it, and then unsafe the trigger. The computer will now aim to hit that position. Since you unsafe your trigger so early, I'm guessing the plane defaults back to using triangulation and using the radar ranging to help with that. No wonder you are having trouble hitting the target. *Edit* Actually, nevermind. Just doublechecked it, and it seems that indeed, the DYK bombing mode doesnt care when you unsafe the trigger, it will continously calculate the release time for whatever the reticule is hovering over once trigger is unsafed.

I feel old now...

Maybe all the cheap modules have these "small features" implemented, because they can spend so much time on it, since they dont have any "big features" to worry about. ;)

The Viggen gets really twitchy when using the wheel brakes. I prefer to use the reverse thrust to slow down before applying any kind of wheel brakes, as wheel brakes will easily make you swerve all over the place which is not something you want while landing.

Tried out the Instant Action "Rocket Attack" mission last night. Went in with "Anf", set to "Attack", proper QFE set and radar ranged the convoy while running in. The rockets hit right on target and completely trashed the center of the convoy. They seem to be working just fine for me.

Like Corvinus says, if you do a bad position fix update or by accident, then you can use the RENSA button under the cover just below the computer inputs keypad. One click on it will revert the last position fix you made. Two clicks will revert all position fixes you've made.

A big fat thumbs up from here. Keep up the good work. :)

Okay, that fixed the problem. The "Speaker & optional Mic Output" setting was set to use "Headset Earphone Steelseries Arctis 7 Chat" audio channel. I changed it to use the "Headphones Steelseries Arctis 7 Game" audio instead, and now the SRS communications properly come from left and right earphone. Thank you for the help. :)

Damn you are right. Just opened the chat output for the headset, and it only uses 1 channel, 16 bit, 48.000 mhz. That would explain it. I'll have to see if I can change it to two channels, or move the chat sounds over to the "Game" audio channels instead.

I'm using a Steelseries Arctic 7 Wireless headset, but I have DTS turned off as it sounds quite bad to me. Here's the .CFG file though. It seems to be saving the settings properly, but it just doesn't take effect in the software. *Edit* Actually wait, I searched through my Steelseries software and found that when i launch DCS, it also uses a sound profile that has DTS enabled which might be what is causing the problem. I will have a look and see if it fixes things. client.cfg

My Simple radio does not obey the rules I set up with fx Radio 1 using the "left" audio channel and radio 2 using the "right" audio channel. Everything just comes out as "Both" all the time which makes it hard to differentiate who is talking. Any idea why SRS doesn't follow the radio channel rules?

I find that the easiest way to air refuel is to line up somewhat with the drogue and then engage the autopilot. It will keep your plane going straight and level, but still allow you to make course correction inputs with your stick. In AP mode these corrections are greatly numbed, so you stand a much lesser chance of overcompensating your inputs. I managed to connect within a minute or 2 on my first attempt doing it like this.

I'm having a problem with simple radio standalone. Basically when I press the "Preview Audio"-button, I get a popup that says "Problem Initialising Audio Output! Try a different Ouput device and please post your clien log on the forums". After that the program closes down. Apparently the program really doesn't like my Steelseries Arctic 7 headset. I've attached the clientlog to this post. I'm running windows 10 64 bit version. I've tried uninstalling and reinstalling the program and installing and running it as Administrator, but nothing has helped. I've been trying to google the error message, but it doesn't seem to be very prominent. I could really use a hand here to figure out what is wrong. clientlog.txt

Put up a replay and let us have a look at what you are doing.

I've noticed this as well when my engine seized while doing the instant action dogfight against the P51. The engine would just instantly stop, and when I went back and watched the replay, I was quite surprised to see that my engine temps went from ideal to max temperature instantly when the engine stopped. This must clearly be a bug of some kind.

I generally use two ways to ID fighters when on the Burning skies server. The first is that it's only the German fighters that shoots green tracers. You can be fairly certain that if green tracers is being shot at something, then that's a badguy. Orange tracers has a good chance of being a Spit or P-51. Second, I look for the rounded wing shape of the Spit. The wings of the Spitfire is fairly unique in that they are rounded all around so that's usually a dead giveaway.

I don't know if it's just me, but I can never get the labels to work on the server. No difference whether I press Shift + F10 or not. Model enlargement doesn't seem to work either for that matter. Makes it extremely difficult to spot anything except when at point blank range.

Team Fishbed will win 25-15 Team Tiggen will win 22-19