United3dArtists Archive

clintonman · Post by **clintonman** » 27 Oct 2019, 22:45

Started putting together some notes for model view processing and converting lightworks scenes.
http://clintons3d.com/plugins/truespace ... faray.html

trueBlue · Post by **trueBlue** » 28 Oct 2019, 01:49

Might want to change this a little bit.

Use the Backup button before opening a Model view to prevent item name changes, movement, material changes and camera and light attribute changes caused by Model view processes.

Backup does not really prevent the above changes.
There is no mention of the Restore button.
Add another step?
Switch the main view to Workspace, select the Restore button, and close Protect Workspace before closing tS?
Maybe mention that Workspace's synchronization with Model does not work in trueSpace7.61 Beta 8
This could be why Model Mesh Processing makes tS unstable?

You do not mention that Model Processing needs to be checked when using Model Mesh Processing, if that is true.

clintonman · Post by **clintonman** » 28 Oct 2019, 16:21

trueBlue wrote: 28 Oct 2019, 01:49 ...
Maybe mention that Workspace's synchronization with Model does not work in trueSpace7.61 Beta 8
This could be why Model Mesh Processing makes tS unstable?
...

Can you give more details about this?
Workspace's synchronization does not work?
Makes Model Mesh Processing tS unstable?

changed wording a bit and mentioned Restore button and model processing in the special mesh section

trueBlue · Post by **trueBlue** » 28 Oct 2019, 17:13

Just my theory, that the lack of synchronization may be the cause of the instability. I posted about an error I received previously with your Hello World scene.

clintonman · Post by **clintonman** » 29 Oct 2019, 06:05

Started translating the help file to the web.

http://clintons3d.com/plugins/truespace ... /About.htm

currently requires javascript to see the side bar navigation

Edit:
added links to the official yafaray docs and some render theory tutorial links

clintonman · Post by **clintonman** » 03 Nov 2019, 16:02

Changes to the animation help

Model Processing - remove step 7
Don't get crashes when only using Model processing so no need to exit trueSpace

Model Mesh Processing - rearrange steps to exit trueSpace sooner
5.) When the render has completed, Exit trueSpace
6.) Open trueSpace
7.) Switch the main view to Workspace
8.) Select the Restore button

from yafaray page on my site fixed/changed
"exit trueSpace if Model Processing was active" to "exit trueSpace if Model Mesh Processing was active"
added link from yafaray page to the online help manual

trueBlue · Post by **trueBlue** » 03 Nov 2019, 17:41

I will correct this info.
Are you okay with the additon of the YafaRay4tS Scene Utilities icon in the YafaRay4tS toolbar?
If so I was going to add info to the complied help file's YafaRay4tS User Interface including info on it's use.

The reason I added it is because I downloaded the YafaRay4tS scene from this link:
https://web.archive.org/web/20160319000 ... nstall.zip
Warning, if you do and load this scene it will overwrite the toolbar (maybe other things too) and you will have to reinstall!!!

Since removing the YafaRay4tS Scene Utilities from the setup library there was no way you could update the scene.
There was one issue with the YafaRay Light Material(s) not updating to the new version.

clintonman · Post by **clintonman** » 03 Nov 2019, 18:42

trueBlue wrote: 03 Nov 2019, 17:41 I will correct this info.
Are you okay with the additon of the YafaRay4tS Scene Utilities icon in the YafaRay4tS toolbar?
If so I was going to add info to the complied help file's YafaRay4tS User Interface including info on it's use.

The reason I added it is because I downloaded the YafaRay4tS scene from this link:
https://web.archive.org/web/20160319000 ... nstall.zip
Warning, if you do and load this scene it will overwrite the toolbar (maybe other things too) and you will have to reinstall!!!

Since removing the YafaRay4tS Scene Utilities from the setup library there was no way you could update the scene.
There was one issue with the YafaRay Light Material(s) not updating to the new version.

Sounds good to me.

trueBlue · Post by **trueBlue** » 03 Nov 2019, 22:03

Been looking at a bunch of Model scn python scripts today.
Discovered you can open a Camera view from script, create objects, among several other interesting things.
Think I may have found a promising solution to the Model Mesh Processing without crashing trueSpace.
Instead of Assigning your script to the Scene, I Assigned it to the object that has the model animation.
In all my test including rendering in all 4 views in the 4View layout, I have had no crashes.
This is without removing the python script, switching back and forth from Workspace to Model, closing and reopening the same scene. Granted this is a small animation but just maybe it may be worth testing.

clintonman · Post by **clintonman** » 03 Nov 2019, 22:24

trueBlue wrote: 03 Nov 2019, 22:03 Been looking at a bunch of Model scn python scripts today.
Discovered you can open a Camera view from script, create objects, among several other interesting things.
Think I may have found a promising solution to the Model Mesh Processing without crashing trueSpace.
Instead of Assigning your script to the Scene, I Assigned it to the object that has the model animation.
In all my test including rendering in all 4 views in the 4View layout, I have had no crashes.
This is without removing the python script, switching back and forth from Workspace to Model, closing and reopening the same scene. Granted this is a small animation but just maybe it may be worth testing.
tempsnip.png

Niiiiccce!

Verified, no crash if the python script is assigned to a scene item instead of the scene. Just have to update the instructions and warning popups.

trueBlue · Post by **trueBlue** » 03 Nov 2019, 22:30

If it is not to much work maybe you could create the ms_flags_object from the python script and then the user assigns the script to it.
That way when it is deleted at the end of the animation, the assigned script goes with it.

Edit: On second thought instead of creating the ms_flags_objectt from script, just copy it to the scene from inside the YafaRay4tS panel.

clintonman · Post by **clintonman** » 03 Nov 2019, 23:07

trueBlue wrote: 03 Nov 2019, 22:30 If it is not to much work maybe you could create the ms_flags_object from the python script and then the user assigns the script to it.
That way when it is deleted at the end of the animation, the assigned script goes with it.

No, but can get the same result by saving the ms_flag_object with the script already assigned, then load if from disk instead of creating it at the start of the animation. This would also eliminate the need for the user to assign the script and no need to have the create python button.

edit: cross post, yeah you get the idea

trueBlue · Post by **trueBlue** » 03 Nov 2019, 23:13

I have been testing this and it is not working without crashing. It could be because of the way I copied the object though. Still needs to be tested!!!

Okay I think I know why it was crashing. It crashes if the ms_flags_object is in the scene before a Backup.
Still needs more testing!

