United3dArtists Archive

Yafaray proof of concept render with modelspace animations included. The box and the particle system are modelspace animations, the ball is workspace.

Also added the ability to view tif file format renders.

Great Clintonman...(as usual)
Have a question (i never use Yafa at this time)...could worth It give a try rendering with Yafa instead the Classic engine of tSp? Are there samples showing both results?
Thanks a lot manteining alive this software...

the_ant wrote: 18 Jun 2019, 06:19 Great Clintonman...(as usual)
Have a question (i never use Yafa at this time)...could worth It give a try rendering with Yafa instead the Classic engine of tSp? Are there samples showing both results?
Thanks a lot manteining alive this software...

Thanks, I don't really know the advantages and disadvantages of the different render engines. You can see some renders here: http://truespace3d.free.fr/index.php/gallery/ and here: http://www.yafaray.org/gallery?g2
I don't know if the tS renders are vray or lightworks.

I think I got it all working now, it's not fully tested yet. Attached are files for anyone interested in trying it out.
Replace the YafarayScripts node found in /Scripts/CustomCommands
Load the YafaRay4tS into a scene, setup and render.

Animation Render with modelspace:
1. have both modelspace and workspace 3d views open
2. autokey to off in modelspace, or you'll end up with a bunch of new keyframes

Change List:
Updates ModelSpace animation time when a ModelSpace View is open - can render modelspace animations
Will display tif renders if the tif loader plugin is installed, Clintons Ext Plugin
Removed Render to File dialog
Cancelled/Abort render error messages are followed by actual cancellation of the render
Close tS and open again and the basic render display will still be valid, iOptiDisplay will still be blank
Added render filename to the iOpti display title bar
Ask for confirmation if batch render is combined with not delete temp files option
new version number 0.9.5
Mostly it was a lot of rewrites to confusing code to make the new changes doable and try to make the whole thing more reliable.


Clintons Ext Plugin can be found at the bottom of this page: http://clintons3d.com/plugins/truespace ... index.html

Shape animation of NURBS, deformation and metaball objects require extra manual steps. All other animations seem to work without it.
1. The Setup panel has a button "Create Modelspace Python file". It writes a python file to the tS folder for later use
2. Check to Default panel option, "Modelside special mesh processing" to make the render use the python script on modelside during the animation render
3. In modelspace open the script editor for the Scene object and
4. Press the Assign button and choose the file "sync_by_visibility.py", found in "C:\trueSpace761\tS\PythonScripts"
during the animation render the script will run and update the shape animations

Thanks Clinton!
Some simple observations:
1.) Status line shows "Rendering..." after render is complete.
Suggestion
Add - Node.Value("/Status Line","Model") = "";
to the OpenDisplayFrame and OpenOptDetectorFrame2 scripts

2.) Do not show the Display node when using the External Viewer.

3.) When switching from View to Camera or visa versa and Rendering, does not render/display correctly until second attempt.
This is true when changing the file extensions too.

4.) About aspect: Update the version number to 9.5

trueBlue wrote: 23 Jun 2019, 13:43 Thanks Clinton!
Some simple observations:
1.) Status line shows "Rendering..." after render is complete.
Suggestion
Add - Node.Value("/Status Line","Model") = "";
to the OpenDisplayFrame and OpenOptDetectorFrame2 scripts

2.) Do not show the Display node when using the External Viewer.

3.) When switching from View to Camera or visa versa and Rendering, does not render/display correctly until second attempt.
This is true when changing the file extensions too.

4.) About aspect: Update the version number to 9.5

Thanks for that. I made changes for 1, 2 and 4. Can't see the behavior in 3 switching camera/view or file extension change. Any other details for this one?
Attached has the 3 changes.

the_ant wrote: 18 Jun 2019, 06:19 Great Clintonman...(as usual)
Have a question (i never use Yafa at this time)...could worth It give a try rendering with Yafa instead the Classic engine of tSp? Are there samples showing both results?
Thanks a lot manteining alive this software... :worship:

Yafaray is a great renderer mainly because it doesnt have lights (hmm, maybe it does, dont remember exactly). Instead you turn any object (material) to make it light. So you can produce very nice renders with alot of complicated lighting. Instead of using point light, you can make a lightbulb with a wire and make the wire emit the light (not just a point but whole wire will shine like in reality). You can use easily objects as area lights etc.

I was playing with it few years ago and I very liked it. Only reason I dont use it is because Vray is still good and mainly - its well integrated. If I get so well integrated solution for Modeler side with Yafaray, i would maybe prefer Yafaray.

Check out this old test render. Its a Spanish flag made shine.

Steps
Enable - Custom Viewer
Select the Render button on the YafaRay4tS panel.
Image shows that the Display node spawns and the image rendered is incorrect. Select the Render button on the YafaRay4tS panel a second time and the rendered image is correct in the Display node.

Change the object's shape, select the Render button on the YafaRay4tS panel, Display node spawns and the image rendered is incorrect.
Select the Render button on the YafaRay4tS panel a second time and the rendered image is correct in the Display node.


Hope this helps.

trueBlue wrote: 24 Jun 2019, 14:49 Steps
Enable - Custom Viewer
Select the Render button on the YafaRay4tS panel.
Image shows that the Display node spawns and the image rendered is incorrect.
Capture.PNG
Select the Render button on the YafaRay4tS panel a second time and the rendered image is correct in the Display node.

