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

Pages: [1] 2 3 ... 27
General Discussion / Re: DR with backburner
« on: 2019-04-18, 15:34:25 »
Oh right thanks Tom, I'll give that a try.

General Discussion / DR with backburner
« on: 2019-04-18, 14:35:24 »
Am I right in thinking that its not possible to use DR with backburner, rendering a single image? You either have to use DR that includes the host workstation OR backburner with a single node rendering the image but you can still use your workstation?

Thanks for the info. I think it is likely that we will stick to CMs and just live with some issues in any extra large scenes which arent as common.

Thanks Dzintas. Yes I like the way we can have different display unit. Good that we can stick with mm there for habit.

For those that jump between M and CM do you run in to issues with real world texture sizes not scaling right with merged assets? CMs look to be working well in my initial tests but we are working on a masterplanning model that is a few city blocks and Metres visually help with the Z fighting no end!

Thanks guys, yes I was referring to system units.

Interesting. Well I might suggest we have a go at at least upping to CMs and give it a try going forward. I can see metres getting a bit frustrating, with a lot of 0.01 sort of measurements going in for me but CMs shouldnt need as many decimal points.

We currently use MM for our scene units in Max, largely as a crossover from traditional CAD drafting and architectural conventions in the metric world. But Maxes default is CM and every asset we buy seems to come as cm. We also sometimes get issues with drawings off the working plane - which perhaps we would get less of if we used CM? Also even in a medium sized scheme I get massive Z-fighting in my perspective view and I wonder if this is just because of the way Max handles small units in a bigger scene?

Anyway it would be interesting to hear what others have their units set to as I'm thinking maybe we should switch if people are getting less problems sticking with CMs.


Can't wait for this. Hopefully it will come soon.

Has any of this been looked at yet? Ive found the same issues but Im not sure if im doing something wrong. Thanks

Bump on this one. It would be really handy if possible.

I see what your saying Juraj, yes that must bake it down. This is what PSD manager does natively which is odd as it must be tampering with the image. I just wish there was PSD export in Max that behaves the same as C4D, which seems more advanced.

Below is a crop of an image I rendered last night on one of our final C4D projects. On the left is the base render and on the right is the base + reflection pass (add). This is at 100% so I would just brush in highlights where needed at lower opacities as it is overblown in parts. But I find it a really handy tool to enhance bits here and there artistically even if its not physically correct. I just need to find a way to get Max to write the tiffs with half float and for PS to recognise it as 16bit like C4D does.

Maybe we should all switch to Affinity! I might dust it off.

EDIT: crap just seen your example image Juraj. That is annoying! More experimentation required then! Thanks for all your help

More good info, thanks Njen. There are a lot of people with a lot more knowledge than me!

I'm going to give the 1.0 gamma output setting with the 2.2 gamma correction in PS a try on a couple of projects as I really want to recreate that type of subtlety in the passes. I dont rebuild images from scratch but I do use them to boost bits here and there.

Do you know if there will be any image degredation by adding the gamma offset as an adjustment layer from 1 to 2.2 in PS?


Ha yes sorry for the OT. Just thought I should set the record straight checking on indigos website again and it looks like the main office is in New Zealand but their second office is in Newcastle. I'd love to bump in to them in the pub I could chat about all this stuff for days!

Hey peeps,

I've been using both throughout the years and I can definitely say there are pros and cons to each. (...) When I switched to 3ds Max it was a whole different experience. The interactivity is a lot more like what you get in Octane in C4D where the IPR updates flawlessly.(...)
(...) I can't tell you how helpful that was for my professional growth as you can really see where the drawbacks of each software are at.


Off-Topic comment :
Talking about Indigo, this piece of science / tech and software is mindblowing. There is true geniuses behind it and I wish its development was being pushed further and wish them the best. I know it's not easy for this small team to implement the most complex algorithms and integrate them in Max/C4D. They already made some impressive exploits.

Funny thing about indigo is its developed about 200 metres from my office in newcastle, UK! I gave the demo a go last year and it is very well integrated in C4D thats for sure. I just struggled with some of the terminology, it seemed very scientific, which no doubt every render engine is under the hood but Corona does a fantastic job of hiding all the tech for idiots like me and at the same time producing the best results, quickly. I was already smitten by Corona so I didnt perhaps give it enough of a chance as I knew Corona was so great and has become and arch viz staple. I feel a bit bad as I should be supporting local tech and the indigo demo vid looks great, so I wish them well in a tough market.

OK so just installed PSD manager and output a 16bit PSD. Interesting result. It has the file as sRGB and it must make the gamma 1 as it saves out and then adds a 2.2 gamma LUT at the top of the PS stack. This gives the nice tonal range I was getting from native C4D PSD 16bit output which PS reads as linear in its colour profile. It also matches the other 32bit tests from just now. I realise that the LUT is just an exposure adjustment layer setting the gamma to 2.2 so I've done that and it works.

So as I think Romullus pointed out you can do the gamma 1 output in MAX for saving out the 16bit TIFF. So Ive tried this along with the exposure adjustment layer fix in PS and it gives the same result which is great, if a little disconcerting that it seems like a bit of an unorthodox step and going against the 'recommended' setting.

My only real concern is, am I degrading my image by adjusting the gamma so severely or is the gamma in this case just a straight visual conversion / reassignment? so its not actually boosting the pixels artificially like if I was to add an aggressive curves layer, leading to banding and image degredation? 

Very much a geek chat this one!

Yes just done another crude test this time out of max with 16bit half float exr and opened in PS with EXR-IO.

The ball on the left is the converted down 16bit version with reflection pass set to screen. On the right is the 32bit original set to add. The ball on the right gives better tonal range with less washing out. I also ran a test from C4D outputting 32bit and 16bit PSD files and visually they looked the same as the 32bit exr version setting the ref to add. i.e. more natural tonal range and less washed out than the sRGB variants.

I've downloaded the PSD manager plugin so will give that a spin.

Pages: [1] 2 3 ... 27