FLAMEGPU/FLAMEGPU2

Curve: Collision handling

Robadob opened this issue · 1 comments

Currently device side curve accesses only confirm that type size matches. This is clearly flawed (most types are 4-byte).

This same flaw is present in unregisterVariableByHash()

Temporary solution, also confirm the unmodulated hash matches. This will be a significant improvement, at the cost of an extra memory read. This is probably worth doing at the same time as #353, or atleast CURVEs component of that change.

The long term solutions to this may only be available via RTC, due to the pre-processing which can be performed.

Surprisingly never updated this to state we could perform it using type_decode if we provide a manually defined enum for every supported type.