Interesting, with using all the default settings, I selected the Export XML button. The Console spawned with a blank screen. Should have waited longer, but after a few seconds, I selected the Render XML button. Console disappeared and rendered. This may happen only on the first render of the day.clintonman wrote: ↑14 Nov 2019, 08:24The image only renders to the selected render path.trueBlue wrote: ↑12 Nov 2019, 17:37The above is from the help file.Use Custom Temporary Directory - Path to the Custom Directory.
Directory for storing generated XML file and temporary YafaRay output image. Default working directory is the same as the output image directory. Use this option if you want to use a different directory from the final image output directory.
Use Custom XML Export file - Use the File browse dialog button for selecting custom XML file export location.
Use a custom filename and directory for the generated XML file. This is useful when generating multiple XML files for batch rendering or for rendering a previously generated XML file.
Export XML - Creates an XML file without rendering.
Render XML - Renders the Custom XML file or the last XML file that was generated.
Not really sure how this is suppose to work, so I will leave it up to you that it is working as expected.
If when using the above options, and an image is suppose to render to these paths, it does not work.
It dose seem to render to the Output Render File path though.
There is one glitch when checking 'Delete XML file after render', and using the Render XML button on second attempt. It will produce a handled error.
Maybe the help file can be amended?
ExportXMLFnSet is using System.SetBusyCursor(true); in your code.
I can confirm that this is not working as you have said previously.
I would suggest removing this just incase it may be causing any problems.
I have no idea why there would be a temporary image in the custom directory.
Use Custom XML Export is for directly rendering a preexisting xml file instead of the normal process of generation then rendering. I'm guessing the export xml is useful only for developers.
Can you explain the glitch more?
Are the steps:
Delete XML file after render
Render and get Error
Any way, the steps to test the glitch is with the:
Delete XML file after render 'checked'
Render XML -> will produce an error.
The glitch I think is the Delete XML file after render is tied to the selected render path. (1 of 3)
If the Delete XML file after render was isolated in the code when using the custom or temporary render paths, then the XML file would not be deleted.
Even with your explanation, I still do not really understand it's use or workflow.
As said, maybe the help file can be amended (with your help) about all of the above.