Author Topic: Forrest Pack and Lightmix/Select not working in Corona 12 update 1, as before  (Read 3394 times)

2024-11-22, 15:53:25

JG_monomiru

  • Active Users
  • **
  • Posts: 144
  • JG
    • View Profile
    • www.gehrcken.de
Recently i installed Corona 12. update 1 and it doesnt render specific light objects (various Polygonobjects with corona light material) in each of their own Light-Select Renderelement - just the main ForrestPack_Object containing all light objects when added to a light-select element.

Before corona 12.update 1 it was behaving that way

FP-object containing multiple Lightobject A and Lightobject B

in Corona 12 hotfix 1 and lower
Lightobject_A --> Lightselect_element A = light only A
Lightobject_B --> Lightselect_element B = light only B
FP-object --> Lightselect_element_FP = dark no light


in Corona 12 update 1
Now those individual light-objects get ignored and it only renderes the FP_object
Lightobject_A --> Lightselect_element A = dark no light
Lightobject_B --> Lightselect_element B = dark no light
FP-object --> Lightselect_element_FP = shows light of A and B combined

This is actually something that makes postproduction very complicated if i cant separate light-sources in Light-Selct / Lightmix anymore... and need for each light-object an individual FP-Object to be created.


Not sure if thats something the new corona verison messed up - or if its on behalf of updated Forrest.Pack

max 2025 / corona 12 update 1 / ForrestPro 9.1.5

ps. It does work with max 2024 / corona 12 hotfix 1 / ForrestPro 9.1.5

So i doubt its caused by forrestpack.
« Last Edit: 2024-11-22, 16:32:13 by JG_monomiru »

2024-11-24, 19:26:38
Reply #1

fercout

  • Users
  • *
  • Posts: 1
    • View Profile
same problem here, forest with Lightobject stop to render after corona 12 update 1

max 2021 / corona 12 update 1 / ForrestPro 9.1.5


2024-11-26, 06:26:16
Reply #2

Alex Abarca

  • Active Users
  • **
  • Posts: 452
  • Corona Certified Instructor
    • View Profile
    • Instagram
I use this workflow at times, but my current projects don't require it at the moment.

I'll stay tuned to see what the result is. I would expect that everything that worked in 12H1 should work on 12U1.

2024-11-26, 10:43:51
Reply #3

JG_monomiru

  • Active Users
  • **
  • Posts: 144
  • JG
    • View Profile
    • www.gehrcken.de
As did I... it was a surprise when I had an older Project rerendered and didn't paid attention to the corona-version i used. And then realized all my Light-Select Renderelements were "empty" - not showing specific objects light.

But regarding the Topics about Forrest Pack and C-12U1 there seem to be more issues between those plugins.

2024-11-26, 12:43:58
Reply #4

Avi

  • Corona Team
  • Active Users
  • ****
  • Posts: 700
    • View Profile
Hi,

I was able to reproduce this. I have logged it in our system to be further reviewed by our devs. We will let you know once we have any update on this.


(Report ID=CMAX-1419)
Arpit Pandey | chaos-corona.com
3D Support Specialist - Corona | contact us

2024-11-26, 13:16:33
Reply #5

Aram Avetisyan

  • Corona Team
  • Active Users
  • ****
  • Posts: 797
    • View Profile
This behavior may or may not be correct or wanted?

If LightSelect element has a forest object selected, I would expect that all the forest objects are in this element - this is the case for Corona 12 Update 1.
While if a only a single light is added to LightSelect element, I would expect only that light to be in the lightselect, not also all its instances in Forest object.
If this was somewhat useful, this - light source and all its instances in Forest object in the same lightSelect element - can be brought back.

But selecting forest object as lightselect element should definitely have the complete Forest object in it.

Let me know what you guys think.
Aram Avetisyan | chaos-corona.com
Chaos Corona QA Specialist | contact us

2024-11-26, 16:28:38
Reply #6

JG_monomiru

  • Active Users
  • **
  • Posts: 144
  • JG
    • View Profile
    • www.gehrcken.de
Well the desired Workflow which has been usable since dawn of corona was that you can have obj/Ids for each object and the Forrest-Object is not represented as an individual Objeckt_Ids in render mask elements.
That way it was resonable and good, that you have the same "logic" with lights and light-select-render-elements. So you don't have a combined Forrest-Pack light select, just the individual objects on their own.
It would be great if there could be a Forrest-Pack_- Lightselect itself... but for my workflow i would prefer to have the used light-items as seperate light-select by itself.

Otherwise i would need to have seperate Forrest-Pack objects for different types of Light-distribution.
Usually I use them for exterior rendering, where you need lots of lights in various parts of the building and various appearance... like linear light for floor spaces etc., suspended lights for office spaces, maybe round suspended lights for lobby or "meeting" zones... and maybe spot lights or  floor lights for conference spaces or else.

So if it could work like it was working all the years since light-mix was a thing, that would be great - also it would make it much more practical to work on older projects. Otherwise we need to start saving older corona-render versions for each older project ... or even worth start over with setting up render elements and also later reconfiguring post-set-ups.

2024-11-26, 16:34:28
Reply #7

JG_monomiru

  • Active Users
  • **
  • Posts: 144
  • JG
    • View Profile
    • www.gehrcken.de
I know Object-Ids and Material_Ids behaved differently in Corona and Vray with Forrest-Pack...

when i worked with Vray before corona-render, i was a bit surprised i didnt had all the forrest-pack object as just one ID... but then i really discovered the potential to have each-distributed object with their own ID... Specially when working with RGB-Masking.
Now after almost 10 Years of working with Corona I definitly don't want this to change...
And also working with Light-Mix for a fair amount of time, i definitly don't want the old "behaviour" to be changed.

So definitly preferring individual sub-lights over a combinded forrest-pack  in light-select element. If there is a technical reason why you can't have both.

2024-12-10, 16:53:03
Reply #8

JG_monomiru

  • Active Users
  • **
  • Posts: 144
  • JG
    • View Profile
    • www.gehrcken.de
Will this Issue be resolved in a future Update?

For now 12u1 is unusable without it.

2024-12-10, 19:49:44
Reply #9

v.p.vlasenko

  • Active Users
  • **
  • Posts: 90
    • View Profile
Just in case someone missed it - same story with FP and masking. You can't add objects into the mask include/exclude as before, only the entire FP object. I think those problems have the same roots.

2024-12-11, 06:52:53
Reply #10

Aram Avetisyan

  • Corona Team
  • Active Users
  • ****
  • Posts: 797
    • View Profile
Hi,

Letting you know that this has been fixed internally (reverted to previous behavior).

For the masking, can you please show, in a simple scene, what you mean, so that can be checked too?
Aram Avetisyan | chaos-corona.com
Chaos Corona QA Specialist | contact us

2024-12-11, 18:33:33
Reply #11

v.p.vlasenko

  • Active Users
  • **
  • Posts: 90
    • View Profile
Sure, here it is:
first image - chaos scatter. Scattered objects - box, sphere and teapot included in r,g,b
second image - forest pack. Same setup, but FP objects aren't visible in the mask(previously it worked the same way as chaos scatter)
third image - FP object included in R channel of another mask. Not 100% sure, but it look like previously it wasn't possible to include the entire FP object in the mask

I just noticed - I messed up with the render setting on the screenshots (didn't show the mask settings), but I think you get the point. 

« Last Edit: 2024-12-11, 18:39:50 by v.p.vlasenko »

2024-12-12, 17:27:21
Reply #12

Aram Avetisyan

  • Corona Team
  • Active Users
  • ****
  • Posts: 797
    • View Profile
I my guess what you are referring to, but please be more specific:

E.g.

X mask element's Y mode worked this/that way in Corona 12 HF1 (for ChaosScatter object and/or FP object) and changed in Corona 12 Update 1.
Or something similar.

It will help to both understand and report the issue the best.
Aram Avetisyan | chaos-corona.com
Chaos Corona QA Specialist | contact us

2024-12-13, 00:02:40
Reply #13

v.p.vlasenko

  • Active Users
  • **
  • Posts: 90
    • View Profile
previously FP worked the same way as Chaos Scatter.

I have 3 objects - box, sphere, teapot.
Then I scatter these objects with forest pack.
To see items scattered by FP I need to include box, sphere and teapot into cshading_mask. That's how it worked before. That's how chaos scatter works.

But now it has no effect on FP. If I include those objects - I can't see FP items in the mask.

Simply - the second screenshot should look the same as the first one, but it doesn't.


2024-12-13, 10:08:14
Reply #14

Aram Avetisyan

  • Corona Team
  • Active Users
  • ****
  • Posts: 797
    • View Profile
I believe what you are saying is the original issue (for lightmix layers), as it is a matter of how/what to include in a (masking) layer.
I have tested it with the fix, and it is indeed working as you say - an object and all its instances in forest object are included in the mask.
Aram Avetisyan | chaos-corona.com
Chaos Corona QA Specialist | contact us