Multiplayer Crashes

[pepin1234]

a Lot of Crashes in MP Open Beta

DCS Crashes.zip

Edited June 4, 2021 by pepin1234

[BIGNEWY]

Hi pepin1234

 

I would try a slow repair on DCS, 

Make sure windows and display driver is up to date 

increase your pagefile, currently it is set to 8027 MB, as you have 16GB RAM you should set pagefile to  16282 MB

 

Let us know if it helps

[VFA41_Hedgehog]

Whoa.  Are you saying that he should set his Windows pagefile to the same size as the amount of RAM on the machine??  That is contrary to everything I have read about pagefile size.  

Edited June 4, 2021 by VFA41_Hedgehog

[Flappie]

1 hour ago, VFA41_Hedgehog said:

Whoa.  Are you saying that he should set his Windows pagefile to the same size as the amount of RAM on the machine??  That is contrary to everything I have read about pagefile size.  

 

 

Don't trust everything that you read, then. DCS has a funny way of dealing with memory. Unless you have 64 GB of RAM, DCS can crash if the given pagefile is too small. Anyway, the issue here is this one:

 

2021-06-04 05:10:33.843 ERROR   DX11BACKEND: Shader "bazar/shaders/model/self_illum_material.fx" failed to compile. Reason:
warning X4717: Effects deprecated for D3DCompiler_47
deferred/shading.hlsl(19,2-63): warning X3206: implicit truncation of vector type
functions/deferred_def_ps.hlsl(47,9): warning X3206: 'BuildGBuffer': implicit truncation of vector type
enlight/atmFunctions.hlsl(966,32-67): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
enlight/atmFunctions.hlsl(966,32-67): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
enlight/atmFunctions.hlsl(966,32-67): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
error X8000: D3D11 Internal Compiler Error: Invalid Bytecode: Failed to parse shader using reference shader parser: 0x8007000e
def_material.fx(32,1-30): There was an error compiling HLSL shader variable

 

I believe all users having this crash solved it doing a slow repair, just like BIGNEWY suggested.

[BIGNEWY]

13 hours ago, VFA41_Hedgehog said:

Whoa.  Are you saying that he should set his Windows pagefile to the same size as the amount of RAM on the machine??  That is contrary to everything I have read about pagefile size.  

 

 

No I am saying if you have 16gb or less you should set your page file higher for a better experience in DCS. If you have 32GB RAM leave it system managed it will be fine. 

[VFA41_Hedgehog]

I guess I was confused by the part where you told him that if he has 16GB RAM he should set his pagefile size to 16GB.  

 

 "...as you have 16GB RAM you should set pagefile to  16282 MB"

[pepin1234]

guys this last update is killing the memory. The game is unstable. I did all what you told me and still not really good. I am missing GUI graphics when I play long or do it something.

[=Skywarp=]

I'm having a lot of freezes in the Multiplayer screen after update do Stable 2.7 since yesterday.

 

Screen freezes and I have to kill DCS in the task manager.

 

I've done a Steam files verification, and deleted fxo/shaders. Helped for one/two times, then the bug returns.

Edited June 13, 2021 by =Skywarp=

[Flappie]

@=Skywarp=Please reproduce the issue then attach your dcs.log file ( C:\Users\username\Saaved Games\DCS...\Logs\dcs.log ).

Does it happen while the MP servers list is refreshing or once you reach a server lobby?

[=Skywarp=]

Hi Flappie!

 

Happens while the MP servers list is refreshing.

[silverdevil]

https://docs.microsoft.com/en-us/windows/client-management/introduction-page-file 

 

when windows runs out of physical memory, infrequently used bits are saved in virtual memory and recalled when needed. if the system has lots of physical memory, then windows does not use virtual memory. when one sets to a static size a pagefile.sys file is created. i do not have a pagefile.sys on my system because of the over abundence of physical memory. leaving windows to manage does not create a pagefile.sys.

 

many moons ago for servers, virtual memory was set to 3 times the amount of RAM. this allowed for "dumping" physical memory during a recovery from a stop error.

[Flappie]

5 hours ago, =Skywarp= said:

Hi Flappie!

 

Happens while the MP servers list is refreshing.

 

If you wait long enough, does the servers list eventually come out of its coma?

 

This is what is described in this thread:

 

 

Edited June 13, 2021 by Flappie

[=Skywarp=]

I taught the glitch was unrecoverable, as I waited for few minutes... so I killed DCS with the Task Manager.

 

This is the message displayed by the Realibility History: "Top level window is idle"

[Flappie]

OK. Please reproduce ths issue, then attach your dcs.log file ( C:\Users\username\Saved Games\DCS...\Logs\dcs.log - may appear as "dcs" ). If you don't do this, neither testers like me nor ED devs will know how this is happening to you.