Not working for me in 4View layout at all. UGH

clintonman · Post by **clintonman** » 04 Nov 2019, 03:16

Made the change and did some tests and saw no crashes.
Switch to 4view layout and quickly got a crash.
Started in 4view several tests and with no crashes.
Switch to default layout and quickly got a crash.

Looks like switching layouts after a model mesh processing render will lead to a crash.

Edit:
If you switch layouts after a render and then immediately exit tS you can avoid the crash. Other than that it's crash free for me. I was going to start removing the python button and change the messaging, but I'll wait for your test results.

trueBlue · Post by **trueBlue** » 04 Nov 2019, 04:22

I tried creating a ms_flags_object from a model object, model nurbs, workspace object, and even using your object.
In 4view layout as soon as I assigned the python script to them and closed the Script Editor, trueSpace crashed.
This was without rendering too!
Hope it works out!
It is nice being able to save and assign to the model animation object.
I think that might be an issue with Import and Export though.
Would be nice if you could create the python file during the start of the Model Mesh Processing and remove that portion from the UI.

clintonman · Post by **clintonman** » 04 Nov 2019, 05:28

trueBlue wrote: 04 Nov 2019, 04:22 ...
It is nice being able to save and assign to the model animation object.
I think that might be an issue with Import and Export though.
...

I don't understand.

Attached is a modified YafaRay4tS containing the ms_flags_object with the python script assigned to it. Also altered the messaging at the start and end of the render. Not all the changes I was planning but good enough for testing. Probably the first step would be to make sure the python isn't assigned to the scene object, your crashes could have bought it back.

trueBlue · Post by **trueBlue** » 04 Nov 2019, 14:43

Test using your YafModelspaceTest06.RsScn with the new YafaRay4tS03.RsObj in the YafaRay4tS layout.
Even though this scene has 20 frames in Model and Workspace, the render stops at frame 10
Set from Keyframes set the End Frame to 20
In Model after the render is complete, the time line did not return to 0 like it use to.

Switched to 4View layout, switched one view to Model and trueSpace crashed.
Reset the Default Context
Switched to 4View layout, and it rendered as above with no crash.
In Model after the render is complete, the time line returned to 0

Was thinking that switching to 4View after rendering from another layout was the only reason for the crashing but that is not the case.
Switching to any layout will crash.

I installed the Unofficial Update and tested assigning the python script to the Model animation object and got simular crashes as above when switching layouts. So no differences there with the ms_flags_object verses assigning the python script to the Model animation object. So I will test with the YafaRay4tS03.RsObj going forward.

trueBlue · Post by **trueBlue** » 04 Nov 2019, 16:31

DoFrameRender
Errors.Add("Render has been canceled... Custom Viewer only works with TGA format files. Change the Output - Render File image file format to tga ", "abort");
This was my mistake. Change 'Custom Viewer' to 'TGA Viewer' in the above

Remove openModelScriptForScene and keysExternalClearScript

Change Alert in CreatePythonSync

SaveSettings script does not replace the YafaRay4tS panel in the /System/YafaRay Folder

clintonman · Post by **clintonman** » 04 Nov 2019, 16:40

trueBlue wrote: 04 Nov 2019, 16:31 ...

Change Alert in CreatePythonSync

SaveSettings script does not replace the YafaRay4tS panel in the /System/YafaRay Folder

CreatePython script will be going away, python exists on the ms_flags_object

FYI, This code says it only copies if the YafaRay4tS does not exist, so if that's the case and it doesn't get copied then the Yafaray Folder.RsObj file will be an empty node.

Code: Select all

	if(!Node.Exists(Destination)) {
		Node.Copy(Space.CurrentScene() + "/YafaRay4tS", "/Yafaray Folder")
	}

trueBlue · Post by **trueBlue** » 04 Nov 2019, 16:51

All I know is, it does not work as expected.
Change your settings in the scene YafaRay4tS panel and select the Save Settings button.
Through me for a loop this morning.
It should delete the YafaRay4tS panel in the System/YafaRay Folder before copying the scene YafaRay4tS panel to System/YafaRay Folder, and then save the YafaRay Folder to disk

clintonman · Post by **clintonman** » 04 Nov 2019, 17:02

I disagree, if you have an old scene with an old version of YafaRay then saving settings will replace the current version on disk with an old yafaray version.

trueBlue · Post by **trueBlue** » 04 Nov 2019, 17:11

Good point!
I guess you can not use the Save Settings button to update the YafaRay4tS panel in System then. Just attributes and not nodes.

trueBlue · Post by **trueBlue** » 04 Nov 2019, 21:59

Is there something I can fix on my end to get past the 10 frame limit?
Other then that, it is working except for the crashes when switching layouts.

clintonman · Post by **clintonman** » 04 Nov 2019, 22:07

I don't know of any 10 frame limit, is there something you can share to show it?

trueBlue · Post by **trueBlue** » 04 Nov 2019, 22:12

I reported that previously.
I am using your YafModelspaceTest06.RsScn from your web site with the updated YafaRay4tS panel.

clintonman · Post by **clintonman** » 04 Nov 2019, 22:45

line got disconnected

trueBlue · Post by **trueBlue** » 04 Nov 2019, 23:20

Thanks.

Animation

Model Processing

Steps to process Model animations from the Anim aspect, with the main view in Workspace and no Model view opened

1.) Select the Backup button and Save your scene

2.) Check Model Processing

3.) Switch the main view to Model and open new Workspace 3D view

4.) Select the Render Animation button

5.) When the render has completed, switch the main view to Workspace

6.) Select the Restore button

Model Mesh Processing

Steps to process Model mesh animations, NURBS. Metaballs, or Deformations from the Anim aspect, with the main view in Workspace and no Model view opened

1.) Select the Backup button and Save your scene

2.) Check Model Processing and Model Mesh Processing

3.) Switch the main view to Model and open new Workspace 3D view

4.) Select the Render Animation button

5.) When the render has completed, switch the main view to Workspace

6.) Select the Restore button

WARNING!
Switching layouts will crash trueSpace if you do not Exit trueSpace first.
Rendering with the main view in Workspace and new Model will crash trueSpace.

YafaRay4tS User Interface

YafaRay4tS Scene Utilities

Import and Export

For importing and exporting YafaRay4tS scene files

Process Imported Scene

Replaces the YafaRay4tS panel in the scene with all of the existing settings, excluding the YafaRay Installation Path. If the Output Render File path does not exist, a default path will be assigned. Updates the texture paths based on the path in the Texture Source Folder.

Gather Textures for Sharing

Copies all of textures in the scene to the Texture Source Folder.

Update YafaRay4tS

For updating previous versions of YafaRay4tS scenes to the current version.

YafaRay4tS Panel

Replaces the YafaRay4tS panel in the scene with all of the existing settings, excluding the YafaRay Installation Path. It does not update the Output Render File path.

YafaRay Materials

Replaces all of the YafaRay Materials in the scene with the current YafaRay Materials.

YafaRay Lights

Replaces all of the YafaRay Lights in the scene with the current YafaRay Lights.

YafaRay Cameras

Replaces all of the YafaRay Cameras in the scene with the current YafaRay Cameras.

D3D Materials

Opens the D3D Material Converter

In order to render in YafaRay4tS, all existing materials in the scene must be converted to a D3D Shader.

From the Default aspect in the D3D Material Converter, uncheck Selected Only, and select the Convert button.

After all of the scene materials are converted to D3D Shaders, you can convert all of the scene materials to YafaRay Materials.

From the YafaRay4tS aspect in the D3D Material Converter, uncheck Selected Only, and select the Convert button.

trueBlue · Post by **trueBlue** » 04 Nov 2019, 23:40

I notice that the python script can still exist in Model.
Can you silently remove it at the end of the animation?
I tested this manually removing it and rendering the same animation several times and works without any issues.

clintonman · Post by **clintonman** » 04 Nov 2019, 23:42

The script should be removed from model view scene, it's not needed anymore and the create python button will be removed. It will only exist on the ms_flags_object

trueBlue · Post by **trueBlue** » 05 Nov 2019, 00:40

Confirmed, must have been a now deleted older scene.

trueBlue · Post by **trueBlue** » 05 Nov 2019, 14:49

Some notes:

hellowWorld.RsScn

1.) Open Output Folder 'incorrect'

Use Custom XML File 'checked'
Output Folder = 'c:\temp' <- Not Correct
Output Render File = 'C:\trueSpace761\tS\Image Folder\text_anim.png' <- Correct

2.) Cancel Render @ Frame 19 - 'canceled after frame rendered'
2.30 min per frame
Add System.SetBusyCursor(true)?
From the Snd Tutorial 5
// Due to fact next loop is not so lucky idea as it take
// all control of the application, set at least busy cursor
System.SetBusyCursor(true);

// Give back the cursor
System.SetBusyCursor(false);

3.) Switch main view from Model to Workspace
05:14:42.230 ERR Failed Modeler->Workspace synchronization on object LODMesh
Run - Sync from Workspace script at the end of animation stops this error.

: Capture2.PNG (10.02 KiB) Viewed 3674 times

4.) Reset Play Range at the end of animation?
Node.Value("/AnimMng", "AnimEnd") = 300
Node.Value("/AnimMng", "AnimTime") = 0

Notes:
Model Processing
Switching layouts does not crash trueSpace
Rendering with the main view in Workspace and new Model view does not crash trueSpace

Model Mesh Processing
Switching layouts will crash trueSpace
Rendering with the main view in Workspace and new Model view will crash trueSpace
Remove Alert and put in Model Mesh Processing instructions?
WARNING!
Switching layouts will crash trueSpace if you do not Exit trueSpace first.
Rendering with the main view in Workspace and new Model will crash trueSpace.

Notice again that the python script is still assigned to the Scene. Note this is a new workspace scene.
Not sure how, when, or why. Thinking it may be that Model saves it state. Even though this is a new Workspace scene, Model's view is in the same state it was when rendering the above scene.

clintonman · Post by **clintonman** » 05 Nov 2019, 16:15

trueBlue wrote: 05 Nov 2019, 14:49 Some notes:

hellowWorld.RsScn

1.) Open Output Folder 'incorrect'

Use Custom XML File 'checked'
Output Folder = 'c:\temp' <- Not Correct
Output Render File = 'C:\trueSpace761\tS\Image Folder\text_anim.png' <- Correct
...

Confirmed, I see it.

trueBlue wrote: 05 Nov 2019, 14:49 ...
2.) Cancel Render @ Frame 19 - 'canceled after frame rendered'
2.30 min per frame
Add System.SetBusyCursor(true)?
From the Snd Tutorial 5
// Due to fact next loop is not so lucky idea as it take
// all control of the application, set at least busy cursor
System.SetBusyCursor(true);

// Give back the cursor
System.SetBusyCursor(false);
...

If you see a busy cursor in your tests then go ahead. I've never seen the busy cursor from script. If you don't see it don't put it in.

trueBlue wrote: 05 Nov 2019, 14:49
4.) Reset Play Range at the end of animation?
Node.Value("/AnimMng", "AnimEnd") = 300
Node.Value("/AnimMng", "AnimTime") = 0
...

No, changing the users timeline for no reason. If they set their play range they probably did it for a reason.

trueBlue wrote: 05 Nov 2019, 14:49 ...
Notes:
Model Processing
Switching layouts does not crash trueSpace
Rendering with the main view in Workspace and new Model view does not crash trueSpace

Model Mesh Processing
Switching layouts will crash trueSpace
Rendering with the main view in Workspace and new Model view will crash trueSpace
Remove Alert and put in Model Mesh Processing instructions?
WARNING!
Switching layouts will crash trueSpace if you do not Exit trueSpace first.
Rendering with the main view in Workspace and new Model will crash trueSpace.

Notice again that the python script is still assigned to the Scene. Note this is a new workspace scene.
Not sure how, when, or why. Thinking it may be that Model saves it state. Even though this is a new Workspace scene, Model's view is in the same state it was when rendering the above scene.
Capture.PNG

If you're testing with the python assigned to the scene then your tests are invalid. Workspace has no connection to model view python, so resetting the workspace will not clear the python from the scene item. You have to clear the model view scene to clear out the python.

trueBlue · Post by **trueBlue** » 05 Nov 2019, 16:32

No, changing the users timeline for no reason. If they set their play range they probably did it for a reason.

Actually the play range gets changed from the YafaRay4tS scripts.

If you see a busy cursor in your tests then go ahead. I've never seen the busy cursor from script. If you don't see it don't put it in.

Not sure what you are suggesting here. Just noticed that Render Cancel does not happen until after the frame is rendered. In this case it was 2.30 mins. Never did see the status message.

