Hi, So i just upgraded to the latest Vray 7 Update 4.2 and also the latest Sketchup 2026 version. Unfortunately ran into a pretty weird issue when copying models from one model to another and even when drag an dropping a model.
As you will see for some reason when i copy a component/group/surface (doesn’t matter) from one sketchup model into another the material doesn’t show up in the Vray UI at all. The model is there, i can select the texture in sketchup but the Vray Material UI doesn’t show it.
The weird thing is if i save the model (test456 in this case) and reopen it the material then shows up without issues and vray recognizes it. As you can see on the below screenshot.
Next i tried drag and dropping one of our car components from our library and the same thing happened. Vray didn’t recognize any of the textures/colours on the car. The materials didn’t render correctly either as you can see there is no reflection on the carpaint
After saving the model and reopening it all showed up in vray and the render also shows the reflections etc. as it’s suppoed to.
I’m wondering if i have some setting incorrectly set up or if this is now standard procedure that when you copy something over you will have to save and reopen the model for it to work correctly with Vray?
Hello @levente_redecky and thank you for reaching out.
Yes, there is a technical reason for this behavior. It is considered expected regarding how V-Ray syncs its Asset Management database with the host application.
When you copy and paste a component between two instances/files using the standard OS Clipboard (Ctrl+C / Ctrl+V), the host application transfers the geometry and standard viewport materials, but the V-Ray Asset Editor does not always trigger a real-time event to register the new V-Ray material definitions immediately. Since V-Ray maintains its own internal database of materials, when pasting via Clipboard, it bypasses the standard file import pipeline, and doesn’t “register” the incoming materials into the Asset Editor list right away—even though the geometry is already in the viewport. To keep real-time viewport performance fast, V-Ray does not constantly poll/scan every object in your model for changed properties. It only parses the full 3D scene hierarchy during specific triggers.
- Saving and reopening the file (or releasing/obtaining the V-Ray license, which effectively restarts the V-Ray core/Asset Editor session) forces V-Ray to rescan the scene geometry. Upon startup, it parses the newly pasted objects and registers their V-Ray materials into the database, making them visible in the list and ready to render.
As a workaround to avoid saving and reopening the model, you can use Extensions → V-Ray → Help → License → Release V-Ray License and reactivating V-Ray by opening Asset Editor again. All materials and textures will appear instantly even if the file is not saved.
I hope this helps explain the issue! Please, let me know if you need further assistance.
Best regards,
Ivanela
Hi Ivanela, Thank you for the reply and explaining this in more detail. All makes sense it just surprised me as an earlier version we used which was still Vray 7 i think didn’t do this and things usually appeared right away after copy pasting. On the other hand with that older version we were experiencing an issue where layered textures didn’t copy over correctly and we had to set all the paths again from scratch more often than not when copying. So far i haven’t experienced that since updating to this latest version so it’s a welcome trade-off 
Hi @levente_redecky ,
Thank you for the follow-up — I’m glad to hear your experience with the latest version is better overall.
As further information on the topic: we have discussed the situation and logged a ticket in our internal system, so that our development team can work on improving the behavior in future V-Ray versions with the goal to keep all currently available functionality and fixes, while also making all copied materials and textures register and appear in the V-Ray Asset Editor immediately.
Best regards,
Ivanela
I have the same issue since the last update
