Messages

1

[Max] General Discussion / Re: ForestPack Masking

« on: 2025-08-03, 20:42:24 »

I think we had this discussion, when it was accidental changed in c12…. Because we got used to the workflow with ids for individual source objects and not Forrest object.
If this source object could’ve maintained and the other would be an optional approach it would be fine. But I like to have individual mask for source objects (trees or furniture etc) to alter it in post.
If only Forrest pack is able to have a mask I’d, then you end up with many Forrest objects for various source objects.

Just as dj_buckley said it’s quite easy to select individual source objects and all apply them same id

2

[Max] I need help! / Re: License Issues ...

« on: 2025-07-15, 12:46:44 »

Rendering works in the first instance of Max which i opened and rendered - but not in the second or third...

3

[Max] I need help! / License Issues ...

« on: 2025-07-15, 12:34:20 »

Hello.

I installed Corona 13 on Max2025u3 and now i got inconsistent Errors when starting to render, or with IR.

That mainly happens, when i have 2 instances of Max2025 opened on my workstation and accessing license from a network-server (i updated license server there to version 6.2.2)
I also tried to log in and log out.

Is it not allowed anymore to have multiple instances of Max opened and accessing the GUI-license with one machine, is it now restricted to the instance of max?

Previously it was possible to have multiple instance of Max opened and do some IR on one instance, and maybe later render the other one... while all instances remain open?

4

[Max] Previews (Daily Builds) / Re: Tiles playground

« on: 2025-06-17, 14:57:54 »

is it possible in corona13 now, to create different gap/grout sizes for horizontal and vertikal gaps?

I haven't been able to test the new version yet - but thought asking might help.

5

[Max] Bug Reporting / Collab -in VFB causing "internal error meesage"

« on: 2025-05-10, 20:29:32 »

When rendering a Scene and accidentally hit "collab" instead of "Lightmix" the rendering stops with "internal error..."

This is kind of troublesome. After this render failure - you need to close max completely to start a new rendering again. Is there a way to let this "Collab" tab disappear - when you're 100% sure you will not ever use it?



max2025 - corona 12 update 2

6

[Max] I need help! / Re: CG-Source Multitexture to CoronaMultiMap Converter?

« on: 2025-03-07, 10:14:13 »

that would be totally helpful - right now i'm also updating everything by hand...

7

[Max] General Discussion / Re: Corona 12 Update 1

« on: 2025-01-23, 08:27:23 »

Well regarding the E-mail notification in December - no such email under the mail i got my corona license registered.

8

[Max] General Discussion / Re: Corona 12 Update 1

« on: 2025-01-22, 19:43:52 »

is this for real? i mean corona 12.update 1 just came out and introduced a lot of pain for many - and you stating here that everything before corona 12u1 will stopp working after 28th of January?

will there be an official information to every license-holder? I mean Tom you're kind of official - but that doesn't mean someone need to accidental read this info in this forum.

what if i have a running project and don't want to change corona versions inbetween?

or are we talking just about the license-server?

9

[Max] Bug Reporting / Re: Forrest Pack and Lightmix/Select not working in Corona 12 update 1, as before

« on: 2024-12-20, 09:14:46 »

Despite I was a bit ranting on certain things.

Thanks its being addressed and taken care of.

Merry Christmas to the Developers and Team!

10

[Max] Bug Reporting / Re: Forrest Pack and Lightmix/Select not working in Corona 12 update 1, as before

« on: 2024-12-18, 08:47:30 »

There are infinitely many test scenarios, and that is why we highly encourage to try or test a few scenes/scenarios, as close as possible to production (with a backup of course), so such things are found and tackled.

I get that the behavior is adopted, but that doesn't mean it is correct or expected, and doesn't it need to be changed or improved?

Still weird you state that a behaviour which was there since many years is "not correct" ... if it weren't correct you could have mention it before. Now that ForrestIvy is there suddenly you change things...reagarding Forrestpack behaviours. It wasn't a problem for many years, but seems to be now.

