All Activity

I dont own the Kiowa so I cant say, sorry

I also have HAGS and Game Mode enabled, and I’m running the latest Nvidia drivers. The results I’m seeing are very similar to the ones I posted earlier, consistent across the last five driver versions. I normally fly in VR, but for these measurements I tested without VR enabled. My CPU cores are unparked as well, otherwise the usual warning would show up in the logs. From what I can tell, the issue is definitely CPU-related, I know there are a lot of factors, but it's clear that there are several users with the same behavior I described and I thought it could give some hints to what's going on here with this issue. If anyone else is seeing the same behavior, it would be helpful if you could share your load times with HT enabled vs. disabled.

Other than GR I can't find anything on youtube for tutorials for SU-27/J-11. Does anyone have any good links? I found one decent looking playlist, but it's in Spanish. I guess I could use auto-translate subtitles, but I'm surprised a module this popular has almost no learning videos?

And, in the end, it worked. After much testing this afternoon/ evening, the solution was to disable G-Sync completely, as simple as that. Even so, I still have to do some testing, because when I open the map (F10) in the Kola scenario, as an example, it freezes for 20 seconds aprox., but after a while, everything works correctly again. One step has been taken, but now I have to get all the peripherals and consoles working, one by one, until they all work together as before. Thank you very much for the help. In any case, in the corresponding section, I suggest to the administrators that, if possible, a tutorial could be created to configure DCS from scratch, with Windows settings, with adjustments in the simulator settings, etc. It's very negative that in the end we'll spend more time configuring the equipment than actually flying. I'm aware that there are 1,000,000 different computers due to their components and OS versions, but I'm sure, a permanent post can be made with these things, updating them at the pace of the administrators or as needed. "Parking cores", "not running in administrator mode", "no game bar", "G-Sync stuff", "V-sync off", etc, etc., etc. A list of recommendations to ensure that installing DCS will not be unfriendly. When everything works fine, there's no problem. When you suddenly update and everything stops working, it drives you crazy. What I discovered today about G-Sync is just one of the 10 or 15 things I've had to change in the process. Thanks again!.

I understand and did all that but to no avail...

So my Shrike missing by like 100ft is a game issue not a setup or me issue?

In a very improbable incident, Russia launched an attack from Belarus, ran through Poland without stopping, and got into Germany, where they occupied Leipzig in an attempt to hold the city hostage, to force Europe to withdraw support to Ukraine. Naturally, the Poles closed the retreat for Russia and now a small corps is stuck in Germany, with no possibility of rescue, bent on causing as much economic damage as possible before being annihilated. They spread out from Leipzig. All this is just an excuse to blow up Currenthills new assets with an Apache on the CWG map. Not having strategic SAM defense, they rely on tactical SAMs like Tor and Pantsir. A small gap between these, have been found with a soviet column moving south, the gap is about 4km, just enough room to send 2 Apaches for an ambush(naturally the AI Apache flew right into the SAM and got shot down immediately. ) We also encountered the offspring between a T90 and Zeus, the TOS-1 is a demi-god, almost indestructible, it took around 200 30 Mike Mikes to start smoking, and then we were out of ammo(Currenthill is on it and it will be adjusted)

In a very improbable incident, Russia launched an attack from Belarus, ran through Poland without stopping, and got into Germany, where they occupied Leipzig in an attempt to hold the city hostage, to force Europe to withdraw support to Ukraine. Naturally, the Poles closed the retreat for Russia and now a small corps is stuck in Germany, with no possibility of rescue, bent on causing as much economic damage as possible before being annihilated. They spread out from Leipzig. All this is just an excuse to blow up Currenthills new assets with an Apache on the CWG map. Not having strategic SAM defense, they rely on tactical SAMs like Tor and Pantsir. A small gap between these, have been found with a soviet column moving south, the gap is about 4km, just enough room to send 2 Apaches for an ambush(naturally the AI Apache flew right into the SAM and got shot down immediately. ) We also encountered the offspring between a T90 and Zeus, the TOS-1 is a demi-god, almost indestructible, it took around 200 30 Mike Mikes to start smoking, and then we were out of ammo(Currenthill is on it and it will be adjusted)

You are supposed to overwrite the existing textures file. You don’t need to unzip it. The Solution Of The Mod manager Was To Easily Change From One Version To The Other Without having, To backup IT Yourself. Other uses Have reported That It Worked Fine on FC

i5 12600k here, hyperthreading is enabled (never disabled it) and have no problem with getting into the menu within 30 to 40 seconds. Cores unparked and when they were parked, the issue was not present either. Something else being affected by hyperthreading might be the issue. HT is pretty dominant these days across all setups, if it was it everyone would see forums melting over it. HAGS on, Game mode on (why both of these are on in my system atm is a long story. HAGS off vs on makes no difference in loading times), nvidia driver 1 version behind from the latest, no VR installed, trackIR app running and no HOTAS app on (VKB HOTAS, its preferences are stored in its hardware). 64gb Ram, 30gb pagefile on a ssd nvme, DCS on a SSD nvme. Just trying to give more details from a setup that is not experiencing the issues. Also, set Shader Cache Size on nVidia control panel or something equivalent on AMD, to Default or some other value but OFF, if you even changed it from Default to OFF. That induces huge loading times with it OFF.

