Home › Forums › Graphics / Blender › OSL issue
- This topic has 8 replies, 4 voices, and was last updated 3 months, 3 weeks ago by kdv.
-
AuthorPosts
-
2024-07-30 at 9:33 pm #76293Ignacio DíazCustomer
Hello there,
I’m having trouble getting the new version of my OSL shader to work. I followed the same procedure to create a new script node, but it didn’t work as expected this time either. Any suggestions on what might be going wrong?
Thanks in advance!
PS: Is it possible to use GLSL scripts with Verge3D? Because there aren’t many learning resources available for OSL.
Attachments:
You must be logged in to view attached files.2024-07-30 at 9:45 pm #76297xeonCustomerI dont have an answer for you but more of a question.
I originally planned on using OSL or GLSL for creating shaders as it was the most efficient for memory and performance. BUT as you mentioned online resources are very limited and really non existent for how to use them in Verge3D but you can implement them the same way you do in ThreeJS. However, why? I found that once I go down the road of creating a decent shader I have done more work that it would have taken me to create an entire project in Verge3D using standard textures and it becomes a cost benefit analysis after that. In the end I always end up on the side of not doing OSL / GLSL shaders due to the time it takes to create them. So I am curious if this is due to a memory related issue, a personal desire, client requirement?Xeon
Route 66 Digital
Interactive Solutions - https://www.r66d.com
Tutorials - https://www.xeons3dlab.com2024-07-31 at 12:55 am #76299Ignacio DíazCustomerMy decision to use OSL or GLSL for creating shaders is driven by a personal desire for greater control in creating procedural texture patterns with Verge3D for custom products. While image textures in Verge3D might be more time-efficient, the flexibility and precision of custom textures are essential for achieving the level of detail and uniqueness I aim for.
2024-07-31 at 2:56 am #76300kdvParticipantwhat might be going wrong?
operations with mismatching types like “highp int + const float” or “highp int * highp float”. it’s not allowed in GLSL.
Puzzles and JS coding. Fast and expensive.
If you don’t see the meaning in something it primarily means that you just don’t see it but not the absence of the meaning at all.
2024-07-31 at 2:57 am #76301xeonCustomerVery cool. Thank you for the insight. If you find a workflow please share your process. Good luck with your endeavor.
Xeon
Route 66 Digital
Interactive Solutions - https://www.r66d.com
Tutorials - https://www.xeons3dlab.com2024-07-31 at 8:26 am #76324Alexander KovelenovStaffHi,
OSL is a really important feature since this is the only way to make custom shaders in all 3 modelling suites we support: Blender, 3ds Max, Maya. Unfortunately, since OSL is converted to GLSL internally, some shaders might not work. I’ve linked your scene into our TODO list for further investigation.2024-07-31 at 1:43 pm #76327Alexander KovelenovStaff2024-07-31 at 6:24 pm #76334Ignacio DíazCustomerMarvellous, I’ll be looking forward to the update. Thanks for the help.
2024-08-06 at 1:34 am #76410kdvParticipantdeleted
Puzzles and JS coding. Fast and expensive.
If you don’t see the meaning in something it primarily means that you just don’t see it but not the absence of the meaning at all.
-
AuthorPosts
- You must be logged in to reply to this topic.