You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This enhancement would make it easier for people to use pre-made 3D models within their p5.js projects. It would broaden the creative possibilities for artists and designers by enabling more detailed and textured 3D models within p5.js projects.
Most appropriate sub-area of p5.js?
Accessibility
Color
Core/Environment/Rendering
Data
DOM
Events
Image
IO
Math
Typography
Utilities
WebGL
Build process
Unit testing
Internationalization
Friendly errors
Other (specify if possible)
Feature enhancement details
Since version 1.9.2, p5.js supports .mtl files, but only for vertex colors (see processing/p5.js#6710).
This request aims to extend that support to include textures loaded by an .mtl file. Implementing this feature would involve creating a new data structure capable of handling both 3D models and their associated textures, potentially multiple per model.
Just came across this issue, and it's great that the .obj and .mtl files functionality is expanded.
Let me know if I can help in any way. Reference: #6710
Increasing access
This enhancement would make it easier for people to use pre-made 3D models within their p5.js projects. It would broaden the creative possibilities for artists and designers by enabling more detailed and textured 3D models within p5.js projects.
Most appropriate sub-area of p5.js?
Feature enhancement details
Since version 1.9.2, p5.js supports
.mtl
files, but only for vertex colors (see processing/p5.js#6710).This request aims to extend that support to include textures loaded by an
.mtl
file. Implementing this feature would involve creating a new data structure capable of handling both 3D models and their associated textures, potentially multiple per model.Example sketch with a single texture: https://aijs.io/editor?user=sableraph&project=multiTextureMaterial_test
The text was updated successfully, but these errors were encountered: