Jump to content

Game stays active after quiting it.


MadJiitensha
 Share

Recommended Posts

I have the same problem. Close DCS, then it stays green on my Library list. But this only happens if the game becomes "unstable" for some reason, like when playing in a server for a while, then GPU RAM skyrocket to more than 6Gb, then everything after that becomes "slow", when you move around menus inside DCS. Upon closing, then it stays running in the background.

Link to comment
Share on other sites

@MadJiitenshaInteresting. Your log file shows DCS is doing its proper closing but the last log line never comes.

Please try adding this folder as an exception in your antivirus software:

 

2021-06-12 16:41:04.034 INFO    VISUALIZER: StopSimulation
2021-06-12 16:41:04.108 INFO    VISUALIZER: Stopped collection of statistic.
2021-06-12 16:41:04.181 DEBUG   LuaGUI: --- onChatMessage---	Mission is over.	nil
2021-06-12 16:41:05.221 INFO    EDCORE: (dDispatcher)enterToState_:3
2021-06-12 16:41:05.221 DEBUG   LuaGUI: --onShowIntermission-GAMEGUI---
2021-06-12 16:41:06.076 INFO    EDCORE: (dDispatcher)enterToState_:5
2021-06-12 16:41:06.344 INFO    DCS: application shutdown
2021-06-12 16:41:06.943 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 0
2021-06-12 16:41:06.947 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 1
2021-06-12 16:41:06.947 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 2
2021-06-12 16:41:07.102 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 3
2021-06-12 16:41:07.233 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 4
2021-06-12 16:41:07.242 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 5
2021-06-12 16:41:07.245 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 6
2021-06-12 16:41:07.249 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 7
2021-06-12 16:41:07.249 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 8
2021-06-12 16:41:07.253 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 9
2021-06-12 16:41:07.253 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 10
2021-06-12 16:41:07.254 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 11
2021-06-12 16:41:07.254 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 12
2021-06-12 16:41:07.255 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 13
2021-06-12 16:41:09.208 INFO    VISUALIZER: SceneManager_Implement::~SceneManager_Implement()
2021-06-12 16:41:09.213 INFO    VISUALIZER: TerrainRenderer::release
2021-06-12 16:41:09.435 WARNING LOG: 1 duplicate message(s) skipped.
2021-06-12 16:41:09.435 INFO    TERRAIN: lSystem::exit()
2021-06-12 16:41:09.435 INFO    TERRAIN: lSystem::CleanScenes()
2021-06-12 16:41:21.531 INFO    DX11BACKEND: DX11Renderer::shutdown()
2021-06-12 16:41:28.146 INFO    DX11BACKEND: textures_count: 0
2021-06-12 16:41:28.146 INFO    DX11BACKEND: textures_size: 0
2021-06-12 16:41:28.146 INFO    DX11BACKEND: buffers_count: 0
2021-06-12 16:41:28.146 INFO    DX11BACKEND: buffers_size: 0
2021-06-12 16:41:28.146 INFO    DX11BACKEND: CB_count: 0
2021-06-12 16:41:28.146 INFO    DX11BACKEND: CB_size: 0
2021-06-12 16:41:28.146 INFO    DX11BACKEND: SB_count: 0
2021-06-12 16:41:28.146 INFO    DX11BACKEND: SB_size: 0
2021-06-12 16:41:28.146 INFO    DX11BACKEND: IB_count: 0
2021-06-12 16:41:28.146 INFO    DX11BACKEND: IB_size: 0
2021-06-12 16:41:28.146 INFO    DX11BACKEND: VB_count: 0
2021-06-12 16:41:28.146 INFO    DX11BACKEND: VB_size: 0
2021-06-12 16:41:28.146 INFO    DX11BACKEND: total_buffers_size: 0
2021-06-12 16:41:28.146 INFO    DX11BACKEND: total_size: 0

 

@AleCislaPlease attach a dcs.log file showing this issue.

A track or it didn't happen.

Link to comment
Share on other sites

  • 3 weeks later...

I think I got the same problem in patch that brought Mi-24P.

Two DCS process are running, both will be increasing resources use at about 25% of CPU, and memory of 6-8 GB of each.

Have not yet had time to trace the reason. But will cause severe fps drops after first spawn and requires killing both process.

 

image.png

 

After 15 minutes it stays like that, the CPU is eaten alive but used RAM is freed.

Killing either one doesn't affect the other.


Edited by Fri13

i7-8700k, 32GB 2666Mhz DDR4, 2x 2080S SLI 8GB, Oculus Rift S.

i7-8700k, 16GB 2666Mhz DDR4, 1080Ti 11GB, 27" 4K, 65" HDR 4K.

Link to comment
Share on other sites

 Share

  • Recently Browsing   0 members

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