Been a while.

[Mike Amos]

Mike-Amos View too.

Kitchen area, note missing colour/items 2d export versus render.

[Mike Amos]

Mike-Amos

May have needed a restart which cures some content glitches.

[Rich O Brien]

@Mike-Amos said:

Kitchen area, note missing colour/items 2d export versus render.

Is the container(group/component) painted or the raw geometry? What does Entity Info say regards the selected container?

[Mike Amos]

May have needed a restart which cures some content glitches.

[Mike Amos]

Mike-Amos

I know, inconsistent.

[pixelcruncher]

That’s definitely also a bug with software. I’m away this week so the next release will come a bit later, but it I will try to fix this there.

[Mike Amos]

You are getting there, no worries. Hoping you have a decent break mate.

[Mike Amos]

OK, I understand the plague that is removing Rayscaper lights.
"Cleanup", is removing the Rayscaper lights.
Frustrating but at least I got something out of today.

[Mike Amos]

Post artificial light death, I have this.

[Mike Amos]

OK, auto exposure OFF (It will get there) and set at 7.5. I also fixed the blind which was rather abused. I have confirmed to my own satisfaction that when items and finishes/colours go missing, a restart of Rayscaper will fix the problem. Also, do not use cleanup for the whole model, elements in turn. Otherwise you will have your Rayscaper lights deleted.

[Rich O Brien]

Your glass is not right. You can see the distortion due to IOR.

Can you screenshot your glass material setup in the Rayscaper dialog?

[Rich O Brien]

Look here how the refraction distorts with Thin unchecked.

[Mike Amos]

I cannot do so but it was definitely selected as 'thin' AFIK. Normal habit is to do so.

No render proceeding ATM due to this report.....

[Mike Amos]

Repeated more than half a dozen times, same subject render.

[Mike Amos]

Rayscaper has reverted to cpu rendering method again.

[Mike Amos]

Stuff is expected with a beta release program, not the end of the world in any way.

I have Maxwell render running the scene so the model is not at fault.

I have had some time to finesse the layout and make sure stuff just 'fits' and is doable.

[pixelcruncher]

Hey Mike,

I'm sorry to hear you're running into these issues with Rayscaper. Would you mind sending me this scene so I can have a look?

Summarizing your woes:

• Auto-exposure is behaving strangely. Mike, I'm still not sure what you mean by this.
• Geometry does not appear in the renders.
• Viewport shows CPU, while you have enabled GPU rendering.
• Rendering fails.

I think it's easier if you send me the scene and, preferably, the logs when such a render failure occurs (https://www.rayscaper.com/getting-help/report-a-bug/#1-export-the-log-files), so I can try to reproduce/fix these problems.

Thanks,
Thomas

[Mike Amos]

@pixelcruncher said:

Hey Mike,

I'm sorry to hear you're running into these issues with Rayscaper. Would you mind sending me this scene so I can have a look?

Summarizing your woes:

• Auto-exposure is behaving strangely. Mike, I'm still not sure what you mean by this.

************Auto exposure doing funky things is a fraction where the interior and exterior are mismatched.

The exterior tends towards overexposure when the interior is properly or slightly underexposed**********.**

• Geometry does not appear in the renders.

Sometimes geometry just fails to export to Rayscaper, that or it is deleted. Restart can fix this sometimes.

• Viewport shows CPU, while you have enabled GPU rendering.

Simples, Sometimes the render window shows CPU rendering with my selecting it.

• Rendering fails.

Mostly when the CPU method is self appointed, nothing in the render window at all.

I think it's easier if you send me the scene and, preferably, the logs when such a render failure occurs (https://www.rayscaper.com/getting-help/report-a-bug/#1-export-the-log-files), so I can try to reproduce/fix these problems.

Thanks,
Thomas