Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags
(1 edit)

Maybe that would work indeed for the example shown on Stack overflow, for any objects that are symmetrically the same on both sides it could work but for example a block of 2x1 where the left side looks different than the right side this may cause problems - also it still would be mirrored, if we're building in Asset Forge keeping in mind that the direction of the arrow is North - and built to the East, it's weird that it renders in my game as West.

I can post more complex / in depth examples tomorrow if you're interested in seeing the problems occuring with different kind of models.

Well I'm not sure if this is within the scope of the program and I'm not sure if I can help you. I don't have any knowledge on Three.JS and the .model files are normally used for just saving and loading Asset Forge models. They aren't meant to be an output type, however if you can make it work I'm all for it.

Do keep in mind that the .model file format might change in a future version of Asset Forge, so not sure if it's the best to work with that.

(2 edits)

Will possible future .model files still be text formatted or encrypted somehow? We could make converters for different versions that's no problem.

I understand, as mentioned in my post i was not sure if this was related enough to Asset Forge / in the interest of the community. I will try figure it out myself somehow, i have just donated to you keep up the good work!

Thanks for the donation, much appreciated :) I have thought of compressing the .model files earlier but felt like that would be unnecessary if the data was a couple (hundred) lines, so I kept them readable.