Messages

1

Hardware / Re: Threadripper Builds

« on: 2019-07-09, 00:54:09 »

Does anyone want to buy my dual Xeon 2696 v3 workstation...? :)

I'm also waiting for the zen2 Threadrippers. Hopefully, single core performance will be on par with the 3900X (~205CB score) and multicore will be double that of my current dual Xeon workstation (4400CB). Like nkilar, I guess I'll wait till the end of the year instead of buying the 3900X or 3950X.

Generally speaking, do you guys think going from a 142 single core cinebench score (which is what I get on my dual Xeon workstation) to a 205 will be noticeable in overall 3ds max "snappiness"?

2

Corona Goodies! - User contributions / Re: CoronaCam Lister

« on: 2019-06-24, 22:46:34 »

Thank you for your effort Christa!

I don't know if your script already has this feature but if I may suggest one it would be the ability to copy and paste properties between cameras, just like PhysicalCamLister (VrayCamLister) from kstudio has:



Note: Copy and paste are the small rectangles on the left. If you right click on them you can choose to copy and/or paste the respective camera settings.

3

Corona Goodies! - User contributions / Re: CoronaCam Lister

« on: 2019-06-22, 12:27:14 »

Hello Christa! Thank you for the screen record. That helps to clarify and I'm afraid the script isn't working on Max 2019. Nor "OK" or "CANCEL" button work. Also, in your video it seems it isn't possible to change tonemapping, only post processing, is that right?

4

Corona Goodies! - User contributions / Re: CoronaCam Lister

« on: 2019-06-21, 12:35:32 »

Hello Christa,

Well, for me nothing happens with the script. The dialog appears but it doesn't allow me to click "OK" or "CANCEL" regardless of what cameras are selected. Only the close window ("X") works. How is it supposed to work? Thanks! ;)

5

Corona Goodies! - User contributions / Re: CoronaCam Lister

« on: 2019-06-20, 17:34:51 »

Hello again Christa! Haven't tested the script as soon as I thanked you in my previous post but I finally had the opportunity to do it and I only get the following dialog.



It doesn't allow me to choose any camera even if I click ok. Suffix and prefix also won't let me choose anything. The only thing working is if I click cancel :)

Thanks!

6

Feature requests / Re: The most wanted feature?

« on: 2019-06-20, 17:17:56 »

As hybrid rendering takes the lead will it ever be considered given the developer's principle of Corona being a CPU only renderer? I suppose it is the most challenging "feature"? If so, would it work like v-ray in the sense that we have to first select GPU renderer and then select CPU to help the GPU or would it work the other way around?

7

Feature requests / V-Ray IPR and Corona IR

« on: 2019-06-15, 13:19:08 »

Hey guys,

Recently tried v-ray 4.20 and although it still isn't any faster on production rendering than Corona (I'm getting Corona being around 70-100% faster), their approach to IPR/IR seems to be more "fluid" than Corona. Can't quite put my finger on it but I suspect the following:

1) Initial image feedback seems faster, even if it is more "degrading" initially. I quite like that approach. Is it possible to replicate it for Corona?
2) Window resolution is much more flexible, allowing us to set any window size we like. I'm aware this has been an onward discussion for a long time but this combined with a faster visual response would GREATLY improve usability IMHO.
3) Being able to make several render regions without having to press SHIFT also seems to be more user-friendly in giving that impression of a fast response.

Don't get me wrong, Corona IR is very fast once everything is computed. It's just that initial response when V-Ray IPR gives you a degraded image almost instantly when Corona IR stays black initially for a couple of seconds.

Also, apart from all the IR suggestions, when making a render region in production is "Computing GI" necessary to be processed for the whole image? I remember a Corona team member responding about this issue and saying there was no way around this. I think V-Ray works without having to process all image data when region rendering although I'm not quite sure about that.

8

Corona Goodies! - User contributions / Re: CoronaCam Lister

« on: 2019-06-13, 14:11:20 »

Thank you Christa! ;)

9

Corona Goodies! - User contributions / Re: CoronaCam Lister

« on: 2019-06-12, 12:27:58 »

Thank you for the script Christa! I get a maxscript error as soon as I drag the script into the max viewport. Running Max 2019 + Corona 4 (tested on v3 and the same error appears). What could it be?

10

Feature requests / Re: Clipping warning in VFB

« on: 2019-06-12, 11:31:25 »

Yes, albedo doesn't cut it in this case because it only warns about input overbrightness. I've since been using romullus hack but a proper clipping tool inside VFB would be very useful.

11

I need help / Re: Custom aperture maps

« on: 2019-06-07, 01:05:54 »

I was actually at that very same page right now :) Thanks for chipping in mh!

I suppose there's no optimal resolution for these kinds of maps since these specific ones are only 210x210px. Very small resolutions can be used for them regardless of the render output size?

12

I need help / Custom aperture maps

« on: 2019-06-07, 00:07:32 »

Saw this image the other day on a facebook group and I was wondering if someone knows where can I find such custom aperture maps? Paid or non-paid.

I remember that the highlighted obstacle map was included in the old Maxwell Render installation but that's about it.

13

Feature requests / Re: Procedural lens effects

« on: 2019-06-06, 23:59:49 »

Very cool lens effects !

Dalton, who is the author of that music?
Very nice piece!

No idea. Maybe Shazam will help you out?

14

Feature requests / Procedural lens effects

« on: 2019-06-06, 01:49:35 »

As per the new v-ray release :)

15

Resolved feature requests / Re: Corona Camera Lister

« on: 2019-06-05, 18:19:36 »

Reviving this topic: do you guys know any camera lister script for 3ds max? I tried http://www.scriptspot.com/3ds-max/scripts/camera-lister but keep getting cldata.dat error.