While making mods for Crashday you may encounter a lot of different crashes and bugs. Problem is, the error messages were meant for developers so they don’t usually give enough info about how you would fix the given bug. But usually it is possible to pinpoint the problematic file and fix the error. For this purpose here is the list of well-known errors and their possible causes.
If you found any error which is not on that list, please report it to the modding channel in Crashday Discord.
Assertion failed
Generally these errors appear when the game got a value it did not expect to. If the game expects a mass as integer on line 3 in some file but finds a great meme
this error will appear. Even then, we still can differ between different assertion fails.
IsValueSetInString
Exact message:
1 | Assertion failed! |
Problematic file: .tun files
.
Possible causes:
- Wrongly specified amount of tuning items at the top.
- Line 3 should be empty.
size<BM_BYTESPERBLOCK
Exact message:
1 | Assertion failed! |
Problematic file: unknown
Possible causes:
- This error appears when the game tries to load a file bigger than it can handle. Usually none of the text files should exceed this limit so the most possible reason is too big .p3d file.
- If it’s a .p3d model chances are you have to many polygons. Reduce to 58k.
wheelwidth > 0
Exact message:
1 | Assertion failed! |
Problematic file: .p3d model of the wheel
Possible causes:
- No “main” mesh found in the model.
mass > 0
Exact message:
1 | Assertion failed! |
Problematic file: unknown
Possible causes:
- Faulty mesh?
- Some dynamic or a car has a zero mass.
you’re assuming errors make sense
that’s a rookie mistake
@Mica
Others
invalid NumPlate-value
Exact message:
1 | The car file contains an invalid NumPlate-value! |
Problematic file: carinfo.cca
. In the error message file =
parameter should show what car caused the crash.
Possible causes:
- You defined a non existent license plate e.g.
narow
(one r is missing). - The engine expected another value at this line position. This probably means you missed some value, added one extra. Possibly incorrect number of damage textures is present.
Expected physics section but found
Exact message:
1 | Expected physics section but found |
Problematic file: carinfo.cca
. In the error message file =
parameter should show what car caused the crash.
Possible causes:
- Number of gear rations is not equal to the amount of gears actually present in the config file (should be number of gears + 1 for rear).
- The engine expected another value at this line position. This probably means you missed some value, added one extra.
Unsupported type for shop article!
Exact message:
1 | Unsupported type for shop article! |
Problematic file: shop.lst
.
Possible causes:
- Part group specified incorrectly. Check .cdo file definition for possible variants.
- The engine expected another value at this line position. This probably means you missed some value or added one extra.
Error: texture couldn’t be found!
Exact message:
1 | Error: texture could't be found! |
Problematic file: missing texture
, carinfo.cca
.
Possible causes:
- The game looks for the texture which is actually missing. Possibly wrong path or name is used somewhere.
- One mesh is listed twice in
carinfo.cca
mesh list.
Could not allocate Index Slot!
Exact message:
1 | Could not allocate Index Slot! |
Problematic file: .cat
Possible causes:
- You forgot a tile name or did not specify the position with auto positioning turned off. Visit file definitions for .cat files for reference.
- Possibly other unknown causes.