Jump to content

Game Crash 2.7


jfnelson0127

Recommended Posts

8 hours ago, jfnelson0127 said:

Thanks Flappie. I've had full screen optimizations disabled for a while, so I don't think this is the culprit unfortunately.

Then you really should give it a go. See here:

 

 

@TRShrumPlease open a new thread and attach your dcs.log file ( C:\Users\username\Saved Games\DCS...\Logs\dcs.log ). I may simply appear as "dcs".

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

On 4/16/2021 at 8:34 PM, BIGNEWY said:

please remove all unofficial mods and run a verify in steam

 

thanks

For me it was resolved by going to NVIDIA control and resetting everything back to default settings and stopping overclocking. Funny thing is before 2.7 my fps after overclocking was between 30-40fps. After 2.7 and without overclocking 50-80fps.

  • Like 1
Link to comment
Share on other sites

  • ED Team
10 minutes ago, DropBear64 said:

For me it was resolved by going to NVIDIA control and resetting everything back to default settings and stopping overclocking. Funny thing is before 2.7 my fps after overclocking was between 30-40fps. After 2.7 and without overclocking 50-80fps.

 

great to hear, thanks for letting us know

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

My problem solved.  Removed ALL Third Party mods and game functions as it should.  Then reloaded one mod at a time to see which ones caused the problem.  A-4E and A-29 worked just fine.  Will start on the remaining later today.  Will post the ones that I have issues with.

Link to comment
Share on other sites

On 4/18/2021 at 11:34 AM, TRShrum said:

My problem solved.  Removed ALL Third Party mods and game functions as it should.  Then reloaded one mod at a time to see which ones caused the problem.  A-4E and A-29 worked just fine.  Will start on the remaining later today.  Will post the ones that I have issues with.

Did you remove all skins? I have deleted every unofficial item except skins. Crashes continue. Attached are my logs. Any new conventional wisdom on solving this aside form "delete mods and verify"?

dcs.20210420-032100.log dcs.20210420-020600.log dcs.20210419-230652.log dcs.20210419-231043.log dcs.20210420-013545.log


Edited by jfnelson0127
Link to comment
Share on other sites

On 4/18/2021 at 5:34 PM, TRShrum said:

My problem solved.  Removed ALL Third Party mods and game functions as it should.  Then reloaded one mod at a time to see which ones caused the problem.  A-4E and A-29 worked just fine.  Will start on the remaining later today.  Will post the ones that I have issues with.

I removed all the mods as well, and the game crashed 2nd time I did restart the custom mission (in there was only using Su-27 and F-15).

So this story about mods causing game crash IS NOT true at all!!!

Link to comment
Share on other sites

I removed all the mods as well, and the game crashed 2nd time I did restart the custom mission (in there was only using Su-27 and F-15).
So this story about mods causing game crash IS NOT true at all!!!
Your logic is flawed - using mods can cause crashes but they are not the only cause of crashes. I don't use mods and had crashes on the second start of a mission.

I followed the advice to rename the saved games Options.lua so DCS recreated it and then redid my DCS options (not the controller mappings) and this fixed it for me.

Comparing the old and new versions of the options.lua file there were quite a few lines for new settings that were not in the old file. At some point when I get the time I will copy the old one back, try changing a setting and then saving to see if this places all the missing values in the file.

Sent from my SM-T835 using Tapatalk

  • Like 1

Windows 11 Home ¦ Z790 AORUS Elite AX motherboard ¦ i7-13700K ¦ 64GB Corsair Vengeance DDR5 memory @ 5600MHz ¦ Samsung 990 Pro 1TB SSD for OS, Samsung 980 Pro 2TB SSD for DCS ¦ MSI GeForce RTX 4090 Gaming X Trio 24GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk4 and MCG Pro ¦ Thrustmaster Warthog Throttle ¦ VKB STECS Throttle ¦ Virpil TCS rotor base with Shark and AH-64D  grips ¦ MFG Crosswinds ¦ Total Controls Multi-Function Button Box ¦ Pimax Crystal

Link to comment
Share on other sites

I have the same problem as you, my file shows me a texture problem with MSAA 4X but if I put it in 2X it's the same thing, I crash too

2021-04-21 10:01:16.223 INFO VIEWER : StartSimulation
2021-04-21 10:01:16.229 ERROR DX11BACKEND : Failed assert `false && "depth buffer must be the same sizes as color targets"` at Projects\render\dx11backend_win8\Source\DX11FrameBufferManager.cpp:99
2021-04-21 10:01:16.229 ERROR DX11BACKEND : the texture <> does not support MSAA 4x
2021-04-21 10:01:16.229 ERROR DX11BACKEND: Failed assert `false && "failed to create texture"` at Projects\render\dx11backend_win8\Source\DX11TextureManager.cpp:704
2021-04-21 10:01:16.231 INFO EDCORE : attempt to write dump information


Edited by mobile83
Link to comment
Share on other sites

42 minutes ago, mobile83 said:

I have the same problem as you, my file shows me a texture problem with MSAA 4X but if I put it in 2X it's the same thing, I crash too

2021-04-21 10:01:16.223 INFO VIEWER : StartSimulation
2021-04-21 10:01:16.229 ERROR DX11BACKEND : Failed assert `false && "depth buffer must be the same sizes as color targets"` at Projects\render\dx11backend_win8\Source\DX11FrameBufferManager.cpp:99
2021-04-21 10:01:16.229 ERROR DX11BACKEND : the texture <> does not support MSAA 4x
2021-04-21 10:01:16.229 ERROR DX11BACKEND: Failed assert `false && "failed to create texture"` at Projects\render\dx11backend_win8\Source\DX11TextureManager.cpp:704
2021-04-21 10:01:16.231 INFO EDCORE : attempt to write dump information

 

Did you restart DCS after changing the MSAA value?

Windows 11 Home ¦ Z790 AORUS Elite AX motherboard ¦ i7-13700K ¦ 64GB Corsair Vengeance DDR5 memory @ 5600MHz ¦ Samsung 990 Pro 1TB SSD for OS, Samsung 980 Pro 2TB SSD for DCS ¦ MSI GeForce RTX 4090 Gaming X Trio 24GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk4 and MCG Pro ¦ Thrustmaster Warthog Throttle ¦ VKB STECS Throttle ¦ Virpil TCS rotor base with Shark and AH-64D  grips ¦ MFG Crosswinds ¦ Total Controls Multi-Function Button Box ¦ Pimax Crystal

Link to comment
Share on other sites

Not if the MSAA value is changed but the change does not take place until you restart

Windows 11 Home ¦ Z790 AORUS Elite AX motherboard ¦ i7-13700K ¦ 64GB Corsair Vengeance DDR5 memory @ 5600MHz ¦ Samsung 990 Pro 1TB SSD for OS, Samsung 980 Pro 2TB SSD for DCS ¦ MSI GeForce RTX 4090 Gaming X Trio 24GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk4 and MCG Pro ¦ Thrustmaster Warthog Throttle ¦ VKB STECS Throttle ¦ Virpil TCS rotor base with Shark and AH-64D  grips ¦ MFG Crosswinds ¦ Total Controls Multi-Function Button Box ¦ Pimax Crystal

Link to comment
Share on other sites

my game just crashed now, here is my log (with msaa x2)

 

I did a slow repair of dcs world

 

Always the same thing, it loads... BIM!!! Crash return desckop

 

I tried to delete the options.lua file, but it's the same thing, it just crashed

 

Honestly it's getting boring, it's stopping me from playing, every two games it does this to me

 

it crashes only in LOAD, it works very well in game

dcs.20210421-115107.log dxdiag.txt

Sans titre.png


Edited by mobile83
Link to comment
Share on other sites

1 hour ago, mobile83 said:

my game just crashed now, here is my log (with msaa x2)

 

I did a slow repair of dcs world

 

Always the same thing, it loads... BIM!!! Crash return desckop

 

I tried to delete the options.lua file, but it's the same thing, it just crashed

 

