Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
It's sad to be forced to pay an extreme extra amount without any warning (30 days is worthless compared to the pricehike).
I can't remember any other situation where I have felt so screwed over as now - and that's comming from the Corona team - who had a reputation of beeing userfriendly and fair.
It's not only Chaos who's having a hard time now - it's also their users.
I don't like this at all, and find it totally unacceptable.
I found the setup to be pretty straightforward (only tried demo plant, since i don't have subscription). There was couple small issues, one with aforementioned translucency setup (the fix as simple as turning off SSS and turning on translucency, all the maps were already plugged where they have to be) and another with normal map handedness (supplied maps are right handed, but setup is left handed, the fix is one click in Corona normal map node). Other than that everything works great and renders nice.
By the way, the renders in the first post are stunning!
Thanks Juraj !
They all actually have 3dsmax+corona setup, it is included inside the .fbx.
You can dowlnoad a free fern model to test it.
https://www.textures.com/download/3DFoliage0032/143200
We also plan to make bigger interior plants in the future.
Contrails distortion looks weird. Could it be somehow improved to better resemble the actual thing?
Also feature request - i would love to have an option for partial cloud coverage. No need for something fancy like painting maps for explicit control, a simple spinner "horizon bias" would be already great - quite often IRL you can see beautiful clouds over horizon, while sky overhead is completely clear, it would be nice to be able to replicate this in Corona.
Hey guys,Hi
Unfortunately can't use two latest DBs (2022-09-13 and 2022-09-20) because of error I'm getting using IR.
I get a message that some bitmap was changed during the rendering and render had to be aborted (example attached). After that render stops. The thing is that I didn't change any bitmaps during the rendering.
This error repeats quite frequently with different "maps that were changed" and makes work with IR not efficient because IR has to be restarted again and again. So I reverted to the DB 2022-09-06 - it works without this error.
Max 2022.3. Win 10
I'm getting this error also with DB 09.06 Max 2021 WIN 10
Yep, I'm also getting this error since updating to latest daily. Max 2023.1
I have a couple of questions, are your textures stored locally or on some network drive/gdrive or something similar?
Are you able to send any of these scenes over to us? If so I can PM you a link to upload it to me.
Thanks,
Rowan
Hi
Unfortunately can't use two latest DBs (2022-09-13 and 2022-09-20) because of error I'm getting using IR.
I get a message that some bitmap was changed during the rendering and render had to be aborted (example attached). After that render stops. The thing is that I didn't change any bitmaps during the rendering.
This error repeats quite frequently with different "maps that were changed" and makes work with IR not efficient because IR has to be restarted again and again. So I reverted to the DB 2022-09-06 - it works without this error.
Max 2022.3. Win 10
Amazing. Big one for me would be to respect real world sizes. So a node drawn at realworld scale would stay at realworld scale when realworld scale is selected in the mapping options! I'm hoping this is an easy one with the right maths for someone far more clever than me. It would save so much time over trying to rescale by eye and then again on different objects.
