Author Topic: 1.2 -> 1.3 proxy rendering discrepency  (Read 4672 times)

2015-11-03, 18:52:27

elindell

  • Active Users
  • **
  • Posts: 55
    • View Profile
Hello, just downloaded and installed 1.3 this morning. My first test is to go back to a render I just worked on and see if I noticed anything odd or, more hopefully, faster noise free render. Unfortunately I found couple issues with 1.3 this morning.

1st issue is that when I opened a scene and hit render I get black frame buffer, its like nothing is in the scene. After a bit of mucking about looking to see if there were any new settings I need to check I just opened a blank file and merged everything. Rendered fine, so something is fishy about rendering old scenes unfortunately I didn't have time to isolated this down to easy to reproduce steps but maybe I can in the future.

2nd issue is that when I merged my old scene and hit render I am able to compare it to a render I did a few days ago with 1.2 and immediately noticed that the reflections were way off on certain objects. In my scene I have several thousand chairs so naturally I have to use cproxy, I was noticing that the reflection on these objects were behaving differently. I converted the proxy's to a mesh and after rendering again they appear like they did in 1.2. Looks like a issue with proxies so I remade the chairs into proxies again and this is where I noticed you guys changed the extension format for your proxies, again. So I had a .cmesh type proxy, which I guess wasn't even up to date with 1.2, oops. I converted the old proxies to new .cgeo and it solved my issues with reflection.

So not sure if this is a bug but it looks like something is wrong with the old .cmesh files, just an FYI for the developers but also anyone else who comes across weird issues with proxies make sure you are up to date with those.

I included the cmesh and cgeo proxy files in a zip file

direct mesh render (correct)


cmesh proxy render (incorrect)

2015-11-04, 11:15:12
Reply #1

hubrobin

  • Active Users
  • **
  • Posts: 61
  • Light transport ninja
    • View Profile
Hi,
thanks for taking the time to conduct the report!

I have just had a look at it, but I couldn't spot any difference between cmesh and cgeo proxy. What I did notice is that in both cases normals on backrest are inverted. Couldn't find any place in legacy cmesh proxy loader that could be causing this. Do you by any chance have the object from which you have created the cmesh proxy? Would it be possible to share the original scene you couldn't render?

Thanks,
Robin

2015-11-04, 13:18:44
Reply #2

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 13702
  • Marcin
    • View Profile
Just a random idea as we do not have the material - did you have anisotropy enabled?
Marcin Miodek | chaos-corona.com
3D Support Team Lead - Corona | contact us

2015-11-04, 18:07:29
Reply #3

elindell

  • Active Users
  • **
  • Posts: 55
    • View Profile
Hi,
thanks for taking the time to conduct the report!

I have just had a look at it, but I couldn't spot any difference between cmesh and cgeo proxy. What I did notice is that in both cases normals on backrest are inverted. Couldn't find any place in legacy cmesh proxy loader that could be causing this. Do you by any chance have the object from which you have created the cmesh proxy? Would it be possible to share the original scene you couldn't render?

Thanks,
Robin

Thank you Robin, here you go, hopefully this helps you see what I'm talking about, also found a setting that may help you pinpoint it.  In the max file are 4 layers of chairs,

1. corona proxy with hotelchair.cmesh loaded with 'keep in memory' checked
2. corona proxy with hotelchair.cmesh loaded with 'keep in memory' UNchecked
3. corona proxy with hotelchair.cgeo loaded ('keep in memory' didn't change anything)
4. the proxies converted to a mesh.

the corona proxy with cmesh loaded and "keep in memory" checked is the one that renders differently than the rest, unchecking that option and the cmesh proxy renders as expected.

Maru they all use same material and didn't see any anisotropy settings enabled so doubt its that, thanks though.

2015-11-12, 18:31:56
Reply #4

Ondra

  • Administrator
  • Active Users
  • *****
  • Posts: 9048
  • Turning coffee to features since 2009
    • View Profile
fixed in daily builds
Rendering is magic.How to get minidumps for crashed/frozen 3ds Max | Sorry for short replies, brief responses = more time to develop Corona ;)