Stephen Green
04-29-04, 02:49 PM
I can't see an official wishlist anywhere, maybe there should be a sticky thread?
Anyway here goes...
I understand that ZB is platform agnostic, and it would be problematic to support features on some apps and not others but...
Anyone who is working on games material is likely to be using multiple maps, however Obj (at least the Max exporter) does not support this, an object with multiple material IDs gets changed to an ID of 1, which means that you would need to break the object into separate chunks per material.
It would be nice if ZB could handle multiple maps per single object.
Secondly, although ZB uses groups for some managment of visible polys, again it would be useful to support named selection sets on a face level from the originating app. Max has this, and I imagine most other apps would as well. This would make managing areas a lot more intuitive if you are using existing names.
Thirdly, more support for overlapping/flipped UVs - AUVs and GUVs are great for film, but bad for Game models.
Overall, I think an alternative to OBJ, with relevant import/export for host apps that supports more data would help, I know it's a lot of extra work but it does seem an area which could be improved IMHO.
Cheers
Anyway here goes...
I understand that ZB is platform agnostic, and it would be problematic to support features on some apps and not others but...
Anyone who is working on games material is likely to be using multiple maps, however Obj (at least the Max exporter) does not support this, an object with multiple material IDs gets changed to an ID of 1, which means that you would need to break the object into separate chunks per material.
It would be nice if ZB could handle multiple maps per single object.
Secondly, although ZB uses groups for some managment of visible polys, again it would be useful to support named selection sets on a face level from the originating app. Max has this, and I imagine most other apps would as well. This would make managing areas a lot more intuitive if you are using existing names.
Thirdly, more support for overlapping/flipped UVs - AUVs and GUVs are great for film, but bad for Game models.
Overall, I think an alternative to OBJ, with relevant import/export for host apps that supports more data would help, I know it's a lot of extra work but it does seem an area which could be improved IMHO.
Cheers