Search the Community

This is an issue with DirectX12 and Vulkan only, presumably due to their multi-threaded rendering implementation. With the following code within the main function, the engine properly resets with DirectX11, but crashes for both DirectX12 and Vulkan, but with different crash errors as can be seen after the main code in this post. As hinted at, these kinds of crashes or freezes do not occur with DirectX11, which restarts as it should. // const Engine::InitParameters init_parameters; // UnigineLogic AppSystemLogic system_logic; AppWorldLogic world_logic; AppEditorLogic editor_logic; // init engine Unigine::EnginePtr engine(init_parameters, argc, argv); // RestartEngine: // enter main loop engine->main(&system_logic, &world_logic, &editor_logic); // if (IsResetting) { IsResetting = false; engine.shutdown(); engine.init(init_parameters, argc, argv); goto RestartEngine; } // return 0; Vulkan: Assertion failed: index < size_t(length) && "Vector::operator[]: bad index", file D:\BA\work\fb3821776bc41fe5\include\UnigineVector.h, line 1085 DirectX12: Usually freezes, but occasionly crashes with the following error instead: Unhandled exception (Access Violation Executing Location 0x00000245C7A42840) thrown in RenderShadows::CPUShaderRenderShadowsAsync::process(int thred_num, int threds_count) Line 2271

with unigine 2.7.1 qt frame after set the D3d11AppQt as sub widget of other widget (the crash bug will not occure in center widget),and start the engine , unigine will get crash over here. after debuging ,find that there was called QApplication::processevent when in setVideoMode function in AppQt when an engine object initialization, the processevent will call the timerEvent. however ,in that time, engine object just do not finish it's initialization, then do the update will cause crash. below is my resolution to fix that.