Honestly it's getting boring, it's stopping me from playing, every two games it does this to me

 

it crashes only in LOAD, it works very well in game

dcs.20210421-115107.log 406 kB · 4 downloads dxdiag.txt 68.04 kB · 3 downloads

Sans titre.png

 

I understand your frustration. Happening to me as well. I am told they are aware of the 2nd load crash bug, and that it's something on their end that is being addressed. See this thread: https://forums.eagle.ru/topic/267836-2704625-open-beta-crash-at-second-mission-load


Edited by jfnelson0127
Link to comment
Share on other sites

5 hours ago, hornblower793 said:

Your logic is flawed - using mods can cause crashes but they are not the only cause of crashes. I don't use mods and had crashes on the second start of a mission.

I followed the advice to rename the saved games Options.lua so DCS recreated it and then redid my DCS options (not the controller mappings) and this fixed it for me.

Comparing the old and new versions of the options.lua file there were quite a few lines for new settings that were not in the old file. At some point when I get the time I will copy the old one back, try changing a setting and then saving to see if this places all the missing values in the file.

Sent from my SM-T835 using Tapatalk
 

I also took your advice, and renames the Options.lua file, so a new one has been created. And so far I did 10 mission restarts and not a single crash.

  • Like 1
Link to comment
Share on other sites

the options.lua file has not changed anything for me, put to the fact that I have to re-parameterize everything, 5th crash loading

 

On the other hand, it also happens to me, whether it is the first load that crashes, about 1 time in 50, while the second load is once in 5

 

I have to keep my fingers crossed with every load

 

you speak too fast, do the tests well before. Me currently, I can do 6 7 missions without crash, sometimes I do 2 that crash, you speak too fast


Edited by mobile83
Link to comment
Share on other sites

Same issue with crashes for me, both in MP and SP, but the timing is fairly random.  Running the game in VR, no full screen no MSAA, no mods.

Modules: A10C, AV8, M2000C, AJS-37, MiG-21, MiG-19, MiG-15, F86F, F5E, F14A/B, F16C, F18C, P51, P47, Spitfire IX, Bf109K, Fw190-D, UH-1, Ka-50, SA342 Gazelle, Mi8, Christian Eagle II, CA, FC3

Link to comment
Share on other sites

I will post this here, not sure if this is the correct thread but....

Since the first 2.7 OB update i had no troubles with missions not loading (first, second, third...time) or DCS crashing for some unknown reason(exception ofcourse the known reasons for CTD...F10 marker F-14/Viggen). But i tried the F-14 and Viggen the last days more often and with the Viggen(once) and the F-14B(4 or 5 times now) DCS stopped working at mission load(first or second time loading the a mission).

I never had such a problem with the F-16/18, JF-17, Mirage2k, Mi-8 or KA-50, they are working like a charm for me. I posted some dcs.log files in the HB 2.7 feedback thread but now i will post them here too, maybe it helps.... or not.

Last crash(dcs3) was me, placing the Stennis and a F-14B(start from carrier runway) on caucasus, hit start from the ME and DCS stopped working. After restarting DCS i did the same thing and the mission loaded.

 

Btw, after the first 2.7OB update i deleted fxo/metashader2 folders and run a repair for file check(everything was ok).

dcs.log dcs2.log dcs3.log

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

Also crashes on my side after ~10mins.

Eventvwr tells me that Weapons.dll is faulting.

Faulting application name: DCS.exe, version: 2.7.0.5118, time stamp: 0x60812393
Faulting module name: Weapons.dll, version: 2.7.0.5118, time stamp: 0x60812307
Exception code: 0xc0000005
Fault offset: 0x00000000000c3560
Faulting process ID: 0x1720
Faulting application start time: 0x01d7390b493906ce
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin\DCS.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin\Weapons.dll
Report ID: 9bc09f85-fbb4-46e0-911a-39827ff560ca
Faulting package full name: 
Faulting package-relative application ID: 

 

 

dcs.log-20210424-134711.zip

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...