Chaos Corona Forum

Chaos Corona for 3ds Max => [Max] Bug Reporting => [Max] Resolved Bugs => Topic started by: Frood on 2018-10-22, 12:38:36

Title: Wrong/old VFB data written to output when using native 3dsMax region
Post by: Frood on 2018-10-22, 12:38:36

Steps To Reproduce:

• Take your favourite teapot scene
• Set ouput to <somewhere>\<somefile>.jpg
• Create a native max region
• Render, look at ouput file
• Move region to another part of the frame
• Render, look at output file

The previously rendered VFB area(s) are written to the output file. Should at least not happen when "Clear VFB between renders" is activated. Even manually clearing the VFB does not correct this. Additionally there should never be a discrepancy between VFB and output after rendering. A save from VFB seems to write correct data.



Good Luck



Max 2016 + 2018 | Corona 2 + v3 dailies + v3 RC1 | Win 10

Title: Re: Wrong/old VFB data written to output when using native 3dsMax region
Post by: maru on 2018-11-09, 10:31:34

Confirmed. We will take care of this.
id=290062937

Title: Re: Wrong/old VFB data written to output when using native 3dsMax region
Post by: maru on 2018-11-26, 11:03:43

We checked how this works in V-Ray.
In V-Ray if we don't clear the framebuffer, it keeps both regions (both in the VFB and in the saved image). If we clear the framebuffer, only the latest region is shown/saved.
This is already fixed in Corona internally, so that it behaves the same as V-Ray. The fix will be included in the upcoming versions.