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.


Messages - maru

Pages: [1] 2 3 ... 843
1
An interesting issue!
How about using two decals - one with the highly polished transparent material (closer to the surface, "affect color" disabled) and one with the full material (farther away from the surface)?

2
Gallery / Re: SOUTHERN POLAND
« on: Today at 16:41:20 »
The images are pointing to some non-existent Dropbox items (or they are inaccessible to external users).

Being Polish myself, I need to ask out of curiosity - why did you choose Poland? :)

3
@cgiout I have create a support ticket #216163 for you - you should receive an email notification

4
I can't reproduce it. Which exact version of Corona are you using? Could you send us any scene where this happens? (it can be just one object with the problematic material)

5
Hi, the vrscan called rca96517.vrscan which is a carbon, renders semi transparent. Carbon stripes render solid but the rest is completely transparent.
While another carbon called carbon.vrscan renders completely correctly.

The material rca96517 does not render transparent for me. In the attached scene, I placed a rectangular light behind the teapot and it appears fully opaque.
Please provide exact reproduction steps.

6
Guys, if you can consistently reproduce a Corona Bitmap looking "worse" in the viewport, please send us a sample scene. I was not able to get anything meaningful.
On the other hand, whatever is happening here, it's probably handled by 3ds Max.
You may also need to check your GPU driver settings - things like anisotropic filtering, texture filtering quality, etc. I am sure those options affect texture quality in the 3ds Max viewport.

7
Would you be able to share the command for ImageEditorCmd to automate this process? I'm not at all familiar with it.

I am sorry, but I'm not sure if I understand that. What exactly do you mean by "this process"?

If you mean just batch converting from CXR to EXR, then you can find the batch script here:
https://support.chaos.com/hc/en-us/articles/4528237016721-What-is-the-Corona-Image-Editor#h_01FDT56CPJ15M39C6W4Z2B5VM7
After unpacking, you will see sample files inside. It converts all CXR files which are placed in the same directory as the batch script itself. If you need to change some options (like output file format) you need to edit the .bat file. You can use your own Postprocess.conf file saved from Corona VFB or CIE.
By default, it outputs all render elements, but you can limit this by editing the batch file.

8
Tone mapping is included in CXR files as metadata so it is not "baked" when renaming CXR to EXR. I am afraid that the proper solution here would be to make Cryptomatte a "regular" render elements, and we have to wait for that. We have it reported internally.


9
Migrated information from https://wiki.corona-renderer.com/ to the Chaos Documentation Portal. When trying to access the wiki (both https://wiki.corona-renderer.com/ and https://corona-renderer.com/wiki), you are now redirected to Corona Docs).
- Corona Standalone - https://docs.chaos.com/display/CS

Moved the installation guide from the Help Center to the Documentation Portal:
- https://docs.chaos.com/display/CRC4D/Installation+Process

Updated denoising articles:
- https://support.chaos.com/hc/en-us/articles/4528493906449
- https://support.chaos.com/hc/en-us/articles/4528591107729
- https://docs.chaos.com/display/CRC4D/General+Settings
- https://docs.chaos.com/display/CRC4D/Corona+Image+Editor
- https://support.chaos.com/hc/en-us/articles/19921888943505
- https://docs.chaos.com/display/CRC4D/Corona+Interactive+Rendering
- https://docs.chaos.com/display/CRC4D/Performance+Settings

Updated the system requirements article:
- https://support.chaos.com/hc/en-us/articles/4665349542417

Created an article for the Corona Edge Shader:
- https://docs.chaos.com/display/CRC4D/Corona+Edge+Shader

Updated the Lister article:
- https://docs.chaos.com/display/CRC4D/Corona+Lister

Added Tile ID to the Mapping Randomizer article:
- https://docs.chaos.com/display/CRC4D/Corona+Mapping+Randomizer+Shader

Added Tile ID to the Multi Shader article:
- https://docs.chaos.com/display/CRC4D/Corona+Multi+Shader

Updated the SSS in Corona article:
- https://support.chaos.com/hc/en-us/articles/4528339318289

Updated the Scene Converter article:
- https://docs.chaos.com/display/CRC4D/Scene+Converter

New error messages:
- https://support.chaos.com/hc/en-us/articles/19921888943505
- https://support.chaos.com/hc/en-us/articles/20443030242193

...plus various other updates and changes to keep all articles up to date.

Note: if you spot any issues, something isn't working, or you would like to share any kind of feedback with us - please contact us here.


10
Migrated information from https://wiki.corona-renderer.com/ to the Chaos Documentation Portal. When trying to access the wiki (both https://wiki.corona-renderer.com/ and https://corona-renderer.com/wiki), you are now redirected to Corona Docs).
- MAXScript - https://docs.chaos.com/display/CRMAX/MAXScript
- Corona Standalone - https://docs.chaos.com/display/CS

Moved the installation guide from the Help Center to the Documentation Portal:
- https://docs.chaos.com/display/CRMAX/Installation+Process

