Vertex Color isn't loading from WRL #15
Labels
No Label
bug
confirmed
duplicate
enhancement
help wanted
High
known issue
Low
Normal
not a task
question
task
v2.4
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: extensions/io_scene_x3d#15
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Thanks for maintaining this add-on as we use .wrl for color 3d printing. This extension was working before, but I think since the recent update the vertex color on imported wrls seems wrong and my files import all blue: vs the same file dropped into 3dviewer.net: . This has definitely worked in Blender with this plugin in 4.1 and up until recently in 4.2, so I'm wondering if a recent change broke things? I've attached a sample file. We have thousands of files like this and we were dependent on Blender and this plug-in in our workflows so would love a solution if possible.
Note - I manually installed the previous version of the plugin and everything works again, so there was definitely a breaking change in the most recent update.
Hi, thanks for reaching out. I will take a look at it after my vacation and hopefully find a solution to your issue. Will update this report accordingly.
In the meantime you can use the previous extension version, you can download it on the extension site under version history.
V2.3.3 should probably work fine: https://extensions.blender.org/add-ons/web3d-x3d-vrml2-format/versions/
Alright, it broke in
c86b76ee55
. Will work on a fix soon. Sorry for the inconvenience.Alright, should work now with the newest extension release
2.3.6
.Tbh i'm not too satisified with the fix performance wise, but currently can't think of any better solution in the moment which displays your file and the ones from
c86b76ee55
both correctly. Anyways should work nontheless.Please reach out again if anything else is broken or behaving differently than you would expect.