For me ForrestIvy behaves a lot like RailClone and i'm ok with railclone not having unique IDs for each subobjects, rather one object-id for the main RC-object - same with Lightmix.
But its a different scenario - i can work with this and have adapted to it.

With Forrestpack it was a cool feature you can have individual IDs/Lightmixselects per suboject and not the whole - even though in some scenarious this might be wanted. But then you could bring it as an option or figure things out with itoo... to add a option-button if masks/lightselects will be individual per suboject or for a FP-object. Then artists have more freedom with controling it.
Other than that I haven't tested it with cryptomatte yet - might be nice to have both masking options in one rendering - like whole FP object in cryptomatte and individual sub-objects in Cmasking-mask

11

[Max] Bug Reporting / Re: Forrest Pack and Lightmix/Select not working in Corona 12 update 1, as before

« on: 2024-12-13, 21:42:52 »

and also its not as odd as it sounds to have some objects in your scene as "master" and then distribute them with forrest pack - so i can easily exchange furniture or lights or whatever when the demand is there for it.
With having unique masks (rgb by object-id) you always can select this specific object and then do some "post-pro" touchups....
Also with lights its quite an efficient workflow when having multiple differen light objects as master and want to distribute them in certain ways and later maybe exchange just the object and not the position.
So you dont need to mess around with 100s of instances in your scene-explorer...

and the fun part is then for photoshop or whatever... you have each light as a light-select element where you can use that in photoshop to enhance certain areas...
 Much faster then always figuring out all the perfect light-setup inside lightmix or even in 3dsmax before...
Sometimes its speedier just do it in post (even though its not as popular as it was 20 years before)

The examples shows ... scene explorer only has 5 objects for this light setup ... 4 different ligths and one forrest-object ...in this "new behaviour" i would have to creat for each light a forrest-object by itself ... or distribute each light as instance.. which is quite a pain in the end.


and sorry for sounding "pissed" before - i appreciate if you introduce new options... but it was weird asking after that sudden and maybe unwanted change appeared, if we would prefer that instead of the old one... i mean we got workflows now on the older behaviour and might even need to work on older projects. i dont really want to install every now and then an older version just to keep working on older projects. that might be ok for really old projects where you kept track of plugins and renderengines and might even just use an old version of max... but not something with "minor" versioning.... like from 12hfx1 to 12update1.

12

[Max] Bug Reporting / Re: Forrest Pack and Lightmix/Select not working in Corona 12 update 1, as before

« on: 2024-12-13, 21:26:48 »

Well the behavior was there for many years... At least for object id and also since light mix was a thing.
So we adapted workflows upon it. So it doesn't seem like a nice idea to suddenly change it... And then ask later if that new behavior is something we want.

13

[Max] Bug Reporting / Re: Forrest Pack and Lightmix/Select not working in Corona 12 update 1, as before

« on: 2024-12-13, 12:00:30 »

it seems the validation or beta of hotfixes are not tested thoroughly enough.
as those things seem to mess up production workflows ... previously i could mostly switch to a new version of corona without so much of fear everything breaks apart. As it might with a new version of 3dsmax and not version-compatible plugins ... when they are released later even sometimes a half year later.

Not sure what happend with corona 12 update 1 ... but releasing an version which alters behaviors as harsh as this is not good. You should consider revoking 12 update 1 or releasing a fix quite soon.

sorry for being that harsh - but I'm supportive of corona for a long time and with increased subscription prices i might be also more demanding.

14

[Max] Bug Reporting / Re: Forrest Pack and Lightmix/Select not working in Corona 12 update 1, as before

« on: 2024-12-10, 16:53:03 »

Will this Issue be resolved in a future Update?

For now 12u1 is unusable without it.

15

[Max] Bug Reporting / Re: Forrest Pack and Lightmix/Select not working in Corona 12 update 1, as before

« on: 2024-11-26, 16:34:28 »

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.