Buzzer1977

My best guess would be they're heavily involved with Heatblur in getting the core adjusted to perform with all the eye candy that will come with the F-4.

When will the Kola map be available on steam? It should be available with todays release, but i can't find it on steam yet. Update: It's now here: https://store.steampowered.com/app/2778890/DCS_Kola_Map_by_Orbx/ #solved

My point is: I'm currently using the 24GB of VRAM when i play, stepping down and fetching textures from main memory will notably lower performance. Therfor i look at the top models only. And of course i want the system to perform and to get the best bang for the buck, but there is no performance data for DCS in VR for the AMD stuff. It's known that the 7000 series was even slower then it's 6000series predecessor in VR. Is this now fixed for DCS with new drivers or is this a system inherent problem of the 7000 series chiplet and/or RAM cache design? That's why i'm asking. Yes, i do have a 3090, but my son doesn't. And that's the reason why i need a new graphics card in the first place. With his current GTX960 he will only see a freeze frame after the other ... So it's basically option 3)

Well, i didn't. But i still don't know which way to go. 7900xtx, 4090 or wait for the next gen. That's the question.

1.) Press "5" on the numpad to solve your 'above the canopy' issue. This will realign your position to default. 2.) The CPU is okay. 3.) More RAM. 64GB should be minimum for DCS 4.) Make sure you have a decent SSD or better two. One for the OS and one for DCS. 5.) A decade old 970 ain't fun. Especially not in VR. P.s. Thank you for your service.

Hi, i'm currently running my rig on a RTX 3090 and a Ryzen9 5950x with 128 GB DDR4. My son currently has a almost decade old GTX960 on a Ryzen 7 5800x3d, also with 128 GB of DDR4. My son really needs a new Graphics card to go VR, so i'm considering the following options: 1.) Buy him a AMD RX7900 xtx Problem: The 7k9 had or still has serious issues with VR titles. Are these fixed with recent drivers especially for running DCS? Pro: It's only €1k 2.) Buy me a 4090 and pass on my 3090 to my son Problem: It's $$$ Pro: I could wait until the 5090 is released and the prices may drop a bit for the 4090. But seeing the high $$$ for old 3090s i doubt there will be a large price drop after the 5090 release. 3.) Wait and buy me a 5090 or RX8000 and pass on my 3090 to my son Problem: Unclear when, what and how much it'll be. Especially if it'll require faster bus then PCIe 4.0 to perform. After experiencing the performance issues with the 3090 on PCIe 3.0 instead PCIe 4.0 i wonder how much running a RTX 5000 series might have issues running on a slower bus. I'm really torn apart what to do. It's only 6-8 month until the new stuff get's released and i'm therfor currently tending towards option 3.) Any suggestions? Regards buzzer1977

Probably a hardware issue and not VA or SRS. Most likely insufficient cooling or insufficient power supply or damaged hardware from insufficient cooling or insufficient power supply.

I added all combinations of SR/TR for the S-300 on the map. All with the same layout, and the same targets circling overhead. Only the SAMs with a clamshell SR haven't even been able to fire once.

S-300 clamshell search radar is broken. A S-300 site with a clamshell search radar won't fire. See attached track, mission file, debrief and dcs.log. S-300-clamshell-bug.log S-300-clamshell-bug.miz S-300-clamshell-bug.trk dcs.log

There are 3 S-300 search radars: Big bird, clam shell, tin shield. None is mobile, all 3 are trailers without a tracktor.

A trailer without a tractor won't move in DCS and is not mobile. All other units required for a S-300 site have at least one mobile version in game. LID-A tracking radar -> just a trailer, therefore not mobile LID-B tracking radar -> mobile

I created a little test mission for all kind of SAMs. Seems like some SAMs have very hard times to shoot down anything. See track and mission. And btw. there's no mobile S-300 search radar. Making the SA-10 search radar compatible would be a nice solution until a real mobile S-300 search radar is available. SAM-performance.miz SAM-performance.trk

The S-300 (SA-10) units lack a mobile search radar, so a S-300 site isn't mobile. All other necessary units are movable, like the LID-B tracking radar. Would be nice to have a mobile search radar to reinforce SAMs in game.

Have tried for several days now to replicate it in single player, but it hasn't happen yet.

How to replicate the Bug

I was able to recreate the issue in the ME that triggered all of this. As you can see, the menu on the right has changed back to "Route" while the main screen is stuck in "Ammo". And as before reloading the mission from File->open results in the same stuck load screen. New dcs.log also added. I'm gonna investigate further how to reproduce it more exactly. dcs.log

I was just building a small plain mission to demonstrate another bug (the low performance with moving ground units), when ME decided not to switch back from "Ammo" to "Route" on a ground unit. I was able to save the mission file, but while reloading it DCS just hung in the loading screen for ever. Mission file and dcs log are added. Moving Units Performance.miz dcs.log

It seems like moving ground units are a performance killer. As soon as i add a few convoys to capture other airfields, performance drops extremely low.

A S-3B tanker got stuck in CAT 1 for ever while placing the launch bar Track file is pretty large because it happened in multiplayer. S-3B tanker stuck on CAT.trk

I've got a F-15E with multiple guided weapons (2*JSOW, 3*GBU-54B, 2*GBU-31(V)3/B, 1*GBU-24) After launching the JSOW via CC i can't switch to the other weapon stations which are still in 'INIT' state. Waiting until TIMPCT doesn't help either, i still can't pick a station in 'INIT'. Is this a bug or works as designed? How can i launch JSOWs with CC and while they're on their way do stuff with the other GBUs ? Track, mission and debrief are added. *SOLVED* Select another PROG with different STA in ARMA Trainig-F-15E-TGT.miz F-15stuckAfter-CC-JSOW.log F-15stuckAfter-CC-JSOW.trk

After some time the F-15E is stuck in A/A mode. Can't switch back to NAV or A/G and the left MFD is stuck with the A/A radar and can't open the menu. Can't attach a track file, because they're way too large as it usually happens in longer missions.

How is your Quest 3 connected ? MetaLink or Steam Link ? Wi-Fi or LinkCable ?

In the example mission a F-14B (cat 3) and a S-3B (cat 4) will always collide on deck of the Forrestal. This results in a damaged F-14B jumping between the deck and the inside of the ship and it's wingman "gliding" over deck with only a few kts faster then the carrier. F-14jumpingDeck.log F-14jumpingDeck.trk Houthi-Hamas-Hezbollah.miz

Has been requested several times since the module released ...

The landing gear collapses after repair. Zipped track file added. Might be related to: P47RepairBug.zip