bitplane wrote:Re-joining this party late, haven't had as much time as I would have liked so can't really contribute to this at the moment.
However, I was browsing this thread and would just like to pipe up and say that if a future binary mesh format is going to include other files like textures and shaders, I think it would make much more sense to use some already existing archive format with the mesh data as a separate entity inside. Compression-less ZIP files or TAR archives wouldn't add much overhead, but would mean that the package could be edited with standard tools, reading it could be done using existing code. At first glance this may not seem like a huge advantage, but when you want to touch up that texture or make a one line change to that shader, you'll be glad you can just open it up and do so without messing around with whatever specific content creation pipeline tool becomes the standard.
Users browsing this forum: No registered users and 0 guests