Skip to content
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

Editor always reports Missing UV1 on RenderComponents #478

Closed
eproasim opened this issue Jul 29, 2021 · 6 comments
Closed

Editor always reports Missing UV1 on RenderComponents #478

eproasim opened this issue Jul 29, 2021 · 6 comments
Assignees
Labels
area: asset import bug Something isn't working

Comments

@eproasim
Copy link

It is known that the editor is currently unable to unwrap UV1 for GLB models; however, even if an uploaded model has a UV1 channel, the editor will always report that it is missing when slecting a RenderComponent to be lightmapped. ModelComponents do not exhibit this behavior. When launching the scene, the RenderComponent will not respond to lightmapped lights, while the ModelComponents will.

Provide as much information as possible. Include (where applicable):

  • URL to a simple, reproducible test case that illustrates the problem clearly:

https://playcanvas.com/editor/scene/1202294

Steps to Reproduce

  1. Open Project
  2. Verify that lightmapping is enabled on RenderComponent, ModelComponent, and Lights (While separate files, imported FBX are identical)
  3. Launch Project
@willeastcott
Copy link
Contributor

Assigned this to you for now @mvaligursky - I know @slimbuck has some involvement in UV1 generation though so feel free to reassign as appropriate. 😄

@eproasim
Copy link
Author

eproasim commented Aug 9, 2021

Quick update. The editor still reports the UV1 is missing and sizes the lightmap at 1x1, but if you multiply the RenderComponents lightmap size by 5,000,000, it will force the map to be 1024x1024 to match the ModelComponent and light the models accordingly.

Not sure what to make of this behavior.

@mvaligursky
Copy link

The issue is on the Editor side - it shows the missign uv1 error even though the mesh contains the uv1. If the mesh contains uv1 this warning can be ignored, as all still works.

The scaling is engine issue that I will have fixed: playcanvas/engine#3528

@mvaligursky
Copy link

related PR for reporting missing UV1 which does not seem to work well (monorepo/pull/391)
@slimbuck

@yaustar
Copy link
Collaborator

yaustar commented Feb 8, 2022

I will settle for rewording the warning to 'may be missing'

@yaustar
Copy link
Collaborator

yaustar commented Mar 2, 2022

released in 1.21.29

@yaustar yaustar closed this as completed Mar 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: asset import bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants