Gunfreak

A G6ed K4

It works great, and it's definitely more enjoyable with the 20mm over the 30mm. It's effective against the Mustang and probably the Spitfire. Not sure if a single 20mm will be very effective a P47.

G6ing the K4

I haven't used the F4 for several patches ago. And haven't paid that much attention to the change log. But doing an air start. I have 4 Sparrow and 2 Sidewinder Bs. When I change from gun or Sparrow to heat. I don't get the Sidewinder hum. Then suddenly I get it. Not sure what triggers it to activate. I was in the middle of a fight so haven't done any testing but the only thing I can think of is that now you have to use the 1st detent on the trigger to activate it. Kinda like the Maverick?

I tried to use your lua, but when I did, all my WW2 fighters were gone from the mission editor Edit, never mind. A comma had snuck in

Will definitely try that. If only we could strangle the engine to get G6 preformance for AI it would be awsome.

My understanding is that the F4 will let you walk around the aircraft before entering

I think the Viggen pilot is female. I think it's a good idea, but there are many good ideas for DCS that either never happens or happens in very slow time. Would be cool if the F4 pilot customisation could be extended to non-Heatblur aircraft.

So the Winwing MFSSB base for the F16 is a cool piece of hardware, however there’s always been something off. The “realistic” mode seem to be anything but realistic according to F16 pilots or pilots who have flown civilian aircraft with a force sensing stick. The force only mode seems to the most realistic one, but it has a serious downside and that is the fact the MFSSB has big nasty dead zone, the completely ruins how it’s supposed to be, trying to do accurate flying like AAR with a big ass dead zone isn’t very nice. So many have used the movement + force. But that’s not ideal either. I’ve had the MFSSB for almost two years now and never quite been happy with it. I got kinda used it it. But it always felt off. I regularly goodled and asked others what settings they used to get the base working right, and you have as many answers as people. Then doing one of my semi regular googelings I found out that for like a year people have found out the dead zone is because of a giant gap(2-3mm) between the roller bearings and sensors, that causes the dead zone as the force sensing won’t kick in until the roller bearings hit the sensor. There are several ways of fixing this, the MacGyver way just shove anything between the two bearings and the sensor, you can use a 3d printed part, or you can even use metal. I did the cheap MacGyver way, and cut small strips of plastic from some random battery package, 3 layers of this thin plastic works well, so 6 small strips. And it works, it really does, dead zone is gone. The F16 answers as soon as you start using force on it. To test I did a quick and easy dogfight with a MiG29. With some acrobatics and low flying to test the stick after winning. Stuff like trying to hit a slow moving damaged mig with guns used to be kinda a pain, with the dead zone, so getting the thing on the thing could be more complicated than it should be. But it was much easier now. So in case you are using the WW MFSSB and have that problem with the base, just find what solution you want, shove it in there, and set the settings to force only and everything is great now.

So the Winwing MFSSB base for the F16 is a cool piece of hardware, however there’s always been something off. The “realistic” mode seem to be anything but realistic according to F16 pilots or pilots who have flown civilian aircraft with a force sensing stick. The force only mode seems to the most realistic one, but it has a serious downside and that is the fact the MFSSB has big nasty dead zone, the completely ruins how it’s supposed to be, trying to do accurate flying like AAR with a big ass dead zone isn’t very nice. So many have used the movement + force. But that’s not ideal either. I’ve had the MFSSB for almost two years now and never quite been happy with it. I got kinda used it it. But it always felt off. I regularly goodled and asked others what settings they used to get the base working right, and you have as many answers as people. Then doing one of my semi regular googelings I found out that for like a year people have found out the dead zone is because of a giant gap(2-3mm) between the roller bearings and sensors, that causes the dead zone as the force sensing won’t kick in until the roller bearings hit the sensor. There are several ways of fixing this, the MacGyver way just shove anything between the two bearings and the sensor, you can use a 3d printed part, or you can even use metal. I did the cheap MacGyver way, and cut small strips of plastic from some random battery package, 3 layers of this thin plastic works well, so 6 small strips. And it works, it really does, dead zone is gone. The F16 answers as soon as you start using force on it. To test I did a quick and easy dogfight with a MiG29. With some acrobatics and low flying to test the stick after winning. Stuff like trying to hit a slow moving damaged mig with guns used to be kinda a pain, with the dead zone, so getting the thing on the thing could be more complicated than it should be. But it was much easier now. So in case you are using the WW MFSSB and have that problem with the base, just find what solution you want, shove it in there, and set the settings to force only and everything is great now.

