AceMcPlane

Nevermind, I tested the track and it doesn’t work at all. I get an error. Something about an unexpected end of the data. Another bug. It’s either because it’s too big of a file or I named it too long? This has happened before. I’ll try to remember to upload another one if it happens again, but I’m using the HMD now to select targets so not likely.

Okay, I saved the Track so that works out. I had to split it into 2 volumes though because of the 50mb limit so download both files this one and the one in the next comment I make . Let me know if the file doesn't work and I'll upload the track over in the DCS User Files instead. Russian Bottleneck on Bridge (2025) - Mission Complete - Scenario 2 - lucky first strike - laser bugged out again stop using wypts to find targets - last landing took two tries hook wasn't down stupid voice attack.zip.001 The bombs stop working after I get the Mission Complete message in the top right and I go after the S-300 System's C2 unit near where the big bird radar was. It's a long mission so fast forward. I think it was the 3rd sortie. Russian Bottleneck on Bridge (2025) - Mission Complete - Scenario 2 - lucky first strike - laser bugged out again stop using wypts to find targets - last landing took two tries hook wasn't down stupid voice attack.zip.002

I noticed after a 2nd sortie dropping laser guided bombs and a long way into a mission the laser can get stuck on the waypoint you set it too and moving it to and selecting a new target after doesn’t work. It gets stuck on the wypt in the hud too and when you drop the bomb it doesn’t track the target and adjust its trajectory. LTD/R switch was in the forward position, the laser kept tracking on my MDF the whole way. It wasn’t crossed out on the HUD or MDF. The only thing that would fix it this time it happened was if I stopped using the wypt system and just pointed my plane to the location and found it by eye. Then it started to work again. I’m sure this must be a bug that only comes up in a long mission with a lot of units to take out. It never happens early on in a mission. Only after like an hour in or more. Resetting everything like the FLIR switch or A/G did nothing too. Really feels like a bug. Thanks.

Ah. I didn’t know you could click on the bombs to bring up the fuze menu. Nice. The bridge I’m punching through is around 40ft high so I’ll definitely be dropping at high altitude with a decent amount of function delay.

Cool, good to know. Thanks for the solution.

A track won't work with the mission I'm playing. The tanks move into position randomly after you take out a nearby air defence system with SLAM-ER's so the plane will target an empty spot with no tank if you replay a track. I appreciate that AndrewDCS2005 uploaded one. So it looks like there have been some updates to the laser guided bombs since I last used them. More realistic is good. I'm going to have to play with this more to know if it's still possible to blow them up under bridges like I did before. I think the fact that I was using the ATFLIR pod instead of the Litening didn't help. It might have been automatically switching its lock to the bridge when it lost sight of the tank as I was over top of it. The last time I had it working, I'd just target a fixed point where they're at instead of tracking them as a moving target. I'm guessing you can change the fuse time now in the UFC or maybe the stores page? That's something I have to fiddle with too. If none of this works EricJ is probably right and I should use a bigger bomb, but based on what I'm seeing I think it's not even penetrating the bridge at all because I'm doing something wrong so I'll keep testing.

I was trying to bomb a tank under a bridge today and it just kept blowing up when it hit the top of the bridge like an instant fuse whether I set it to delay 1 or delay 2. Is there something I'm missing or is this just not working right now? I haven't used GBU-12's with a delayed fuse in a while, but I don't remember this ever being a problem.

Cool. Thanks!

Do I have this right or should up and down be reversed? I want it the same as a real hornet. I know I'm overthinking it, but I want to be sure.

Every other time playing a mission there's no explosion sound while some of my bombs or missiles hit their targets. 1-2 out of 4 missiles, for example, might have no sound when they hit even if they're spaced apart. I'm watching the explosion from F7 view from another ground unit. I thought I was too close to the target that was getting blown up, but that wasn't it. It's happened further away, close up, with bombs, with missiles, etc. It happens randomly. I think it's a bug so reporting it.

Thanks for the input. Update: I’m am leaning back towards GPU now so you might be right. The issue happens most often while switching to the map screen or changing views. I do that a lot because I’m making videos & recording with OBS. Luckily, I ruled out OBS as being the problem by getting the issue to happen without it running. That was one of the reasons I thought I might need a new CPU. I’m focused on thunderstorm carrier landings right now, but when I get a chance I’ll do more troubleshooting and update this.