If you're testing with the python assigned to the scene then your tests are invalid. Workspace has no connection to model view python, so resetting the workspace will not clear the python from the scene item. You have to clear the model view scene to clear out the python.

This morning, I only used two scenes, the YafModelspaceTest06.RsScn and the helloWorld.RsScn with the new YafaRay4tS panel.
It was after testing these scenes, that I noticed the python script in Model. I have not been assigning any scripts.
I'll keep a watch out as I am not sure when it happened.
Never the less these are just observations.

clintonman · Post by **clintonman** » 05 Nov 2019, 16:45

trueBlue wrote: 05 Nov 2019, 16:32
No, changing the users timeline for no reason. If they set their play range they probably did it for a reason.
Actually the play range gets changed from the YafaRay4tS scripts.
If you see a busy cursor in your tests then go ahead. I've never seen the busy cursor from script. If you don't see it don't put it in.
Not sure what you are suggesting here. Just noticed that Render Cancel does not happen until after the frame is rendered. In this case it was 2.30 mins. Never did see the status message.
...

I'm not seeing the YafaRay changing the play range. Can you give steps so I can see it?

I'm saying I have tried this command and never seen any difference in the cursor. If you got it to work then do it. That's what I'm saying.

Code: Select all

System.SetBusyCursor(true);

clintonman · Post by **clintonman** » 05 Nov 2019, 16:51

trueBlue wrote: 05 Nov 2019, 16:32 ...
Never the less these are just observations.

Just saying you may need to re-observe with a good scene, since a bad scene may mess up your tests.

trueBlue · Post by **trueBlue** » 05 Nov 2019, 16:52

With the Animation view open, Set the play range to 0 - 300
Load the YafModelspaceTest06.RsScn
Same with the helloWorld.RsScn

trueBlue · Post by **trueBlue** » 05 Nov 2019, 16:57

Here is a new Yafaray Camera I am adding to the setup library.
Y4tSv.0.9.7
Yafaray EntryPoint Camera
When the scene loads the view will switch
to this Camera's view.

In the YafaRay4tS/Camera aspect,
with this camera selected,
select the Set Camera button when
rendering from a Camera View.

clintonman · Post by **clintonman** » 05 Nov 2019, 17:12

trueBlue wrote: 05 Nov 2019, 16:52 With the Animation view open, Set the play range to 0 - 300
Load the YafModelspaceTest06.RsScn
Same with the helloWorld.RsScn

Thanks, test shows it's not coming from YafaRay4tS. I removed the Yaf node and it still happens. Also tested with fresh scene with animated torus. Clear scene, set range 0 to 300 and when reload the scene it changed the play range to the animation keys on the torus.

clintonman · Post by **clintonman** » 05 Nov 2019, 17:14

trueBlue wrote: 05 Nov 2019, 16:57 Here is a new Yafaray Camera I am adding to the setup library.
Y4tSv.0.9.7
Yafaray EntryPoint Camera
When the scene loads the view will switch
to this Camera's view.

In the YafaRay4tS/Camera aspect,
with this camera selected,
select the Set Camera button when
rendering from a Camera View.

Fine with me, as long as still have access to a camera that does not automatically switch the view.

trueBlue · Post by **trueBlue** » 05 Nov 2019, 17:15

Just confirmed that those scenes also assign the python script in Model.

clintonman · Post by **clintonman** » 05 Nov 2019, 17:18

trueBlue wrote: 05 Nov 2019, 17:15 Just confirmed that those scenes also assign the python script in Model.

Right, none of the scenes have been updated since your discovery of placing the python on a scene item instead of the scene.
Edit: I don't plan to update them or the help/webpage until you're done with testing and changes.

trueBlue · Post by **trueBlue** » 05 Nov 2019, 18:49

Were you planning any changes to YafaRay4rS?
If so can you share the latest?

clintonman · Post by **clintonman** » 05 Nov 2019, 18:51

I haven't made any changes cause I thought you were making changes.

trueBlue wrote: 04 Nov 2019, 16:31 DoFrameRender
Errors.Add("Render has been canceled... Custom Viewer only works with TGA format files. Change the Output - Render File image file format to tga ", "abort");
This was my mistake. Change 'Custom Viewer' to 'TGA Viewer' in the above

Remove openModelScriptForScene and keysExternalClearScript

Change Alert in CreatePythonSync

SaveSettings script does not replace the YafaRay4tS panel in the /System/YafaRay Folder

trueBlue · Post by **trueBlue** » 05 Nov 2019, 19:02

I am not making any changes to your code. Only suggestions. The biggest one being the Sync from Workspace, if it is doable.
Edit: I am hopeful that this may help with crashes too!

clintonman · Post by **clintonman** » 05 Nov 2019, 19:08

OK, I'll be making changes soon.

clintonman · Post by **clintonman** » 05 Nov 2019, 23:33

fix animation end on frame 10
doframerender changed message as requested
remove all model view scene based python scripts, button and time stamp

tried running sync after model view render but didn't work, sendkeys did not - command node still in place in case you want to make a go of it

2 sample scenes did not need to be updated for the new python method since the python was not loaded into the scene. uploading a fixed helloWorld scene now

TODO: update documentation and make official release

trueBlue · Post by **trueBlue** » 06 Nov 2019, 02:03

tried running sync after model view render but didn't work, sendkeys did not - command node still in place in case you want to make a go of it

I tried to in a different way and was able to get the send key to work, but the error still persisted.
I removed the command node, fixed the UI, and changed the date to November 05, 2019
Uploaded the changes to the Update(s)
The YafaRay4tS Help is updated too
Let me know if you need help with the changes and or images.

clintonman · Post by **clintonman** » 06 Nov 2019, 02:16

Great, it'll be nice to wrap this up.

trueBlue · Post by **trueBlue** » 06 Nov 2019, 02:21

clintonman wrote: 06 Nov 2019, 02:16 Great, it'll be nice to wrap this up.

Amen! To THAT!!!

Thanks for everything!

clintonman · Post by **clintonman** » 06 Nov 2019, 04:17

I altered some of the wording in the D3D Material conversion. A complex scene with a lot of objects will fail to convert to a YafaRay materials only scene.

"After all of the scene materials are converted to D3D Shaders, you can convert some or all of the scene materials to YafaRay Materials.
From the YafaRay4tS aspect in the D3D Material Converter, choose to check or uncheck Selected Only, and select the Convert button.
The complex nature of YafaRay materials limits the number of scene items with YafaRay materials applied to about 800 objects."

