Home › Forums › Graphics / Blender › Verge3D for WordPress Texture Loading Issue
- This topic has 9 replies, 2 voices, and was last updated 23 hours, 8 minutes ago by 3up3down.
-
AuthorPosts
-
2025-01-02 at 1:51 pm #796273up3downCustomer
Hey Verge3D community,
I’m encountering a perplexing texture loading issue within the Verge3D WordPress plugin. I have a 3D glove model with customizable paisley patterns. The paisley textures are applied to separate planes that were created in Blender and exported to Verge3D.
The Problem:
While other textures in the scene load without any issues, the paisley textures are not displaying on the 3D model. I’ve confirmed that the paisley texture images exist in the same directory as the other working textures.
Troubleshooting Steps Taken:
Verified that the image paths in the Verge3D project and any related JavaScript code are correct.
Confirmed that the paisley texture file names match exactly (including extensions) with the names referenced in the code.
Ensured there are no hidden characters or encoding issues in the file names.
Cleared the browser cache to rule out caching issues.
Checked the browser console for any errors related to the paisley textures or Verge3D, but found none.
Used the Verge3D debugger to step through the puzzle logic and inspect variables, but couldn’t find any obvious issues.
Tested with a minimal Verge3D scene to isolate potential conflicts, but the problem persists.Verge3D for Blender – Version: 4.8.0
Blender version: 4.2.2I’m stumped as to why these specific textures aren’t loading within the WordPress plugin. Could there be a configuration issue or compatibility conflict I’m overlooking? Any insights or suggestions for further debugging would be greatly appreciated!
2025-01-02 at 1:53 pm #796283up3downCustomer**UPDATED**Link to page: https://3up3downsports.com/product/custom-your-glove/
2025-01-03 at 10:09 am #79639Alexander KovelenovStaff2025-01-03 at 6:36 pm #796493up3downCustomerThanks for your quick reply!
I did try your recommendations. Unfortunately, the issue remains.2025-01-04 at 7:54 am #796563up3downCustomerin checking the developer console, I am seeing the following error, which is odd I do not have this issue with the other options.
visual_logic.js:290 Uncaught TypeError: Cannot read properties of undefined (reading ‘thumb_leather1-color’)
at visual_logic.js:290:48
at wooProductAttribute (visual_logic.js:291:8)
at PL.init (visual_logic.js:2867:5)
at Palm Pull Through.js:53:20
at v3d.js:1:1416503I have confirmed the puzzle is properly setup.
2025-01-04 at 8:41 am #79658Alexander KovelenovStaff2025-01-06 at 4:48 am #796723up3downCustomerSorry for the delay. Please let me know if these screenshots help.
Attachments:
You must be logged in to view attached files.2025-01-06 at 7:07 am #796773up3downCustomerI am also noticing this error: V3D-AM-WARNING: No suitable manifest file found.
2025-01-09 at 6:02 am #79722Alexander KovelenovStaffI see no critical errors in the console you provided. I believe there is a logical issue in the puzzles scenario itself. There are some hints that might help in debugging it:
1. Use more print to console to find our the possible reason of this misbehavior.
2. Temporary disable blocks that are not relevant to this particular functionality. This will help you in narrowing it down.
2025-02-04 at 7:39 am #800683up3downCustomerThank you for your response. I did as you suggested, however, unfortunately I am still having problems. Attached are the error messages I am seeing in my chrome developer console. Based on these errors come on do you have any additional recommendations?
Your assistance is appreciated as I have been working on this for some time to troubleshoot.
Attachments:
You must be logged in to view attached files. -
AuthorPosts
- You must be logged in to reply to this topic.