Cruiser18

I'm "cheating" and using Virpils T50 throttle that allows me to adjust the detents. Makes life a lot easier especially for planes like the F18 where you hardly notice when the AB kicks in.

That's what planes do when you don't have a computer holding your hand. What kind of planes are you used to flying? If they are all FBW planes then that might be your issue.

Interesting. If I'm reading that correct, then the fully armed AA craft with more fuel at 20.000 feet, spend less fuel going at a speed, compared to a clean craft with less fuel? ...That seems wrong somehow.

When you say airspeed, do you mean throttle setting/engine RPM? Because airspeed is not really tied to the fuel flow, fx going insanely fast in a dive with the throttle at idle will let you have a really fast airspeed with very low fuel flow. So, are you trying to say that the fuel consumption is constant at a given altitude, no matter what the throttle setting is and despite the fuel flow gauge rising along with the throttle setting?

Didn't you receive mails with the product keys? You should still be able to validate them on the DCS site.

I read an account by a pilot on how to do carrier landings with the F-14 and I believe his words were "You are always trimming like crazy". But yeah, when you come into the brake with the wings swept back you should already be trimmed somewhat to keep the nose up because of the lack of lift from having the wings swept back. After the brake when you sweep the wings forward, the trim should be so that your nose will not drop hard because you lost so much speed, because now your wings are unfolded and you are already well trimmed.

1: Not sure, sounds like it should work from what you've said. Worked fine for me yesterday on GAW. 2: You have to unsafe your weapons (sounds like you've done that, since you can fire missiles) and you must also unsafe the gun with another little red switch that is down on the front left panel. It looks like a smaller version of the weapons safety switch with a little safety on it. 3: I don't remember the exact name, but the main buttons I've bound for countermeasures is called something like "Activate countermeasures program" and the other I use is "Panic countermeasures". On the panel at your right knee there's a row of switches for the RWR etc. Furthest to the right is a switch that activates the countermeasures system. The rotary next to it controls the program the dispenser will use. I usually set it to program 1, which will dispense 6 chaff when I hit the dispense button. Reference the kneeboard for what the different dispense programs do and find the one that suits you. Using the panic button I believe I pump out 6 flares and 6 chaff. This is nice for when someone fires a missile at me at close range as it should cover both IR's and radar guided missiles. For long range engagements, the regular program with only chaff is best because only radar missiles works at long range anyways and shooting flare will just give away my position. If you use the Eclair pod, which gives you way more chaff and flare, remember to activate it. Its the litle square box on your front left in the cockpit, hanging on the edge of the canopy frame.

I think of it in the way that Tacview shows the truth, because it does not care about the error factors that cockpit instruments are exposed to (damage, misalignment, air pressure, temperatures, inherent inprecision etc). Basically, your cockpit instruments give you their best guess at how fast you are going. Tacview has access to the "truth" and show you how fast you were actually going.

For me the manual is the reference when you run into something where you need detailed knowledge of how things work, like how to set up the weapons correctly, takeoff/landing speeds and other procedure stuff like that. With a new module, I usually start it up in free flight first to get the basic bindings done, throttle, stick, pedals all that stuff. Then fly around for a bit to get a feel for the plane. After that, I usually start digging into doing some takeoff and landings. Usually I will start working my way through the training sessions that might ship with the module. If there are no training missions available on early access launch for the module, then these days with we are in a situation with DCS where most modules are "handed out" to flight celebrities on youtube where they will show off the systems and procedures before the module is actually released to the public (usually as early access), so these videos are always available for reference if need be. Once all the basics are squared away for the module, I start digging into the advanced stuff, or the things that makes that particular module special. This is where the manual comes in handy to really understand how it works. A personal peeve of mine is to learn how to start up the module manually. Just sit with the checklist and start it up a good handful of times and then slowly put the checklist away and start it up from memory and if I can't remember a step I just quickly look at the checklist. I know that quickstart is often available for every module, but I really like starting up a module manually as a litle show of skill and besides you never know when ED is going to break the autostart sequence for a module. :P