Edit: animation page chm file has "Rendering with the main view in Workspace and new Model will crash trueSpace" I don't think that's true anymore.

edit: online help file updated now.

trueBlue · Post by **trueBlue** » 06 Nov 2019, 13:23

Want to make sure that any changes to the compiled help file are correct before I make the final update.
Quote from your last update to the Material Converter

added limits warning for the convert d3d to yafaray materials to help prevent crashes - limits to processing 200 materials at a time, 3 runs for a total of 600 is somewhat safe and 4 runs for a total of 800 may or may not crash, anything over 800 guaranteed crash

Do you want to redefine your correction?

After all of the scene materials are converted to D3D Shaders, you can convert some or all of the scene materials to YafaRay Materials.
From the YafaRay4tS aspect in the D3D Material Converter, choose to check or uncheck Selected Only, and select the Convert button.
The complex nature of YafaRay materials limits the number of scene items with YafaRay materials applied to about 800 objects.

BTW...the D3D Material Converter has a link to your website.

Edit: animation page chm file has "Rendering with the main view in Workspace and new Model will crash trueSpace" I don't think that's true anymore.

I am getting mixed results with the Mesh Model Processing scene when testing the above workflow.
First test after rendering, closing the new Model view, tS crashed.
If I switched the new Model view to Workspace first before closing it, no crash.
It is difficult to get tS in a un crash state. Simply resetting the default context does not work.
Fairly sure it has to due with Model's save state and also Workspace's lack of synchronization with Model.
Hence when switching the new Model view to Workspace first before closing it.

You have dead links in your online help file
YafaRay4tS installer
YafaRay Lights
YafaRay Light Material
new pic

: image001.png (3 KiB) Viewed 3850 times

New pic and info
YafaRay4tS Setup

: image008.png (13.8 KiB) Viewed 3850 times

Included with YafaRay4tS is a YafaRay Setup library that includes:

YafaRay4tS.RsScn with YafaRay Light setup and a Yafaray Camera.
YafaRay4tS toolbar.RsObj script that reloads the toolbar.
YafarayVolume.RsObj Volume Region object for Uniform and Height Fog.
Yafaray Camera.RsObj includes a script to select DOF distance and additonal settings.
EntryPoint.RsObj A Yafaray EntryPoint Camera. When the
scene loads the view will switch to this Camera's view.
In the YafaRay4tS/Camera aspect, with this camera selected,
select the Set Camera button. when rendering from a Camera View.
Several objects that are used to create a D3D Preview of the Background.
Tiff Loader.RsObj for loading and displaying Tiff images in trueSpace.

In the History, I am going to change the date to:
YafaRay4tS version: 0.9.7
November 05, 2019

Last but not least, I made a significant discovery when rendering an 2 min image this morning.
While it was rendering, I clicked on the Display, it disappeared, and when it finished rendering, the Bitmaps Base library was opened.

: Capture3.PNG (242.36 KiB) Viewed 3838 times

This has always been an issue, but I have discovered a solution by changing it to a Clickable Bitmap.
Also added a WinId to the OwnedBy attribute to it's panel frame.
Changed the TIFF loader in the tSDisplay and YafaRay4tS Setup library too.
Here is a scene you can try with the changes.

clintonman · Post by **clintonman** » 06 Nov 2019, 18:46

"First test after rendering, closing the new Model view, tS crashed.
If I switched the new Model view to Workspace first before closing it, no crash.
It is difficult to get tS in a un crash state. Simply resetting the default context does not work.
"

Confirmed for special mesh processing crash when exit floating model view
Don't see getting stuck in crashed/unstable state.

You have dead links in your online help file
YafaRay4tS installer
YafaRay Lights
YafaRay Light Material "

I see the broken Light Material link, don't know where the other 2 links are.

Will update online help to match the chm file changes.

trueBlue · Post by **trueBlue** » 06 Nov 2019, 18:54

Another issue with the Save to File on the iOptiViewer when rendering to the TIFF format.
There is no option to save as a TIFF format for one, and even if there was I am not sure if it would work.
Saving to an available format does not work either. IE.. png, bmp, etc...
Most likely, the only way for this to work, would be with your plugins?

clintonman · Post by **clintonman** » 06 Nov 2019, 18:58

"Changed the TIFF loader in the tSDisplay and YafaRay4tS Setup library too."

Don't see any problems with your test scene.

Do not remove the button from the TIFF loader in the library. Just makes it less useful.

Removing buttons in general makes things more difficult to troubleshoot. When removed from a command node you can't run it in isolation anymore unless you add the button back in or load the run activity node from the library and hook it up.

clintonman · Post by **clintonman** » 06 Nov 2019, 19:05

trueBlue wrote: 06 Nov 2019, 18:54 Another issue with the Save to File on the iOptiViewer when rendering to the TIFF format.
There is no option to save as a TIFF format for one, and even if there was I am not sure if it would work.
Saving to an available format does not work either. IE.. png, bmp, etc...
Most likely, the only way for this to work, would be with your plugins?

I see it. It needs to change to save from the Tiff loader instead of the image.

trueBlue · Post by **trueBlue** » 06 Nov 2019, 19:06

clintonman wrote: 06 Nov 2019, 18:58 "Changed the TIFF loader in the tSDisplay and YafaRay4tS Setup library too."

Don't see any problems with your test scene.

Do not remove the button from the TIFF loader in the library. Just makes it less useful.

Removing buttons in general makes things more difficult to troubleshoot. When removed from a command node you can't run it in isolation anymore unless you add the button back in or load the run activity node from the library and hook it up.

LOL, that is because I made the modifications!

Buttons???
I changed the Bitmap attribute to a Clickable Bitmap.
This stops the Bitmap Base library from showing.

trueBlue · Post by **trueBlue** » 06 Nov 2019, 19:10

clintonman wrote: 06 Nov 2019, 19:05
trueBlue wrote: 06 Nov 2019, 18:54 Another issue with the Save to File on the iOptiViewer when rendering to the TIFF format.
There is no option to save as a TIFF format for one, and even if there was I am not sure if it would work.
Saving to an available format does not work either. IE.. png, bmp, etc...
Most likely, the only way for this to work, would be with your plugins?
I see it. It needs to change to save from the Tiff loader instead of the image.

Long as it does not break saving as another format. Right?

