Teriander

No I haven't. I've read others have reinstalled from scratch to resolve the same issue I'm facing, but I'll try that. Thanks!

Hello, I think I need to reinstall DCS from scratch. But I have a lot of options and joystick configurations for various modules I do NOT want to setup from scratch. What is the best way to save ALL joystick settings for all modules? Is that possible or do I need to save them out one module at a time? Also possible to save Graphic settings, etc., without having to take a screenshot of my settings for each tab? Thanks

I came to see if others were having this issue as well and it looks like I'm definitely not alone. I can not believe ED says they can not reproduce this issue. It happens to me every time on the GS server. Destroyed bandits will sometimes remained locked even after the bandit has crashed into the mountains. Breaking lock is impossible unless I cycle ACM modes. Undesignate will not break the lock of the destroyed target. It is random, but it definitely happens. A new bug since 2022. NEVER had this issue on previous F-18 patches.

Hello, when I playback a track in 4K on my monitor but the recording was recorded in VR, the playback tracks my head position correct. But if I try to change the zoom with num / or * keys since it's too zoomed in, it breaks tracking the head position from the recording. Is it possible to restore a track playback to follow the head position from the recording? Everything else plays back correct when changing the zoom. Just the head tracking information becomes disabled for some reason.

Aim-9X F-18C Bug. Problem - AIM-9X will cease to operate under certain conditions after jettison of fuel tanks. The missile will not attempt to detect heat sources, stop following HMD, and will not fire. Works best for me when armed with 6 AIM-9X, Centerline tank, and 6 AIM-120s. Other conditions may work also. Steps to reproduce: 1. Turn on your HMD (tested with HMD set to blank) 2. Check Master ARM ON. 3. Check your fuel tank Jettison is set to the centerline and the knob is not set to safe. 4. Happens the most often after engaging 2 bandits, so make sure you have fired 2 AIM-9X now. 5. While still in AIM-9X mode, jettison your fuel tank now. 6. Your AIM-9X should no longer function. Track attached to demonstrate the issue. My system specs: Windows 10 Reverb G2 Geforce 3090 128 RAM Ryzen 3950x F-18_9X_BreaksOnJettison.trk

First. I didn't create a track because this is easy to reproduce. Create an early morning scene with clouds just like my scene, and look at the sun with clouds in the front. You'll have an identical problem. I also want to state this ONLY happens when the sun is behind clouds. Looking at the sun in clear skies is perfect. In the image below, you'll see the clouds in front of the sun looks very bright. If you were in a dogfight the bandit and the HMD or HUD, would be very difficult or impossible to see and read. This is caused by over-exposure from cameras. Or too much light bouncing in the volumetric clouds. Now, before you say, "But this is pilot/character eyes", sure. But the engine uses Cameras and you're looking through a camera simulated as human eyes. Just like the cameras in the real world. The best solution would be an option to control how much light bounces through the clouds. Or a reduced parameter. If that is not an option, can the exposure be corrected? Yes, but at a cost. If the exposure increases when looking at the sun, it will appear correct, other areas will become darker. Such as the cockpit, and that is not good. Unless the exposure uses an "auto-exposure" method where when the user is looking outside towards the sun, the exposure values increase making the sun appear not as bright. Looking at anything else would make the exposure values drop, making everything else look normal. This is exactly what happens with real-world cameras. Alternative solution? Yes, it would be to provide the user with a simulated visor, just like the ones used in the real world. Right now in DCS, your visor is always up. All day, every day. Real world pilots deal with the sun and the clouds that bloom from it, by lowering their visors. We should also have this option.

The F-18C has as radar bug that allows the AIM-9X and the WACQ radar mode to lock onto targets beyond 10nm. Even beyond 20nm. This should never happen. I've provided video proof and a track file. This is easily reproduced by first selecting the AIM-120, switching to WACQ mode, then switching to the AIM-9X. You can now lock onto targets beyond 20nm with the AIM-9X. Why is this a concern? First, searching for targets within 10nm is very common to have the 9X ready and WACQ mode, but can be distracting when you lock a target beyond 20nm. Second, it can also be considered a cheat since the 9X will detect heat sources at 20+nm to spot targets while your radar is free to continue to scan in WACQ mode. This does not appear to be a known issue. When I reported this on Discord, ED sent me a beginners guide to the F-18C radar... Video - F-18_WACQ_Locks20Miles_Away.trk

I've noticed on PVP servers, some users will return to spectator to prevent from being killed. This prevents a score kill from registering and there's no public announcement of the player returning to spectator. A simple solution would be to prevent an airborne player who is within 15 miles or so of an enemy from returning to spectator. This could be an optional feature set by the server. I personally know players that pay attention to kill counts on PVP servers for various reasons, and this option will help balance the kills and prevent cheating.

When playing Single player in the F-18, I can easily spot the enemy AI F-14s AIM-54s fired at me. In multiplayer I did not detect them fired from a player. Tested twice and same results. Is this a bug? My radar settings and engagement distances + altitudes were identical.

When I get on a bandit's 6 O'Clock, and place my HMD in HACQ mode over the bandit, it locks a target 30+ miles away. Did it twice on this track and plenty of times before since the new patch. Suggestions? F-18_HMD_Locks_32Miles_Away.trk

I'll have to run the tracks again and time it. I don't have a chance now. But that very well could be the issue.

I've used different settings in 3 different tracks. I believe in Track 03, I was in RWS and STT when fired and the results were the same. Maybe it was Track 02. But once the 120 auto tracks itself to the target when its within 10nm, it shouldn't matter if Im locked TWS or RWS, It's in Fire-And-Forget mode.

Hello, Flying an F-18 at 37,000 feet at mach 1. Bandit is a Il-78 at 30,000 on my nose. Bandit is set to not take evasive action, zero chaff, and will only flight straight and on course, no matter what. Fired a AIM-120 when the bandit is at 50nm. Maintained lock the entire path. The 120 has plenty of speed and altitude to reach the target and continues to track, but misses the Il-78 by a matter of 100ft or so. EVERYTIME. Why is this? I've included 3 tracks. The 03 track I removed all Chaff from the bandit, just to make sure it wasn't chaffing. Same results. F-18_AIM120_Fail_00.trk F-18_AIM120_Fail_01.trk F-18_AIM120_Fail_03.trk

You do know the events in the story are not real either, right? There is a reason it's called "fictional." Fake squadrons, characters, or sometimes even names of vessels are used to help protect those of their real counterparts. The only thing that is real are the procedures and even this is sometimes manipulated. Can't wait to see your reaction when you find out "Top Gun" wasn't real.

Baltic Dragon, I did not have a problem completing mission 8, but mission 9 appears to have a bug. "Olive" or 410, never takes off because she is stuck on the deck behind parked F-18s. Thus, she sits there and never moves. I've accelerated time, no change. What is the solution to this?

I've been playing DCS since 2012, this is the best Campaign I've played so far. On mission 6 now. Highly recommend it. This also comes from someone who has also developed a campaign. Make sure you read the book "Raven One!"

All, I've updated this campaign to support Supercarriers. Have fun! https://www.digitalcombatsimulator.com/en/files/3305784/

Has anyone had an issue with waypoints ranges not decreasing when flying to them?

Looks like I was correct again about the AIM-120 range being inaccurate. After all this time. I accept everyone's apology. "Corrected flight dynamics of AIM-120 missiles based on our latest CFD research. All changes increased the launch range by about 10-20%." https://www.digitalcombatsimulator.com/en/news/changelog/openbeta/2.5.5.41371/

Running the A-10C Free Flight, the TGP is black for me on A-G mode. Not sure why. Attached is the track. Is it black for you? A-10C_TGPisBlack.trk

Is the IFF system still not working?

Where could I get the latest Moose release?

Thanks Pimp!

Awesome! Thanks again. On a side note, the Moose.lua seems a bit heavy. Is it possible for me to strip what I don't need and keep the functions that allow the "Static Spawn" lua to work, or is the whole script pretty much necessary? Just trying to reduce the number of functions on my mission as possible. But if I need it all, I'll use it!

Thanks for sharing that post Tony, that's awesome. I've replied to it because I'm having issues getting that file to work in my mission. We'll pick up from there! Thanks!