SignorMagnifico

Also noticing random orange flickering as many have described. Deleted fxo and metashaders, deleted terrain shaders, and ran a repair of DCS. Running 2.5.6.57949 beta patch released today, Windows 10 update 19042 (20H2), and Nvidia driver 457.30. GTX1080. Will attach a track if I can get one. Here is a track and a .mp4 video of the issue: https://www.dropbox.com/s/q2v2ygitg41k98k/FlickeringBug.rar?dl=0

Also experiencing the issue in the latest open beta 2.5.6.57530. Not using any mods at the moment. I tried a repair of the install, deleting fxo and metashaders, and I still have the issue. Looks like it might have to be patched.

Update: Checked again a few minutes ago, and the module was delivered. I'm able to download it now. It seems like there was just a lot of demand for this module. Thanks, ED!

Bought the A-10CII during my lunch break, so it can download by the time I'm off work. Order shows paid, my payment method shows it was charged, but status is stuck in "processing." Client doesn't prompt to download the module when DCS is launched, and I go into the module manager. Guess I'm downloading it after work, after all. It seems we crashed ED's servers with all the people buying the upgrade.

I see. It would be nice though if they could at least give it the same guidance as the GBU-16 and GBU-10, which are working, until they can implement the more realistic guidance, so we can at least use the bomb until they are finished. Right now, we are unable to test this bomb at all, and it is effectively just dead weight in its current state. I can understand if there are technical limitations to doing this, though.

In the open beta patch released today DCS 2.5.6.54046, the GRCV button does not work as it should in the F-18. When pressing this button, it changes the radio modulation from AM/FM and vice versa. This should not be the case. This appears to be similar to the closed thread here: https://forums.eagle.ru/showthread.php?t=283586&highlight=GRCV. I have attached a track file with the issue. F18RadioBug.trk

The GBU-24 bug is still present in DCS 2.5.6.53756 open beta. All other LGBs track just fine using the LANTIRN pod in the F-14, but the GBU-24 fails to attempt to track. The link below has a track and .mp4 video file demonstrating the bug. https://www.dropbox.com/s/c8u2te7llpae4ku/GBU24Bug.rar?dl=0

Still experiencing missing runway textures at random on current open beta 2.5.6.52437. Here is a track file from a mission I flew on Growling Sidewinder and some screen shots as well as the DCS log. https://www.dropbox.com/s/e5dlq2z91h8k7dq/RunwayTextures.rar?dl=0

I don't have a track to prove this, but on almost every server I flew last night on the latest DCS version DCS 2.5.6.52437 open beta, I noticed frequent rubber banding of planes despite having good ping to servers (typically <100 ms). I don't have rubber banding issues in other games like IL-2, and my packet loss tests show 0% packet loss.

The GBU-24 bug is still persistent in DCS 2.5.6.52437 open beta current version. Using the LANTIRN pod in the F-14, all other laser guided GBUs are able to track and hit targets. However, even with the laser on prior to the time of release, the GBU-24 follows a ballistic glide path without ever tracking the laser. GBU24bug.trk

Here is a track replay of an F-16 Instant Action mission I flew. No markings on the runway. Happens randomly. Latest DCS open beta. https://www.dropbox.com/s/7me6tnzxpf2wzty/runwaytextures.trk?dl=0 Also here is the log file dcs.log

Really you should only be using one form of antialiasing at a time. MSAAx4 with MFAA enabled looks better to me and costs less than SSAA at 1.5 or 2x. Mixing antialiasing results in significant performance loss. The only one that makes sense to combine would be FXAA, since it has a minimal performance cost, but I don't like how FXAA looks and leave it off. MFAA basically reduces the cost of MSAA by 50%, so MSAA x4 with MFAA enabled has the performance hit of MSAA x2. https://www.nvidia.com/en-us/geforce/news/multi-frame-sampled-anti-aliasing-delivers-better-performance-and-superior-image-quality/

