Problem
FBX import fails when Custom Property have enum with out of range selection. For example enum with list of 3 text values, and value number 5 being selected will prevent import.
Solution
Give textual warning in console instead of assert failure. Do not import Custom Properties with incorrect values.
Alternative solution
Import Custom Property with empty value.
Why?
Most of time problematic Custom Properties are irrelevant to user and it would be preferrable to be able to import FBX despite incorrect custom property selection.
Example File:
File is result of 3dsMax 2016 file being exported with 3dsMax 2020.