WebGL Model Viewer Issues

[Orion Pobursky]

This is a master thread for problems with the WebGL based model viewer used by both the PT and the model viewer on the main site.

[Orion Pobursky]

This is a master thread for problems with the WebGL based model viewer used by both the PT and the model viewer on the main site.

I've noticed that there are a handful of parts on the PT that are refusing to load:
https://www.ldraw.org/cgi-bin/ptdetail.c...s/2655.dat

Not sure if this extends to the Model Viewer. Further troubleshooting is required. If you find any others that don't load, please post them as a reply to this post.

[Orion Pobursky]

I've noticed that there are a handful of parts on the PT that are refusing to load:
https://www.ldraw.org/cgi-bin/ptdetail.c...s/2655.dat

Not sure if this extends to the Model Viewer. Further troubleshooting is required. If you find any others that don't load, please post them as a reply to this post.

I've fixed the issue with the above part. This has to do with the way studs are loaded in buildinginstructions.js. There may be other files with similar issues. Please report hem here if you encounter them.

[Lasse Deleuran]

I've fixed the issue with the above part. This has to do with the way studs are loaded in buildinginstructions.js. There may be other files with similar issues. Please report hem here if you encounter them.

I went back to the documentation for this in the sample files, and found:

Code:

    <!-- buildinginstructions.js optional libraries: Generator.js for quick creation of some primitives. Required for studs.js which can create customized studs. StudioTexmap.js allows for Studio 2.0-created files -->   
    <script src="js/LDRGenerator.js"></script>
    <script src="js/LDRStuds.js"></script>
    <script src="js/StudioTexmap.js"></script>

Are you also using LDRGenerator.js? If so, then they should have worked without the fix. And in that case, there is a bug which has to be remedied.


I am currently looking into the bootstrapping of ldconfig.ldr (rather than colors.js), so I am currently working in this part of the code base.

[Orion Pobursky]

Are you also using LDRGenerator.js? If so, then they should have worked without the fix. And in that case, there is a bug which has to be remedied.

It's being included. Then I call:

Code:

LDR.Studs.makeGenerators('', LDR.Options.studHighContrast, LDR.Options.studLogo);

This lines up with the example code on GitHub. Is there something else that need to be called?

[Lasse Deleuran]

No, that should do the trick.

My plan is to rewamp the part generation components, so that they can be more reliable and allow easier on-demand loading while using the library. That should fix this kind of issue reported here.

Right now part files from Generators and Studs are generated even though they might not be needed. I want to lazy-load all of these to improve performance. However. This requires that all generated parts correspond to the official ones, so that using the library doesn't result in inconsistencies.

[Magnus Forsberg]

Here is another one that doesn't load
https://www.ldraw.org/cgi-bin/ptdetail.c...709p0h.dat

[Orion Pobursky]

Here is another one that doesn't load
https://www.ldraw.org/cgi-bin/ptdetail.c...709p0h.dat

That one loads for me. Trying hard refreshing to flush the cached Javascript.

[Magnus Forsberg]

Yes, sorry.
The webGL loads, but there is no preview image in the corner and no dependencies on the part page.

[Orion Pobursky]

Yes, sorry.
The webGL loads, but there is no preview image in the corner and no dependencies on the part page.

Fixed