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

Pages: 1 [2] 3 4 ... 8
16
[Max] I need help! / Re: Saving colormapped EXR 32bit
« on: 2017-05-13, 10:22:10 »
Thanks for the tip, I came across the same problem once. Good to know there's an easy fix!

17
[Max] I need help! / Re: cVFB Behavior during IR, Options?
« on: 2017-05-11, 16:24:27 »
+1 for this. I also dont like the window expanding, I prefer the old behaviour.

18
Hi everyone,

I'm pretty sure i haven't touched anything in Photoshop lately, but for some reason I'm finding a noticeable color discrepancy between my VFB and Photoshop. It probably is PS related, but I wanted to seek for help here, as you all probably use the same workflow I use.

I've been quite happy with the new tonemapping capabilities of the framebuffer, so I do most of it inside Max, then export to 16bit TIFF to do some touchups in PS, collapse to 8bit and send to client. Today, I just noticed a major color shift from the Corona VFB (same as in CIE) to PS, the only remedy is showing Proof Colors (set to Monitor), but after saving a copy the shift is back. I'm pretty sure I've havent touched anything in PS, and this behaviour didn't occur before 1.6 (??)

I'm pretty bad with color profiles,and most info I can find is related to printing, etc.. So any tips on setting up a correct workflow are more than welcome (Max> Tonemapping> touchup in PS> export for client). BTW, my monitors are correctly calibrated using DisplayCAL, and Ididn't notice this behaviour before. Thanks in advance.

19
I believe the 2d pan/zoom on max viewport and the VFB doesn't match. As soon as I "zoom in" on the viewport while interactive rendering is active, I see a different area of the scene on the VFB and the difference increases as I keep zooming in on the viewport.
Anyone else noticed this?

+1
+1

20
DR is very buggy. I'm finding incorrect status reports and failure to start on nodes arbitrarily with RC6. Its a scene that used to DR fine with 1.5, no special stuff, just geometry and textures, and some displacement. No internet use on any machine while launching renders, maps have correct paths... :(

21
Gallery / Re: Skanna Kivi
« on: 2017-02-14, 16:34:19 »
Congratulations, I really like it!

22
Hi all,

I'm trying to obtain a single element I forgot to add during the main render. I need the CShading RawComponent set to Reflect element, and i'm trying to render it with "Render only masks" activated, but all I get is a solid black image. Is this behaviour correct?

23
Well... Then I'm in big trouble. :(

Lo-res previews sent to client have already been approved, and they all have bloom and glare. Hi-res finals need to be rendered in the nodes due to memory and need of the main comp to keep working. Deadline is way before the release of 1.6.

Going to have to buy a temporary Fairsaas to get out of this one... :(

24
Hi guys,

I've been working on this and I'm starting to get the grip of it. Here are a few remarks:

- Maru's system: The big drawback of lowering local computer thread usage and letting the nodes do the hard work, has the big disadvantage of having the scene still loaded on the main computer, thus allocating the required RAM memory. This is quite problematic, since many of my scenes take most of the available RAM and make it quite impossible to keep working on another scene.

- TomG's system: Backburner seems like the best way to deal with this. BUT I loose the availability of the Corona Framebuffer and all the convenient options it has for post production (Bloom, glare, etc...). Rendered image is saved as an EXR and that's about it. I've tried saving as CEXR, but I get and "Error creating file output" message... Any way to deal with this? Would CEXR make it possible to load the image back in the framebuffer?

Thx for your help.

EDIT:
Trying to save CEXR with backburner just won't do anything. Job will be stopped and nothing will be rendered. I've seen a fix for batch rendered images (changing the extension after render is done) but it won't work with backburner since it doesn't render anything at all.

25
TomG: I'm not very familiar with Backburner, might have to learn to use it if push comes to shove... Did you find any problems with rendernode licenses (acting as individual workstations) using this Backburner method?

Maru: Your idea seems easy, but even if the threads are lowered, scene is still loaded in RAM memory... That might be a big problem.

Any idea of when the new DR might be available?

26
Hi all,

Is there any way I can send scenes to render ONLY on my slave PCs (nodes) without clogging my main workstation? I'm currently working on many different projects and need to be developing new scenes while rendering others. I have a BOX license... Any tips?

Might just have overlooked some setting, but I can't seem to find the way for such an easy task.

Thanks!

27
[Max] I need help! / Re: LUT Files
« on: 2016-07-29, 16:23:44 »
Very useful, thanks!

28
Yeah Maru, just rendered the elements, I love that feature.

Long time ago I learned (the hard way) rendering the elements individually helps with RAM usage a lot! Glad we have that feature.

BTW, I've had this same problem repeated a few times now, but it seems to come and go randomly. Once I try to recreate it it's usually gone... But never had it while rendering elements individually, so at least I know the safe option.

If it persists and I can recreate it i'll send in the scene. Thx.

29
Thanks guys,

Dionysios.TS: I'm on 2014 and only started seeing this problem since updating to Corona 1.4

Maru: I'm re-rendering one of the scenes to replicate the problem. If it happens again I'll be sending the scene for debugging (looks like it's not happening anymore)

So I guess I'm going to have to render all the masks again, dammit... :(

30
Hi guys

I've just discovered something quite odd. I ran a bunch of renders and saved them in the usual manner. 32bit EXR with all render elements (Cmasking_ID and CGeometry_Zdepth) added automatically as layers to the resulting EXR. I've always worked this way and it's the first time i see the following:

When I reopen the EXRs in Photoshop the MatID pass is textured, instead of being bold and bright colours as usual. There is quite a bit of light/shadow (or albedo?) information in the masks, which makes it impossible to use reliably. I'm attaching an example.

Can anybody help me out? I've re-rendered only the elements in one of the images and saved it straight to TIFF from the VFB and it came out as it should. What went wrong with the EXRs?

Pages: 1 [2] 3 4 ... 8