vv3sl3y

well i'll be damned, somehow copying your settings worked :D thank you very much for your help! now I can also edit my settings without having to delete them everytime :lol: no idea what caused the problem but as far as i know it is solved now :P

well first time i've booted i got an error about not able to read memory 0x00000000 but that was one time only after that i haven't seen it, havent tried after rebooting though maybe it'll give the error again, then i'll remember to take a screenshot the config i have after starting dayz and editting the settings ingame are: language="English";adapter=-1;3D_Performance=100000;Resolution_Bpp=32;Resolution_W=1920;Resolution_H=1080;winX=16;winY=32;winW=800;winH=600;winDefW=800;winDefH=600;refresh=60;Render_W=1920;Render_H=1080;FSAA=4;postFX=0;GPU_MaxFramesAhead=1000;GPU_DetectedFramesAhead=3;HDRPrecision=8;lastDeviceId="";localVRAM=2147483647;nonlocalVRAM=1095507968;vsync=0;ssaoEnabled=0;AToC=15;SWLayersCount=0;PipQuality=3;PPAA=4;Windowed=0; the directx and vcredist versions i've installed were the ones provided with dayz itself included in the dayz folder in steam every time i start dayz it says this programm has stopped working, it asks if i want to debug dayz with visual studio but that message screen also freezes when it pops up :| Spec of my PC are:CPU: AMD fx8120GPU: AMD HD7950RAM: 8GbOS: windows 8.1

i only use -nosplash atm, earlier i used -skipintro and -nopause but those don't have any affect either

I've installed the 0.53 update and i can't really play it at the moment. I've done several things now like reinstalling the game, reinstalling drivers and the suggestion from battleeye to reinstall vredist and directx. so i've started to delete multiple files and found out that it is the dayz.cfg that's causing the game to crash. i have to delete it before i can play, that means that i always have to redo all the settings. I've tried starting DayZ up thus generating a new DayZ.cfg and closing it instantly to avoid self applied changes but dayz crashes then. anyone who has any suggestions about this? the problems started at 0.53, never had any issues like this with previous updates.