I love the shaking of the F-14. It gives me a very easy visual and audio indicator of when I am overstressing the airframe. I dont understand the people talking about not being able to hear the plane. When I go into the afterburner detent, the afterburners lights on with a boom and keeps going with a rumble all the time. If only the F-18 had this. On that plane I most definitely are having trouble telling when I go into AB if it wasn't for the detent on my Virpil MT-50 throttle. If a person is having trouble hearing the afterburners on the F-14, I would think its an issue of really low volume or headphones of poor quality. Anyway on topic, I am against a slider for cockpit shaking and it's not just because it doesn't bother me. The shaking is how the real thing reacts. I believe that realism and accuracy should be observed whereever possible since this is supposed to be a sim. The shaking is part of the F-14 experience and should be treated as the challenge of flying that module.

Okay, I fixed the issue myself. I went over the source code and found that the program on startup will check for a "whitelist.txt" file where peripherals GUID's are stored. By default it seems this file does not exist. The source code does contain a GUID for the virpil stick and virpil throttle, but the throttle GUID was not correct. In short, all I did was make a "whitelist.txt" file in the SRS standalone directory and put the GUID for my Virpil throttle in it that I saw in the log file, in this case "204703eb-0000-0000-0000-504944564944". Now SRS recognizes my virpil throttle again and I can assign buttons to it. I did not find any mentions of the whole whitelist.txt file anywhere in the documentation, so I thought I should throw it in here for anyone else that might experience the same problem.

I'm having trouble with getting to bind keybinds with my Virpil MT-50 throttle. SRS simply doesn't allow me to bind keys to it anymore, despite being able to do that in previous versions. I took a look at the clientlog and I found this of particular interest: 2019-08-03 15:58:44.2042 | Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager | Found Device ID:6f1d2b60-d5a0-11cf-bfc7-444553540000 Mouse Usage: Undefined Type: Mouse 2019-08-03 15:58:44.2042 | Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager | Adding Device ID:6f1d2b60-d5a0-11cf-bfc7-444553540000 Mouse 2019-08-03 15:58:44.2042 | Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager | Found Device ID:6f1d2b61-d5a0-11cf-bfc7-444553540000 Keyboard Usage: Undefined Type: Keyboard 2019-08-03 15:58:44.2042 | Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager | Adding Device ID:6f1d2b61-d5a0-11cf-bfc7-444553540000 Keyboard 2019-08-03 15:58:44.2152 | Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager | Found Device ID:204903eb-0000-0000-0000-504944564944 VPC WarBRD Stick Usage: Generic Type: Joystick 2019-08-03 15:58:44.2152 | Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager | Adding ID:204903eb-0000-0000-0000-504944564944 VPC WarBRD Stick 2019-08-03 15:58:44.2152 | Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager | Found Device ID:014024f0-0000-0000-0000-504944564944 System Control Usage: Generic Type: Device 2019-08-03 15:58:44.2152 | Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager | Found Device ID:204703eb-0000-0000-0000-504944564944 VPC MT-50 Throttle Usage: Generic Type: Supplemental 2019-08-03 15:58:44.2152 | Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager | Found Device ID:014024f0-0000-0000-0000-504944564944 System Control Usage: Consumer Type: Device 2019-08-03 15:58:44.2152 | Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager | Found Device ID:12601038-0000-0000-0000-504944564944 SteelSeries Arctis 7 Usage: Consumer Type: Device 2019-08-03 15:58:44.2152 | Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager | Found Device ID:12601038-0000-0000-0000-504944564944 SteelSeries Arctis 7 Usage: -189 Type: Device 2019-08-03 15:58:44.2152 | Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager | Found Device ID:2e271e7d-0000-0000-0000-504944564944 ROCCAT Kone Aimo Usage: Consumer Type: Device 2019-08-03 15:58:44.2152 | Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager | Found Device ID:2e271e7d-0000-0000-0000-504944564944 ROCCAT Kone Aimo Usage: Generic Type: Device 2019-08-03 15:58:44.2152 | Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager | Found Device ID:508106a3-0000-0000-0000-504944564944 Programmable Hotkeys Usage: Consumer Type: Device 2019-08-03 15:58:44.2152 | Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager | Found Device ID:2e271e7d-0000-0000-0000-504944564944 ROCCAT Kone Aimo Usage: Ordinal Type: Device 2019-08-03 15:58:44.2152 | Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager | Found Device ID:18720b05-0000-0000-0000-504944564944 AURA LED Controller Usage: 255 Type: Device 2019-08-03 15:58:44.2152 | Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager | Found Device ID:2e271e7d-0000-0000-0000-504944564944 ROCCAT Kone Aimo Usage: Telephony Type: Device Apparently, the Virpil Throttle does not get a "Adding device" service like my Virpil joystick does. Why is that?

