After I’ve installed fresh display drivers and disabled mods. It seems like DCS gets more and more unstable with subsequent updates.
I’ve had insisted to me, to the point of being threatened with warning, that ED’s project managers have the big picture in mind. And, yet, the game is increasing in instability.
Am I crazy or at some point in 2.9 did we not have carrier flood lights illuminating aircraft cockpits? I swear that was a thing because I distinctly remember a few sessions where the flood lights lit up my cockpit enough to not need a flashlight for startup, but recently the cockpits have been pitch black, and I can’t find any screenshots or videos to “prove” my memory isn’t gaslighting me.
I’m not a guru on DCS crashing but, at a very high level this can sometimes get you looking in the correct place…
When it does a CTD in your “Saved Games\Logs” folder there should be a file:
dcs.log-[date]-[bunch of numbers].zip, ie; dcs.log-20241208-123456.zip
In that file is a file with the extension .crash.
It is a text file. Open that in your text editor and you’ll see lines that are mostly unusable to the end-user, with the exception of the 3rd line, like so:
-------------- 20241203-102446 --------------
DCS/2.9.9.2474 (x86_64; MT; Windows NT 10.0.22631)
This line >>> C:\Program Files\Eagle Dynamics\DCS World\bin\GraphicsCore.dll
…bunch of stuff you wont be able to use.
This hints it may be something with the graphics hardware, like drivers. Or shaders - the ‘GraphicsCore.dll’
When I fat-finger my scripts I’ll see;
C:\Program Files…\Lua.dll << meaning I’ve likely hosed up something in my scripts == my fault (then I look elsewhere like the dcs.log file and it can show me the exact line if my error).
This lua example I’m sure not useful to you but you can see how it might tell you what ‘town’ the problem resides (graphics hardward/drivers or the lua engine in the above examples). Finding the exact address can be a bit trickier.
It’s a lot since I made a texture for DCS … I did read something about Eagle Dynamics making them locked? What happens? Users can’t make liveries anymore?
S-3 had some stuff locked. A while back its files got moved from the Bazar folder to CoreMods/tech/HeavyMetalCore, which appears to be the payware HD assets they’re working on.
Inside that there’s a Textures folder that has a zip of the S-3B and other assets. The 3D model is locked in some “.edce” files in the Shapes folder, meaning we can’t even check the model or liveries in the Model Viewer.
S-3B liveries still work from the Liveries folder in Saved Games, but a filename change broke the description.lua files. All of the dds files used to be “low_S3BViking_” but now they’re “low_KS-3A_.” Fix those in the description.lua and it works.
The change doesn’t make any sense because the KS-3A never went into production. “Tanker” Vikings are just stock Vikings with a buddy store.
F1EE: Fixed nonoperating lights of the Barax control panel.
F1BE rear seat ‘fuselage tanks selected’ light on the fuel quantity gauge was made operational.
F1BE. Fixed bug with some lights staying lit at the rear seat without electric power being available.
Fixed navigation and formation lights not working in multiplayer for flyable aircraft.
Adjusted power on/off dynamics of navigation/formation lights.
Adjusted visual look of the landing/taxi light cones.
Fixed search light (police light) cone direction - 45º for single seater and and 22º for two seater.
Fixed blank radar screen, when ‘(C+M or SW) R’ mode is enabled, and radar modes other than ‘HA’, ‘IC’ or ‘TEL’/‘BZP’ are selected. Now the radar will stay in ‘IC’ mode with ‘(C+M or SW) R’ enabled.
F1BE: Fixed radar render in multimonitor configuration.
The radar now correctly sets the ‘emission active’ flag (it is used by AI for emission detection).
Radio and navigation:
Fixed not operating test function in TRAP-136 (‘Green’) radio.
Fixed a bug with inability to communicate with a radio station via TRAP-137B, when the attempted frequency is the same as of the preset channel 20.
Fixed IDN TACAN flag not showing when TACAN signal is lost.
Fixed IDN VOR flag not showing when signal is lost.
Fixed IDN TACAN distance showing a non-zero value under the flag when TACAN distance is not available.
IDN TACAN bearing now stays at the last known value, when the TACAN station is not received.
Input:
Fixed not working Monitoring Light ‘push’ (light test) and ‘rotate’ (light brightness) actions of the old IFF panel variant.
The lights brightness potentiometers of both IFF panels versions are initialized at maximum brightness now (previously was 0).
F1BE TRAP-137B (‘Red’) front seat radio can’t be reached from the rear seat anymore.
Both radios preset channels animation is now in sync with the corresponding channel selectors animation.
Manual gravity drop thumbwheel animation was fixed.
Manual gravity drop thumbwheel animation is now accelerated with time when it is set by ‘Decrease/Increase’ input commands.
Fixed ‘TACAN mode selector Clockwise/Counterclockwise’ commands not reacting on input when the selector has reached OFF or A/A position.
F1EE Navigational Indicator ‘Additional vector bearing/distance adjustment’ switch results now in accelerated bearing/distance change when it is held pressed.
Textures and 3D models:
Fixed landing gear wheels animation of the single seater.
General:
Replaced custom Belouga BLG66 bombs by DCS standard ones.
Added Belouga BLG66 bomb to AUF-2 bomb rack.
F1 C-200 (AI) can now carry the BARAX pod.
AI now uses bottom strobe and orange tail navigation lights (white tail light will be never though visible as AI uses only steady nav lights pattern).
AI now sets formation light brightness according to the current day of time.
Improved taxi, takeoff and climb training mission: Forced realistic comms, added instruction to press U + V pushbutton, IFF mode 4 forced not installed and modified several trigger messages.
Updated Flight Manual - F1EE IDN description and table.
Minor visual fixes in the module Special Options menu.
Fixed F1BE Solo Flight checkbox position in ME UI.
DCS: C-101 Aviojet by AvioDev
Improved textures of the following bombs:
BLG66
BR-250
BR-500
BIN-200
Campaigns
DCS: UH-1H The Huey Last Show Campaign by SorelRo
Subtitles added to all radio communications and crew chat
F-4E updated to the latest F-4E AI
Time compression stop during the voice communication
Other AI updates
DCS: F-16C The Gamblers Campaign by Baltic Dragon
Mission 01: fixed issue with flight lead diverting and not landing at H4.
Mission 03: added a note to prevent players from using GBU in certain scenarios which could lead to mission stalling.
First 1 minute test:
F18 Lot 20
Over Baghdad at ~1500 AGL
Looked good. And with all those buildings and such it ran pretty well. Note this was in 2D 1440 but saw nothing bad [compared to say Syria].
Can someone refresh me here: This map WILL be extended south at some point, right?
For the full version of DCS: Iraq you will receive the entire red area, with the higher detailed blue and green areas as well. (The red area outside the green and blue areas will be in lower detail.)
For the DCS: Iraq North you will receive the entire red area with the higher detailed blue area. (the green area will be low detail with this option)
For DCS: Iraq South you will receive the entire red area with the higher detailed green area. (the blue area will be low detail with this option)