Highwayman-Ed Posted April 30, 2020 Posted April 30, 2020 I ran into an issue with a mission that has a delayed start for the player when using VAICOM, which only occurs in the current Open Beta (2.5.6.47404). I appreciate that this will likely be pushed across to VAICOM to resolve, but I'm raising the ticket here as the issue is not present in the DCS Stable branch and the mission featuring the delayed start for the player works fine there. The mission itself loads perfectly, and the player sees the F10 map whilst the mission assets are loaded for the first couple of seconds, but when control is transferred to the player, DCS crashes to Desktop. DCS Log excerpt: 2020-04-29 11:11:30.017 INFO Dispatcher: loadMission Done: Сontrol passed to the player 2020-04-29 11:11:31.587 INFO DCS: dbox not found , skip 2020-04-29 11:11:31.587 DEBUG LuaGUI: ----onSimulationResume--- 2020-04-29 11:11:31.684 INFO EDCORE: (wcTanker)enterToState_:0 2020-04-29 11:11:31.684 INFO DCS: wcTanker::onEvent:4 2020-04-29 11:11:31.684 INFO EDCORE: (wcTanker)enterToState_:1 2020-04-29 11:11:31.684 INFO EDCORE: (wcTanker::Channel)enterToState_:0 2020-04-29 11:11:31.684 INFO EDCORE: (wcTanker::Channel)enterToState_:1 2020-04-29 11:11:33.774 ERROR wInfo: can't open Objects[Oil rig] table 2020-04-29 11:11:33.774 ERROR GRAPHICSVISTA: Can't open model Oil rig. 2020-04-29 11:11:33.797 INFO EDCORE: try to write dump information VAICOM output: 11:11:30.918 Nearest ATC: CVN-74 John C. Stennis. 11:11:30.918 Player New callsign entered module FA-18C Hornet, unit callsign 211 11:11:30.917 DCS mission | R1 M04 0.6.0 I've attached the crash dump to this post for review. dcs.log-20200429-111134.zip No mods, cleaned and repaired version of DCS Open Beta 2.5.6.47404 Intel i9-9900KF @5.2GHz MSI Z390 Gaming Pro Carbon 32GB G.Skill Trident Z DDR3200 RAM MSI RTX 2080 Ti Gaming X Trio 40" Panasonic TH-40DX600U @ 4K Pimax Vision 8K Plus / Oculus Rift CV1 / HTC Vive Gametrix JetSeat with SimShaker Windows 10 64 Bit Home Edition [sIGPIC][/sIGPIC]
Recommended Posts