OK, I see it. It doesn't hurt anything but I will alter the install to remove those lines.trueBlue wrote: ↑14 Jul 2018, 15:39 In the present released Update 4 reset.js file these 2 lines exist:RC-13 Does not remove these 2 linesCode: Select all
RsFileIO.LoadObject( rosDir + "\\Scripts\\preobjects\\Yafaray Folder.RsObj", "/"); RsFileIO.LoadObject( rosDir + '\\Scripts\\clintonobjects\\ReloadCustomScripts.RsObj', "/Scripts");
So as I understand it, this process is still being run twice!
I can remove these lines in the upcoming release but, for backwards compatibility I would suggest that you address this with your installation script.
Yafaray4tS v0.9.0
- clintonman
- Captain
- Posts: 5432
- Joined: 21 May 2009, 21:08
- Type the number ten into the box: 0
- Location: California
- Contact:
Re: Yafaray4tS v0.9.0
Re: Yafaray4tS v0.9.0
Tested again.clintonman wrote: ↑14 Jul 2018, 16:11Is this 1 issue or 2 issues?
The error comes from disable internal viewer?
optdetector is an internal display, so it won't work if internal display is disabled
I am not getting an error this time using Rosetta icons.
If I enable Internal Display Viewer it works.
If I disable Internal Display Viewer it does not work.
New - If I use Rosetta Render Object nothing renders nor does Render to File if checked.
YafaRay Render icons work as expected
All of YafaRay4tS - Render buttons do not honor Use Render to File if checked
- clintonman
- Captain
- Posts: 5432
- Joined: 21 May 2009, 21:08
- Type the number ten into the box: 0
- Location: California
- Contact:
Re: Yafaray4tS v0.9.0
The YafaRay4tS node render buttons are not set to use the render to file dialog. Only the toolbar buttons have that option.
Re: Yafaray4tS v0.9.0
Got that. Crossed post!
Shouldn't the Render buttons honor that though?
Great work on the Render Area!
Well except for the panel editing.
Not so sure of the value or use of exposing the Render Area attributes though.
Also suggest that you change the Render to File's Render Scene button to Render.
It is miss leading when you use the different Render icons and that is the way tS Render to File is.
Shouldn't the Render buttons honor that though?
Great work on the Render Area!
Well except for the panel editing.
Not so sure of the value or use of exposing the Render Area attributes though.
Also suggest that you change the Render to File's Render Scene button to Render.
It is miss leading when you use the different Render icons and that is the way tS Render to File is.
- clintonman
- Captain
- Posts: 5432
- Joined: 21 May 2009, 21:08
- Type the number ten into the box: 0
- Location: California
- Contact:
Re: Yafaray4tS v0.9.0
Not seeing this. Any steps to reproduce the problem?
Re: Yafaray4tS v0.9.0
Think I found out what's up with the zero bytes issue
- clintonman
- Captain
- Posts: 5432
- Joined: 21 May 2009, 21:08
- Type the number ten into the box: 0
- Location: California
- Contact:
Re: Yafaray4tS v0.9.0
Nope.
will change
- clintonman
- Captain
- Posts: 5432
- Joined: 21 May 2009, 21:08
- Type the number ten into the box: 0
- Location: California
- Contact:
Re: Yafaray4tS v0.9.0
I can reproduce by setting photon mapping as the lighting method and reducing the photon counts to 5.
Now need to figure your xml file permissions problem.
Re: Yafaray4tS v0.9.0
It is the Glass material (default settings) that is causing that error.
I repainted with Shiny Diffuse and now my image has some bytes
Also the xml file issue is not a problem now
I repainted with Shiny Diffuse and now my image has some bytes
Also the xml file issue is not a problem now
- clintonman
- Captain
- Posts: 5432
- Joined: 21 May 2009, 21:08
- Type the number ten into the box: 0
- Location: California
- Contact:
Re: Yafaray4tS v0.9.0
OK glad you figured it out.
The install not showing Setup aspect is solved
The renaming the Render Scene button is easy
Install removes those 2 redundant lines from the reset.js file
There is no way to get error messages from YafaRay renderer, so no way to automatically solve issues like the "not enough photons to render" issue.
May want to add a note to documentation that some errors can only be seen in the windows console.