clintonman · Post by **clintonman** » 06 Nov 2019, 19:18

fixed to save tiff format render image

clintonman · Post by **clintonman** » 06 Nov 2019, 19:22

trueBlue wrote: 06 Nov 2019, 19:06
clintonman wrote: 06 Nov 2019, 18:58 "Changed the TIFF loader in the tSDisplay and YafaRay4tS Setup library too."

Don't see any problems with your test scene.

Do not remove the button from the TIFF loader in the library. Just makes it less useful.

Removing buttons in general makes things more difficult to troubleshoot. When removed from a command node you can't run it in isolation anymore unless you add the button back in or load the run activity node from the library and hook it up.
LOL, that is because I made the modifications!
Buttons???
I changed the Bitmap attribute to a Clickable Bitmap.
This stops the Bitmap Base library from showing.

Just talking buttons in general. Removing the button from the Tiff Loader in the library makes it so you can't press a button and load the image via a dialog. Without the button you have to manually type the full path to the tif image. Doesn't matter as much that you removed it from the tiff loader inside the yafaray node.

trueBlue · Post by **trueBlue** » 06 Nov 2019, 19:34

Okay I guess you are totally misunderstanding me.
I did not remove any buttons.
Here is the modified TIFF loader.
Click on the Bitmap attribute. Nothing happens, correct?

Now try it with your TIFF loader. Shows the Bitmap Base library, correct?
May have to coax it to show at first. Click, Double Click, and or Ctrl + Click it.
Does not eliminate Ctrl + Click though!

Also with the Display, the issue with showing the Bitmap Base library does not show unless you are in the middle of a long render and after it is completed. Or maybe when you Cancel the render.

Can you give instructions on how to save an Image.tif to disk?

clintonman · Post by **clintonman** » 06 Nov 2019, 20:28

trueBlue wrote: 06 Nov 2019, 19:34 Okay I guess you are totally misunderstanding me.
I did not remove any buttons.
Here is the modified TIFF loader.
Click on the Bitmap attribute. Nothing happens, correct?

Now try it with your TIFF loader. Shows the Bitmap Base library, correct?
May have to coax it to show at first. Click, Double Click, and or Ctrl + Click it.
Does not eliminate Ctrl + Click though!

Also with the Display, the issue with showing the Bitmap Base library does not show unless you are in the middle of a long render and after it is completed. Or maybe when you Cancel the render.

Can you give instructions on how to save an Image.tif to disk?
Screenshot.png

Yep, only know what you show me and you only showed me the stripped down tif loader inside the Yafaray node. Nothing removed so I''m happy.

So is the Display fixed? or is it still broken somehow?

Don't see tif in the list, so guess it can't be done.

trueBlue · Post by **trueBlue** » 06 Nov 2019, 20:33

Yes you included it in your update.
Maybe you could use your GetRenderFile script?
Edit: Tried to insert the code here, but I am getting the 403 Forbidden Error

trueBlue · Post by **trueBlue** » 06 Nov 2019, 22:07

Reported this before, the Scene Utilities/YafaRay4tS Panel script unchecks all viewers.

: Capture2.PNG (3.6 KiB) Viewed 4132 times

When you select Render, you get an error.

: Capture.PNG (5.5 KiB) Viewed 4135 times

Then the TGA Viewer opens.

Load the helloWorld scene
Select the Yafaray4tS Script Node button
Select the Open Scene Utilities button
In the Stack, change the YafaRay4tS panel to Setup
The panel in the Stack is deleted except the title bar.
YafaRay4tS panel in the scene is still present, If I add

Code: Select all

UserInterface.OpenToolPanelViewEx2("", "", Space.CurrentScene() + "/YafaRay4tS", 3, 1, 0);

to the bottom of that script, problem solved.
The Stack is soooo strange!

I like the way you are using the Esc keyboard key to cancel a render!
Why can't the Cancel Render button work the same way?
Why can't the Render Animation button script and the Render animation toolbar LMB command work the same way?

clintonman · Post by **clintonman** » 07 Nov 2019, 00:16

trueBlue wrote: 06 Nov 2019, 22:07 Reported this before, the Scene Utilities/YafaRay4tS Panel script unchecks all viewers.
Capture2.PNG
When you select Render, you get an error.
Capture.PNG
Then the TGA Viewer opens.

Load the helloWorld scene
Select the Yafaray4tS Script Node button
Select the Open Scene Utilities button
In the Stack, change the YafaRay4tS panel to Setup
The panel in the Stack is deleted except the title bar.
...

I'm not seeing that at all. Maybe you're missing a step? When I open the helloWorld scene the Scene Utilites in the scene pops up a panel. I use it and don't get viewers unchecked. If I remove it and run the scene utilites from the button also no unchecking of viewers.
If you don't get the popup when loading the helloWorld scene then your scene maybe different from mine. If so you can post and I can take a look at it.

trueBlue · Post by **trueBlue** » 07 Nov 2019, 00:36

Okay, I narrowed it down, if you save a scene with Disable All Viewers 'checked'.
Load the scene.
Run Scene Utilities/YafaRay4tS Panel button.
Open up the Setup aspect.
All viewers are unchecked.

clintonman · Post by **clintonman** » 07 Nov 2019, 00:39

trueBlue wrote: 06 Nov 2019, 22:07 ...
I like the way you are using the Esc keyboard key to cancel a render!
Why can't the Cancel Render button work the same way?
...

How are they different?

clintonman · Post by **clintonman** » 07 Nov 2019, 00:51

trueBlue wrote: 07 Nov 2019, 00:36 Okay, I narrowed it down, if you save a scene with Disable All Viewers 'checked'.
Load the scene.
Run Scene Utilities/YafaRay4tS Panel button.
Open up the Setup aspect.
All viewers are unchecked.

I have made some mods to the YafaRay4tS.RssObj

loaded helloWorld scene
checked disable all viewers
saved scene
new scene and load scene back in
close the scene utilities popup
open scene utilties from button
press yafaRay4tS Panel button
viewers are still checked, disable all viewers is unchecked which is expected because of some problem with reading/writing that value

so still not seeing it.

trueBlue · Post by **trueBlue** » 07 Nov 2019, 00:56

clintonman wrote: 07 Nov 2019, 00:39
trueBlue wrote: 06 Nov 2019, 22:07 ...
I like the way you are using the Esc keyboard key to cancel a render!
Why can't the Cancel Render button work the same way?
...
How are they different?

