Hello there, !

As I'm working to improve the import system within SceneForge, I had a quick question that I'd love your thoughts on as a user of the app!

Unlike many other 3D engines, when you import a file (model or material) into SceneForge, it simply stores a reference to where that file is on your hard drive.

This is similar to Adobe Premiere, for example, where if the file is moved or deleted, the app won't be able to load the data into your project.

But, as I'm working on improving the import system, I was thinking of switching to the other method of importing: Copying Files.

This would mean that, similar to Unity or Unreal, SceneForge would instead make a copy of the desired file within your project folder. This means that after it's imported, you can freely delete, change, or move the source file, and your project won't be affected.

The drawback of this is that it creates new files on every import, increasing the size of the project folder and taking up more hard drive space. That being said, it would make all project folders fully portable, allowing you to easily upload, share, and transfer them anywhere you want.

I would love your thoughts on this!

Do you think a file-copying-based system is better than the current path-based system?

Thanks for reading!

• Judah Mantell, Founder @ SceneForge.app