Corrupt Files, same map second time

[Aimee]

This is the second time i try to join a game and i get kicked out due to corrupt files. This has happend twice now on the same map, previous time was 3-4 weeks ago so not a new bug.
The only way to get back in, is by verifying the game files on steam and then start the game back up. Meaning i have to completely skip the current match.

Screenshot of the error code;
https://steamcommunity.com/sharedfiles/filedetails/?id=3387467895

[Aimee]

It was a 3mb file(s) that had to be redownloaded that got corrupted. In case this helps narrow it down.

Now i got a game warning.
https://steamcommunity.com/sharedfiles/filedetails/?id=3387558715
Im not sure if it was from the game crashing, that i was gone for a bit. Or if its the ''smurfing'' part. If its the later, then the detection for smurfing needs some work.

[Fulcrum.Armulus]

Wait is this problem still ongoing?

[Aimee]

Originally posted by Fulcrum.Armulus:

Wait is this problem still ongoing?

It appears so, exactly the same as last time. So it might be map related.
The warning did not get me banned luckly, but i hope it does not cause any issues in the future.

[Bakaczor]

Just started a game and same problem. Needed to repair the game, but half of the match was gone...

[Bakaczor]

Originally posted by Bakaczor:

Just started a game and same problem. Needed to repair the game, but half of the match was gone... Different map though.

Different map though, so it is not map related. My file had ~600MB.

[Bakaczor]

Originally posted by Aimee:

It was a 3mb file(s) that had to be redownloaded that got corrupted. In case this helps narrow it down.

Now i got a game warning.
https://steamcommunity.com/sharedfiles/filedetails/?id=3387558715
Im not sure if it was from the game crashing, that i was gone for a bit. Or if its the ''smurfing'' part. If its the later, then the detection for smurfing needs some work.

Also got the same notice after the match ended.

[Fulcrum.Armulus]

Ok, here's a more updated version of this issue.

If you use the official website: within the starting page of the launcher, in the right hand lower corner, you will find three dashes, click→Repair→Confirm, and the game will sort this out itself.

If you use steam: Within you Steam page, find Strinova, enter and right click →Properties→Installed Files→Verify integrity of game files, and steam will sort this out then enter the game.

Screenshots on how this works will be uploaded on the faq of the game in the next couple days.

If this doesn't work, I will need your uid.

[Yme]

Originally posted by Fulcrum.Armulus:

Ok, here's a more updated version of this issue.

If you use the official website: within the starting page of the launcher, in the right hand lower corner, you will find three dashes, click→Repair→Confirm, and the game will sort this out itself.

If you use steam: Within you Steam page, find Strinova, enter and right click →Properties→Installed Files→Verify integrity of game files, and steam will sort this out then enter the game.

Screenshots on how this works will be uploaded on the faq of the game in the next couple days.

If this doesn't work, I will need your uid.

I have this issue too but on the Base 404 map. i've tried verifying the game files multiple times but it still gives me the exact same issue, anything else i can do?

[Akane]

Originally posted by Fulcrum.Armulus:

Ok, here's a more updated version of this issue.

If you use the official website: within the starting page of the launcher, in the right hand lower corner, you will find three dashes, click→Repair→Confirm, and the game will sort this out itself.

If you use steam: Within you Steam page, find Strinova, enter and right click →Properties→Installed Files→Verify integrity of game files, and steam will sort this out then enter the game.

Screenshots on how this works will be uploaded on the faq of the game in the next couple days.

If this doesn't work, I will need your uid.

The problem is solved by checking files only for one game session, the next time you log in, it's the same. Deleting a certain file that causes this error and restoring it manually gave the result for a slightly longer period of time.