Updated denoising articles:
- https://support.chaos.com/hc/en-us/articles/4528588388113
- https://support.chaos.com/hc/en-us/articles/19921888943505
- https://support.chaos.com/hc/en-us/articles/4528596854289
- https://docs.chaos.com/display/CRMAX/Performance+Tab
- https://docs.chaos.com/display/CRMAX/Scene+Tab

Updated the system requirements article:
- https://support.chaos.com/hc/en-us/articles/4665349542417

Created an article for the Corona Edge Map:
- https://docs.chaos.com/display/CRMAX/Corona+Edge+Map

Updated Converter articles:
- https://support.chaos.com/hc/en-us/articles/4526289638033
- https://docs.chaos.com/display/CRMAX/Corona+Converter

Updated the Lister article:
- https://docs.chaos.com/display/CRMAX/Corona+Lister

Added Tile ID to the Mapping Randomizer article:
- https://docs.chaos.com/display/CRMAX/Corona+Mapping+Randomizer

Added Tile ID to the Multimap article:
- https://docs.chaos.com/display/CRMAX/Corona+Multi+Map

Updated the SSS in Corona article:
- https://support.chaos.com/hc/en-us/articles/4528498501137

New error messages:
- https://support.chaos.com/hc/en-us/articles/19921888943505
- https://support.chaos.com/hc/en-us/articles/20443030242193
- https://support.chaos.com/hc/en-us/articles/20283060170257

Updated the Corona Color Map article:
- https://docs.chaos.com/display/CRMAX/Corona+Color+Map

...plus various other updates and changes to keep all articles up to date.

Note: if you spot any issues, something isn't working, or you would like to share any kind of feedback with us - please contact us here.


11
There is a problem with displaying CoronaBitmap in viewports. Plugging exactly the same image file (be it .jpg .png .bmp, it doesn't matter) to a std Max Bitmap slot and CoronaBitmap slot, and then trying both on a corona material (Legacy or Physical, don't matter) always results in visible difference between the two in the viewport, in favor of the std Max Bitmap. Corona bitmap displays so poorly that any accuracy adjustments to mapping on objects need to be performed with std Bitmap just to see what you're doing, cause you cant see sh*t trying to use Corona bitmap, which displays blurred, compared to Max Bitmap (at exactly the same bitmap settings. And yes - cranked up)

When calling something sh*t, could you please at least attach a screenshot?
Here is mine - I was about to play a game of "guess which one is Corona", but I actually got visible difference in the "1234" bitmap, probably because it's stretched.
The other ones look identical, so I can't confirm your statement "always results in visible difference".

12
Just noticed right now that vrscans materials don't render correctly, sometimes objects appear as transparent or semi transparent...

Can you share which exact Scans are rendering incorrectly?

13
[Max] I need help! / Re: wxWidget Debug Error
« on: 2024-02-27, 13:18:00 »
Unfortunately, I don't think we can help if we don't reproduce the error. If you can share any scene where it has appeared at least once, please do.
Other than that, it will be most likely fixed with the new VFB, which is planned to be a part of Corona 12.

14
Hi, first of all, thank you for your feedback. We rely on it, and it is what makes Corona better. But at the same time, I would like to ask you to stop being hostile and offensive. I understand that things sometimes get frustrating, but such messages will not help you, even if something you don't like is a result of a bad decision. Saying thigs like "fix it!" or "you messed up!" is something we will not tolerate.


In certain past versions of Corona there was an ingenious keyboard shortcut that worked in VFB Corona to quickly create region render fields.
All you had to do was press Shift + left and create regions.  It sped up the workflow nicely.
I will make sure that this is reported.

Quote
The second question is why the Road Map Corona lists only 2 people introducing new innovations in subsequent versions? Are Martin Šik and Ondra Karlik the only programmers in the Corona team? :D No one else is writing new lines of code? I once saw a picture from 5 years ago of people working on Corona and it was over 20-25 people if I remember correctly, how is it possible that only 2 people have been developing Corona for several versions?
I take it as a joke and Tom has already explained that, but I can assure you that Corona is being developed by many more than 2 programmers. :)

Quote
The third annoying thing since 2-3 versions of Corona, is every time you open an interactive rendering or final, you have to manually expand Tone Mapping, by default either all of them are closed, or Bloom and Glare are open.
I will make sure that this is reported.

15
I could reproduce the issue when using the noise limit. It was discussed here and Romullus correctly explained what is going on: https://forum.corona-renderer.com/index.php?topic=34688.0
With a black background, there is more contrast in the scene, so even if you render the scene to the same quality, the reported noise level will be different.
I agree that this is problematic since the same noise limit value should guarantee more or less the same quality. Using a black background override is a common workflow, for example when replacing background in post.

As a workaround, I would suggest using the noise limit with an additional pass and/or time limit. For example, you can set your noise limit to 2%, but you may not want to render your frame for more than 1 hour or 200 passes.

We do have this reported internally.
(Internal ID=1310588860)

Pages: [1] 2 3 ... 843