Generally there are lots of places where we prevent the user from doing bad things.
A quite wished for feature here is the ConcurrentModificationException for the SceneGraph: A simple if !Thread.currentThread().getName().equals("jMe3-MainThread") before every SceneGraph Modification would help debugging those issues much much better, but would slow everything down.
This could be an assertion. As could be checking for non-uniform scale on non-root-nodes etc pp.
Note: The above shouldn't be implemented as is, because with proper locking accessing from another state is okay, as can this issue be caused by other things as well (forgetting to call the right updated methods on a custom viewport). Also I think a custom engine build with diagnostic logging on everything in the Spatial class with stacktraces might help more in that case.
Still there are quite a few things where assertions could happen over a NullPointerException or others.
Generally there are lots of places where we prevent the user from doing bad things.
A quite wished for feature here is the ConcurrentModificationException for the SceneGraph: A simple
if !Thread.currentThread().getName().equals("jMe3-MainThread")before every SceneGraph Modification would help debugging those issues much much better, but would slow everything down. This could be an assertion. As could be checking for non-uniform scale on non-root-nodes etc pp.Note: The above shouldn't be implemented as is, because with proper locking accessing from another state is okay, as can this issue be caused by other things as well (forgetting to call the right updated methods on a custom viewport). Also I think a custom engine build with diagnostic logging on everything in the Spatial class with stacktraces might help more in that case.
Still there are quite a few things where assertions could happen over a NullPointerException or others.