Lt.Salty

Hi Guys I just tested the new Cold War Germany Map with my Quest 3 on an AMD Ryzen 7800X3D with a RTX4080 super and 64gb of ram. And it runs pretty well, I have groundtextures on Low and textures on medium but somehow on certen assets like the Fernsehturm, some balons or parked civilian Airplanes at Tegel Airport, the right and left lense of the headset differ in what they display. One shows the asset while for the other lens doesnt render completely. On the lens that wont render the asset correctly, the asset pops in an out depending on the viewing angle. Has anybody experianced something similar? I never saw that effect before on any map. It might it be a VRam bug, but im not sure, the average FPS are fine though. If the topic should go to the VR section please move it there, but it seams to be map related.

With your input and reference to the manuel I tested it again yesterday, and you are right it was the LGB that's responsible for the break away X cue. The curcumstances still don't quite match the discriptions in the Manuel, then again it's from 2023, who knows what changed. I have the fuzes set, master arm on, a/g selected and I'm flying at 25k ft (unlike in the track). Then for as long as I don't have a tgt designated I get the Breakaway X. Once I designated a tgt it's gone, I'm not sure it's supposed to be that way but it is a repeatable pattern and doesn't appear to be a bug. Than you for your help guys!

Thanks for the Help guys. And I'll try your tipp tomorrow Mucho. It's also defenity not a hight advisory sighn. I first noticed it in a campain mission where I flew at about 25k ft. And during all that time, the cross was flashing... Which also makes me question the dud cue a bit. On that mission I was carriing two lgbs and 2 hydra rocket pots. The fuze of the lgbs was set and they worked but I think the X was still flashing, even with a designated target.

I just tested it again and you are partially right, in one mission i had no GPS (even tough the setting was in 89), so the hsi page read ifa rdr under the aircraft symbol but that wasn't what cause for the X on the rdr and Hud screen. The ins alighnment is OK every time, that seams not to be the issue. And to be fair I don't even know if the WPNS DEGD advisory on the bit page is connected to that, but It might be. I just know, that as soon as I turn on the radar and select a/g, that pesky sporadic blinking X appears.

Hi there, I got a slight problem I haven't encountered before in about 2 1/2 Years of flying the hornet. On the last 3 cold starts on the carrier I wasn't able to clear a WPNS DEGD advise on the bit page, no matter what I did. On top of that when I wanted to use the radar in A/G or A/A mode I got a flashing X on the hud and radar screen and I suspect both are connected. At first I thought the culprit could be a faulty ins alignment, but it happened 3 times no matter if I used stored hdg or not, and it also didn't matter if I selected ifa or nav after an ok alighnment. After choosing nfa it also showed a different text with rdr at the end on the hsi under the aircraft symbol with a timer counting up. I also never noticed that before. I did the cold starts on Syria and Caucasus Has something changed in the startup procedure that I missed and is it a new feature or just a bug? I attached a picture of the X on the screens and a track file. Weapons degd.trk

Ok... well, I highlighted the step for you with a higher resolution picture. The task is: authenticate Charly - Foxtrot 1. Step (green): Down the 1. row to find C (Charly - Nato Alphabet) 2. Step: (red): follow that row to the left until you find F (Foxtrot) 3. Step (red): from there drop down one row to find Q (Quebec) 4. Step (mustard): go back to the left to find D (Delta) Solution: You authenticate Quebec - Delta

I think reflected explained it in the intro of his F-16c campain, you also really need to use it there. You take the first highlighted collum and search for the letter you want/need, then go right until you hit the second letter that was given to you, or want to get authenticated. From there you go down one row to the letter below. And then left to the first collum again. As an example from the table above, you are supposed to authenticate Charly Foxtrot: 1.collum on the left to C, then right until you hit F and under F you find A (Alpha) in row E (Echo). So you authenticate Alpha Echo.

It is a problem in SP as well and probably comes down to a change in the bomb/laser code logic for the bombs that was introduced when the fuzes where updated, or a bit later, who knows. The fix is an update of the mission template in the editor. Open the Mission, click on the ordonace on the Jet and open the new Fuze menu, click OK and repeat or copy that setting for all bombs on the jet. That worked for me in all the instant training missions I tested. They where all borked before and after that jester woke up out of his slumber again and did his RIO Magic in the back seat again.

I think i fixed the take-off Problem. The blocking element (Jeep) on the runway for the flight lead wasnt doing its intended job blocking him and somehow screwed up his take off. I fixed his placement to a position closer the taxiway and now its working. I also changed the wind direction slightly, which probably wasnt necessary but since i have no real clue about the ME and takeoff behavior and it is working i left it as is. F-4E_CMP_Frog-7_M4(Wind151at6_working ).miz

I solved my problem..by updating to an AM5 system. Thank you Intel. Maybe it is not just your 13900/14900 systems that are having problems, but who knows.

Hi all I'm just reflying this fantastic campaign and might have found a bug. In Mission 3 and 4 at launch during the clearing turn from cat 1 with 10-20deg. to the right, I get the message from departure that I'm still within 7 miles and not cleared VMC, what ever VMC is. I'm not above 500ft and I'm also pretty sure a clearing turn is mandatory. I don't know if the following missions are also affected because I'm not further along yet. Also an possible idea for your next campaign update, could you please include the BRC's on the mission cards or in the briefings? I know I can just open the F10 map and measure, but that kills the immersion.

I tried disabling DLSS/DLAA too, but it didn't help. I also tried it with and without MSAA 2x and 4x, VSYNC on/off, plus with Process Lasso I also disabled Hyperthreading and the windows dynamic priority boost, assigned specific cores and excluded those cores of all other programs. But all in all I had no real success. It worked twice out of maybe 20 attempts with various settings but no permanent success. On those two attempts where it worked I was using 4xMSAA, Vsync on, Hypertheading off and windows dynamic priority boost also off. But I could not replicate it. For starters, I'm using an Intel I5 13600K with an Asus Z790 Mainboard and 64GB DDR4 Ram, RTX 3080 and Win11.

This is a very strange bug. I just watched the replay of my MT track i posted above, since you couldn't replicate the Bug. Behold, in that replay somehow everything works for me as well. The triggers fire and my wingman engages the target twice after she drops smoke, which is strange because in game it definitely never worked. But again when I play the mission, instead of just watching the track file, there she just drops smoke and then returns to follow me indefinitely. I recorded an in-flight video to highlight the bug for you and saved the new corresponding track file of that session as well as a Tacview file. I also rewatched the new track file four times and there the triggers worked once and failed the other three times. Youtube Video of the Bug - the interesting part starts at 17:40. I hope that's enough for documentation purposes. R1M7 StopFlag Bug MT Version 11.03.24.trk Tacview-20240311-180228-DCS-R1 M07.zip.acmi

Are there any news? I recently even upgraded my ram to 64gb 4000mhz in the hope that this would somehow eliminate that bug for me, but no such luck. If more tracks are needed I can provide those, also from different missions.

I'm having the same problem, but it for me, it is not limited to MT but also occurs in ST. Attached is a MT track of Mission 7 of Baltics Raven One campaign where I encountered it numerous times. Furthermore, I also encountered it in other Missions, but to provide a track, this will hopefully do. I would have attached an ST track as well but the 50mb limit prohibits that. R1M7 StopFlag Bug MT Version.trk Upload problem solved. R1M7 StopFlag Bug ST Version.trk