Never mind, the problem came back again just as bad as before so no solutions found so far. Drat.

I’m trying things suggested and so far not much is changing. Setting the max frame rate to 72 in the Nvidia control panel instead of just the game might have helped reduce it a little. Setting the VR bitrate to max in virtual desktop if you have a good 6E router is the number 1 step to reduce the problem. At least it’s still okay if you keep your head still while it’s happening with these 2 steps. as for the CPU or GPU decision, I hear AMD’s X3D CPUs really help with this so I was about to upgrade… and they’re all gone.. Oh well. I’ll wait.

I just checked it now. Seems good. It stays around 1-2% like you said. I’m very anti-bloatware so only what I need running.

Nice. I’ll try that. It was set to 120 FPS. I can’t set it to the same as my headset though. I have the Quest in 72hz mode. I’ll have to try 75 FPS since the slider in DCS doesn’t go in smaller intervals. Might have to try 80hz mode if that doesn’t work.

32GB Yea, my paging file is on a m.2 NVME drive. It’s on my system drive & DCS is installed to a different NVME drive.

Cool, I’ll try testing those. Thanks. I do have 4 sticks of ram instead of 2. They are the same model number, but with different version numbers. Same timings though. I extensively tested that with memtest and it passed everything. Multiple overnight tests. I can’t rule out there being differences between the controllers or something. That’s the only thing that’s making me lean towards upgrading my platform instead of the GPU. I really have a feeling it is GPU related though just because I didn’t get this issue with a GTX 1080 but I was running an older version of DCS so there’s too many variables to know. The classic too many changes at once.

Oh maybe it’s weather. I’m working on a heavy thunderstorm mission. I think it happened in a different time though too with no weather. Yea I got it to happen while just flying around the Persian gulf map one time. It happened in the main menu too with no mission loaded so IDK what to think.

It says that I’m CPU limited when there aren’t any stutters and says I’m GPU bound when it’s stuttering. This happens on the lowest game settings too. Seems like a bug when you change views or open the map to me, but I’d still throw money at fixing it in the short term

My stutter in DCS comes and goes. When it happens, I have to take off the Quest 3, put it down, wait 2 minutes, come back to it and it’s back to normal again. when I had the HP reverb, I could get it to stop happening by alt-tabbing. would upgrading my platform or graphics card help? which would you do?

.9900k .3070 I’m getting serious stutter that happens 2 or 3 times each session that turns my VR into a slideshow. It happens when I switch views or open the map. It’s like the terrains get stuck loading or something or at least I thought so until it happened in the map editor too. I have to put down the headset and leave it for at least 2 minutes for it to go back to normal. It might be the 8gb of VRAM not being enough on the GPU, but I really don’t want to do an upgrade and find out that I still have the bug. Which upgrade would you do? Platform or graphics card?

Update: I tried Virtual Desktop, bought the recommended 6e Router for it and the problem still keeps happening. Sometimes it even happens when I’m not even in a mission in the map editor or settings window. *** maxing out the VR Bitrate in the Streaming settings on Virtual Desktop changed the behaviour of the bug. Now it does the same thing my HP Reverb does when the bug hits. It’s not as bad and the frame rate isn’t as low and frame times aren’t as high when it’s happening. It’s still pretty bad, but this is information. The problem affects all VR headsets. Using the Quest over a link cable or without increasing the VR bitrate with Virtual Desktop just causes the problem to be a lot worse while it’s happening.

The stutter came back You have to restart to get rid of it still too. All of this troubleshooting still reduced the frequency of the problem by a lot, but OMG I hate this bug. I hope Eagle Dynamics is working on fixing it all together.

Update: the stutter is still gone but the white transparent bar in the lower side of my right eye came back so that wasn’t HDR that caused it. I have my screen resolution set to the right eye for the window to capture it so I’m thinking it’s something in windows not in the game settings if it’s not connected to the landing lights or position lights or something. I did have them on while it happened. Changing views around with F2, F3 and alt-tabbing etc fixes it temporarily for now but it likes to keep coming back. I’ll update this again if I ever figure out what’s causing it.

That sucks. Here’s a picture of my settings from after I got the problem to go away. I reset everything to defaults beforehand some maybe that helped too. I was able to increase most of the graphics settings after this, but it’s a good baseline.