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

BUG: Property rendering can't load the models #83

Open
BrandVV opened this issue Jan 3, 2024 · 4 comments
Open

BUG: Property rendering can't load the models #83

BrandVV opened this issue Jan 3, 2024 · 4 comments

Comments

@BrandVV
Copy link

BrandVV commented Jan 3, 2024

When I try to view a propertie over the NexusDashboard, it will show me the Content under: Property Content with the correct items.
As soon as I try to render a singe item or view the XML of the model I will get a 500 error from Nginx, and when I try to render the full propertie, I will just get the green sqare empty.

The Console of the Dashbaord throws this error: [ERROR] Exception on /properties/get_model/70368744177671/mtl/2 [GET] -> FileNotFoundError: [Errno 2] No such file or directory: 'app/cache/BrickModels/mesh\\ftcommunityitems\\rew_modularcastlealtcolor_gate.lod2.mtl'

When I check, all of the folders under app/cache do contain what they should, but the BrickModels folder is empty.

I do not know how to sole this unfortunately, and would appreciate every help.

@aronwk-aaron
Copy link
Member

It has to do with file path mismatching. DLU server had the same and it was solved recently. I just need to implement the same logic

Mainly affects some FT (free trial) release models and ninjago release models

@BrandVV
Copy link
Author

BrandVV commented Jan 3, 2024

Okay, thank you very much for your fast answer.
I really appreciate it.

@aronwk-aaron aronwk-aaron changed the title Property rendering can't load the models BUG: Property rendering can't load the models Jan 5, 2024
@aronwk-aaron
Copy link
Member

closing as a environmental issue

@aronwk-aaron
Copy link
Member

actually, I do need to fix this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants