jasonbirder Posted July 18, 2020 Posted July 18, 2020 (edited) Currently the moment I enter a mission...DCS freezes... Its not just taking a long-time to rebuild shaders etc as i've left it for up to an hour... No need to attach a track file as I don't get beyound the "Loading" splash screen (NONE of the loading bar fills) I suspect it may be something to do with my saved games/dcs files...I moved the whole folder and let DCS create a new one...after doing so it now loads as far as dcs terrain graphics unit 97 caucasus.ng5 Any clues? Obviously i've run DCS repair before posting as well! I've attached a log filedcs.log Edited July 18, 2020 by jasonbirder
Sn8ke Posted July 19, 2020 Posted July 19, 2020 I have had the same issue the last three open beta updates. Asus Prime Gaming Wifi7 // Intel 14900K @5.5GHz // 64Gb DDR5 6000MHz // 3090 RTX // 4TB Samsung NVME M.2
Flappie Posted July 19, 2020 Posted July 19, 2020 Hi jasonbirder, this is the last intelligible message that appears in your log file: 020-07-18 11:18:38.002 INFO EDCORE: 0.000 s landscape5::navGraph5File 2020-07-18 11:18:38.002 INFO EDTERRAINGRAPHICS41: ITerrainGraphicsImpl4::openTerrain() END 8.591309 s 2020-07-18 11:18:38.002 ERROR_ONCE DX11BACKEND: render target 'mainDepthBuffer_copy' not found 2020-07-18 11:18:38.002 ERROR_ONCE DX11BACKEND: render target 'DummyShadowMap' not found 2020-07-18 11:18:38.259 ERROR VFS: VFS_open_write: CreateFile(C:\Users\Jason\AppData\Local\Temp\DCS\temp.theatre): Access is denied. 2020-07-18 11:18:38.259 ALERT LUACOMMON: Error: GUI Error: [string "./MissionEditor/modules/me_mission.lua"]:3771: attempt to index local 'f' (a nil value) GUI debug.traceback: stack traceback: [C]: ? [string "./MissionEditor/modules/me_mission.lua"]:3771: in function 'addTheatreToZip' [...] After some research, I've found another case here. Please read this thread thoroughly and tell us if you can get rid of this issue. ---
ED Team BIGNEWY Posted July 20, 2020 ED Team Posted July 20, 2020 2020-07-18 11:18:38.259 ERROR VFS: VFS_open_write: CreateFile(C:\Users\Jason\AppData\Local\Temp\DCS\temp.theatre): Access is denied. 2020-07-18 11:18:38.259 ALERT LUACOMMON: Error: GUI Error: [string "./MissionEditor/modules/me_mission.lua"]:3771: attempt to index local 'f' (a nil value) GUI debug.traceback: stack traceback: [C]: ? [string "./MissionEditor/modules/me_mission.lua"]:3771: in function 'addTheatreToZip' [string "./MissionEditor/modules/me_mission.lua"]:3816: in function 'save' [string "./MissionEditor/modules/me_mission.lua"]:3734: in function <[string "./MissionEditor/modules/me_mission.lua"]:3717> (tail call): ? [string "./MissionEditor/modules/me_mission.lua"]:6808: in function 'play' [string "./MissionEditor/modules/me_quickstart.lua"]:271: in function 'func' [string "./Scripts/UI/ProgressBarDialog.lua"]:154: in function 'updater' [string "./Scripts/UpdateManager.lua"]:64: in function <[string "./Scripts/UpdateManager.lua"]:40> Your log shows an issue with your me_mission.lua have you any mods or made any edits to this file? Try my crash advice below it may help thanks 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, PIMAX Crystal
ThorBrasil Posted July 20, 2020 Posted July 20, 2020 I caught the same problem. |Motherboard|: Asus TUF Gaming X570-PLUS, |WaterCooler|: Corsair H115i Pro, |CPU|: AMD Ryzen 7 3800X, |RAM|: Corsair Vengeance LPX 32GB 3200MHz DDR4, |SSD|: Kingston A2000 500GB M.2 NVMe, |SSD|: Kingston 2.5´ 480GB UV400 SATA III, |SSHD|: Seagate Híbrido 2TB 7200RPM SATA III, |GPU|: MSI Gaming 980Ti, |Monitor|: LG UltraWide 34UM68, |Joystick 1|: Thrustmaster Hotas Warthog, |Joystick 2|: T.Flight Rudder Pedals, |Head Motion|: TrackIr 5.
Fox1981 Posted August 14, 2020 Posted August 14, 2020 Solution for NAS Hey Guys, I had the same problem. In my case the problem was caused by a setting in my NAS. I'm saving the folder "saved games" on a NAS drive. This NAS drive had a wrong setting in the filesystem option. After I changed the wrong setting, the game was able to create the files which were marked as an error in the log file. Maybe this can help you! :thumbup:
Recommended Posts