Why you should be careful when using mods in DCS.

Given alll the ST specific bugs people are reporting, then yes quite a lot. I even had someone on a dcs Facebook group not knowing that MT even existed.

Haven't done a proper DCS video in almost a month with family vacation, there has been little time to spend hours editing videos. I took out the Apache a module I’m absolutely not great at, but we did put warheads to foreheads, protecting the Chinook MEDEVAC, as they picked up 3 wounded British soldiers, in the process we neutralized the Taliban threat that had attacked the British land rover column. As I went in for landing, I discovered I had a deadzone on my collective exactly were the hover point was with the current weight of the helicopter, ground hover seems to be around mid 70s power, but my collective jumped from low 70s to mid 80s, meaning I either fell too fast to the ground or shot into the air. Concentrating on my collective and trying to find that point, I naturally paid little attention to the cycling and things went downhill, but I did manage to get back into control, and did land okish, no damage. Sucky landing on an otherwise very successful mission.

Haven't done a proper DCS video in almost a month with family vacation, there has been little time to spend hours editing videos. I took out the Apache a module I’m absolutely not great at, but we did put warheads to foreheads, protecting the Chinook MEDEVAC, as they picked up 3 wounded British soldiers, in the process we neutralized the Taliban threat that had attacked the British land rover column. As I went in for landing, I discovered I had a deadzone on my collective exactly were the hover point was with the current weight of the helicopter, ground hover seems to be around mid 70s power, but my collective jumped from low 70s to mid 80s, meaning I either fell too fast to the ground or shot into the air. Concentrating on my collective and trying to find that point, I naturally paid little attention to the cycling and things went downhill, but I did manage to get back into control, and did land okish, no damage. Sucky landing on an otherwise very successful mission.

Haven't done a proper DCS video in almost a month with family vacation, there has been little time to spend hours editing videos. I took out the Apache a module I’m absolutely not great at, but we did put warheads to foreheads, protecting the Chinook MEDEVAC, as they picked up 3 wounded British soldiers, in the process we neutralized the Taliban threat that had attacked the British land rover column. As I went in for landing, I discovered I had a deadzone on my collective exactly were the hover point was with the current weight of the helicopter, ground hover seems to be around mid 70s power, but my collective jumped from low 70s to mid 80s, meaning I either fell too fast to the ground or shot into the air. Concentrating on my collective and trying to find that point, I naturally paid little attention to the cycling and things went downhill, but I did manage to get back into control, and did land okish, no damage. Sucky landing on an otherwise very successful mission.

This happens with or with out waypoints set up crazy apache.trk

You can't do anything with the accuracy, but you can make units immortal or invisible to other AI. Then have ground units fire at points. That way you'll have ground battles that last longer. The invisibility and immortality can be turned of at moments you feel appropriate

Because now infantry or tanks will wipe each other out in seconds. Naturally that doesn't happen in real life

Bohemian DCSpsody

@BammBamm has provided a track.

Which is true for all medium range missiles in DCS. AMRAAM C can reach out and touch someone at almost 60nm under ideal circumstances. Get down to 6000 feet and the same missile is almost useless at 14nm

DCS looks fantastic 2024 graphics except water. Which look 2006. The two ww2 sims I fly have har superior English channel water. Looks far more real. I had hoped Afghanistan with its big flowing river would be the start of a major water overhali from ED, but doesn't look like it. Helmand river looks exactly like all the other rivers. As in elongated lakes.

I've watched several videos and I follow them. When they press in the ILS frequency they get command steering right away, I only get it some times. Then suddenly the command steering circle just disappear. On top of that I don't get ATC while flying on line, only in singleplayer. comand stering.trk

Nope

I planned on doing that but apparently Kandahar doesn't have ILS. Does the ILS work right on Banak?