Esc shows a Console Alert
Sometimes the Cancel Render does not show the status message and if it does, it quickly disappears.
What I am seeing is several inconsistencies with the Render buttons, toolbar Render commands, some alerts use the Console Alerts, some use tS Alerts, and status messages.

As an example
Render animation toolbar command

Code: Select all

OfflineRender.OpenView('',0,0);if (Node.Exists('/Scripts/Commands/RenderAnimation')){Activity.Run('/Scripts/Commands/RenderAnimation');}if (!Node.Exists('/Scripts/Commands/RenderAnimation')){OfflineRender.RenderAnimation('')}

Render Animation button script.

Code: Select all

Activity.Run("%THIS_NAME%" + "/RenderAnim2");

Both give different results

clintonman · Post by **clintonman** » 07 Nov 2019, 00:57

trueBlue wrote: 06 Nov 2019, 22:07 ...
Why can't the Render Animation button script and the Render animation toolbar LMB command work the same way?

How are they different and how do you want it to be and why?

virgin ts animation button
OfflineRender.OpenView('',0,0);OfflineRender.RenderAnimation('')
OfflineRender.OpenPreferencesPanel()

unofficial update animation button
OfflineRender.OpenView('',0,0);Activity.Run('/Scripts/Commands/RenderAnimation');

yafaray toolbar animation button
OfflineRender.OpenView('',0,0);
if (Node.Exists('/Scripts/Commands/RenderAnimation')){Activity.Run('/Scripts/Commands/RenderAnimation');}
if (!Node.Exists('/Scripts/Commands/RenderAnimation')){OfflineRender.RenderAnimation('')}

clintonman · Post by **clintonman** » 07 Nov 2019, 01:11

trueBlue wrote: 07 Nov 2019, 00:56
clintonman wrote: 07 Nov 2019, 00:39
trueBlue wrote: 06 Nov 2019, 22:07 ...
I like the way you are using the Esc keyboard key to cancel a render!
Why can't the Cancel Render button work the same way?
...
How are they different?
Esc shows a Console Alert
Sometimes the Cancel Render does not show the status message and if it does, it quickly disappears.
...

The cancel messaging can be adjusted by copying some code from RenderFrame into ProtectWorkspace.

Can't do anything about render animation without clear direction.

trueBlue · Post by **trueBlue** » 07 Nov 2019, 01:16

clintonman wrote: 07 Nov 2019, 00:57
trueBlue wrote: 06 Nov 2019, 22:07 ...
Why can't the Render Animation button script and the Render animation toolbar LMB command work the same way?
How are they different and how do you want it to be and why?

virgin ts animation button
OfflineRender.OpenView('',0,0);OfflineRender.RenderAnimation('')
OfflineRender.OpenPreferencesPanel()

unofficial update animation button
OfflineRender.OpenView('',0,0);Activity.Run('/Scripts/Commands/RenderAnimation');

yafaray toolbar animation button
OfflineRender.OpenView('',0,0);
if (Node.Exists('/Scripts/Commands/RenderAnimation')){Activity.Run('/Scripts/Commands/RenderAnimation');}
if (!Node.Exists('/Scripts/Commands/RenderAnimation')){OfflineRender.RenderAnimation('')}

The above using the Render animation toolbar
Next render the same scene with the Render Animation button.
This is all related to using Disable all Viewers and all viewers being unchecked.
Also using Disable all Viewers gets turned off after a render.
Do not know why the Scene Utilities/Yafaray4ts Panel button is giving you and I different results, but I can duplicate over and over again with the steps I provided.

viewers are still checked, disable all viewers is unchecked which is expected because of some problem with reading/writing

Bingo!
Could this be the reason?
From the incorporated Scene Utilities/YafaRay4tS Panel button script.

Code: Select all

		if(connector[3] & CONFLG_IN && !(connector[3] & CONFLG_HIDDEN)) {
			if(Node.ConExists(Destination, connector[0])) {
				if(connector[0] == "Yaf_Path" || connector[0] == "useRenderToFile") {
					continue;

clintonman · Post by **clintonman** » 07 Nov 2019, 02:37

Cancel Render button and esc key have the same behavior with error message added to the errors object.

trueBlue · Post by **trueBlue** » 07 Nov 2019, 20:07

Sorry Clinton, but the problems with the YafaRayBar render scripts in the YafarayScripts are a show stopper!
I was able to get the Render Animation icon working by adding Activity.Run(Space.CurrentScene() + "YafaRay4tS/RenderAnim2"); in the YafarayScripts/AnimationRender script, but I was not able to overcome the TGA errors.
There seems to be alot going on with the Render to File, Output Render File image formats, and your beloved TGA Viewer!
Do not know how complicated this could be to incorporate into all of your scripts, but maybe you could read the Output Render File's image format, and if it is tga, spawn the TGA Viewer. If it is not tga, use the internal viewers?
Here are my notes:

YafaRayBar
Render Animation script
If Disable All Viewers (useRenderToFile) is checked and the Output Render Render File image format is anything other then the TGA format you get an error.
If you change it to the TGA format and LMB select Render animation, nothing is rendered.
Same for all other image formats, nothing is rendered.
The only thing this script does is open the YafaRay4tS Anim aspect

Render Scene script
If Disable All Viewers is checked and the Output Render Render File image format is anything other then the TGA format you get an error.
If you change it to the TGA format and LMB select Render animation, nothing is rendered.

Render Object script
If Disable All Viewers is checked and the Output Render Render File image format is anything other then the TGA format you get an error.
If you change it to the TGA format and LMB select Render animation, nothing is rendered.

Render Area script
If Disable All Viewers is checked and the Output Render Render File image format is anything other then the TGA format, you get a Alert with no message.
TGA format does render.
Note: Add RMB select in 3D Space to deactivate in help file

All of the above Render scripts (sometimes) give an alert with no titlbar text with a message Error loading file, file 'path' must have an extention of 'tga' See post Re: YafaRay for trueSpace 2019 Post by trueBlue » Wed Nov 06, 2019 2:07 pm

YafaRay4tS panel
Setup
Disable All Viewers does not stay active.

YafaRay4tS Scene Utlities

YafaRay4tS Panel script and Process Imported Scene script
Add
UserInterface.OpenToolPanelViewEx2("", "", Space.CurrentScene() + "/YafaRay4tS", 3, 1, 0);

If Disable All Viewers is checked, all viewers get unchecked

YafaRay Lights script
Spot/Angle changes to 2.00

YafaRay Materials
D3D Preview button(s) in an Activated state are not honored. Workaround - Deactivate/Activate

clintonman · Post by **clintonman** » 07 Nov 2019, 20:48

trueBlue wrote: 07 Nov 2019, 20:07 ... TGA errors.
...beloved TGA Viewer!
... if it is tga, spawn the TGA Viewer. If it is not tga, use the internal viewers?
...
other then the TGA format you get an error.
... the TGA format ...
... the TGA format you get an error.
... TGA format ...
... TGA format and LMB ...

... the TGA format, you get a Alert with no message.
TGA format does render.
... must have an extention of 'tga'...

...

Hope you see the pattern there. I give you 2 choices 1) keep it the way it is or 2) we remove the tga viewer.
I've mentioned before that the tga viewer is a pain. The amount of work needed to make it run smoothly with all other changes is not worth the effort.

trueBlue · Post by **trueBlue** » 07 Nov 2019, 21:50

clintonman wrote: 07 Nov 2019, 20:48
trueBlue wrote: 07 Nov 2019, 20:07 ... TGA errors.
...beloved TGA Viewer!
... if it is tga, spawn the TGA Viewer. If it is not tga, use the internal viewers?
...
other then the TGA format you get an error.
... the TGA format ...
... the TGA format you get an error.
... TGA format ...
... TGA format and LMB ...

... the TGA format, you get a Alert with no message.
TGA format does render.
... must have an extention of 'tga'...

...
Hope you see the pattern there. I give you 2 choices 1) keep it the way it is or 2) we remove the tga viewer.
I've mentioned before that the tga viewer is a pain. The amount of work needed to make it run smoothly with all other changes is not worth the effort.

