Closed LethalDumpster closed 2 years ago
By far the most time is spent importing prop models. Performance optimizations for the model importer would need to be either done in Blender Source Tools or I would need to create a new model importer for the addon. This is definitely not a priority at the moment, but I might consider it in the future.
I see. Would there atleast be a way to cache and skip already ported models(as fbx) within a directory? I understand that may sound odd, but while testing same or even multiple maps, I think it was obviously getting redundant. FBX should import to blender faster anyway, sooo bonus if not first time porting something? -Applies primarily to props ofcourse
It could be possible to use library .blend files to cache the imported data. The native blend format would probably work better than fbx or other alternatives. With 49e970b947774ee4afc2cdbcca8b1ea457ecc54f and f0df6d04cb6f20fb8743d5d619aee3a7da4eccc2, all the required information to recreate previously imported data is now saved to the .blend file, so adding an external cache should be feasible.
Dont mind me, just putting this up so I can ask about some possibilities, im loving this addon! Would it be possible within the near future to split the workload between threads? Or doing dirty, and just having multiple instances of the software work on different chunks of a .vmf at a time?