Timeline for "Texture Space" vs "Texture Map"
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 26 at 18:55 | vote | accept | Orange in Dark | ||
| Jan 26 at 18:54 | comment | added | Markus von Broady |
SDATA represents what you saved there. If you connect "Position" it becomes an alias of the vertex/edge/face position. Saving position is often used to store original position, then temporarily move for some reason, and then move back to the stored position. If you connect "UV Map", then SDATA becomes the UV map, which tells you what 2D coordinate on a texture (UV simply means XY, but other letters are used to not confuse 3D space, and texture 2D space) a given point is assigned to. Research "UV unwrapping" to understand this.
|
|
| Jan 26 at 18:40 | comment | added | Orange in Dark | Thanks ❤️❤️❤️ as always helpful. Could you kindly ❤️elaborate on your answer in relation to "Texture Space" vs "Texture Map"? I’m new to the 3D modeling world and would like to know what the SDATA attribute describes. Is it a ‘texture map’ or ‘texture space’? I am that rookie.😊I’ve learned many keywords this week, but I’m having trouble putting them together in a way that makes sense to me🤷♂️ | |
| Jan 26 at 17:31 | history | answered | Markus von Broady | CC BY-SA 4.0 |