-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
should glTF specify unit property ? #23
Comments
probably not, but converter needs to. converter parameter: unit size in meter |
Sounds good to me. |
@RemiArnaud does unit size in meters need to be a dae2json option? It is already part of COLLADA with the |
the converter needs to know what unit to convert to, so yes, it is a the application need to deal with whatever it gets if it does not have |
There are only two choices: put a units metadata field in the format, or mandate glTF units (presumably at meters). I'm ok with either, but I have a pretty strong preference for doing it the COLLADA way. That way artists and programmers can work in whatever they feel comfortable with and the engines/readers don't really care. They just have to convert from the specified units to their native runtime units. This doesn't seem to be broken in COLLADA, why fix it? |
I have been thinking about this one for quite some time. I say - let's use 1 meter as the glTF unit. We already say we are Y_UP, so it is aligned previous decisions. Surely make it simple to mash-up models from various part of the web - exact same coordinate system. I have reviewed a bunch of use cases in my head, so ready for arguments now :-) |
Any updates here? I thought I originally included the |
Any update? |
I am fine with meters too... |
Adding converter label since this will require converter support. |
@fabrobinet any update on converter progress for this. There is some interest. |
@pjcozzi what exactly needs to be done ? dev-4 is fully packed and I could use some help on this one :) |
This would just rescale positions so that the units are meters if the input COLLADA units are not meters. |
I'm all for meters with the conversion @pjcozzi mentions. I've spent way too much time maintaining converters where units can change per file, and trying to work out what was intended when files with different units reference each other. Knowing that 1 == 1 no matter what sounds like heaven. |
ok with me, we'll have to be careful of animations and make sure their translations are rescaled too... |
I'm ok with this - as long as we understand that it puts all the onus on Tony On Mon, Jan 20, 2014 at 8:14 PM, Fabrice Robinet
Tony Parisi tparisi@gmail.com Read my book! WebGL, Up and Running |
Indeed, that's always the choice we make. More work on the converter, less work to import models for viewers&engines... |
All sounds good. Good point about the animations. |
+1 -- Remi On Tue, Jan 21, 2014 at 9:41 AM, Patrick Cozzi notifications@github.comwrote:
|
Hey, any update on this? |
Keeping for spec |
@tparisi for the draft 1.0 spec, add:
|
…e-metadata Restore EXT_feature_metadata alongside EXT_mesh_features
No description provided.
The text was updated successfully, but these errors were encountered: