Itoo Software Forum

Forest Pack => Forest Pro (*) => Topic started by: FC2603 on February 04, 2021, 09:40:46 am

Title: Visible to Camera
Post by: FC2603 on February 04, 2021, 09:40:46 am

I'd like to use a forest object only for the shadows they create and so would normally just select the layer, uncheck visible to camera etc. and that would do it. It doesn't seem to work on forest objects and I can see from a previous post back in 2016 the workaround suggested was to convert the object to instances using forest tools.

The problem with this is that I'd like to move the objects around in the items editor and change the geometry/distribution so converting to instances pretty much means the positioning is set without moving things individually. Is there a way to make the object invisible to the camera?

Title: Re: Visible to Camera
Post by: Rokas on February 04, 2021, 09:51:40 am

select not the layer with FP, but FP object itself:

(https://i.imgur.com/jg85TGe.png)

Hope this helps.

Title: Re: Visible to Camera
Post by: FC2603 on February 08, 2021, 03:44:32 pm

Thanks. Thought I'd already tried that but can see it working now.

Title: Re: Visible to Camera
Post by: ldotchops on January 09, 2025, 06:52:23 pm

Hi, I have tried this with the new Forest Ivy but not having any luck. is there a way to make it work correctly?

Title: Re: Visible to Camera
Post by: Michal Karmazín on January 10, 2025, 09:46:20 am

Hi,

I’ve just performed some quick tests with the Object Properties > Rendering Control > Visible to Camera option disabled, and it appears to work correctly in both V-Ray 7 and Corona 12. Could you please specify the renderer you are using?

Best regards,

Title: Re: Visible to Camera
Post by: ldotchops on January 12, 2025, 11:01:55 pm

I am using Redshift

There is also redshifts own object properties which still don't work

Title: Re: Visible to Camera
Post by: Michal Karmazín on January 13, 2025, 11:07:39 am

For render engines without an SDK, such as Redshift and several others, we cannot add support ourselves. Instead, we offer an internal API written in C++ for the 3ds Max SDK. Renderer developers can use this API to generate instances directly in their engines. Therefore, the implementation of our plugin features depends primarily on the developers of each specific render engine, and I suggest reaching out to them directly (https://www.maxon.net/en/support-center) or via their forum. I'm afraid there isn't much more we can do on our side, although we will happily collaborate with them if improvements can be made. Thank you for your understanding.

Best regards,