I do, been looking at your scripts. I vote to get rid of it. As said the way it is now is a show stopper! There is online converters to convert to a tga.

I am also on the fence with your newest addition (I have not tried it) with the Cancel Render. I know I said I liked it. It was more about them being different. But the truth is (my personal opinion) I do not like Alerts that you have to click to dismiss. The only problem with the status message was it was dismissed to fast. If you could make it like the Status Message.RsObj in the Update(s) where you could set the amount of time before it is removed, that would be awesome!
Including this one:
System.Alert("WARNING! Switching layouts will crash trueSpace if you do not Exit trueSpace first.")

clintonman · Post by **clintonman** » 07 Nov 2019, 23:39

trueBlue wrote: 07 Nov 2019, 21:50 ...
I do, been looking at your scripts. I vote to get rid of it. As said the way it is now is a show stopper! There is online converters to convert to a tga.

I am also on the fence with your newest addition (I have not tried it) with the Cancel Render. I know I said I liked it. It was more about them being different. But the truth is (my personal opinion) I do not like Alerts that you have to click to dismiss. The only problem with the status message was it was dismissed to fast. If you could make it like the Status Message.RsObj in the Update(s) where you could set the amount of time before it is removed, that would be awesome!
Including this one:
System.Alert("WARNING! Switching layouts will crash trueSpace if you do not Exit trueSpace first.")

Ok then, away with it. And there's no need for a tga converter, you can render and display tga without it.

FHembree · Post by **FHembree** » 08 Nov 2019, 06:22

Must admit I have not been following this thread much as I would like, but instead just quickly glancing over it. I have tried some of the Yafaray updates but one problem I find is that they
can not render my older files created under previous versions such as 7.6 n 8 etc, so I deleted the newer versions such as 9 and later because of material incompatibilities. I see there is
a script "D3D Material Converter" to convert d3d materials to YafaRay but is there a script to convert older YafaRay materials to the current versions of Yafaray materials?

So for compatibility reasons, I prefer versions 7.6 and 8 even though I may be missing some or a lot of newer features.
I also like the Material interface of these versions better.

trueBlue · Post by **trueBlue** » 10 Nov 2019, 05:16

clintonman wrote: 07 Nov 2019, 23:39
trueBlue wrote: 07 Nov 2019, 21:50 ...
I do, been looking at your scripts. I vote to get rid of it. As said the way it is now is a show stopper! There is online converters to convert to a tga.

I am also on the fence with your newest addition (I have not tried it) with the Cancel Render. I know I said I liked it. It was more about them being different. But the truth is (my personal opinion) I do not like Alerts that you have to click to dismiss. The only problem with the status message was it was dismissed to fast. If you could make it like the Status Message.RsObj in the Update(s) where you could set the amount of time before it is removed, that would be awesome!
Including this one:
System.Alert("WARNING! Switching layouts will crash trueSpace if you do not Exit trueSpace first.")
Ok then, away with it. And there's no need for a tga converter, you can render and display tga without it.

Can hear that?!

Several thousands lines of code being reworked and removed from several different nodes!
Huge undertaking.
Hope it goes smoothly.

No doubt, this update is going to make it much easier to use!

clintonman · Post by **clintonman** » 12 Nov 2019, 02:26

First draft of "no tgaviwer version"

The TGA_Viewer is the default external viewer and not a special stand alone viewer.
The render viewer toggle buttons have been replaced by push buttons.
Disable All Views changed from checkbox to a push button.
"Custom Viewer" changed to "External Viewer" to show that it is the opposite of the "Internal Viewer".
Invalid viewer options will be adjusted at render time to the most sensible values. The visible values do not change. An altered copy of the options is used at render time. If the External Viewer is not valid then an error message.
TODO: add question dialogs for some of the adjustments

Scene Utilities "update yafaray node" updated for the new "no tga"/"disable all views" logic.

There was a lot of changes so there may be some bad behavior here and there or we may be lucky and it works almost perfectly.

trueBlue · Post by **trueBlue** » 12 Nov 2019, 17:15

Awesome update Clinton!!!
You did great!
Tested using all of the viewer options using the Render buttons and icons, except for Animation.
Including launching Gimp in the External Viewer's path
All is working without errors, except for handled TGA error, which is expected.
The only thing I notice is when NOT using the Viewer buttons, but using the check boxes, the viewers do not spawn in some cases. Never the less everything still renders without errors!
As an example, uncheck all of the viewer options except the OptDetector Viewer.
Help file does mention that the Internal Viewer must be checked when using the OptDetector Viewer, so all is good!
Thought about suggesting that the check boxes be removed, but then there would not be any indication which viewer is enabled.
Actually, changing the check boxes Type to On/Off buttons works better IMHO.

Next test animation...