Purely cosmetic stuff should be safe, stuff that only adds things should be safer than stuff that changes existing things, but that's only usually true. (especially check ones that add events or change things regarding units, buildings, etc. Your best bet would be to check the bigger mods you have and see if any incompatibilities are listed or if people complain about crashes in the comments. If it's not the program will crash, but there'll be a message somewhere in the log that says WHERE in the code it crashed, and the developer can use that to find out what the problem is.īut if there's no information besides 'false' it doesn't tell an end-user anything at all.Ĭould be that the dump file the message mentions has more information but it's really hard to diagnose errors like this without access to the code. there's code that reads the size of a stack of units and then does an 'assert' that the stack size is more than 0.

It's a programming thing that developers (who have access to a program's source code) use to check certain assumptions. Issue is that 'assertion failed: false' doesn't mean anything and doesn't give any information. Purely cosmetic stuff should be safe, stuff that only adds things should be safer than stuff that changes existing things, but that's only usually true.It's happened to other people and yes, it's very likely a mod. kisak-valve added the Game compatibility - Unofficial label on May 2. I dont believe this is purely a nvidia issue (the game is rated playable on the store). Your best bet would be to check the bigger mods you have and see if any incompatibilities are listed or if people complain about crashes in the comments. A crash reporter opens and closes after a second or two.

It's happened to other people and yes, it's very likely a mod.

Age of wonders 3 assertion failed false