mklengel Posted June 2, 2021 Share Posted June 2, 2021 I checked the available informations (pagefile, update gfx drivers, reinstall DCS, renaming user DCS folder) but quitting DCS is not possible without the windows task manager. The music plays forever but DCS does not quit. Log file is attached. dcs.log Link to comment Share on other sites More sharing options...
Flappie Posted June 2, 2021 Share Posted June 2, 2021 Hi. We can see at the end of your log the game is struggling to get some CPU power: ERROR SOUND: render time = 0.433766s exceeded allowed slice of 0.022000s Please ensure these options are disabled in DCS.exe properties: If this behavior doesn't stop, add this folder as an exception in your antivirus software: "E:\SteamLibrary\steamapps\common\DCSWorld\" Don't accept indie game testing requests from friends in Discord. Ever. Link to comment Share on other sites More sharing options...
mklengel Posted June 3, 2021 Author Share Posted June 3, 2021 (edited) I checked the properties of DCS.exe - everythingwas disabled according to your screenshot. I've added the exception as suggested. After starting DCS I quit without going into my F/A-18C and the same as yesterday: endless music, DCS does not quit. New log file dcs.log is attached. The log file shows some error messages, e.g. ERROR EDCORE: Can't open file 'bazar/shaders/enlight/clouds.hlsl.' from fs 2021-06-03 15:02:52.718 WARNING DX11BACKEND: Shader enlight/clouds.fx:DIRECTX11=true;RAYMARCH_BY_DOWNSAMPLED_NEARFAR_1_4;USE_DCS_DEFERRED=1; is outdated as file bazar/shaders/enlight/clouds.hlsl is modified. Why the error messages? Is my (new) installation corrupted? After this I deinstalled the Nvidia Experience Drivers completly and installed this drivers new. The problem remains - see DCS2.log. dcs.log dcs2.log Edited June 3, 2021 by mklengel Second try with reinstalling GFX drivers Link to comment Share on other sites More sharing options...
Flappie Posted June 3, 2021 Share Posted June 3, 2021 These shader related error messages are OK: everybody is having them. Here is the end of your log: 2021-06-03 15:12:25.199 INFO DCS: Screen: MainMenu 2021-06-03 15:12:26.912 INFO SOUND: Using SSSE3 for peak calc. 2021-06-03 15:12:26.912 INFO EDCORE: (dDispatcher)enterToState_:5 2021-06-03 15:12:26.919 INFO DCS: application shutdown 2021-06-03 15:12:26.992 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 0 2021-06-03 15:12:26.995 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 1 2021-06-03 15:12:26.995 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 2 2021-06-03 15:12:27.095 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 3 2021-06-03 15:12:27.176 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 4 2021-06-03 15:12:27.181 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 5 2021-06-03 15:12:27.183 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 6 2021-06-03 15:12:27.184 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 7 2021-06-03 15:12:27.185 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 8 2021-06-03 15:12:27.185 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 9 2021-06-03 15:12:27.186 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 10 2021-06-03 15:12:27.186 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 11 2021-06-03 15:12:27.186 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 12 And here's mine: 2021-06-02 11:28:12.415 INFO DCS: Screen: MainMenu 2021-06-02 12:04:59.720 INFO SOUND: Using SSSE3 for peak calc. 2021-06-02 12:04:59.728 INFO EDCORE: (dDispatcher)enterToState_:5 2021-06-02 12:04:59.761 INFO DCS: application shutdown 2021-06-02 12:04:59.802 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 0 2021-06-02 12:04:59.804 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 1 2021-06-02 12:04:59.805 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 2 2021-06-02 12:04:59.897 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 3 2021-06-02 12:04:59.974 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 4 2021-06-02 12:04:59.979 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 5 2021-06-02 12:04:59.981 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 6 2021-06-02 12:04:59.982 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 7 2021-06-02 12:04:59.982 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 8 2021-06-02 12:04:59.983 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 9 2021-06-02 12:04:59.983 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 10 2021-06-02 12:04:59.983 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 11 2021-06-02 12:04:59.983 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 12 2021-06-02 12:05:00.368 INFO VISUALIZER: SceneManager_Implement::~SceneManager_Implement() 2021-06-02 12:05:00.368 INFO VISUALIZER: TerrainRenderer::release 2021-06-02 12:05:00.380 WARNING LOG: 1 duplicate message(s) skipped. 2021-06-02 12:05:00.380 INFO TERRAIN: lSystem::exit() 2021-06-02 12:05:00.380 INFO TERRAIN: lSystem::CleanScenes() 2021-06-02 12:05:00.393 INFO DX11BACKEND: DX11Renderer::shutdown() 2021-06-02 12:05:00.489 INFO DX11BACKEND: NVIDIA API exit OK 2021-06-02 12:05:00.489 INFO DX11BACKEND: textures_count: 0 2021-06-02 12:05:00.489 INFO DX11BACKEND: textures_size: 0 2021-06-02 12:05:00.489 INFO DX11BACKEND: buffers_count: 0 2021-06-02 12:05:00.489 INFO DX11BACKEND: buffers_size: 0 2021-06-02 12:05:00.489 INFO DX11BACKEND: CB_count: 0 2021-06-02 12:05:00.489 INFO DX11BACKEND: CB_size: 0 2021-06-02 12:05:00.489 INFO DX11BACKEND: SB_count: 0 2021-06-02 12:05:00.489 INFO DX11BACKEND: SB_size: 0 2021-06-02 12:05:00.489 INFO DX11BACKEND: IB_count: 0 2021-06-02 12:05:00.489 INFO DX11BACKEND: IB_size: 0 2021-06-02 12:05:00.489 INFO DX11BACKEND: VB_count: 0 2021-06-02 12:05:00.489 INFO DX11BACKEND: VB_size: 0 2021-06-02 12:05:00.489 INFO DX11BACKEND: total_buffers_size: 0 2021-06-02 12:05:00.489 INFO DX11BACKEND: total_size: 0 === Log closed. It seems your freeze is caused by the "SceneManager_Implement::~SceneManager_Implement()" function. Please add the attached file in your "C:\Users\username\Saved Games\DCS\Config" folder. It will enable the log debug mode. Then replicate the issue, and attach the resulting dcs.log file. Hopefully, we'll see more things. autoexec.cfg Don't accept indie game testing requests from friends in Discord. Ever. Link to comment Share on other sites More sharing options...
mklengel Posted June 4, 2021 Author Share Posted June 4, 2021 Log with DEBUG attached. Quitting via Task Manager... dcs.log Link to comment Share on other sites More sharing options...
hornblower793 Posted June 4, 2021 Share Posted June 4, 2021 @Flappie I have looked at the log and there is no difference at the end - it just stops dead after the following line INFO EDOBJECTS: lTypeObjectManagerImpl::clear 12 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 More sharing options...
mklengel Posted June 4, 2021 Author Share Posted June 4, 2021 Whatever I do - quitting with the Task Manager results in (last lines of dcs.log): 2021-06-04 12:39:26.013 DEBUG LuaGUI: ~~~Gui.doQuit() 2021-06-04 12:39:26.019 INFO SOUND: Using SSSE3 for peak calc. 2021-06-04 12:39:26.028 INFO EDCORE: (dDispatcher)enterToState_:5 2021-06-04 12:39:26.061 INFO DCS: application shutdown 2021-06-04 12:39:26.140 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 0 2021-06-04 12:39:26.143 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 1 2021-06-04 12:39:26.143 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 2 2021-06-04 12:39:26.249 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 3 2021-06-04 12:39:26.336 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 4 2021-06-04 12:39:26.342 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 5 2021-06-04 12:39:26.344 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 6 2021-06-04 12:39:26.346 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 7 2021-06-04 12:39:26.346 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 8 2021-06-04 12:39:26.347 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 9 2021-06-04 12:39:26.347 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 10 2021-06-04 12:39:26.347 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 11 2021-06-04 12:39:26.347 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 12 Link to comment Share on other sites More sharing options...
Flappie Posted June 4, 2021 Share Posted June 4, 2021 (edited) Please try these steps: Rename your "Saved Games\DCS" folder as "DCS_backup" (do NOT delete this folder, it contains your custom controls and settings) Still not fixed? Run a "slow" DCS repair. Still not fixed? File a support ticket. Add a link to this thread to speed up investigation. Edited June 4, 2021 by Flappie Don't accept indie game testing requests from friends in Discord. Ever. Link to comment Share on other sites More sharing options...
mklengel Posted June 4, 2021 Author Share Posted June 4, 2021 I did this (but no DCS repair because I'm using the STEAM version, instead I did check files in STEAM). The problem remains. DCS.exe is in an unusable state - see screenshot. Log file attached. I'll create a support ticket. dcs.log Link to comment Share on other sites More sharing options...
Recommended Posts