SignorMagnifico

No, I do not have any ship mods installed. I tried this on a clean installation. I think it's possibly related to this campaign using the old Stennis 3D model. It was updated in 2.7.15.25026. I tried making a simple mission in the editor using the Stennis and placing some aircraft on it, and I'm able to see the carrier just fine.

I tried playing this mission today in version 2.8.0.32235.1, and the aircraft carrier is now invisible. The F-18s are just floating on the deck. There is also a severe screen flickering issue, but I posted about that in a separate thread. Anyone else having this problem?

I tried playing the same mission again in the current version 2.8.0.32235.1, and the flickering is still there. The only difference is that now the carrier is invisible. Any progress report on fixing this bug?

Thanks! This worked. I can launch at night by cycling the light switch. The flight director directions are still wrong, though.

Bump. Still having this issue in the current DCS 2.7.17.29140 Open Beta. I'm completely unable to launch from the supercarrier in the F-14A at night. During the day, I can launch. In both cases, the flight director gives the wrong instructions, and it's almost like I'm recognized as an F-18 instead of an F-14. I also noticed that the F-14A spawns on the carrier with the nosewheel in the kneeled position. Not sure if that is also causing the issue. Track files attached. https://www.dropbox.com/s/748bvwrdkos4yif/F14SCBug.rar?dl=0

Finally, some good news! I also noticed more black squares more often on the Caucasus map. Not sure if that has something to do with it. Thanks for the help. The mission write protections also cause issues for me with replicating bugs like this one, too. I understand the need for copyright, but, at the same time, the mission editor is the fastest way to isolate a problem.

Same driver version. It’s in the DxDiag I attached.

Managed to replicate this issue again. This time, the track is much shorter because the issue happens at the beginning of the mission. You can see the flickering starting at about 20 seconds into the YouTube video. I attached a track where I was able to replicate the problem as well as a DXDiag and screenshots of my DCS and Nvidia Control Panel settings. I noticed that the issue could be linked to MSAA settings within DCS. When I toggled off that setting, I wasn't able to reproduce the texture flickering when playing back the track. Running DCS 2.7.16.28157. https://www.dropbox.com/s/s9tzwkv0fg7nxt8/DCSTextureFlickering08-14-22.rar?dl=0 DxDiag08-14-22.txt

I just recently formatted my drive and installed Windows 11 on a new NVME SSD, and the issue persists on the same track I sent earlier. I'm able to reproduce the issue every time when watching the track by using CTRL + Z to speed up time. It takes me about five minutes of watching the track to get to the issue. (About 10:23AM mission time on final approach right up until landing.) This is on as fresh of a DCS installation as one can get and on the latest version as of today. (DCS 2.7.16.28157) Forgive me, but I don't see how track length is a problem when I can reproduce the issue every time in about five minutes by speeding up the track playback speed. As a workaround, the devs could try editing the mission file from Mi-8 The Crew Campaign (1.1 Salon) to an air start at 10:23AM and land between the cones. I'm unable to edit the mission file to achieve this because DLC campaigns are copy protected.

+1

Yes, it looks like I was only arming the stations and not the bombs. The fuses work as expected. Please mark as resolved. Thanks!

Tried using the new bomb fuses in the mission editor as well as flying a training mission, but it seems as if the bombs in the P47 aren't working no matter what fuse is selected. Anyone else experiencing the same issue?

The AAA Zu-23 unit appears to be missing textures. The gun is flat green with no textures both in-game and in the encyclopedia. I tried removing all mods and repairing DCS, but the error persists. Anyone else have this problem? Running DCS 2.7.15.26783 Open Beta.

Just confirming the Syria kneeboard folder does not work as of 2.7.15. The maps included in the default kneeboard don't include airport charts for TACAN, radio, etc. Would be nice to have this folder working like it does with the other maps.

Also having this issue. Seems similar to this one.

The texture flickering issue appears to have returned in the latest DCS version 2.7.15. 100% reproducible for me when flying the second mission from Mi-8: The Crew Part One Campaign. No texture flickering occurs at the beginning of the mission, but it starts right at the end of the mission when landing at the same spot the mission started. I remember the previous conclusion regarding this bug was that it had something to do with mirrors and the sun's position, and the mission takes place close to sunset. The sun changes position by the end of the mission. I disabled all mods, deleted fxo and metashaders, repaired my DCS installation, and I was still able to reproduce the issue. I hope this helps with resolving this bug. I recorded the issue happening with mods disabled. Track file attached at the drop box link, and the issue can be seen happening in the YouTube video starting at 1:09. https://www.dropbox.com/s/pqb4uw92g1qul8f/textureflickeringbug.rar?dl=0 DCS Version: DCS 2.7.15.26783 Open Beta Hardware: DX diag attached. DxDiag07-08-22.txt

hurricanetest.miz

In my current testing, the gun range indication on the map for the Flak41 seems to be accurate even with the KDO40. The Flak37 is able to engage at further ranges and higher altitudes than the Flak41. Doesn’t seem right.

Thank you for the advice, but I know how to use a Phoenix missile. The missile works fine under these circumstances. What I am saying is that it does not work when fired at 30 degrees. The expected behavior is that the missile should use the extra energy to intercept the target with the extra loft. However, the missile instead overflies the target and fails to track. For me, the problem happens both online and offline. Unfortunately, I cannot provide tracks since they do not work.

So far a fun campaign! There appears to be an error in Mission 8; however. This is the night mission where you have to destroy a convoy with a pair of Mi-28N's. When returning to base, one of the Mi-28N's lands at the player startup position, so the mission cannot be completed because he takes the player's landing spot. The only way to beat the mission right now is to land carefully on the same helipad as the AI Mi-28N. Running DCS 2.7.10.19473.

I’ve been noticing this as well. Shooting at 30k-40k ft at a target 50-65nm away, if I pitch up 30 degrees to maximize the loft, the missile often overshoots the target after going into space, usually flying directly over the target. This results in the missile failing to track the target after reaching the pitbull distance. Here is a link to a YouTube video of the issue recorded today. I tried to include a track file, but, as usual, it doesn't work for the F-14. I tried running the mission from a server and saved the server track, but it's still completely off.

Confirmed. Appears to be resolved. I tried playing back my tracks with the issue, and I'm not seeing the black screen. Will have to play more tonight to see if the issue comes back.

In Mission 13 of Memory of the Hero Campaign (Combat Spirit), one of the soldiers in the landing zone randomly explodes. This seems to coincide when the friendly Su-25 is shot down. I'm pretty sure it's trigger related. Anyway, I have attached a track file and a video of the bug happening. Hopefully this can be fixed when this campaign is revisited. Noticeable @49:56 in this video as well. Track file: https://www.dropbox.com/s/hhdzesk3dd36ee1/Mission13Bug.rar?dl=0

Thank goodness it’s not just me lol. Hopefully Heatblur can find a solution.

I've noticed in the Tomcat some strange texture flickering that happens only when the mirrors are enabled. When I look at the mirrors, I see a black box appearing on the screen. I tried using the mirrors in other aircraft at the same airfield, such as the F-18 Hornet, and I didn't have the same problem. It only happens with the Tomcat so far. I have attached track files and a YouTube video of the issue happening. Track files: https://www.dropbox.com/s/ibcynnayl6jjab1/TomcatMirrorsBug.rar?dl=0