Works the tutorial was just bugged I made a mission and it works for me thanks!

Thank you!

I don't have the Germany map. But I have the Afghanistan map. I fly mostly the F-16. I got the Apache too, but... never really tried it out My problem now is that my headset is at my cabin, far from where I live. I brought it there along with my PC to test and fly a little during our summer vacation. Norwegian summer = usually lots of rain and <profanity>ty weather. Then I went home here where we live, about two weeks ago, only for a weekend (that was the plan) before I was supposed to return to the cabin - but for several reasons I can not go back to our cabin yet... so. Here I am. Home. Where I have my F-16 "cockpit" and most of my flying gear. But no Crystal Super headset Hopefully I will get a chance to go pick it up later this week. I have read that the Germany map is more demanding, so perhaps stable over 72 fps over Berlin won't be possible. Don't know. The maps I have tested are Kola, Syria, Caucasus, Afghanistan. I have not installed latest DCS update. And I am on an earlier version of Pimax Play, and I don't have the latest Crystal Super firmware either. Since everything worked so well for me I was hesitant to do any Pimax upgrades... Now I have to wait anyway until I get my headset back here.

Yes it’s awesome

That was allegedly fixed according to the 2.9.19.13478 changelog: However, HARMs will also hit destroyed emitters with perfect accuracy. The attached .trk an Tacview show an HTS-targeted PGM5 POS PB shot at an active P-19 followed by a second POS RUK shot. The second shot was fired shortly before the P19 was destroyed. However, it will still home on the dead P19: Tacview-20250901-193008-DCS.zip.acmiHARM_HTS_POS_hits_dead_P19.trk Same applies for an initial HAS POS shot followed by three HAS shots. All follow-up shots will home on the destroyed P19: Tacview-20250901-194932-DCS.zip.acmiHARM_HAS_hits_dead_P19.trk

Thanks for the help, SD Quick update although it may not last…. I updated my BIOS and since I can’t run all 4 sticks with XMP enabled and at its rated 6400Mhz, I backed off the memory speed from 5600 CL36 to 5400 CL36 and locked in my voltage to under 1.3, watts at 307 Still running my 14900k at 5.5Ghz tested it twice and both times I was able to reach the desktop on safe mode to make my changes. If this changes or “breaks” I’ll report back. conclusion: it appears memory timings and memory settings may affect windows ability to boot into safe mode but it’s just a guess. So far all things point to BIOS update since changes in the older BIOS wasn’t helping but we will see. So far so good

LOC28 at Bardufoss is offset 2.1° to the north, and the LOC is located to the south of the runway (as opposed to the usual location, along the extender centerline, ~300m beyond the threshold of the reciprocal rwy), so you will definitely get some unusual indications on your CDI when on the ground. https://aim-prod.avinor.no/no/AIP/View/Index/141/2025-06-12-AIRAC/html/eAIP/EN-AD-2.ENDU-en-GB.html#AD-2.ENDU

ah, ok…. missed that no idea

+ 3 months and a week to be exact

Quick update: BIOS, Nvidia and Intel Arc update hit me last week so I just updated *everything* and tested again with hyperthread support enabled. Double clicked the regular BIN executable (not the MT executable) From desk top to DCS main menu with HT enabled - 2:03, as in two minutes, three seconds From desk top to DCS main menu with HT DISabled - :43, as in forty three seconds This isn’t a user issue. I hope ED looks into this because it looks like hyperthread support is broken in DCS. For better transparency I did notice that the max CPU temp to bring up the DCS main menu was 73 with HT enabled and 58.5 with it disabled. Seems par for the course. - Confirmed all cores UNparked.

Except he was talking about using a mod manager and that the files would be overwritten each time DCS updated?

@Calvin.Pimax Ive been doing what I can to get pimaxplay 1.41.2 to run DCS with quadviews. I have multiple issues with DCS crashing that appear related to quadviews. Im using only quadviews within PP. I have uninstalled the openrx items. 1) without quadviews I get a pretty soil 35fps and DCS seems crash free. (im using syria instant action f14 takeoff from turkey the night one as a test) 2) with quadviews I get a pretty solid 35 fps or 60fps or 85 fps it just depends on how it feels during that launch I guess I cant find anything related to this not even resolution / global settings vs game settings. More resolution I get maybe 85 fps then i dial it back and I get 35 fps 2) with quadviews running like crap (35 fps) and settings low say 70% render resolution dcs wont crash or wont crash quickly. 3) with quadviews running great like 80-90 fps at 100 or 150% render resolution It usually crashes in a minute to 10 minutes or on final load screen just before you click "fly" or whatever with the background and cockpit visible behind that window. there is no consistency or obvious pattern to which outcome im going to get. Is there anything I can submit or provide you that could help isolate this issue?

Dynamic weather has been mostly untouched since DCS 1. It does not even support the "new" clouds from 2021.

Ahhh...Gotcha!