'Render on Save' images are low resolution

[byTomm]

Hello,

I render a picture 4000px wide, dropped the view in the 'render on save' area.

Now every time I save my document, the automated renders are only 1333px wide.

Is there an option to keep the same file size?

This auto render is a great feature, hope there is a button I missed!

Looking forward to your answers,

Tomm

[lucasproko]

Hey @byTomm,

This is a great question. Currently, we do not have the experience built in-product to allow this functionality. The problem arises that if you render a 4,000 x 4,000 pixel image, it costs 16 Cloud Credits. Thus, if you dragged that image into the Render on Save area, then every time you saved the file, we would need to extract 16 cloud credits from your account. Given that many Saves occur during small modeling changes, you would end up being charged for a number of images that you may not actually want. So for now, we limit all subsequent renderings to a 1 CC cost. 

That being said, we are evaluating what we can do in this area because it would be ideal to allow users to render downstream images in the original resolution. This is where I'm going to turn the question on you - what would be your expectation for this functionality? Would you want to be charged silently? Would you like to have a separate dialog box pop up on all future saves for each view asking whether you'd like to render it? Would you prefer having a single dialog box on every Save that has a separate row in it for each view? We have a number of other ideas, but I'd love to hear your thoughts.

Thanks!

[es412]

Why cant these images be rendered locally if the original is?

[byTomm]

Dear Lucas,

I realized I didn't reply on your message, apologize.

I think Elliot83, posted the same question in reply to your message a I got.

I render locally, at this point I don't want to pay extra for cloud rendering, but that 'Render on Safe' feature is so great I hoped it was available for local renders too.

Having multiple views that render in high quality, for output for my clients, on one single 'save' command would be great.

Looking forward, Tomm

[Anonymous]

hello , i was searching for same issue about the saved renders , and i'm convinced with your answer it make sense .

but i wish could save the camera location so i can render the object in the exactly same camera position in different materials ( for presentation purposes ).. that's why i use the saved renders but i dont like the quality of the basic render .

thanks

yousef 

[laughingcreek]

have you tried creating a new "named view"?

[Anonymous]

Saving the camera position is also a huge issue for me. I've had success using the animation workspace to set my camera views. I can then select the view I want, switch to render and as long as my lens settings are the same as original everything lines up perfectly. My main issue with that is I have to plan this out ahead of time and I can't test the lens in the animation workspace.

[Anonymous]

Also,

Please just allow us to change the resolution for the render on save in the settings somewhere and default this to local. The fact that it would default to something that cost real world money is absurd. Customer should always be asked before spending their money. This is theft in my opinion. Also, pretty lame that you can't just open up the image and change the render setting once the low res is rendered. Well, you can, let me re-state that, that you can't change the setting and render locally! This is designed to force customers into purchasing your tokens that you've designed ways to steal back unknowingly simply through saving the file. 

[jordan_crt]

Has this issue been resolved to be able to change the resolution of "RENDER ON SAVE" images which are locally rendered?

Not sure why it defaults to such a low resolution, is there a place to change this default if it can't be changed on a per-document basis?

Workarounds exist, but it would be nice not to have to queue so much up for a revision!

Thanks