Here's a screenshot of the settings I'm using now. SSAA is unreliable at the moment and I find that MSAAx4 with MFAA enabled in nVidia control panel looks better and costs less. I get about 100 FPS at altitude, 80FPS on the deck in most cases. In supercarrier, FPS drops to about 30 - 40, and in the MiG-21 with radar on my FPS is lol.

So, I just tried to replicate your results in a simple mission file I created. I set the F-14 to US Blue Coalition and the Kuznetsov to USAF Aggressors (Blue) Coalition, and, after landing on the carrier, Jester didn't eject. Do you have a copy of the mission file you used?

For me the carrier only talks to me during landing once I’m about 30 miles out. I don’t get a response during startup or takeoff.

I think this should be left in as a feature lol. RIO ejects to avoid capture by the Russians.

Does anyone else experience massive FPS drops about 45 minutes into the OCA Strike West mission in this campaign? I flew the mission twice, and I get the frame rate drops at the same point but when located in different parts of the map. It drops to the point of a slide show. The first time was in the northern area of the map while pursuing IL-76s, and the second was over the airfield target. However, both happened around the same time in the mission. In the second instance, once I left the target area at about 52 minutes into the mission, the FPS returned to normal. Track file: https://www.dropbox.com/s/elgvmfefgocxa8v/ocastrikefpsbug.trk?dl=0 Running DCS 2.5.6.50979. Supercarrier version of the campaign.

I am also having this issue with the bomb racks rendering for certain loadouts. They work fine for Mk84s; however, for Mk83s and under the bombs appear to be floating underneath the Tomcat. Running DCS 2.5.6.50979 open beta.

Updated to nVidia drivers 451.48. MiG-21 FPS bug is now present regardless of PhysX CPU or GPU preference setting. Makes no difference in FPS in other modules. Oh well.

Found this issue again using the latest DCS open beta. I sent my wingman at the end of a mission to refuel from an S-3 tanker, and he lined up above the basket, missing it completely. I have attached a track file and a screenshot of the issue. Not sure if this is limited to the F-14. I have not tested this with other modules. Mission track file: https://www.dropbox.com/s/7cp2jzfn9xu7mjp/refuelingbug.trk?dl=0 Edit: Tested wingman refueling process in blank mission made in the ME. Wingman refuels just fine in F-14 and F-18. Issue appears to have been limited to mission 2 of Cage the Bear cold start supercarrier campaign or is intermittent.

There is something going on with PhysX and DCS. When set to CPU, the MiG21 frame rate bug goes away. With PhysX set to GPU, my FPS drops to 30 or less, with CPU I can maintain 80. Doesn’t have as big of an effect on other modules, though, but something is going on there.

See instructions here https://www.evga.com/support/faq/FAQdetails.aspx?faqid=59024

I might have a workaround for this. It was suggested in another section of this forum. I also have an nVidia card and experience severe FPS drops when the radar is turned on and pointed at the ground. However, I went into my nVidia Control Panel settings and set the preferred PhysX processor to my CPU instead of my GPU. Now, I don't get the FPS drops anymore. I hope this helps someone. [Edit] Updated to drivers 451.48 and issue occurs regardless of PhysX processor preference setting. May not have solved the problem originally, too, as the performance I observed initially could have just been for one flight.

Genius! I tried this solution, and it worked for me. I was getting about 27 - 30 FPS on the supercarrier on Mission 3 of Cage the Bear for the F-14. After forcing PhysX to CPU, I get about 31 - 35 FPS. Another side benefit is that this solves the MiG-21 radar FPS bug. There is a bug with the latest nVidia drivers that causes my FPS to drop by 50% (from 60 to about 30 or less) when the radar is turned on and pointed at the ground. However, with PhysX set to CPU only, I don't experience the FPS drop and can maintain about 80 FPS with the radar on with the ground. This guy is on to something!

Update: I tested again with the patch released today, and I had no issues with CCRP drops on the multiplayer server. Issue appears to be resolved.