Change the object's shape, select the Render button on the YafaRay4tS panel, Display node spawns and the image rendered is incorrect.
Select the Render button on the YafaRay4tS panel a second time and the rendered image is correct in the Display node.


Hope this helps.

So the internal display should be closed when using the external viewer. No point in having 2 viewers open. I'll set it so non-active viewers are closed.

clintonman wrote: 24 Jun 2019, 15:33 So the internal display should be closed when using the external viewer. No point in having 2 viewers open. I'll set it so non-active viewers are closed.

That was my thought.
Just noticed that you are misunderstanding me.
In my test I have been using the Custom Viewer pointed to the TGA Viewer.
This is the one that opens both viewers.
The External Viewer is working as expected.


Looks like http://www.yafaray4ts.org/ is no longer online.
So if you are willing, maybe you could setup a link on your website for YafaRay4tS? Suggestion
Add an Alert to the Create Modelspace Python file button script describing its use and confirm that it was created.
1. The sync_by_visibility.py file was created and only needs to be created once.
2. Enable the "Modelside special mesh processing" in the YafaRay4tS - Default aspect, to make the render use this python script in Model space during the animation render.
3. In Model space open the Script Editor for the Scene object and...
4. Press the Assign button and choose the file "sync_by_visibility.py", found in "C:\trueSpace761\tS\PythonScripts"
during the animation render, the script will run and update the shape animations.


The YafaRay4tS toolbar's YafaRay4tS Settings icon LMB command. As shown in the help file the LMB command should show the Default aspect in the Stack.
It runs the Yafaray Settings LMB Command script.
The way it is now it is creating another scene.
Thinking this may be an unwanted behavior IF the YafaRay4tS panel is existing in the current scene.
Can you look at that script?
If the YafaRay4tS panel exist in the current scene, show the Default aspect in the Stack.
If it does not exist then run the script as is.


Curious!
Having YafaRay4tS render Model space animations.
Doesn't that open a can of worms with Workspace Materials and Lights getting corrupted?

trueBlue wrote: 24 Jun 2019, 15:52 ...
The YafaRay4tS toolbar's YafaRay4tS Settings icon LMB command.
Capture2.PNG
As shown in the help file the LMB command should show the Default aspect in the Stack.
It runs the Yafaray Settings LMB Command script.
The way it is now it is creating another scene.
Thinking this may be an unwanted behavior IF the YafaRay4tS panel is existing in the current scene.
Can you look at that script?
If the YafaRay4tS panel exist in the current scene, show the Default aspect in the Stack.
If it does not exist then run the script as is.


Curious!
Having YafaRay4tS render Model space animations.
Doesn't that open a can of worms with Workspace Materials and Lights getting corrupted?

Did all the changes as suggested. Except for the last one.

LMB
1. if vray is the active render it returns with a message
2. if vray is not will load the YafaRay4tS scene
conclusion: only vray scenes will not be replaced by the YafaRay4tS scene

RMB
1. switch to yafaray renderer
2. if no YafaRay4tS node in the scene will load the YafaRay4tS scene, copy the YafaRay4tS node and open aspect number 6
conclusion: if no YafaRay4tS node in the scene, then the scene will be replaced

Final conclusion: both LMB and RMB are designed to easily replace the current scene with the YafaRay4tS scene. Not sure how it should work, but some kind of warning may be needed when using that button.

As far as modelspace materials that's a good question and I wasn't even aware of the light corruption problem.

Edit other changes:
changed the yafaray4ts link to use the web archive and added my yafaray webpage
removed Use Render To File and Use External Viewer
If internal viewer is checked will use it, otherwise uses the external viewer

Edit:
Looking at the archived yafaray4ts site and a lot of the useful info was lost, so I'll remove the link from the About and add a link on my website for "history" reasons

YafaRay4tS Help has a more up to date History.
When I created that help file, I used all of the information that was on that web site.
In version 9.0, I included all of your updates in the help file.

With regards to the LMB command the help file states:
YafaRay4tS Settings
LMB = Opens the Default aspect in the Stack/Panel
Opens a new YafaRay4tS scene if Yafaray is the current selected Offline Renderer.

RMB = Opens the Setup aspect in the Stack/Panel
Opens a new YafaRay4tS scene if the YafaRay4tS object is not present.
Also switches to the Yafaray Renderer if it is not the current Offline Renderer.


The YafaRay4tS panel gets lost in the Stack.
Was hoping that the LMB would open the Default aspect in the Stack/Panel if the YafaRay4tS exist in the scene.
If the YafaRay4tS does not exist in the scene, Opens a new YafaRay4tS scene if Yafaray is the current selected Offline. Renderer.

Couldn't the above be a If/Else script?
There is a Scene Changed warning that can be Canceled. It just does not show the Default aspect in the Stack.

Thanks for all of the modifications, I'll try out your changes tomorrow.

Edit: I tired you newest update.

I compared the LMB and RMB scripts to the previous update and there is no changes.
The link to your web site does not work. This works: Not sure why you eliminated the Use External Viewer and Render to File.
1.) Makes the Help file useless in this regards.
2.) Render to File is all messed up (Hint - Whack the Mole R2F Button(s) scripts) with the YafaRay4tS Setup/Viewers
You do know there is a Render to File toolbar icon, right?

I think this has the LMB/RMB behavior you requested.

trueBlue wrote: 26 Jun 2019, 02:47 ...

Edit: I tired you newest update.

I compared the LMB and RMB scripts to the previous update and there is no changes.
The link to your web site does not work. This works:

Code: Select all

RsTool.OpenWebPage("www.clintons3d.com/plugins/truespace/rendering/yafaray.html")

Not sure why you eliminated the Use External Viewer and Render to File.
1.) Makes the Help file useless in this regards.
2.) Render to File is all messed up (Hint - Whack the Mole R2F Button(s) scripts) with the YafaRay4tS Setup/Viewers
You do know there is a Render to File toolbar icon, right?

Almost didn't see this. Don't get any notifications from old posts editing.

Did you copy YafaRay4tS node into the /Yafaray Folder? LMB RMB won't run from the YafaRay4tS in the scene.

Fixed the link.

Internal/External is decided only by the Internal checkbox, since removed the ability to have more than 1 viewer active. The combination of Internal and External also made the code more confusing.
"You do know there is a Render to File toolbar icon, right?", I know now that you mention it. I'll adjust it to work with the toolbar icon, meaning the Render and Animation buttons will be simplified.

I've been looking at the modelspace material issue and it looks like it'll need something like the "protect workspace materials" script. You mentioned there was a problem with modelspace lights too. Can you direct me to more info on that?

clintonman wrote: 26 Jun 2019, 15:20 I think this has the LMB/RMB behavior you requested.

This one works great, Thanks!
I have noticed the first Workspace Spot light being replaced with a Model Spot light numerous times when switching to Model.

Also when using the Model's Scene Editor, YafaRay Lights get moved.
Here is a scene with a Model (only) animation that rendered successfully using YafaRay4tS 9.5
This is a simple Model animation of a Yafaray Camera keyframed to look at a keyframed moving Sphere. No Workspace animation used. Default Bridge settings (Auto).
Note that the default Yafaray4tS scene (lights) were used. When using Model's SE all of the lights moved to where they are now. The lights were not modified by me in any way. I do not believe that this is a YafaRay4tS 9.5 issue because the lights moved before rendering the 20 frames.
Removed due to update

trueBlue wrote: 27 Jun 2019, 05:58

clintonman wrote: 26 Jun 2019, 15:20 I think this has the LMB/RMB behavior you requested.

This one works great, Thanks!
I have noticed the first Workspace Spot light being replaced with a Model Spot light numerous times when switching to Model.

Also when using the Model's Scene Editor, YafaRay Lights get moved.
Here is a scene with a Model (only) animation that rendered successfully using YafaRay4tS 9.5
This is a simple Model animation of a Yafaray Camera keyframed to look at a keyframed moving Sphere. No Workspace animation used. Default Bridge settings (Auto).
Note that the default Yafaray4tS scene (lights) were used. When using Model's SE all of the lights moved to where they are now. The lights were not modified by me in any way. I do not believe that this is a YafaRay4tS 9.5 issue because the lights moved before rendering the 20 frames.

Glad to hear the LMB RMB is working. I'll attach the latest below.

I have a theory about the lights. I think the Yafaray4tS scene was created with workspace only version of truespace so when the scene loads it doesn't properly sync with modelspace. If I load the scene, sync to modeler and save the scene, the lights look good when reloaded.

clintonman wrote: 28 Jun 2019, 02:56 I have a theory about the lights. I think the Yafaray4tS scene was created with workspace only version of truespace so when the scene loads it doesn't properly sync with modelspace. If I load the scene, sync to modeler and save the scene, the lights look good when reloaded.

The YafaRay4tS scene that is included in the Unofficial update was created using the newest lights v9.0.
Here is what I notice that is repeatible.
Load the Yafaray4tS scene in Workspace.
Switch to Model.
The YafaRay Spot, 1 and YafaRay Infinite, 1 are renamed to YafaRay Spot,1 and YafaRay Infinite,1 removing the space between the comma and number.
Switch to Workspace.
The lights seem to be unchanged.
Switch to Model, open the Scene Editor and scrub the timeline.
Switch to Workspace.
All of the lights are moved together at different locations as pairs. IE: Spots together and Infinite together as shown in the scene I shared.


Using the default Workspace scene in the above senario, the Spotlight2 gets changed to a Model light and all the lights move as mentioned above. Very strange indeed and is related to the Scene Editor.
So far no other lights in the scene are affected by this oddity.


Can you please try the exact steps above and confirm this?
Be sure to use the Scene Editor's scrubber.

trueBlue wrote: 28 Jun 2019, 16:12

clintonman wrote: 28 Jun 2019, 02:56 I have a theory about the lights. I think the Yafaray4tS scene was created with workspace only version of truespace so when the scene loads it doesn't properly sync with modelspace. If I load the scene, sync to modeler and save the scene, the lights look good when reloaded.

The YafaRay4tS scene that is included in the Unofficial update was created using the newest lights v9.0.
Here is what I notice that is repeatible.
Load the Yafaray4tS scene in Workspace.
Switch to Model.
The YafaRay Spot, 1 and YafaRay Infinite, 1 are renamed to YafaRay Spot,1 and YafaRay Infinite,1 removing the space between the comma and number.
Switch to Workspace.
The lights seem to be unchanged.
Switch to Model, open the Scene Editor and scrub the timeline.
Switch to Workspace.
All of the lights are moved together at different locations as pairs. IE: Spots together and Infinite together as shown in the scene I shared.


