Author Topic: rendering on different resolution effects result  (Read 2595 times)

2013-12-02, 13:08:24

zeitgeist

  • Active Users
  • **
  • Posts: 17
    • View Profile
Hi everyone

Started my first project with corona renderer and came across a strange bug.
Rendering on different resolutions effects the final result.

The Image in the attachment shows the same rendering. I didn´t change any settings except the resolution in the Max Common Rollout.
(Images are rescaled for better comparison)

Somehow it seems to be connected to the bump map on the material.
I attached the scene file, so you can test for yourself.

Rendered with A5 on max 2014.

What i tried so far:
reduce bump value -> seems to lower the error
turning up the polygon count on the chair -> no effect
merge to new scene -> no effect


Thanks for the nice renderer btw. Really love it so far.


2013-12-02, 13:25:51
Reply #1

Ondra

  • Administrator
  • Active Users
  • *****
  • Posts: 9048
  • Turning coffee to features since 2009
    • View Profile
This is probably caused by different amount of filtering in both images - when you change resolution, the area of texture that spans single pixel changes, and therefore you can get different results. Glossy + bump is extremely sensitive to any changes, so it is probably causing it. You can try changing texture blur amount, you should get the same different results as when changing resolution
Rendering is magic.How to get minidumps for crashed/frozen 3ds Max | Sorry for short replies, brief responses = more time to develop Corona ;)

2013-12-02, 14:58:00
Reply #2

zeitgeist

  • Active Users
  • **
  • Posts: 17
    • View Profile
You´re right. I set the blur amount to 1,45 and it looks exactly like my previouse (low res) render.
Thanks for the help. I will post the project in the gallery in the next days.
Really pleased with the result so far.

2015-06-04, 11:46:48
Reply #3

Ludvik Koutny

  • VIP
  • Active Users
  • ***
  • Posts: 2557
  • Just another user
    • View Profile
    • My Portfolio
It's a known problem. I've logged in on mantis.

Marked as resolved but escalated to mantis.
« Last Edit: 2015-06-04, 11:56:42 by Rawalanche »