Title: Renderking – Vray Texture Pack v3 for C4D Renderking Vrayforc4d new material pack (released 4/16). 150 materials total. Cinema4d and Vray only. Our texture are all 2048×2048 pixel seamless to give you a great quality and a high level details, they are made by many layers: diffuse, specular, normal, bump, diplacement. Vray Texture Pack v3 is made for MAC and PC.
I did a test from an existing C4D file. I used 'Save Project With Assets' and it gathers the file specific assets into a folder with the file. That folder includes a Tex folder. When I chose the file in VW for Import Cinema 4D Textures it worked as expected. There do seem to be some limitations as to what VW will see/use but when I use Send to Cinema 4D to send back the other way the textures arrive in the same state they left in. You can see the differences below with the same texture in C4D and VW.Kevin.
![]()
I did a test from an existing C4D file. I used 'Save Project With Assets' and it gathers the file specific assets into a folder with the file. That folder includes a Tex folder.
![]()
When I chose the file in VW for Import Cinema 4D Textures it worked as expected. There do seem to be some limitations as to what VW will see/use but when I use Send to Cinema 4D to send back the other way the textures arrive in the same state they left in.
You can see the differences below with the same texture in C4D and VW.KevinYes! I am told the import should be completely non-destructive to preserve the VW C4D workflow even after imported textures have been used. It's a bit problematic with textures in C4D.Generally a black color means very likely just a missing Texture.You can search for missing Textures and correct these.Normally C4D creates a 'tex' folder beside the file where it will find all textures by default.So the Textures have relative (or no) Paths.If you create a new texture by loading an image from somewhere else, C4D will ask to savethat asset in your. Thanks.The I had to 'Install' the lib4d file and drop texture folders into the Maxon application folder structure to get the textures to work. I then set the path in C4D as described. It was not hard - and they work perfectly in C4D (as far as I can tell - since I have never used it before - I am just trying to get the textures out). When I save with assets - the folder it creates seems to make no distinction between the textures from the library pack and the default textures - but VW has an issue with the lib pack textures.Frustrating.
I had build 6 cubes and attached 6 materials out of my Visualize Lib.When I saved the file with assets, those preset textures came in a tex folder beside that file.I did not try just pulling Materials in the Manager without assigning these.Maybe that would work too.Try with those C4D default Libs, in case you special commercial Lib is somehow different.But the Material will still have that Preset//. Path applied.So C4D would find these textures as it knows where Preset// is. And even if there wouldn'tbe such a texture, it would search in the tex folder nearby and find it there.I doubt that VW will have the same intelligence in that case And still don't really knowin which way that C4D Mat import works.I think when importing Mats, and Textures available, VW will import those images intothe VW file as always (?). Fail.Applying it to cubes does not seem to be any different than just pulling into the manager as I was doing before. Both the commercial texture and the default export the same way.
Both create a tex folder with images and maps, but the commercial ones do not import.It is definitely an issue with the commercial textures. The question now is it every texture that is not default or if some textures have a some sort of protection that is purposefully getting in the way of the VW import. I reached out to the texture company to see if they had any idea why this is happening.
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |