Getting periodic halts to the game that I am able to skip or break. This is what is being shown in the log output.
[20:30:47.6678533][ 32684][ win32_stack_trace] StackWalker::OnSymInit : .;C:\Program Files\Epic Games\SinsII;C:\Program Files\Epic Games\SinsII;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols; , 530 , range [20:30:47.8099904][ 32684][ unit_move] ASSERT(_segments.empty_or_contains_only_locked_segment_now(_this_unit.get())) [20:30:48.8100460][ 32684][ app_output] WARNING: Timed out waiting for error_dialog_result (most likely due to deadlock between main_and_rendering_mutex OR tbb worker thread). ASSERT(_segments.empty_or_contains_only_locked_segment_now(_this_unit.get()))
[20:30:47.6678533][ 32684][ win32_stack_trace] StackWalker::OnSymInit : .;C:\Program Files\Epic Games\SinsII;C:\Program Files\Epic Games\SinsII;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols; , 530 , range
[20:30:47.8099904][ 32684][ unit_move] ASSERT(_segments.empty_or_contains_only_locked_segment_now(_this_unit.get()))
[20:30:48.8100460][ 32684][ app_output] WARNING: Timed out waiting for error_dialog_result (most likely due to deadlock between main_and_rendering_mutex OR tbb worker thread).
ASSERT(_segments.empty_or_contains_only_locked_segment_now(_this_unit.get()))
Hello! Is there any particular circumstance youve been seeing cause this? Next time if possible please hit break so the error reporter pops up and can be submitted as well
I will do that when it happens again, it doesn't seem to happen often but when it does it's in a random burst of a few of them. Also it seems to make the game freeze for a few seconds, looking at my system resources my GPU goes to 0% usage and the process goes to Not Responding and then it starts working again fine with great performance. I have tried doing a repair install, etc. CPU is an i9-14900KS and Corsair 48GB 7600MT/s memory.
I hit break this time
[19:08:19.3794026][ 18680][ gui_view] WARNING: command_data(render_prim2d_rect) capacity exceeded : 1000 [19:08:19.3813569][ 18680][ game_client_camera] WARNING: seconds_since_last_render_frame 1.5630001 > 1 [19:08:32.8013999][ 29852][ win32_stack_trace] StackWalker::OnSymInit : .;C:\Program Files\Epic Games\SinsII;C:\Program Files\Epic Games\SinsII;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols; , 530 , range [19:08:32.9448562][ 29852][ unit_move] ASSERT(_segments.empty_or_contains_only_locked_segment_now(_this_unit.get())) [19:08:33.9450718][ 29852][ app_output] WARNING: Timed out waiting for error_dialog_result (most likely due to deadlock between main_and_rendering_mutex OR tbb worker thread). ASSERT(_segments.empty_or_contains_only_locked_segment_now(_this_unit.get()))
[19:08:19.3794026][ 18680][ gui_view] WARNING: command_data(render_prim2d_rect) capacity exceeded : 1000
[19:08:19.3813569][ 18680][ game_client_camera] WARNING: seconds_since_last_render_frame 1.5630001 > 1
[19:08:32.8013999][ 29852][ win32_stack_trace] StackWalker::OnSymInit : .;C:\Program Files\Epic Games\SinsII;C:\Program Files\Epic Games\SinsII;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols; , 530 , range
[19:08:32.9448562][ 29852][ unit_move] ASSERT(_segments.empty_or_contains_only_locked_segment_now(_this_unit.get()))
[19:08:33.9450718][ 29852][ app_output] WARNING: Timed out waiting for error_dialog_result (most likely due to deadlock between main_and_rendering_mutex OR tbb worker thread).
I get this error too. It happens in late game when there is a lot of things gong on, seeing its on a large map with 9 other ai's. Its happened at many different times and actions at that point. You can ignore it and continue to play but some odd things occur, like the resetting advent points into its psy abilities. Its never happened till this last big patch.
Yes, same. I can continue playing but I do see some strange behavior with things resetting. I've seen it on TEC Enclave vs TEC Primacy only so not related to just Advent I assume.
I have been playing on the early access build and I don't get that bug on several start to finish match's. But the surrender crash is still 100% present.
Were you getting the error on the current non-beta release?
EDIT: Disregard, I didn't realize you were a prior responder.
its all good. I am just glad that it seems to not be happening anymore at least for me and it stays that way. That update sure has changed some things lol. Impossible AI can't get a titan out at the 55 min mark like it always use to.
Have you tried the early access to the update yet? Just wondering if it went away for you or not in that case.
There are many great features available to you once you register, including:
Sign in or Create Account
