Search the Community

There has been a lot of discussion around the current state of the targeting pods available to the F-16. I was wondering if ED has some plans on the roadmap for adjusting the ATP to have a further zoom than the legacy TGP, or have it be able to properly focus using the focus option? One thing with the Legacy TGP is that it zooms 5x further than the sniper pod currently (4x zoom) and it has a significantly better clarity overall. This isn't the case in any IRL scenario, the Sniper is supposed to be leaps and bounds better than the litening TGP right? but most people are finding the long warmup time and lack of clarity/zoom of the ATP to be less desirable than just swapping back to the Litening and staying with that. I understand that the ATP warmup time is said to be realistic, which is fine, but dropping to a solid 5 minutes would make the game much better. I mean we don't make everything "realistic" in DCS right? for example the HARM/MAV..etc.. batteries just run forever rather than having the limited runtime they would have IRL. It would be a solid QOL update to drop the warmup time to something less than 10 minutes for the many that don't typically do hot starts. It would be great to use the ATP in a non-TV-XR/WHOT-N/W-XR mode to see any clear picture. Especially in the integrated IR mode. I added an image of the integrated mode. From what I understand this was supposed to be IR+TV? like, you can see through clouds possibly? (someone keep me honest here), but this appears to simply be WHOT in TV mode and its extremely blurry at 8.7nm and clouds still very much block visibility. The focus mode can be set to blurry, or more blurry, but at any different distance it really doesn't do much? Not complaining, just trying to see if I am just crazy for thinking the ATP should have much better optical resolution than the Litening pod.

Hello! The magnetic compass indicates 1O instead of 18(See pic).

It says here that the wheel is used to manually enter a range of 0 to 1200 meters in the "forecast-track" gun mode when there is no IRST lock.

Hello I've checked if the man range wheel implementation was already mentionned by ED but didn't find it. Is it planned to implement the manual range wheel ? At this moment the TDC range management is a big problem for antenna elevation. Here is a video showing these particular cases. Have a good day

Hello, I would like to report a problem with the speed of the MiG 29. The MiG 29 does not accelerate that much, it is much slower, this module of the MiG 29 has astronomical performance that needs improvement. Secondly, the MiG 29 loses speed very poorly in real life, it loses speed much faster. Regards.

I got the NS430. I absolutely love the implementation in the Fulcrum. However, when I wanted to remove the NS430 by unchecking it from the NS430 Special menu, I still had the empty bracket when I popped into the plane. My first thought is that it's actually a fantastic bracket!.... and I love that you can see in in the external model. The only way to get rid of the bracket seems to be disabling the NS430 module, which requires a restart of DCS. Not a big deal. Would it be difficult to have the bracket disappear with the NS430 when simply unchecking it? Otherwise, incredible module! -Ryan

I read on Wiki that using the deck cannon was not possible with the under-hull auxiliary tank: "Original production MiG-29 aircraft cannot fire the cannon when carrying a centerline fuel tank as it blocks the shell ejection port. This was corrected in the MiG-29S and later versions" Is that true or not? I know that there is a hole through the tank to vent the gases from the APU, but this is the first time I've heard of this restriction...

In RWS and TWS modes TDC/ target bullseye position on radar page always follows TDC instead of showing BE position of L&S target when you have one like it used to do before the MSI patch. Radar BE position bug.trk

Navigating this new plane was not making any sense to me until I realized that the desired course pointer (the white one) was actually acting as the bearing pointer for the nav system’s upper buttons, wp a/d, points. While the bearing pointer (the yellow one) was acting as the pointer for the lower buttons, rsbn/adf beacons. Of course, that is contrary to the manual’s descriptions, as the white pointer is supposed to align with the programmed track between waypoints for you to keep the yellow pointer inside of to maintain course. Is this by design, a known bug, a temporary work around, or a misinterpretation in the manual?

So, I modded my virpil pedals with a damper and took of the springs. This way I don't have to recenter my rudderpedals between trimming. Yes, I also changed the settings in DCS to pedals without springs etc. Here is the kicker. I'm able to fly around, go into hover and all that jazz, but when landed and trying to taxi down the runway, helicopter is a complete "ass". Slight inputs on the rudder/torque to turn makes the whole tail to kick out, try and counter it with a slight touch, and it overshoots like crazy. Makes it impossible to taxi either out on a runway or back to parking after landed. I'm also seing some strange behaviour with the SCAS on the torque. When collective is completely down, no hand on stick, and everything is centered, I can see the green indicator for the SCAS is working. It's not enought to make the chopper turn. But any input on rudders make the tail kick out, trim release pushed or not. Is this normal? I know it's WIP, but the way it behaves on the ground is just crazy.

Hello guys! I noticed the PRMG channel indicated on the kneeboard for all runways I've selected in the mission editor is wrong(always indicates Ch1) . For the RSBN it's ok, see pics for Senaki

Probably something silly, but I bound the speed brake in controls, but it does nothing. I don't see a speed brake extending. Am I missing something?

So the pneumatic pump sound keeps repeating.

In "Navigation And Landing", Wags tells us that when setting up a route for the Fulcrum in Mission Editor, the first three Waypoints are divert airfields, and WP number 4 (silly as it may seem) is the first "real" route point. Currently, AI FF Fulcrums do NOT interpret the first three WP as Divert Airfields. Worse, if you set up a group for you and an AI wingman, and follow Wag's instructions, your Wingman will happily fly to the first route point (your first divert Airfield), abandoning you while you fly to WP 4. Here's a simple demo. Enter the airborne group, and see your wingmen fly off to Kobuleti, while your first mission WP is Sukumi. fulcrum me tests.miz

I imagine it might be user error but ... 1) Can't get the Ekran to test and work. Says Ekran fail on the main Ekran screen. 2) I've only once got the CAY / AFCS to work and thereby activate the Damper. Works fine in Autostart. I think I'm doing the same thing each time?

Hello. Is HUD size adjustable ? It is kinda too small for me. Harder to see small numbers. In comparison, HDD is perfect with size.

It would be nice if we could mix the R-27R/T and ER/ET instead of only having one or the other on both rails.

Having an issue where I have to keep moving my head around to see all the information on my HUD. I would move my head in all the way then zoom out a bit and it gets semi better, but then goes back to being cut off on each side anytime I zoom anywhere in the cockpit. I am sitting 19" away from my monitor so I don't think its a distance issue on my end. null Does anyone have a fix for this in settings? Thanks!! null

Hello, dear ED team. I wanted to point out small but annoying irregularity considering JFS startup. In real life, JFS starter turbine is cranking using 2 compressed gas reservoirs. As you know, start 1 for one "bottle" and start 2 for both at the same time. Problem is that in real life JFS reservoirs are exhausted a bit less than 2 minutes (can't remember where I've seen this info on their duration) after START switch is set to 2 (or 1), while in DCS they are infinite and will never exhaust. With this, timing is crucial when bringing engine to life. Right after SEC light dissapears and RPM hits ~20%, handle is immediately placed to idle position in order to finish engine start up before reservoirs (or one reservoir) are depleted. Refilling those reservoirs is not an easy task ! Right now we don't have to pay attention to this and can idle engine whenever we like, which is wrong. Can this be simulated in the future ? Where: 1.) JFS is actually timed about 2 minutes and if throttle is not placed in idle position in this time frame (too late), JFS stops, JFS indication light goes out, engine cannot be started and we need to request ground crew option to repair aircraft or add additional Ground crew menu option for "JFS reservoirs refill". 2.) If we attempt to set throttle to idle too early, before SEC light is off and RPM is less then ~20%, it should be simulated as hot start - there’s not enough airflow to keep the engine cool. FTIT should indicate hot start where engine start up should be aborted to prevent possible damage (maybe this is already simulated, I forgot to test it). https://theaviationgeekclub.com/starting-the-engine-on-an-f-16-viper-is-different-from-most-other-jet-aircraft-heres-why/amp/ Thank you for your time. Best regards.

I noticed that the trim speed seems to be a bit fast for fine adjustments. I had hoped ED would improve on that a little.

I have no idea if this is correct or not but since these are two different ways of launching the same missile, AGM88, this behavior has surprised me. I will explain: When I'm in HAD mode with the AGM88 normally a white oval appears indicating the missile's maximum firing range, so far everything is normal. But if I switch to WPN, POS trigger mode and select PB (Prebrief) and then switch to HAD, to my amazement, the range oval disappears!!! I think it shouldn't be like that because these are two completely different shooting modes and the options in one shouldn't affect the other. I hope you clarify this for me. PD: If I put any other mode like EOM or RUK in WPN, everything is back to normal in HAD mode. THX

Hi, I set the ECM to both self-protect mode and barrage mode at startup. I used both functions during combat with the ECM enable light on as it should be. On the way back, I turned the ECM off and then back on, following normal procedures for turn on ECM in barrage mode (ECM mode, countermeasures set, etc.). However, the ECM enable light never came on again with the aft command in barriage mode, as if the ECM was no longer functional. I experience the same problem turning on for the first time the ECM when in flight instead of at F16 startup. Maybe do I miss somthing? Thanks for your help.

There are 2 things that I find kind of implausible with regards to the behaviour of systems in the Hornet, here is the first one. The Dispensor switch has 3 positions: OFF-ON-BYPASS What I find not very plausible is, that when I turn it ON, let it do all its self-tests and then turn it to BYPASS, because....well I come to that later.... But let´s say, I turn it back to ON subsequently, it goes through its selftest again and then remains in STBY mode. Now why do I find that unplausible?: The bYPASS position is a position beyond the ON position, so I would consider it a submode of it being ON. Apparrently you can release Chaff/Flare, so it must be on somehow. Why do I find it annoying?: Let´s think about what the usecase of the BYPASS position might be... There are 2 that come to my mind. The first one is an "items check" during the Fence-in in order to check if C/F dispense correctly. It is kinda´hideous that after that you have to go through all the button presses on the EW page in order to set your desired progarm...let aloe the waiting time for the self-tests. The other use case would probably be training sorties, where you don´t want to dispense that many C/F on every press, but chust want to do it for the purpose of training, but therefor rather more often per sortie. Do I have proof, that my claim is correct, and switching fom BYPASS to ON should not trigger the self-test and simply return to it´s last state? No. I simply think it would make more sense. CMDS Logic.trk

mission time 23:59. TV mode shows the same image as Whot. TV should have higher resolution and a black image at night.

So i have this issue where mavericks do not slave to the new targeting pod, i tried to follow the guide on youtube but either i am doing something wrong or i dont know what else, but the mavericks just arent reaacting to the pod in any way shape or form. (i hope this trackfile is the righ one since i dont realy understand this). LastMissionTrack.trk