Lord Vader

Hi all We are aware the IR laser is visible under certain circumstances when it shouldn't. This isn't a F/A-18C exclusive bug. Thank you for your patience, we'll be fixing this in a future update.

Hi @skywalker22 We are aware of this issue and hope to fix it in a future patch. Thanks anyway.

Hi @royphsle I'm not entirely sure I understand your issue. The ejection seat handle does have textures on my side. The only reason I can think of is that you may have mods installed or just require a metashader clean up. Please supply a picture for our analysis. As for the other item, please try to keep it one issue per thread. But answering that question, the functionality of that switch has been discussed earlier in this forum:

Hi @Stroke 3 Please PM non-classified documentation to support your claim to @BIGNEWY so we can analyse it. Thanks

Hi @Glide Overall performance of graphics and/or instrumentation varies a lot between systems. Adding or deleting items in missions can certainly affect it. If you do feel this is an issue and not a need for optimization you can record a track and, if possible, a video with the FPS counter shown for our analysis.

Hi @ex81 The SAI is just a back up artificial horizon, known to suffer precession after a while. The same will happen in other modules, such as the F-16C. Like @ASAP suggested, caging the SAI again in level flight will correct it but only until it drifts again.

Hi all. This has been discussed several times before, regarding ranges, angles and timing at which George may or may not engage. In some cases, we've seen user errors introduced, other times George's own programming can interfere with his performance in certain conditions. All I can say at this moment is that George is a very complex system and we'll continue to improve the way it works. For now, guarantee stability, good LOS and within the ranges.

Hi @drz400dude Please supply a track replay with the issue occurring for our analysis.

Hello all. All we can say for now is that the weapon's GPS self-guidance logic is being worked on currently. This is not "abandoned" or "half-baked", it involves proper simulation and implementation and that takes time to make it as accurate as everyone expects. We thank you for your patience and please wait for future updates.

Hi again, Like I said in the other post, we're working on a standard for this particular operation.

We're working on a standard for this particular operation, but thanks for the suggestion.

Hi @bengo This is working according to the available documentation. The SAT option for the MAP type will only work up to 25km and selecting a range above it will revert the type to STICK as you describe.

Hi @Weidlich The operation of loading/unloading ammunition involves the plugging/unplugging of power supply to the units, this is for weapons or pods. In DCS when you request rearming, even if you keep weapons or pods, the crew will unload and load all stations. Thus, power supply is turned off and requires a power cycle. This is currently intended behaviour. This can change in the future, but for now you do require to turn off the hardpoints during rearming or power cycle after it's complete.

The Spin Recovery mode is not designed for aerial combat. Even if it's realistic to actually choose weapons, the pilot has to be more worried about recovering the aircraft if he's in a flat spin.

Hi @SUHANG The loading of different fuzes will produce a MC LOAD fault and will not allow the activation of any fuze on any of the affected bombs. This is correct behaviour. Although set like a fuze and often (wrongly) depicted as a fuse, the DSU-33 is actually a proximity sensor and indeed you need to choose the tail fuze when it's equipped. But don't worry, the bomb will still airburst at about 20 ft.

Glad you sorted it out, yes, the Spin Recovery activates when it detects the conditions of an uncontrolled lateral (yaw) spin by instructing the pilot to move the stick to one direction on the MFDs while it attempts to lower the nose to gain speed. It's not designed to do any enhancement on the pitch axis. Maybe your are referring to the G-limiter (paddle) button? That one, indeed, adds an extra authority on the pitch axis.

It was @Magic Zachthat proposed a mod to make the glass blue. We agree, there are no pictures to support that claim. Regarding what, precisely? What I said was, we analysed our DCS: AH-64D, including consulting our own SMEs about it, and concluded that "our current model of the canopy is correct".

@Tomcat388th What changed was the addition of the fuse options that could have altered the way the weapons are energized. DCS World is continuously being refined and improved almost on a daily basis. We try to make improvements based on solid information we may gather from public documentation or Subject Matter Experts. Sometimes we may even get things wrong, it has happened. This is the reason why we need proper documented evidence. That's all.

Ciao @perryverde Are you referring to the key binding or the actual function? If this is related to SRS, please report it to the correct forum.

Hi @aurocia The binding seems to be working correctly. If this is related to SRS, please report it to the correct forum.

@Tomcat388th Though I understand what you are saying and follow your logic, we can't change behaviours solely based on assumptions. If you have non-classified public information that switching weapons shouldn't safe them, please send this information via PM to @BIGNEWY.

Hi @MemphisBelle Like @Tholozor said, the VOR/DME frequency at Beirut-Rafic Hariri is 112.60MHZ is a paired frequency with TACAN 73X. For that reason, you will see your TCN receiver affected. This is working as intended and not a bug.

Hey @450Devil Maybe there's a typo and you mean the top left corner, not top right? In any case, can you supply a track replay of this event?

Hi @Phil C6 Can you please elaborate on this? The crash recovery mode is only active when the plane detects the conditions to engage. What do you mean "always active"? Also, please add a track replay if you feel this is an issue.

The title of this thread is misleading. What you are referring to is the ground object level of detail in distance and this has nothing to do with the F-16C TPOD itself. Asking for this to be moved. Thanks for understanding.