Grouped proxies in reference mode crash Vray 7 GPU

[ritoo]

If a group containing vray proxies* serves as geo for a forest in reference mode - it'd crash Vray 7 GPU 100%.
*- a group of regular meshes instead of proxies renders fine. Vray CPU renders grouped proxies just fine.
Please fix it!
P.S. grouped proxies in the regular image mode do work (though in one case of (progressive rendering)  I had some wild PC freezing, the mouse barely moved). Vray 6 GPU doesn't have this issue.

[iToo]

I cannot reproduce this issue. I used a group of teapot proxies distributed by reference mode, FP 9.1.6, Max 2025, V-Ray 7 Hotfix 1.

Please, send us a simplificated scene and we'll test it here.

Thanks,

[ritoo]

I cannot reproduce this issue. I used a group of teapot proxies distributed by reference mode, FP 9.1.6, Max 2025, V-Ray 7 Hotfix 1.

Please, send us a simplificated scene and we'll test it here.

Thanks,

Thanks for reply, I sent. Is it OK on your end? I used Max 2023, don't think it matters.

[iToo]

With your scene i can reproduce the problem here.
According to the debugger, crash happens in one of the V-Ray modules. I just reported it to Chaos.

[ritoo]

nice, thank you

[ritoo]

In attached picture (group-v7) you can see yet another problem with groups in vray7. The group members (meshes this time, no proxies) are rendered in wrong (random) order. instead of pyramid+torus+teapot combo I get 3 teapots (and it changes randomly in the next render). Vray 6 doesn't have this problem.
Is it also Vrays 7  inner problem?
Please sort it out ASAP 'cause groups as geo is essential thing for us
P.S. Less important: With any vray version, when forest is displayed in proxy mode, all group members are being placed in one point, which is wrong (see group22.png).  The cloud mode shows it right way though.

[iToo]

Probably it's the same problem.
Chaos confirmed us the crashing issue is a bug introduced in V-Ray 7 GPU. They will release a fix asap.

I will check the viewport bug, which has not relation with the other issues.

[ritoo]

Firstly, no more crashes with the latest vray build. Grouped proxies in reference mode are rendered right as well. Many thanks!
However, grouped geometry in image distribution mode is rendered wrong way - only one group member (instead of whole group) is rendered, or (if group members are proxies) vray substitutes all group members with one.
In reference mode vray also substitutes all group members with one group member (see the picture above)

[iToo]

However, grouped geometry in image distribution mode is rendered wrong way - only one group member (instead of whole group) is rendered, or (if group members are proxies) vray substitutes all group members with one.

I can confirm this problem happens also with the latest nightly build, although the crashing bug is fixed.

I just reported it to the Chaos team.

[ritoo]

Hello, today I tried the most recent build of FP+Vray 7 and it  appears the "groups as geo" support is broken:

1.Group as Geo+VrayCPU+FP in image mode       = only one group member is scattered.
2.Group as Geo+VrayGPU+FP in reference mode  = one group member substitutes all other group members (see attached pic)
3.Group as Geo+VrayCPU+FP in reference mode  = OK

Since you got ins in Chaos, could you please help to resolve (preferably preferably for a long period the issue?
P.S. Chaos Scatter renders groups correctly

[iToo]

Hello, Chaos just included the GPU fix in the latest nigthly compilation (build 32953). Please download and test it.

Regarding problem 1, i cannot reproduce it. Group works fine in CPU mode.
I used the attached test scene (just switch from GPU to CPU mode). Please, can you compare it with your scene ?

[ritoo]

>>>Regarding problem 1, i cannot reproduce it. Group works fine in CPU mode
I sent an example to Helpdesk, is it reproducible in it?

[iToo]

>>>Regarding problem 1, i cannot reproduce it. Group works fine in CPU mode
I sent an example to Helpdesk, is it reproducible in it?

In this case, items in the group are not visible because are colliding between them, and Collision checking is enabled.
Please try to separate items in the group, or adjust collisions settings.

[ritoo]

Oh! you nailed it Thank you so much
But is there a way to tell collisions to treat the group as one entity? If there isn't one, could it be implemented?

[ritoo]

>>But is there a way to tell collisions to treat the group as one entity? If there isn't one, could it be implemented?
I took a look, it works this way in Chaos Scatter. Frankly, its rather logical..