Replies: 8 comments 6 replies
-
FYI (a very incomplete list of some users who may have opinions on this): @pushmatrix @mikkoh @mrdoob @donmccurdy @hybridherbst @lucadalli |
Beta Was this translation helpful? Give feedback.
-
I'll need to think about this in great detail. However:
I love an FOV of 30 degrees. The reduced perspective warp is way better for commerce applications.
This one is a bit hairy for us as we'd need to backfill and generate all preview images again but it might be worth it. 🤔 We need to experiment with this and just do some thinking around this. If we're thinking of a 2.0. One thing I'd like to propose is componentizing Model Viewer more. I think one of the best things about Model Viewer is how quickly you can get up and running and have a consistent API for users/developers to interact with models. Increased adoption for 3D. One of the downsides I see of Model Viewer is that there's less innovation in rendering technology. I'd love it if the webcomponent was separated from the renderer. I've done some prototyping around this where I had a webcomponent wrap and it acts as a translation layer between or a custom renderer. This might be a fine approach but not ideal. Also I'd like to add that having a consistent renderer across multiple channels is great. Like making sure 3d models are always rendered the same regardless of where you distribute content is really good. But I wonder if there should be some leeway here for increased innovation. Pinging |
Beta Was this translation helpful? Give feedback.
-
+1, I got tripped up on this option at one point. What would you think of changing the units of the renderer.toneMappingExposure = Math.pow(2, modelViewerExposure); |
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
-
Here are the proposed items sorted from my world view. Unaffected by - covered manually and varies by model Unaffected by - force to this already Unaffected by Didn't know it was there Don't care |
Beta Was this translation helpful? Give feedback.
-
I've been thinking about the 30 degree FOV as default. I still like this FOV better but I may not been clear above that we'd also need to regenerate all preview images for all of our merchant models |
Beta Was this translation helpful? Give feedback.
-
One thing that I'd love to see in 2.0 but not sure if you want to go that route: being able to attach custom GLTFLoader extensions more easily. Note that this wouldn't need to be "official" or "supported", just "possible" would be enough – e.g. one more symbol or so that allows doing more advanced things without having to recompile / rebuild model-viewer from scratch. |
Beta Was this translation helpful? Give feedback.
-
I had missed this one:
which unfortunately means that the behaviour of "click on image to get 3D model" now requires a programmer - not ideal... (noticed because it broke some of our "model galleries" and now custom code is required instead of just writing HTML). The only example for that is rolled into the "Customize loading experience with your own HTML" example, which adds additional complexity. A separate example for just "click on image to get 3D" would be great. |
Beta Was this translation helpful? Give feedback.
-
We're coming up on the 2-year mark since
<model-viewer>
1.0, having done 12 releases since then. We have been carefully following semantic versioning rules to avoid breaking changes for our diverse user base, but this has caused parts of our API to become less beginner-friendly as our newer best-practices have not become defaults. This makes it feel like the time has come to reset with a v2.0 release.To be clear, we still want to make updating to v2.0 easy for our users, so we're mostly looking to change features that are little-used or will improve the experience on most sites. We can't promise when v2.0 will ship, but hopefully sometime this summer. This thread is to gather feedback on our proposal; please help us make v2.0 our best release yet!
The following is a roughly-prioritized list of breaking changes we're considering. This list will be updated as the conversation progresses. Much of this is designed to reduce cruft in our code base to ensure we minimize bugs and keep code quality high. Please comment regarding any that you agree or disagree with and why. Suggestions of other changes that you would like to see are also welcome.
enable-pan
default, with default field-of-view narrowed to 30 degrees (12 degree default minimum). This gives the default framing a "longer lens" with reduced perspective warp.enable-pan
to true, replacing theenable-pan
attribute withdisable-pan
.bounds="tight"
.scene-graph-ready
event.progress-mask
; equivalent to setting its part todisplay: none;
. This will keep the poster from appearing lightened during loading.reveal
attribute. Use "manual" anddismissPoster()
instead to achieve this behavior.interaction-policy
attribute, allowing only the default "always-allow" behavior.interaction-prompt
attribute.interaction-prompt-style
attribute, allowing only the default "wiggle" behavior.--poster-color
, making the poster always have a transparent background.seamless-poster
attribute, making the behavior as though this option is always enabled. Note this in combination with the previous bullet means there is no longer a transition fade between poster and model, so seamless posters as generated bytoBlob({idealAspect: true})
or our editor are strongly recommended.touch-action
default frompan-y
tonone
.environment-image
toneutral
, renaming the current default aslegacy
.package.json
module
to point tolib
instead ofdist
. For JS users,main
will still point to our bundle indist
, but this change will send TS users to our lib so they can build and tree-shake it themselves, which is best practice. Also, our lib already contains all our*.d.ts
files.Image.setURI
method from our materials API. Use thecreateTexture
method instead.exportScene
options to match three.js r143. Specifically, removeembedImages
(always true now) andforcePowerOfTwoTextures
. AddforceIndices
.preload
event, as there is no longer any distinction from theload
event.ar-modes
default towebxr scene-viewer quick-look
.Beta Was this translation helpful? Give feedback.
All reactions