Using the default Workspace scene in the above senario, the Spotlight2 gets changed to a Model light and all the lights move as mentioned above.
Capture.PNG

Very strange indeed and is related to the Scene Editor.
So far no other lights in the scene are affected by this oddity.


Can you please try the exact steps above and confirm this?
Be sure to use the Scene Editor's scrubber.

Yep, that's some weird stuff alright. Confirmed except for YafaRay light renaming, could be my install is out of date, loading Yafaray scene lights already have no space in the name. Unfortunately, I won't be able to do any more testing till after the weekend.

Workspace adds a space in the name by default.
The YafaRay4tS Lights library has the scene lights and a space in the name.
If you have Model open when you load them it renames them.
BTW what started this, I was testing YafaRay4tSv9.5 by incorporating the Scene Editor into the layout as shown.
Was seeing if I could over come the Materials becoming corrupted by not having the Model view opened.
The test did render a Model and Workspace animation successfully without have the Model view open.

I did some testing.

I wasn't seeing the lights rename because of my bridge settings. If bridge is set to "ON" then items are renamed immediately. When set to "Auto" items get renamed when the model space view is open. Workspace makes copies with a trailing comma, space and a number. Models space does the same thing without the space. If there is either no comma or no space then the names are preserved.

Model space Scene Editor should be avoided. If it is not at frame 0, new objects added to a scene will get unwanted model space key frames applied to them. The AutoRecord setting has no effect. Scrubbing can cause the lights to blow out and some items to move.

Materials and spotlight color needs to be backed up before going to model space. Several model space actions can damage the workspace settings. I think the spotlight color needs protecting because model space reads the light material in workspace and sets the color based on that. The yafaray spotlights have been altered to match the yafaray render via the material so model space changes a color (1,1,1) to something like (20,20,20) causing the lights to blow out.

Workspace settings, like infinite light rotation values, don't all make it over to modelspace, so it needs to be forced.

1. Bridge off
2. make some small change like changing the view or selecting something
3. Bridge On and sync from workspace
4. if there is no sync dialog try again

The default scenes second spotlight changing to modelspace spotlight is just plain nuts.

That's all I know so far. It looks like the problems can be worked around.

I found a solution to the spotlight being replaced by a modelspace spotlight.
Fix is to export the "Map size" and "Enable shadows" connectors on the Spot Preferences node.
The spotlight was also being replaced if you go to modelspace and toggle the shadows or change the value of the shadow map size. My guess is that modelspace tries to read/change a value, doesn't see it so assumes a bad object and replaces it.

I have it mostly worked out now. Attached is a script to protect workspace from modelspace random changes. There was a lot more messy things with the bridge going from model to work space than I originally thought. Have to do more testing to see if anything else is happening.
This will be a replacement for the protect materials script with a new icon shown above.

It backs up by:

• 1. rename items to be modelspace compatible - changes end of name from [comma-space-number] to just [comma-number]
  2. fixes lights by exporting map size and enable shadow connectors
  3. saves materials and light colors
  4. saves the matrix values of all items to protect their positions

It restores by:

• 1. copy the matrix values back
  2. copy the materials and light colors back into place

2. fixes lights by exporting map size and enable shadow connectors

Have not tried your script yet.
Seems that exporting the attributes would break the interface "Spot Preferences" from working.
The original light(s) have ALL of the attributes exported out.

Just found out camera fov and spot angle are also effected by modelspace/bridge.

Looks like I will need to fix all of the lights in the update.
Might be awhile.
Here is an updated Spot and YafaRay Spot
Removed due to update

I notice that when I use Model to change the Map Size it does not change the values on the node.
This is true with Model or Workspace lights.
Also changing the Attenuation changes the Angle.

trueBlue wrote: 11 Jul 2019, 18:23 Looks like I will need to fix all of the lights in the update.
Might be awhile.
Here is an updated Spot and YafaRay Spot
Spot.RsObj
YafaRay Spot.RsObj
I notice that when I use Model to change the Map Size it does not change the values on the node.
This is true with Model or Workspace lights.
Also changing the Attenuation changes the Angle.

I don't see the Attenuation changing the Angle. Changing the Falloff dist changes the AttQuadratic value which seems correct to me. This is testing on a Model spotlight and old Workspace spotlight from unpatched truespace.
It looks like some information doesn't pass through the bridge and some only goes one way.
If you export the Area light visible connector to the top of a model area light, it changes when you click Render geometry in the area light options. If you check it on Workspace model doesn't see it.
The new Area lights aren't recognized by Model as area lights. It comes across as a point light. I have no idea why. I striped the light down to look just like the model area light and it still came over as a point light. I will test with vray to determine if it sees it properly.

Latest protection script adds spotlight angle and camera fov.
Edit: fixed bug

The only thing I can think of with regards to rendering model animation in YafaRay4tS is do your animation first with the Bridge off in Model. Then transfer the animation to a Workspace animation and Model light values to YafaRay4tS lights.

trueBlue wrote: 13 Jul 2019, 16:11 The only thing I can think of with regards to rendering model animation in YafaRay4tS is do your animation first with the Bridge off in Model. Then transfer the animation to a Workspace animation and Model light values to YafaRay4tS lights.

I didn't think about that. I was only considering the opposite, workspace animations with a few modelspace animations that aren't possible in workspace like, vertex, facial and particles added in.

The workspace protection scripts seem to be ready, so I'll be doing some animation tests next and adding some of the protections to the process.

I tested and the new area light works in vray, so no worries there.

First test result is good. I used the d3d render script combined with the workspace protection to render a test particle animation. Top is the protected slightly shinier d3d material and the bottom is the appearance without the protection. The exact same technique can protect the yafaray materials during its render.

Here is a YafaRay4tS scene that I am testing crossing over the Bridge (Auto) and your ProtectWorkspace script.
Both Spot lights have all of their Spot Preference attributes exported out, which seems to stop Model from replacing either of them with Model lights. Still have the problem where the Spot light moves though.
Your script seems to be working when restoring any changes made in Model's Light interface except when changing Attenuation. Only "Squared Falloff with distance" seems to work when restoring. No Falloff and Linear Falloff breaks the lights and does not get restored. From what I am noticing it looks like Intensity does not work well when crossing the Bridge. Might be testing this in the wrong way, most likely should not be using Model to change the lights.
Removed due to update

trueBlue wrote: 15 Jul 2019, 18:42 Here is a YafaRay4tS scene that I am testing crossing over the Bridge (Auto) and your ProtectWorkspace script.
Both Spot lights have all of their Spot Preference attributes exported out, which seems to stop Model from replacing either of them with Model lights. Still have the problem where the Spot light moves though.
Your script seems to be working when restoring any changes made in Model's Light interface except when changing Attenuation. Only "Squared Falloff with distance" seems to work when restoring. No Falloff and Linear Falloff breaks the lights and does not get restored. From what I am noticing it looks like Intensity does not work well when crossing the Bridge. Might be testing this in the wrong way, most likely should not be using Model to change the lights.

When you say the spotlight moves I assume you mean when you switch to modelspace? If so the workaround is to force synchronization from workspace first.
I didn't notice the attenuation changes so the script does not save any of those values.
There's no way the model and yafaray lights can match because the yafaray power value changes the color output.
I'll check out the scene to see what you got.

Edit: Just reread your post. The script is only used to stop the automatic and seemingly random changes made by modelspace, not to protect against a user purposely making changes in modelspace.

It turns out my Bridge was not even working unless I did as you suggested by manually invoking the Bridge Synchronization. I reset the default context and it seems to be working now. I understand how your script works. I was trying to invoke Model changes in order to test your script. It mostly works except what I had mentioned. Nevertheless one should not be using Model to adjust YafaRay4tS lights.
I do question the fact that your script exports attributes and does not Restore them, breaking the interface as mentioned earlier. And or anything else unknown to me at this time.

trueBlue wrote: 16 Jul 2019, 20:13 ...
I do question the fact that your script exports attributes and does not Restore them, breaking the interface as mentioned earlier. And or anything else unknown to me at this time.

Are you saying it should un-export the "shadowmap size" and "enable shadow" connectors when the restore is run?

Yes, other wise they will no longer work.

New version un-exports the "shadowmap size" and "enable shadow" connectors when the restore is run.

YAY! Seems to work as expected.
I was able to break it in an unexpected way by deleting the backup nodes and running Restore again.
Looks like you recreate those nodes when you run Backup.
Any harm in deleting those nodes when you run Restore with your script?

Also I would suggest adding a Status message with date and time to the ProtectWorkspace node.
The status message can get loss and there is no clue of what state it is in.
This would come in handy when saving the scene and reopening at a later date.

clintonman wrote: 13 Jul 2019, 15:12 If you export the Area light visible connector to the top of a model area light, it changes when you click Render geometry in the area light options. If you check it on Workspace model doesn't see it.
The new Area lights aren't recognized by Model as area lights. It comes across as a point light. I have no idea why. I striped the light down to look just like the model area light and it still came over as a point light. I will test with vray to determine if it sees it properly.

In Workspace with the Bridge On, create two Area lights and switch to Model.
What do you see?
Now with Bridge Auto, create two Area lights and switch to Model.
Crazy!

trueBlue wrote: 19 Jul 2019, 15:56

clintonman wrote: 13 Jul 2019, 15:12 If you export the Area light visible connector to the top of a model area light, it changes when you click Render geometry in the area light options. If you check it on Workspace model doesn't see it.
The new Area lights aren't recognized by Model as area lights. It comes across as a point light. I have no idea why. I striped the light down to look just like the model area light and it still came over as a point light. I will test with vray to determine if it sees it properly.

In Workspace with the Bridge On, create two Area lights and switch to Model.
What do you see?
Now with Bridge Auto, create two Area lights and switch to Model.
Crazy!

Yep, "Crazy" is a good word for it. It also works with bridge on if you copy an existing area light, but it doesn't work if you use the copy button, you have to drag a copy.

So I am at a loss here with regards to fixing the lights and or if they need to be fixed.
The Updated workspace lights have their Preferences attributes disconnected from parent panel.

You have said that exporting the Shadow and Map Size helps in some way.
Also something about the Spot Angle.

What exactly is happening with the above?

Does this happen with the Bridge set to Auto and or On?

trueBlue wrote: 19 Jul 2019, 19:08 So I am at a loss here with regards to fixing the lights and or if they need to be fixed.
The Updated workspace lights have their Preferences attributes disconnected from parent panel.

You have said that exporting the Shadow and Map Size helps in some way.
Also something about the Spot Angle.

What exactly is happening with the above?

Does this happen with the Bridge set to Auto and or On?

Exporting Shadow and Map Size stops modelspace from converting the light from workspace to modelspace style, so the unoffical updated lights and Yafaray lights don't get altered. My guess is that modelspace sees the lack of Shadow and Map size as invalid lights and so replaces them.
Spot Angle is just one more thing that gets changed by modelspace, just like it changes the positions. It's not exported, the value is just saved and restored.
I haven't tested every combination of Auto vs On for the bridge. Many but not all changes happen because of scrubbing the time in the modelspace scene editor.

Okay Thanks!
I can confirm that toggling the Shadow from Model also causes Model to replace the updated Spot and Projector lights.
Exporting their Preference's attributes fixes that.
Now I need to figure out why scrubbing makes them move.
Their mesh was changed and have a BinaryOp attached.
Edit: Changing the mesh does not help. WTH?
Edit2: Just confirmed that a Model Spot light also moves when using the scrubber. This is true even after Synchronization.
Including with the Bridge On and Full Merge. It reverts back to the previous position.

Off subject but I was wondering what you might think about this.
With a Model and Workspace window open, drop this into a Workspace scene and transform an object.
Try viewing from the same Camera on both sides.
Saves the overhead of running with a timer.
Oddly this object can NOT be minimized.
New - Camera FOV widget
Removed due to update

trueBlue wrote: 22 Jul 2019, 19:05 Off subject but I was wondering what you might think about this.
With a Model and Workspace window open, drop this into a Workspace scene and transform an object.
Try viewing from a Camera on both sides.
Saves the overhead of running with a timer.
Oddly this object can NOT be minimized.

That is interesting. The mouse connectors have to be visible in the link editor or it doesn't work. It inspired me to try adding bridge sync command to a widget. It didn't work. I also tried connect it to the VolumeTree node inside the Project, it can be minimized and still work. When it's not visible it seems to run 1 step behind any motion of the object. It's strange but maybe a step closer.

Edit: Just found out connecting to VolumeTree stops modelspace widgets from working properly.

Edit: I was wrong about the widget not working. It works, but only updates after the mouse button is released.

Used an iOpti camera, Recorder, and Synchronize together.
Other cameras do not work like this in the above setup.

trueBlue wrote: 04 Aug 2019, 02:50 Used an iOpti camera, Recorder, and Synchronize together.
Other cameras do not work like this in the above setup.
Capture.PNG

Completely over my head. I don't know what I'm looking at and I don't know if it's a good thing or a bad thing.

clintonman wrote: 04 Aug 2019, 03:12 Completely over my head. I don't know what I'm looking at and I don't know if it's a good thing or a bad thing.

It is a good thing!

Two views are in sync viewing from the iOpti cam in Workspace and Model.
Meaning that with the Synchronize script running and not having to view from it, the iOpti cam still works.
Other cameras do not work like this in the above setup.
Most likely because the iOpti view is a window rendering the 3D Space.

Animated GIF
Ball animated in workspace.
Torus is a modelspace animation
The metaballs shows the python script updates the shape.
Yafaray materials protected from modelspace changes.

I found a bug while testing where option "create xml files and batch render" wants to open with the tga external viewer. Other than that it's all working.

Cool!

Latest YafaRay changes

Can use modelspace animations
Uses the new ProtectWorkspace script - includes protection for names, material, matrix, spot light angle and camera fov
New animation abort method - closes the animation loop to prevent other processing. The old way of setting to the last frame causes a problem with big modelspace particle animations. It will calculate all the way to the end of the animation.

Animation aspect has new checkbox options:
Protect from workspace - activate protection from modelspace
Name - protect item names
Camera Fov/Spot angle -
Transform Matrix - disabled by default because will interfere with workspace transform animations
Materials -
Special mesh processing - for NURBS, metaball and other techniques that require special processing to update workspace from modelspace

Setup aspect has a "Create Modelspace Python file" button - one time run that installs the python file required for special mesh processing

note: used with the new YafarayScripts.RsObj
See previous posts for other changes

Couple of questions?
What is Protect from Workspace?

If it is what I think it is (If checked, runs ProtectWorkspace), shouldn't it be checked by default?
Did you include all of these attributes in the Reset Default Settings?
Also you have these on the Animation aspect.
Shouldn't these be on the Default aspect?

You have YafaRay4tS version set at 9.5
Is that correct?

trueBlue wrote: 21 Aug 2019, 14:55 Couple of questions?
What is Protect from Workspace?

If it is what I think it is (If checked, runs ProtectWorkspace), shouldn't it be checked by default?
Did you include all of these attributes in the Reset Default Settings?
Also you have these on the Animation aspect.
Shouldn't these be on the Default aspect?

You have YafaRay4tS version set at 9.5
Is that correct?

Protect from Workspace - oops should have been Protect Workspace or Protect from Modelspace
Forgot to add them to the global default reset.
The ProtectWorkspace only runs with animations so I put it in the animations aspect.
ProtectWorkspace should not be on by default because it's a special case. Only used if some modelspace animation are needed. Also std truespace has no modelspace.
Maybe it should be 0.9.5? anything over 0.9.0 will work

Edit: note - need to add check for protect workspace script existence as a safety check and turn off if not present

Forgot to comment on the image

Protect - off by default, not always needed and std has no modelspace
Name - off by default, but can go either way
Camera and Spot - on
Transform - off, can interfere with workspace transform animation
Materials - on
Special - off, only needed for certain kinds of modelspace mesh animations

Gotcha!
Seems to me that this version 9.5 should be used with tS7.61 only.
And tS7.61 Standalone should use version 9.0 only.

trueBlue wrote: 21 Aug 2019, 16:59 Gotcha!
Seems to me that this version 9.5 should be used with tS7.61 only.
And tS7.61 Standalone should use version 9.0 only.

I didn't have time to list all the changes:
protect workspace/modelside animations
ability to view tif file format renders
Cancelled/Abort render error messages are followed by actual cancellation of the render
Added render filename to the iOpti display title bar
Ask for confirmation if batch render is combined with not delete temp files option
a lot of rewrites to confusing code to make the new changes doable and try to make the whole thing more reliable.
Status line fixes
Do not show the Display node when using the External Viewer.

There are other changes too, but there was a lot of back and forth so I need to review what all changed.

Small changes to the interface:
YafaRay4tS
Anim
Moved and shortened the Protect Workspace attributes to look similar to the WorkSpaceProtect.RsObj
Default
Reset the Default Settings
Removed the specialMeshes attribute.

WorkSpaceProtect.RsObj
Changed Misc to Lights
Removed due to update

trueBlue wrote: 21 Aug 2019, 18:07 ...

WorkSpaceProtect.RsObj
Changed Misc to Lights

Misc also does camera fov

YafaRay4tS

fixed bug - the restore workspace node was not connected to the ProtectScene connector. Changed to read remotely instead of direct connection
safety - check for existence of ProtectWorkspace node, if not found turn off ProtectScene
changed Lights in the Animation aspect to Lights/Cameras for the Misc connector
The defaults for the ProtectScene options were already setup for the global reset - the global reset automatically resets all connectors of the YafaRay4tS node.

ProtectWorkspace

changed Lights to Light/Camera for the Misc connector

Edit:

Here is a link to the unpublished Protect Workspace page:
http://clintons3d.com/plugins/truespace ... space.html

Finally testing this in Rosetta.
Found a minor detail:
CreatePythonSync script: * Change 'Default aspect' to 'Anim aspect' (Fixed) * One to many Back Slash between trueSpace761 and tS. (Fixed)
* Add C:\trueSpace761Std\PythonScripts (???) Ideas?
* Need to create a PythonScripts folder for the Rosetta update. (???) Ideas?
* Move 'Create Modelspace Python File' button to the Anim aspect. (Fixed)

Note: The 'Output - Render File' path to the image file is different in Rosetta and tS761

trueBlue wrote: 23 Aug 2019, 04:07 ...
* Add C:\trueSpace761Std\PythonScripts (???) Ideas?
* Need to create a PythonScripts folder for the Rosetta update. (???) Ideas?
* Move 'Create Modelspace Python File' button to the Anim aspect. (Fixed)

Note: The 'Output - Render File' path to the image file is different in Rosetta and tS761

Python scripts don't run on Rosetta, is modelspace only. If it created the python file then that's a bug, it should not create it for Rosetta.
The 'Create Modelspace Python File' button belongs on the Setup, because it's a one time setup thing.

It looks like the reset for that connector is broken. It's supposed to set the image path automatically.

Fixed the reset for the image file name by re-exporting the connector and linking back to all the panels it was used in.
Changed Default to Anim
Couldn't find the extra \ in the [4. Press the Assign button and choose the file "sync_by_visibility.py", found in "C:\\trueSpace761\\tS\\PythonScripts"\n']
Based on the YafaRay4tS from the last beta release, so modelspace button is still in setup tab where I think it belongs.

Edit: Tested modelspace python button in old Unofficial Rosetta 4 and it gives the message, "Python script is only valid for the full version of trueSpace."

Thanks!
I have uploaded the changes to the Update(S)
In case you do not know, the YafaRay4tS.RsObj in the Yafaray Folder.RsObj and the YafaRay4tS.RsScn files are different in trueSpace 761 and trueSpace761Std updates.
The differences is the path for the Output - Render File, and so they are saved that way.
I entered a different Description for each scene with the version and program.
Y4tSv.0.9.5
trueSpaceBeta 7.61
Y4tSv.0.9.5
Rosetta Beta 7.61

Hope you do not mind!
I made a small change to the CreatePythonSync.RsObj for the Alert.

trueBlue wrote: 23 Aug 2019, 16:05 Thanks!
I have uploaded the changes to the Update(S)
In case you do not know, the YafaRay4tS.RsObj in the Yafaray Folder.RsObj and the YafaRay4tS.RsScn files are different in trueSpace 761 and trueSpace761Std updates.
The differences is the path for the Output - Render File, and so they are saved that way.
I entered a different Description for each scene with the version and program.
Y4tSv.0.9.5
trueSpaceBeta 7.61
Y4tSv.0.9.5
Rosetta Beta 7.61

