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 - TomG

Pages: [1] 2 3 ... 409
1
[Max] I need help! / Re: Black color in viewport render
« on: Yesterday at 13:42:33 »
Most welcome! I recommend the "Corona 13" solution :) But the others should work too. I hope you get everything up and running as expected quickly and painlessly!

2
[Max] General Discussion / Re: Offline VR
« on: Yesterday at 13:41:21 »
This would have to be some third-party tool, if it exists, that would make something like an .exe, or that has an app you can install on the VR device.

Also, do you mean real-time VR, or just a virtual tour but done in VR (that is, still images that are stereoscopic, and have hotspots to move from one still image to another)?

As such, since it is outside the realm of Corona itself, I've never looked into whether such apps exist so can't say which ones are out there :) Maybe folks in the community can chime in.

3
[Max] Daily Builds / Re: Are you still using the old VFB?
« on: Yesterday at 13:34:37 »
We are planning to make at least some changes to the VFB 2, yes, so the more details provided here on things you don't like, the better, as that will help guide us on what we decide to adjust this time around :)

4
[Max] I need help! / Re: Black color in viewport render
« on: 2025-07-01, 14:22:52 »
This is most likely a material with some volume effect to it, that is applied to non-closed geometry (think glass or water, applied to a flat plane). Because the geometry is not closed, and cameras can now detect when they should be classed as being inside a volume (to allow the "camera half submerged in a pool" type render), then the camera sees itself as being inside a volume.

Solutions: Close the volume (don't use flat planes, since nothing in reality has zero thickness). Remove the volume effect from the material. Or use Corona 13, that has a fix for this (basically looking in two directions rather than one to establish whether the camera is inside a volume).

5
1. Check each image, there are options for how the view is displayed, including "camera default" or "which direction you walked here from". If the "camera default" is backward from what you expect, rotate the camera (180 degrees by the sound of it) in the scene to re-render, or there may be some option to set a fixed direction among the camera default and direction you walked here from settings. I usually go with "the direction you walked here from" since that makes sense from the perspective of walking around through the scene :) And then it doesn't matter what camera orientation was used in the scene (except for the first image that starts the virtual tour)

2. Labeling hotspots for automatic hotspot generation can be done by labeling the image filenames, so an image for the living room called "Living Room" will cause its hotspot to be called "Living Room" by default. I generally rename the images prior to uploading them (click the image name in the "upload to collaboration" dialog in the VFB), or you can rename the images once they are uploaded then re-run autohotspots and all connections to the living room image will be renamed "Living Room" (easier than editing each hotspot manually after doing the autohotspot generation).

Let me know if that answers the questions!

6
[C4D] I need help! / Re: Intel AI Denoiser
« on: 2025-06-30, 13:47:10 »
Seems to be true in my single test so far, at least for LightMix Multipass elements - even with the "Apply denoising" checkbox checked, the LightMix is not denoised with Intel, but is if NVIDIA or Corona denoising is selected.

7
Unfortunately, there are no plans to develop Corona for any other DCCs than the two currently supported - this is because it would cause a significant slowdown in Corona's development and updates for 3ds Max and Cinema 4D due to the dev hours that would have to be spent on a conversion, and that's something that would be counter-productive. Curious as to why you don't list V-Ray as a real alternative? Maybe there's some feedback that can be given to the V-Ray for Houdini team? https://chaosvray.ideas.aha.io/?project=VHOUDINI for suggestions! Or the Chaos forums for bugs. Thanks!

8
General CG Discussion / Re: disappointment with corona 13
« on: 2025-06-28, 00:24:20 »
All I want is normal production-ready crypto mattes in 2025. I have been waiting for them since 2018.

Can you explain in what way they are not production ready? They are just industry standard cryptomattes already. Now, it seems that Nuke (I think it was - one of the video editors anyway) uses some additional (not part of the actual cryptomatte) metadata and without that metadata, Nuke doesn't process it the way it would process things otherwise. Is this what you mean? Let us know so we can take a look into it :) But right now the cryptomatte from V-Ray and from Corona works the same in, e.g. Photoshop or Resolve.

PS or is it that it has to be saved to CXR, which then need renaming to EXR and the renaming step is what causes problems?

9
What would be incredibly useful - or essential really - is knowing your scattering settings. Can you share a scene (best done by opening a ticket, as keeps the scene between you and support, https://support.chaos.com/requests/new ), or at very least a screengrab of the settings. OFC the settings for a Scatter are too long to fit in one screen so that might take some work. You could also just strip a scene down to the scatter with some default objects, if you can't share the actual models or scene etc. for NDA reasons.

Given there are so many ways Scatter can be used (on splines, in areas, with masks, with height or angle limitations, in volumes, in clusters that can be set up in various ways, edited with the paint tools, etc. etc.) it would be important to know just how it is being used here. Thanks!

Oh, and example images showing the results from one machine and the results from another too, so could see in which way it's changing.

10
BTW, why do you want it, given that all the materials are now in Cosmos? Which is a genuine question, I am interested in why you want to use the Corona Mat Lib instead to access the same materials.

11
Bear in mind that the image size in the IR is determined by the size of the window, so that can be smaller than the output settings (often the case, where if you want an 8K final render, you don't want to wait that long for your IR and the smaller window size is better).

12
Great you tried it out, and great it fits your needs :) Thank you for the feedback (and I'll pass it along to the Cloud team). Enjoy using the Virtual Tours, and keep an eye on things coming from the Cloud team as there is more to come this year. Cheers!

13
Glad to hear you solved it - and I also wanted to say thank you for coming back and sharing what the solution was, as this can be a great help to others, and let's face it, it's pretty easy to not take the time to come back and report on the fix because you've just had to spend time figuring it all out and want to get back on with the important things like rendering and working on the project. So, big thanks!

14
This one was news to us too :) So not something that has been kept a secret, and really it has only come to light on the creation date of that video a week or so back. Following from that video, we may add some checkbox someplace that basically does "render to 2x resolution then downscale", leaving you as a user to reduce the passes / noise target as you see fit, and apply whichever denoiser you choose though preferably Intel. We are going to revisit the denoising UI, since it has grown from one to three options and in two places (IR and final), so it could use a bit of tidying up.

TBH I am still not convinced of setting either of the AI denoisers because a new user could load up Corona and press render... . and it doesn't work. I get that established users will go "Oh, looks like Intel hasn't updated to handle the new 60 series card that I am using, I guess I will wait for an OIDN update, meantime I'll swap to another denoiser", but for a new user, the whole "It just works out of the box" statement would seem like a lie and they'd be left very confused.

There's also the issue of "reset to defaults" being something that should fix ANY problem, and same thing again, if NVIDIA or Intel break their denoisers somehow at any time, then reset to defaults will just be resetting things to something that doesn't work.

You can of course set your own default scene that loads on startup of the DCC, and in that store the settings you want to use every time, all without us having to change what the Corona defaults are. And this is my preferred solution, as then the defaults are the things guaranteed to work, but you are free to create your own standard settings via a default startup scene - best of both worlds!

15
Can you share some examples? That is, a 12 render then same scene in 13, plus a screengrab of the material set up (or, a version of the scene, can even be stripped down to just a cube with the offending texture applied etc. so long as it shows the difference in 12 and 13).

Pages: [1] 2 3 ... 409