That’s true, but he would need to clone it if he was going to attach multiple copies of the model at once so I tossed it in there as “food for thought” in case later on he decides he needs multiple instances attached at the same time. If I recall correctly, jME’s asset instances are even smart about cloning themselves and don’t spuriously duplicate heavy data (like image data backing a texture).
1 Like
…by calling assetManager.loadModel()… which would clone it or load it as needed.
No need to manually clone it in this case because it makes code dependent on a potentially spurious optimization and opens it up to not cloning as efficiently as required (if the wrong options are passed).
1 Like
Good to know. I’m going to tuck that one away for future use. 
1 Like