Hope you do not mind!
I made a small change to the CreatePythonSync.RsObj for the Alert.
Alert.PNG

I don't mind.
FYI, Output - Render File connector reset was fixed, so you could open the file in either version and reset the connector. So if I take your YafaRay4tS.RsScn file from Full into Rosetta and pressed the reset it would be the same as the Rosetta specific YafaRay4tS.

Thanks!
Yeah, I knew that, just wanted it to work right out of the box.
Could have swore (can not find it, maybe it was in the Update 4) that either the Display or iOpti viewer had a toolbar that used your Clintons3D Package/Utility functions to save images in different formats verses the present Library2.DlgGenericSave('', Space.CurrentScene() + "/YafaRay4tS/tSDisplay/Image", 3); command.
Not sure using this command is a good idea, depending on what is presently selected or not selected in trueSpace.
Seems to me that being able to save images in different formats would be much better!

I found the difference from the update 4 and update 5
In update 4 the Display was named Image But doing so causes an error. So you have to change the word Display to Image in all of the connected OpenOptDetectorFrame scripts.

There's nothing in Clintons3D Package/Utility functions to directly save images in different formats. Both v0.9.0 and v0.9.5 have a Library2.DlgGenericSave button on the ioptDisplay window.

edit:
v0.9.0 has image formats in the list and v0.9.5 seems to be missing the images formats

Cross Post
See the previous post

I see, that's why the image formats are missing.

trueBlue wrote: 23 Aug 2019, 17:14 ...
So you have to change the word Display to Image in all of the connected OpenOptDetectorFrame scripts.

Actually, you just change the button to use Display instead of Image.

Trying to reply about using your plugin with code but:

Look at the Save As script in Preferences/Save As Object

trueBlue wrote: 23 Aug 2019, 17:40 Trying to reply about using your plugin with code but:
Capture.PNG

That's strange, try again.

trueBlue wrote: 23 Aug 2019, 17:47
Look at the Save As script in Preferences/Save As Object

Ok, I'm looking at it, now what?

clintonman wrote: 23 Aug 2019, 18:09

trueBlue wrote: 23 Aug 2019, 17:47
Look at the Save As script in Preferences/Save As Object

Ok, I'm looking at it, now what?

clintonman wrote: 23 Aug 2019, 18:09 There's nothing in Clintons3D Package/Utility functions to directly save images in different formats.

I remember using it for image formats in YafaRay4tSv9.0 but con not find it anywhere.

What do you think about using tS761's render to File?
Added benefit of saving at different sizes might be a good thing! And or YafaRay4tS's Render to File. But then you lose the Presets.
Edit: Forget YafaRay4tS's Render to File because if you render to say like the Desktop it brings with it the Yaf_render.cmd and changes the Output Render File path. Ugh!
Edit2: Render to File just renders a snapshot of 3D Space including the grid, lights, camera, and objects. Not the rendered file.

trueBlue wrote: 23 Aug 2019, 16:57 Thanks!
Yeah, I knew that, just wanted it to work right out of the box.
Could have swore (can not find it, maybe it was in the Update 4) that either the Display or iOpti viewer had a toolbar that used your Clintons3D Package/Utility functions to save images in different formats verses the present Library2.DlgGenericSave('', Space.CurrentScene() + "/YafaRay4tS/tSDisplay/Image", 3); command.
Not sure using this command is a good idea, depending on what is presently selected or not selected in trueSpace.
Seems to me that being able to save images in different formats would be much better!

That command, Library2.DlgGenericSave('', Space.CurrentScene() + "/YafaRay4tS/tSDisplay/Image", 3);, is set to export the image node, so it doesn't matter if anything else is selected.

DlgGenericSave ( szFileName,szTargetName,dwFlags)
szFileName is '', so it opens a dialog
szTargetName is Space.CurrentScene() + "/YafaRay4tS/tSDisplay/Image". If it was blank then it would save the current selection
dwFlags is 3, so it allows synchronous and asynchronous save - whatever that means

Thanks for the clarification.
I have made the following modification in the tSDisplay I have also updated the YafaRay4tS.RsScn
Added an Auto Run script that copies the YafaRay4tS.RsObj from the Yafaray Folder to the Space.CurrentScene()

I have uploaded theses changes to trueSpace 7.61 Beta 8 Unofficial Update 5 'Beta' and trueSpace 7.61 Beta 8 Std Unofficial Update 5 'Beta' threads

trueBlue wrote: 24 Aug 2019, 16:33 Thanks for the clarification.
I have made the following modification in the tSDisplay
Capture.PNG
I have also updated the YafaRay4tS.RsScn
Added an Auto Run script that copies the YafaRay4tS.RsObj from the Yafaray Folder to the Space.CurrentScene()

I have uploaded theses changes to trueSpace 7.61 Beta 8 Unofficial Update 5 'Beta' and trueSpace 7.61 Beta 8 Std Unofficial Update 5 'Beta' threads

When does the autorun script run or is the autorun a part of the updated YafaRay4tS scene?

The Run.RsObj is included with the scene.
It is set to 'Run automatically' when the scene loads.
It copies the YafaRay4tS.RsObj from the Yafaray Folder to the scene and deletes itself.
This was necessary to get the user's (saved) YafaRay4tS.RsObj.
I made a mistake in the previous scene by including the YafaRay4tS.RsObj in the scene.