I really don;t know what to say about this bug. It came on me for the first time today. I played for an hour or more before i didnt do or change anything with my system. I chose the star map decided to play against empire, entered the map and this happened.
Game turned off, tried to restart it, to rejoin the game but it popped out again.
EDIT: the map we were playing was Pandora. The Lost expedition. And it was Commander type of game.
Happen to me a lot of time, Haven’t see a common factor, happen in the loading, in the first warping, or after 5min of game. Strange.
Just ignore it, click on cancel on the 5-7 pop-up and you’ll be able to play without any problem
Hi, it has happened twice and I can only assume it’s patch related as the game has been fine until today. I know it states it will send a report, but this is the bug forum for a beta game so, here you go!
Hi, it has happened twice and I can only assume it’s patch related as the game has been fine until today. I know it states it will send a report, but this is the bug forum for a beta game so, here you go!
Module: (game.exe folder location)
Source: CosmoSim\SpaceShipController.cpp(203)
Owner: Vandeer
Assertion: ‘direction.IsNumber()’
Cheers!
if you press cancel, you get another 6 or so pop-ups saying other sources, just keep pressing cancel and you can play on.
Star conflict froze when I tried to load into my first pve game since the patch.
Joined game pve game (blackwood shipyard), game loads correctly, countdown timer works fine. Go to spawn, game freezes. Alt-tabbing showed that there was a Star Conflict related pop-up window saying ‘assertion failed: direction.isnumber()’
I couldn’t hit ok to auto-send the report since Star Conflict’s black screen covered up the window every time I tried. Anyways, I closed the error window from taskbar, then a few more error windows, then Star Conflict dropped back to the log-in screen (as expected, I presume)
Got more error messages at beginning of a beacon hunt, sector conquest match. They occurred at the same time (right after spawn in), but there were more and the game didn’t crash to the log-in screen afterwards.
I was typing in the chat on the battle-prep/map/score/loading screen (whatever you want to call it) as the game was starting and it immediately crashed with this exact error.
When I logged back in the game asked if I wanted to rejoin the battle, tried twice, each time I got this error immediately after the load screen. I never tried clicking cancel in the “Assertion Failed” dialog box though.
Game is virtually unplayable after last patch. 9/10 times i launch i get some crap error code with no information on it except for steam users (0xC0000022) Error report does nothing. When in game 30% of the time it crashes with assertion failure, if it hasn’t ctashed already.