Remember that you cannot start the engine if you move the throttle as that will move it out of the starter position. I suspect that this will also prevent the quick start from working. To get the throttle handle back into the proper starting position, you have to click the litle button to the right of the throttle handle (think its called engine shutdown button or something). After that, don't touch the throttle again as that will pop it back out of starter position. Now try the engine start. Once the engine is running, you can use the throttle handle again.

Huh interesting. I've never experience having the rotors clash, no matter how fast I'm going. I only experience it when doing really sudden movements while going fast or making extremely violent combat manoeuvres. The ALT AP usually makes really smooth inputs and have never caused a blade clash for me. If you are worried about it making clashes though, you can just use the barometric altitude hold which will stop it from making any input changes while keeping you level. Of course that means you will have to avoid obstacles manually, but that would cause a rotor clash for you, same as the autopilot would so I don't see a difference there. ^^

I generally use the AP channels for all the trivial stuff where I can plan all the moves several seconds in advance, like flying between waypoints, takeoff, landing and setting up for a hovering position to shoot targets. Flight director I use when I know I will have to improvise a lot, like heavy combat maneouvres. Contrary to most people, I like to use the altitude AP while flying from point to point. Especially when flying low, it's handy to keep me from accidently hitting the ground because it slowly started ascending up towards the helicopter. Altitude AP with altitude radar will keep me at a set height above the ground even if it starts tilting a bit (unless it tilts A LOT, like with a hill, but I should really be paying enough attention to the front to know it a hill is comming up). Flying all AP off is only something I really do if I've suffered battle damage and lost hydraulics. No reason to make things hard on myself when the systems have been designed to help with the flying. If I want a "hands-on" helicopter flight, I'll go grab my MI-8.

The typical solution I use that works for pretty much all planes is to set the Tacan for the desired Airport, set the course on the course ring to the same heading as the runway at the airport, and then just follow the direction given by the ATC until the Tacan signal direction and the course overlaps with eachother. Then you just turn onto the course and you should be lined up for the runway.

It could probably be possible. I believe the newsletter mentioned though that the team that is working on the Hind is the team behind the MI-8, so they are probably a bit too busy to implement new stuff for the MI-8 at the moment. :P

May he rest in peace.

VIRPIL also have pretty good customer support. They are pretty quick with responses and have sent me software updates and spare parts to resolve small issue I've had here and there. Would definitely recommend them.

Some bomb modes allows for radar ranging to determine the impact point and calculating a precise release point. I believe the dive bombing mode is one of those. Other bombing modes requires a QFE to be set for the target point, as the computer will need that to calculate the proper height to release the bombs. I believe the BK 90's need a proper QFE as well to release at the proper height above the targets.

The Viggen is not a loitering aircraft like the Harrier and the A10, but it can do it if it has to since it can carry Mavericks. The Viggen is mainly about planning your strike in advance, fly in below the radar, drop your bomb loads on the enemies and then fly out again full speed. The biggest curve for the Viggen is that it's so differently designed compared the "standard" planes. F.eks. you don't get much in terms of hud elements. Many of the elements you get are context sensitive, like Time To Target progress bars and while they are incredibly useful, they also take time to learn how to use if you come from A-10 and Harrier. The Viggen is a ton of fun though and I recommend getting it.

It could also be that Jester is "locked" to the blue side, and anything he sees that is a red coalition plane is labeled a bandit, even if Jester himself is on red coalition?

Very nice. Just grabbed the book off Amazon for my kindle. Sounds like a good read. Looking forward to the campaign. ^^

Dont know if someone's suggested it before, but do you have a replay file where it happens? Much easier to determine what the problem is then.

I am not an expert on use of the rudder, so I cannot give much advice on that, but a few hints to dogfighting with the F-14: Make sure the roll stabilizer is turned off. Try and keep your AOA at max 15 in your turns. This will help you preserve your airspeed. Airspeed is important, because you need it to be able to keep an optimal turnrate. You should never pull hard on the stick in a dogfight, unless it's the make or break moment. Only do that if it will keep you from getting shot down by the other guy or if it will grant you that good shot opportunity that will send your opponent down in flames. The rest of the time, you are just wasting your precious airspeed. Remember, the objective of a dogfight is to preserve your speed and movement potential, while making your opponent waste his own.