Buzzer1977

Hi, i'd like to buy the FC3 to FC2024 upgrade for my son as a gift, but i can't find it in the shop. I only can see the full FC2024 version to buy. How can i buy him the upgrade? I'm on steam, while he uses the native version. Regards Buzzer

German documentation with auto translate subtitles about the German F-4 tactical evaluation during a NATO exercise in 1977.

Found the issue: *PEBCAC I've copied the wrong version of the file to the server directory. *Problem Exists Between Chair And Computer

It seems like it's a issue with MIST or IADS

Here's the dcs.log. But the only thing i can see is the connect/disconnect of the external BD drive i just dropped from my desk.

I've got a mission (mission file attached), that works fine on a locally hosted multiplayer and in standalone, but doesn't have any slots on dedicated server. Seems like there's just a option set that i'm not aware of, or the ME somehow corrupted the file, or dedicated server has a issue. This is how multiplayer looks on a locally hosted server. Syria-MkIV.miz

Same here.

The F-4E radar sometimes has problems seeing large targets like a Tu-160 or Tu-95. I can easily find and lock up on fighters like the MiG-21, but the radar struggles with larger targets. At first i thought it would be a AIM-7 issue, but it looks more like the F-4E radar. Sample track and mission added. At the end of the track you can see how hard it was to get the target locked. I had to get within 3-4 NM to find a Tu-95 and a Tu-160, whilst i could find and lock onto the MiG-21 and even the Tu-22 at the start easily from far greater distance. F-4E-radar-problems.trk F-4E-AIM-7-bug.miz

Same here. I have a track (see file attached) with these AIM-7 issues. Problems: 1) I have a lock, but can't fire. (No, the center tank is already jettisoned or i still have the two AIM-7 in the back) 2) I can fly directly behind a behemoth sized Tu-160 and can't get a lock. Different, but same problem with AIM-9: 3) Sometimes i can only fire the first AIM-9 Sidewinder, the second one is somehow stuck P.s. I'm aware of the " I am encountering weird behavior, like some weapons not working", but i don't have any external mods installed. the AIM-7problems.trk

Waiting for the Phantom ... ... and I just can't simply sit and wait. Any suggestions when it will get released today (times in UTC)?

a KC-135 would be a sufficient KC-707 replacement. The difference is minor. It's basically the same aircraft with just a few inches difference in fuselage diameter and a few ft in length.

Having seen in some prerelease footage, that the F-4E will come with a Iranian livery as well, there should be a corresponding KC-135 for Iran. But there is no Iranian KC-135 in DCS, only a Iranian KC-135MPRS, and both lack Iranian liveries. This should be a easy one to fix. 1) Add IRN to the KC-135 config file 2.) Grab a free IRIAF and a IIAF livery and add it to DCS, or ask @sadjad-vosoul to provide one of his great liveries. This shouldn't be much of a big deal, but would improve DCS authenticity a lot.

AI KC-130 goes inverted and climbs almost to space at super low speed of only 64 km/h. KC-130-inverted-FL900.log KC-130-inverted-FL900.trk

It just happened again. Might just be coincidence but it again happened on the Kola map.

Attaching the debugger failed, but it reported some stuff that looks interesting: ... The thread 17468 has exited with code 3735929054 (0xdeadc0de). The thread 'pc_network_thread' (4384) has exited with code 3735929054 (0xdeadc0de). The thread 'Thread 0x0000234600238800' (2400) has exited with code 3735929054 (0xdeadc0de). The thread 21068 has exited with code 3735929054 (0xdeadc0de). ... The thread 23684 has exited with code 3735929054 (0xdeadc0de). The thread 'rtc-low-prio' (26364) has exited with code 3735929054 (0xdeadc0de). The thread 'AudioDeviceBufferTimer' (4892) has exited with code 3735929054 (0xdeadc0de). The thread 4680 has exited with code 3735929054 (0xdeadc0de). ... The thread 21600 has exited with code 3735929054 (0xdeadc0de). The program '[15696] DCS.exe' has exited with code 3735929054 (0xdeadc0de). DCSdbglog.txt dcs.20240503-135018.dmp dcs.20240503-135018.crash

I was running a mission on the new Kola map, when DCS just froze. After switching to the TaskManager i can't switch back to DCS. The DCS.exe process is still active, but the DCS icon in the Taskbar is missing. Added the DCS.log and the mission file. I'm gonna try to attach the debugger to see if i can do a dump or at least get a stack trace. Update: Can't attach the debugger to the process null dcs.log Kola-1.miz

I can't add track files, debrief logs, mission files to the external Orbx bug reporting, to make bug fixing easier.

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.