Loading...
> >

Quirk with Geometry Shell?

SimonJMSimonJM Posts: 5,982
edited December 1969 in Technical Help (nuts n bolts)

I am possibly 'abusing the privilege' but thought I'd check out a suggestion I made to someone about how to, simply, replicate something they had done in Reality/LuxRender in Octane, via the OcDS plug-in. At the time I was not at home so no access to much so was working from memory and hope ...! ;)
The suggestion was how to get an 'overlay texture' working. Not sure what the original figure that was used was, but the process was to give it a normal set of skin textures, then to apply 'goop' and a set of transmaps to a GeoShell, adjusting texture in Reality.
From memory I seemed to recall having issue in OcDS wit GeoShells and trying to work out just what surface belonged to what - the figure or the shell and having no fun whatsoever! I then recalled the wonderful PGE tool and put that forward as an idea - grab a load of the polygons of the shell and allocate them to a new surface with an obvious and unique name so they can be easily identified within OcDS. Now back home I have tried doing that and ... well, it all goes very strange on me!

First off, is using PGE on a GeoShell a valid thing to try?

It seems to select a single, entire, MAT zone regardless of what you think you have selected. And after that the 'normal' MAT zones go haywire - with the Forearms selected as a surface in the viewport I have Nipples selected in the list of surfaces. Hovering the mouse over the Hips the helpful popup declares 'Neck' and if I select Forearms in the list of surfaces the Feet get highlighted in the viewport!

Thus my questions - should I be slapped and locked up and told not to be silly? If not, is it just me and my install of 4.6.2.120 that does this? I recall a similar issue with some of the GeoGraft stuff which was later fixed.

Comments

  • Richard HaseltineRichard Haseltine Posts: 100,941
    edited December 1969

    I wouldn't expect that to work - a geometry shell shell, like an instance, is a second item reading the geometry of the original item so that there's no need to duplicate it (nor the rigging and deformations) - as a result it doesn't own any polygons of its own for you to edit.

  • SimonJMSimonJM Posts: 5,982
    edited December 1969

    Richard Haseltine said:
    I wouldn't expect that to work - a geometry shell shell, like an instance, is a second item reading the geometry of the original item so that there's no need to duplicate it (nor the rigging and deformations) - as a result it doesn't own any polygons of its own for you to edit.

    That is pretty much what I expected, but it still does some really weird things! :)
Sign In or Register to comment.