Hello. Recently, I was trying to figure out how to populate some points with an asset from V-Ray Cosmos Browser through a grasshopper script that I made. The script worked well for my needs, but when I try to render these geometries with V-Ray, the assets just have the simplified proxy geometry and lost its materials as well. I almost certainly that I am doing something wrong, and this is not a bug. So, I would like to know how to proceed to make it works (populate some points with asset from Cosmos Browser through grasshopper script and have those geometries rendering properly with V-Ray).
I would like to not share my files here (actually, this would be a little bit complicated), but I can share my thought about it (I think there is no necessary to have the files to figure out what is wrong - of course, I need your solutions, since I do not know what is wrong):
This was the rendering after I have created the geometries with grasshopperâs script to move an geometry (an tree from Cosmos Browser) to many point, in order to populate these points. Also, this was my result:
By the way, in the script, I plug the Tree Asset from Cosmos Browser in the âGeoâ component. If you need to replicate the problem, I am sure that is possible to use any type of tree asset from Cosmosâ Library.
This would never work. A cosmos geometry is not a GH geometry - it is a VGeo that can only be plugged into a component that accepts a VGeo. Generic transformation components like move or rotate wonât work.
What you want to do is called scattering. There are two ways to scatter V-Ray objects in GH - a
Scatter component - non-deterministic random scattering;
Thanks a lot, Nikolay! Yes, I was doing this. At the beginning, I was not aware about the different between a VGeo and a GH geometry (I did not even know about Vray components in GH, indeed - maybe I just needed to do a bit more research before posting a topic with this question on Rhino Discourse, but that is okay).
Now I was dealing with another issue. When rendering, I am using the âV-Ray Render in Projectâ component to have any geometry in the Rhino Model included with the VGeometries in the final render. But for some reason it only returns the model geometry, not the scattering done in GH with the model geometry.
This was rendered with the âV-Ray Render in Projectâ component, which should render the scattering made in GH with the geometry of the rhino model, but the result is not as expected. The floating tree is just a Cosmos asset placed in the project, this is not from the GH.
I will provide some files (different from the original, but with the same logical process) with the script and the model.
[https://we.tl/t-tQhcsGPsbt] (Pack Project + GH file) => WeTransfer link including Pack Project and GH script, but it will expire in 3 days, so if necessary I can upload this file again after this period.
scatter_vgeo_cosmos.gh (17.7 KB) => The GH file, if needed to replicate the problem with just the script (by the way, the model has only one surface as a plane and a Dome Light with an HDRI as a light system, so the model is straightforward replicable).
those are textures to cosmos assets. Make sure the assets are fully downloaded, no missing files. If necessary delete and re-download the assets in question
Yes, Nikolay, the asset was fully downloaded. Even though, I deleted and re-downloaded the assets, but the problem persists. I was wondering if the special character in my name is the problem. Iâm not sure, but might GH have trouble finding directories with special characters? I have a Latin name, which has an accent over a letter. My directory also has the same special character. Maybe that could be the problem now?
Yes. After changing the username directory, I got it. Therefore, GH couldnât load files if there are special characters in their names. It was a headache, but now everything is working. Thank you for your attention through all the problems, Nikolay.
alright, thanks. Weâll check here and file a bug report if necessary
It is not actually GH, but the sender that transfers the assets to Rhino, right ?
Hi Nikolay.
Iâm not sure, but the error occurs when you try to render something from GH through V-Ray components (as we saw with that isolated tree in the âV-Ray Render in Project Componentâ image, when you try to render something from, for example, Cosmos Browser, there are no errors). So, even if someone tries to use a V-Mesh with a certain path location, the bug will occur. So, itâs probably the sender that transfers the assets to Rhino, as you said.
I would like to let you know that the issue with rendering geometry with file paths containing special characters with âRender in Projectâ is now resolved and the fix will be included in the next major update.
