Hi !
Here is a bug report.
I tried to enable the Height Map in my PBR Material but the render indicates to me that I need to create UV attributes thanks to the Texture SOP 
Is there a node to create easily UV with POPs ?
Edgar - SARV
I also have another question:
Is it possible to free the GPU memory like it was possible with the TOPs and the unload() function ?
Edgar - SARV
Hello Edgar,
For POPs, the UV attribute is named Tex. POPs like the Sphere, the Grid, the Torus or the Box will generate this attribute. You can also use the Texture Map POP to generate the texture coordinates.
The warning message might be misleading, we should fix this.
As far as I know, this is not possible for now. The node has to be deleted to free up it’s memory.
Hello Guillaume,
Even if I have Tex attribute on my sphere I still have the warning message and my geometry is not rendered.
I hope that the unload() method will be implemented. Never tried the destroy() yet, hope it will work well with POPs
Last and important thing :
On the “Learning about POPs” Notion page, there is this link Login | Podio and I always get this error :
Edgar
Hello Edgar,
I looked closer at the rendering and it seems that the texture coordinates are not used, so it definitely looks like a bug we have to fix.
EDIT: In an upcoming version, the rendering warning is gone and the texture coordinates are used by the materials.
The link on the ‘Learning about POPs’ is internal and should not be there. This will be fixed.
Thank you for reporting these issues!
hello
I’m having similar problems
I have an obj from houdini with UV, Normal, P attributes and TD is asking for Tex attribute. What exactly do I do using the Texture Map POP?
thanks so much
I think you need to rename the UV attribute to Tex. Should be possible with an Attribute POP. Otherwise (e.g. if datatype or array length problems) the Math POP can do it. No need for Texture Map POP if you already have UV coords.
(Using POPs since less than a week so I might be wrong in all of this)
Thank you i will try that
still no idea, quite confusing
@konxompax, it looks like your model already has a vertex Tex attribute (not a point attribute).
cheers i’ll have a look at the data base
installed the lastest update and it worked! thanks for all your help