United3dArtists Archive

clintonman · Post by **clintonman** » 13 Jun 2018, 22:21

trueBlue wrote: 13 Jun 2018, 22:06 ...
Lighting Method Switch
Disconnecting/Reset the 'Change detect'/Reconnecting the Watch Dog before saving the Yafaray Folder seems to help.
I have tested this several times today by Reseting the Context after performing the above. So far it works everytime.
You know best, so whatever you decide. Not working sometimes is not good.

Watch dogs have given me troubles in the past but it looks like it effects you even more. Can you try this script to see if it switches the stubborn lighting model?
Also the script reads special folders for desktop and documents, maybe we default renders to the users documents, or use that path to get to the users pictures folder.

trueBlue · Post by **trueBlue** » 13 Jun 2018, 22:13

clintonman wrote: 13 Jun 2018, 21:51 I think the yafaray and render paths should not have a default value. There is no installer for Yafaray so it can potentially be anywhere. even Blender comes with installer and not installer options so can't depend on the blender scripts location either.

The sharing of scenes is a pain. I think add a button that will read the render path and yafaray path from the saved yafaray4ts node would make it easier.

For rendering maybe we have it default to a folder inside truespace if the path is blank or does not exist.

another option maybe read some kind of path from the registry.

Well as you know, presently it is set to a path from a previous version.
Folder inside tS sounds great. Easy to get to. One for Animation and one for Images. Even better would be like tS's Render to File

It is possible to create a Popup panel just like this.

trueBlue · Post by **trueBlue** » 13 Jun 2018, 22:06

clintonman wrote: 13 Jun 2018, 21:37
trueBlue wrote: 13 Jun 2018, 19:14 Yafaray toolbar - Yafaray Settings
This is not working for me and I remember bringing this up before.
It looks like a Watch Dog problem.
When I select the above icon it does not run:
Code: Select all
Activity.Run(Space.CurrentScene() + "/YafaRay4tS/Lighting Method Switch")
portion of the command.

Wondering if it would be better to run:
Code: Select all
UserInterface.OpenToolPanelViewEx2("" , "" ,Space.CurrentScene()+"/YafaRay4tS", 10, 1, 0);
Like you said the problem is the watchdog. The script that gets called does run the Userinterface... command.
I think the easiest solution is to have an extra button to push for when it gets stuck. The button would just run the command directly or actually maybe better to run the watchdog which would "wake it up" for future use.

Lighting Method Switch
Disconnecting/Reset the 'Change detect'/Reconnecting the Watch Dog before saving the Yafaray Folder seems to help.
I have tested this several times today by Reseting the Context after performing the above. So far it works everytime.
You know best, so whatever you decide. Not working sometimes is not good.

clintonman · Post by **clintonman** » 13 Jun 2018, 21:51

I think the yafaray and render paths should not have a default value. There is no installer for Yafaray so it can potentially be anywhere. even Blender comes with installer and not installer options so can't depend on the blender scripts location either.

The sharing of scenes is a pain. I think add a button that will read the render path and yafaray path from the saved yafaray4ts node would make it easier.

For rendering maybe we have it default to a folder inside truespace if the path is blank or does not exist.

another option maybe read some kind of path from the registry.

clintonman · Post by **clintonman** » 13 Jun 2018, 21:37

trueBlue wrote: 13 Jun 2018, 19:14 Yafaray toolbar - Yafaray Settings
This is not working for me and I remember bringing this up before.
It looks like a Watch Dog problem.
When I select the above icon it does not run:
Code: Select all
Activity.Run(Space.CurrentScene() + "/YafaRay4tS/Lighting Method Switch")
portion of the command.

Wondering if it would be better to run:
Code: Select all
UserInterface.OpenToolPanelViewEx2("" , "" ,Space.CurrentScene()+"/YafaRay4tS", 10, 1, 0);

Like you said the problem is the watchdog. The script that gets called does run the Userinterface... command.
I think the easiest solution is to have an extra button to push for when it gets stuck. The button would just run the command directly or actually maybe better to run the watchdog which would "wake it up" for future use.

trueBlue · Post by **trueBlue** » 13 Jun 2018, 19:29

I have made these changes if you are interested:

YafaRay4tS panel
Yaf_Path - Additional Combo Control for entering Blender and Standalone paths.

Libraries
Added version "Y4tSv.0.9.0" to the library Discriptions for all nodes.
YafaRay4tS scene and light setup - Changed the Spot light's color to 140 140 140

Update YafaRay Render Node script
Changed the Alert to "Conversion to YafaRay4tS v0.9.0 complete."
Incorporated it into a Popup.

Render node
Changed defauts:
params.Param('vtData') = "C:" + "\\" + "Program Files" + "\\" + "yafaray_v3" + "\\" + "bin" + "\\" + "yafaray-xml.exe";
params.Param('vtData') = "C:" + "\\" + "Temp" + "\\" + "yaf_test.png";

Lighting Method Switch
Disconnecting/Reset the 'Change detect'/Reconnecting the Watch Dog before saving the Yafaray Folder seems to help.

trueBlue · Post by **trueBlue** » 13 Jun 2018, 19:14

Yafaray toolbar - Yafaray Settings
This is not working for me and I remember bringing this up before.
It looks like a Watch Dog problem.
When I select the above icon it does not run:

Code: Select all

Activity.Run(Space.CurrentScene() + "/YafaRay4tS/Lighting Method Switch")

portion of the command.

Wondering if it would be better to run:

Code: Select all

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

trueBlue · Post by **trueBlue** » 13 Jun 2018, 16:01

Misc aspect - Restore Defaults
Changes Yafaray install path to:
C:\Program Files\YafaRay\yafaray-xml.exe
Up to you, but my thought is to not change that as it creates an Alert "Unable to find YafaRay. Is it installed?"
Or change it to the Standalone path?
C:\Program Files\yafaray_v3\bin\yafaray-xml.exe

Kind of a pain to always have to change that path with old scenes etc...
To the left of the insatll path is a > text control "Yaf_Path", if you right click it select Reset does the same thing as above.
Could make that a Bitmap Button Control - LMB = Standalone path / RMB = Blender path

Or add a Combo Control underneath

: Capture.PNG (16.22 KiB) Viewed 5098 times

Your Update YafaRay Render Node script
The Alert reads:
System.Alert("Conversion to YafaRay4tS v0.8.0 complete.");

the_ant · Post by **the_ant** » 13 Jun 2018, 15:07

Thanks treuBlue...i'll wait for that..

trueBlue · Post by **trueBlue** » 13 Jun 2018, 15:03

the_ant wrote: 13 Jun 2018, 14:51 Help me!...little confuse in the maze of upgrades...how can i set tsp761 with UnoffUpg by TrueBlue within vRay and YafaRay last functions ?

As for the Unofficial Update 4, I would wait until it is released with the YafaRay4tS. I will post when it is ready and upload it here :
viewforum.php?f=55

trueBlue · Post by **trueBlue** » 13 Jun 2018, 14:56

Just noticed two things with the Update v5
Yafaray scene and light setup.
The first spot light is messed up, not sure why that happened. Still investigating why.
The Material Editor was saved with Vray enabled. That is fixed. Not released yet.

the_ant · Post by **the_ant** » 13 Jun 2018, 14:51

Help me!...little confuse in the maze of upgrades...how can i set tsp761 with UnoffUpg by TrueBlue within vRay and YafaRay last functions ?

trueBlue · Post by **trueBlue** » 13 Jun 2018, 13:27

Just realized I did not save the scene and ight setup with the new lights.
Basically they are just missing the new mesh for the spot lights.

clintonman · Post by **clintonman** » 13 Jun 2018, 03:38

Web page has temporary content until the next release with the new lights etc.
2 changes required by users is change yararay folder and render location. will be sure to note it.

trueBlue · Post by **trueBlue** » 13 Jun 2018, 03:34

Update v5
viewtopic.php?t=5446&p=52492#p52492
Dam! Forgot to save the lights in the Library. Edit: Fixed and uploaded again.
Lights in the primitives are good to go.

trueBlue · Post by **trueBlue** » 13 Jun 2018, 03:06

No.
Edit: Okay Ill upload the changes in a few.
Edit2: Just so you know incase you want to advise users that they may have to change the settings in Setup.
All three scenes are same absorbscatter.

clintonman · Post by **clintonman** » 13 Jun 2018, 03:01

trueBlue wrote: 13 Jun 2018, 02:52 I know the mesh is exported as an output. I was referring to Latitude, Longitude, and Size that are exported out as inputs. I will not mess with the Sphere light. I was wanting to change the Point light's shape though. It is not hooked up to anything except like mentioned above. Makes no sense that they are of any value other letting a user change it's size. But I am not sure.
I have fixed the Light's matrix values.
Also changed the Shapes for the Sun, Directional, IES Spot, and Spot. Same as the new tS lights.

The scene should be in the YafaRay4tS Setup library

Ok I see it.
Did you change the mesh for the area light? If so the export will need to be redone to match it.

Edit: Yafaray doesn't care about the point light mesh or mesh inputs. So you can do whatever you want to it's shape.

clintonman · Post by **clintonman** » 13 Jun 2018, 02:58

I'm setting up a web page for the samples scenes. Has temp content now.

http://clintons3d.com/plugins/truespace ... faray.html

trueBlue · Post by **trueBlue** » 13 Jun 2018, 02:52

I know the mesh is exported as an output. I was referring to Latitude, Longitude, and Size that are exported out as inputs. I will not mess with the Sphere light. I was wanting to change the Point light's shape though. It is not hooked up to anything except like mentioned above. Makes no sense that they are of any value other letting a user change it's size. But I am not sure.
I have fixed the Light's matrix values.
Also changed the Shapes for the Sun, Directional, IES Spot, and Spot. Same as the new tS lights.

The scene should be in the YafaRay4tS Setup library

clintonman · Post by **clintonman** » 13 Jun 2018, 02:39

Shot from Blender sphere light.
I will be adding an option to the light for exporting the mesh or not after you get the update squared away with the lost changes etc.

Edit: My mistake, there is already an option to render the mesh or not.

Edit: Did some test renders and it does get brighter when it gets bigger.

clintonman · Post by **clintonman** » 13 Jun 2018, 02:33

trueBlue wrote: 13 Jun 2018, 01:06 With the included YafaRay4tS scene I just did a test and changed to color for both Spot lights, 140 140 140. Does not seem to change the render so much but that is pretty close to what tS looked like before. Less bright.

Just noticed the several lights are still messed up. I will fix it with the next update.
I guess my changes did not get saved. Errrrr

With the Yaf Sphere light and Yaf Point light, does the Sphere mesh's attribute need to be exported and does the size matter?
Size is connected to the color multiplier too, is that necessary?

I dont see any included YafaRay4tS scene. Where do I find it.
All tS lights, not just Yaf lights have their mesh exported.
Size of the sphere light is used in the render.
Don't know about the size connection to the color multiplier. I can only image it's there for a reason. Bigger==Brighter? If so then it needs to be connected to reflect the changes in the preview. Only way to tell is if you do some renders with different values and see if it's needed or not.
The mesh of the sphere is written to the renderer to make the light visible. It's an option in Blender. In tS it always makes a mesh.

trueBlue · Post by **trueBlue** » 13 Jun 2018, 01:06

With the included YafaRay4tS scene I just did a test and changed to color for both Spot lights, 140 140 140. Does not seem to change the render so much but that is pretty close to what tS looked like before. Less bright.

Just noticed the several lights are still messed up. I will fix it with the next update.
I guess my changes did not get saved. Errrrr

With the Yaf Sphere light and Yaf Point light, does the Sphere mesh's attribute need to be exported and does the size matter?
Size is connected to the color multiplier too, is that necessary?

trueBlue · Post by **trueBlue** » 13 Jun 2018, 00:35

New update
viewtopic.php?t=5446&p=52492#p52492

trueBlue · Post by **trueBlue** » 12 Jun 2018, 23:48

clintonman wrote: 12 Jun 2018, 23:15
trueBlue wrote: 12 Jun 2018, 22:33 Fixed the button.
YafaRay4tS Scene Lights light setup
Just notced that the Lights were different using the newest installation B4.
It loads the Lights from the Setup library.
So I am in the process of fixing that. When I exchanged the lights with the new lights, the scene became extremely bright.
The only thing I can see that is different from the old spot lights using the Spot Preferences is the Spot light's Constant was changed from 5 to 8. Changing them back to 5 makes it even brighter.

Yafaray Lights in the libray and primitives
Also noticed that the lights in the primitives and libray had their matrix values all different.
Meaning that when you load them with the widget, some point up. etc...
I fixed all of them so they match tS lights. So now the primitives and library lights all match.
Thinking now that we do not even need the Yafaray Lights library except for the installation.
May be use the Yafaray Lights library for some light setups?
Sounds good.

The lights need to match the renders.
Be sure to do test renders when changing the light attributes, otherwise it'll look good in tS and not so good when you render. There's plenty of room for variation, since I couldn't find settings that really matched up closely. Radical changes will break it though.

I noticed that you used a bitmap control for the button to get nice highlighting. It was made for the big square buttons with icons, so if you made some kind of image and applied it to the button that might make it readable and highlightable. Just a thought...

I have used this image before for the Bitmap Button Control as well as icons.

: Button.PNG (217 Bytes) Viewed 4263 times

I like that control because you can have a tooltip, left, and right commands. But I am with you, do not like that is not 3D and that hiduous horzontal what ever you want to call it.

trueBlue · Post by **trueBlue** » 12 Jun 2018, 23:39

That was just a test.
All the lights have the same light attributes that are in your last installation B4 except the matrix values.

I saved the lights in the library from the primitives so they are in sync. Also did a little panel editing with the lights.
I will upload what I have in the present Update 4.
I guess you will be able to harvest what you need for your installer from that. OR?

clintonman · Post by **clintonman** » 12 Jun 2018, 23:20

trueBlue wrote: 12 Jun 2018, 22:33 ...
The only thing I can see that is different from the old spot lights using the Spot Preferences is the Spot light's Constant was changed from 5 to 8. Changing them back to 5 makes it even brighter.

...

Sounds like you're changing the lights, did you change them back?

trueBlue · Post by **trueBlue** » 12 Jun 2018, 23:18

I am not changing anything except the matrix values.

clintonman · Post by **clintonman** » 12 Jun 2018, 23:15

trueBlue wrote: 12 Jun 2018, 22:33 Fixed the button.
YafaRay4tS Scene Lights light setup
Just notced that the Lights were different using the newest installation B4.
It loads the Lights from the Setup library.
So I am in the process of fixing that. When I exchanged the lights with the new lights, the scene became extremely bright.
The only thing I can see that is different from the old spot lights using the Spot Preferences is the Spot light's Constant was changed from 5 to 8. Changing them back to 5 makes it even brighter.

Yafaray Lights in the libray and primitives
Also noticed that the lights in the primitives and libray had their matrix values all different.
Meaning that when you load them with the widget, some point up. etc...
I fixed all of them so they match tS lights. So now the primitives and library lights all match.
Thinking now that we do not even need the Yafaray Lights library except for the installation.
May be use the Yafaray Lights library for some light setups?

Sounds good.

The lights need to match the renders.
Be sure to do test renders when changing the light attributes, otherwise it'll look good in tS and not so good when you render. There's plenty of room for variation, since I couldn't find settings that really matched up closely. Radical changes will break it though.

I noticed that you used a bitmap control for the button to get nice highlighting. It was made for the big square buttons with icons, so if you made some kind of image and applied it to the button that might make it readable and highlightable. Just a thought...

trueBlue · Post by **trueBlue** » 12 Jun 2018, 22:33

Fixed the button.
YafaRay4tS Scene Lights light setup
Just notced that the Lights were different using the newest installation B4.
It loads the Lights from the Setup library.
So I am in the process of fixing that. When I exchanged the lights with the new lights, the scene became extremely bright.
The only thing I can see that is different from the old spot lights using the Spot Preferences is the Spot light's Constant was changed from 5 to 8. Changing them back to 5 makes it even brighter.

Yafaray Lights in the libray and primitives
Also noticed that the lights in the primitives and libray had their matrix values all different.
Meaning that when you load them with the widget, some point up. etc...
I fixed all of them so they match tS lights. So now the primitives and library lights all match.
Thinking now that we do not even need the Yafaray Lights library except for the installation.
May be use the Yafaray Lights library for some light setups?

clintonman · Post by **clintonman** » 12 Jun 2018, 18:46

Can you get rid of the horizontal highlight. It's hard to read and the button doesn't even look like a button.

trueBlue · Post by **trueBlue** » 12 Jun 2018, 17:35

The one that sets the DOF Distance

: Capture.PNG (11.53 KiB) Viewed 4289 times

Here is the new one

clintonman · Post by **clintonman** » 12 Jun 2018, 17:00

trueBlue wrote: 12 Jun 2018, 14:12 Not really happy with how the Yaf Camera loads into trueSpace.
Thought I would remove it from the Yafaray Library and include it in the Camera Primitives.
Code: Select all
RsTool.AddPrimitive('/Widgets/Tools/Primitives/Primitive tool','{B1D12AD1-47D4-4e6c-8227-DC80FF55D7BB}{A46795D3-0DE2-4ed8-9FB6-91D84FB9F1EB}(/Preferences/Cameras/Factory preferences){/Preferences/Lights/Preferences}','/Preferences/Cameras/Yafaray Camera');
Does renaming it from Yaf Camera to Yafaray Camera a problem?
Also if you do not mind I was practicing your DRY method.
...

Cute.

, nope, renaming has no effect and I like the idea off "keeping it dry"

and moving it to be with the other camera(s).

trueBlue wrote: 12 Jun 2018, 14:12 ...
Is it okay if I move your Start selection script to a button?
Yafaray Camera.PNG

What is the Start selection script?

trueBlue · Post by **trueBlue** » 12 Jun 2018, 14:12

Not really happy with how the Yaf Camera loads into trueSpace.
Thought I would remove it from the Yafaray Library and include it in the Camera Primitives.

Code: Select all

RsTool.AddPrimitive('/Widgets/Tools/Primitives/Primitive tool','{B1D12AD1-47D4-4e6c-8227-DC80FF55D7BB}{A46795D3-0DE2-4ed8-9FB6-91D84FB9F1EB}(/Preferences/Cameras/Factory preferences){/Preferences/Lights/Preferences}','/Preferences/Cameras/Yafaray Camera');

Does renaming it from Yaf Camera to Yafaray Camera a problem?
Also if you do not mind I was practicing your DRY method.

Is it okay if I move your Start selection script to a button?

: Yafaray Camera.PNG (11.46 KiB) Viewed 4288 times

clintonman · Post by **clintonman** » 12 Jun 2018, 01:23

trueBlue wrote: 12 Jun 2018, 01:13 Will do. Just posting here as any updates pertain to Yafaray4tS only/ I am done with any further updates other then Yafaray4tS.

Thanks, 3rd time was the charm. I tried the update page version and it was too old, then the download a couple of pages back and it was a bad download. Downloaded again and all is good now.
Next I'm going to clean up the sample scenes and post them. A lot of them have oldish versions of the Yaf node and materials. Then comes documentation.

trueBlue · Post by **trueBlue** » 12 Jun 2018, 01:13

Will do. Just posting here as any updates pertain to Yafaray4tS only/ I am done with any further updates other then Yafaray4tS.

clintonman · Post by **clintonman** » 12 Jun 2018, 00:51

Sounds good. I have one more request. Can you version your uploads until the final release? Something like "tS7.61B8.4.Preview9" and then just remove the "Preview" postfix when it's done. It would be easier to see the updates, especially at the rate you are making changes.
Did you udate the main post or just the post a couple of pages back from this post?
I'll download both.

trueBlue · Post by **trueBlue** » 11 Jun 2018, 22:19

I uploaded the changes you requested.
If you right click the Library Place in the Material Editor the Yafaray Materials become available in the RS Main Library place.
Or are you wanting them to be in the D3D Materials library place? Edit: Included in both places

Edit: Updated the update 4 to include all recent changes.
Right click the Library Place to enable Yafaray Materials and Components - Compositing in the D3D Materials library place.
Also put links to download Yafaray v3.3.0 in the About aspect

clintonman · Post by **clintonman** » 11 Jun 2018, 20:14

trueBlue wrote: 11 Jun 2018, 18:13 Here is my contribution to all your hard work. Thank YOU!
YafaRay toolbar buttons
Added OfflineRender.OpenPreferencesPanel() commands where appropriate.
Added Apply/Remove Smooth Normals button.
Capture.PNG
Has not been fully tested and no safe guard code is included. IE if node.exist etc...
Seems to work thus far without errors.

Edit: Changed the Render Setting buttons.

Added Activity.Run("/Yafaray Folder/YafaRay4tS/Switch2Yafaray");OfflineRender.OpenPreferencesPanel()

Added the Switch2Yafaray script to the included Yafaray Folder.

Looks good. Don't see any issues here.

I do have a request. How about buttons for the yafaray camera and the volume object. They exist in the YafaRay4tS Setup library. Also would it be possible to add the Yaf materials library to the material editor list?

trueBlue · Post by **trueBlue** » 11 Jun 2018, 18:13

Here is my contribution to all your hard work. Thank YOU!
YafaRay toolbar buttons
Added OfflineRender.OpenPreferencesPanel() commands where appropriate.
Added Apply/Remove Smooth Normals button.

: Capture.PNG (4 KiB) Viewed 4247 times

Has not been fully tested and no safe guard code is included. IE if node.exist etc...
Seems to work thus far without errors.

Edit: Changed the Render Setting buttons.
Added Activity.Run("/Yafaray Folder/YafaRay4tS/Switch2Yafaray");OfflineRender.OpenPreferencesPanel()
Added the Switch2Yafaray script to the included Yafaray Folder.

Edit2: Added Yafaray Camera and Yafaray Volume buttons
Edited the YafaRay4tS panel, mostly the bottom portion Output - Render File to be consistent on all aspects.

: YafToolbar.PNG (3.92 KiB) Viewed 4232 times

clintonman · Post by **clintonman** » 11 Jun 2018, 16:47

trueBlue wrote: 11 Jun 2018, 15:02
clintonman wrote: 11 Jun 2018, 14:33 Got it.
Does the C3DReset work with Vray installed?
Yes. So far I have only tested installing this update to a fresh tS761 installation and then just now installed Vray and Reset the Default Context. Switched back and forth rendering from YafaRay4tS and Vray. Not seeing any problems so far.

Off topic, Rendering a Sphere from either Camera or View looks squashed in the internal Display. The image opened in a Photo Editor looks fine. 500x500

Internal viewer isn't square so square picture will be squashed. iopti viewer doesn't have that problem. that's reason support was added for it.

trueBlue · Post by **trueBlue** » 11 Jun 2018, 15:02

clintonman wrote: 11 Jun 2018, 14:33 Got it.
Does the C3DReset work with Vray installed?

Yes. So far I have only tested installing this update to a fresh tS761 installation and then just now installed Vray and Reset the Default Context. Switched back and forth rendering from YafaRay4tS and Vray. Not seeing any problems so far.

Off topic, Rendering a Sphere from either Camera or View looks squashed in the internal Display. The image opened in a Photo Editor looks fine. 500x500

clintonman · Post by **clintonman** » 11 Jun 2018, 14:55

Did some quick tests and it's looking good.

clintonman · Post by **clintonman** » 11 Jun 2018, 14:50

clintonman wrote: 08 Jun 2018, 03:37 ...
Latest Yafaray v3.3.0 can be found here: https://github.com/YafaRay/Blender-Exporter/releases
and here: https://github.com/YafaRay/Core/releases
One is made to work with Blender and the other is standalone, either one will work.
...

This was several pages back so decided to repost these links.

clintonman · Post by **clintonman** » 11 Jun 2018, 14:39

trueBlue wrote: 11 Jun 2018, 08:06 Here is the update for trueSpace 7.61
Yafaray4tS B4 included
...

I think something is missing. I see the libraries and toolbar but no actual yafaray4ts. The only yafaray buttons that work are the yafara lights.

Edit:
Nevermind, forgot to reset to default context

clintonman · Post by **clintonman** » 11 Jun 2018, 14:33

Got it.
Does the C3DReset work with Vray installed?

trueBlue · Post by **trueBlue** » 11 Jun 2018, 08:06

Here is the update for trueSpace 7.61
Yafaray4tS B4 included
Added a YafaRay4tS scene and layout
Updated the D3D to Yafaray script in the Material Editor
Updated the tS761 Toolbars.RsObj
Updated the Toolbars.RsObj
Changed the PostReset to C3DReset and moved some of the commands to the reset.js file

C3DReset is as follows

Code: Select all

function Execute(params)
{
Activity.Run("Scripts/ReloadCustomScripts");
if (!Node.Exists("/Offline renderers")) {
RsFileIO.LoadObject(System.GetMainDir() + '\\scripts\\preObjects\\Offline renderers.RsObj', '/');
try {
Node.Create("Clintons3D Package/Yafaray", "/Offline renderers");
} catch (err) {
System.Trace("Error: Clintons3D Package plugin should be installed first");
}
}
if (!Node.Exists("/Offline renderers/Yafaray")) {
try {
Node.Create("Clintons3D Package/Yafaray", "/Offline renderers");
} catch (err) {
System.Trace("Error: Clintons3D Package plugin should be installed first");
}
}
Node.Delete(System.ThisName())
}

The above changes were made because several times the Yafaray render node was being created in System without the Offline renderers node using the PostReset script.

Edit: Added Yafaray Materials to the Material Editor
Right click the Library Place to enable Yafaray Materials and Components - Compositing in the D3D Materials library place
Added New Yafaray toolbar buttons

Edit4: All lights have been modified in primitives and the library
Yafaray Camera is a primitive now
Scene, and Light setup has the new lights

Edit5: Fixed the Lights again.

Edit6:
tS7.61B8.4_YafaRay4tS9_6

YafaRay4tS panel
Animation - Added Width and Height

Libraries
Added version "Y4tSv.0.9.0" to the library Discriptions for all nodes.
YafaRay4tS scene and light setup - Changed the Spot light's color to 140 140 140

Update YafaRay Render Node script
Changed the Alert to "Conversion to YafaRay4tS v0.9.0 complete."
Incorporated it into a Popup.

Render node
Changed defauts:
params.Param('vtData') = "C:" + "\\" + "Program Files" + "\\" + "yafaray_v3" + "\\" + "bin" + "\\" + "yafaray-xml.exe";
params.Param('vtData') = "C:" + "\\" + "Temp" + "\\" + "yaf_test.png";

Lighting Method Switch
Disconnecting/Reset the 'Change detect'/Reconnecting the Watch Dog before saving the Yafaray Folder seems to help.
Update4:
Add Render Scene icon to the Material Editor.
Changed loading the Tube object to a primitive. Only for loading, does not work like other widgets.

Edt7:
tS7.61B8.4_YafaRay4tS9_7
Updated Clintons3dPlugin.rsx v.1638412
Image Folder and Animation Folder added to the main directory for rendering images, both include an Image.png.
D3DView.RenderToFile.Settings.xml added that is set to the Image Folder
YafaRay4tS panel updated 6/15/2018

clintonman · Post by **clintonman** » 11 Jun 2018, 06:24

Updated installer:
Fixed DOS window stuck open
Unhides error message about tga files that comes from the TGA_Viewer executable
Selects Yafaray as the offline renderer during the install
Does not delete Yaf toolbar when uninstalling
after setup opens to the setup tab

ContextSurvival script:
copies PostReset script to the preobjects and alters the reset.js file to use it

PostReset script:
option to open extra toolbars during context reset
deletes itself if loaded to "/"

clintonman · Post by **clintonman** » 11 Jun 2018, 04:00

trueBlue wrote: 10 Jun 2018, 15:11 ...

With the YafaraytS installation, if you run the installation after it is installed it throws an error.
Yafaray4tS Reinstall.PNG
To fix that, if you add a check for the file version on the AboutBitmap's attribute 'YafaRay4tS_Version', and create a Question Yes/No/Cancel
Yes = "Would you like to run the Uninstall?"
No = Delete the script
Cancel = Delete the script

...

Not seeing that here. That error usually happens if a file or folder is active and open.
I ran installer 3 times without any file permission errors.

clintonman · Post by **clintonman** » 11 Jun 2018, 02:32

Found a fix for the DOS window not closing. Inside RenderFnSet node is code to run the TGA viewer. Adding "start" to the beginning of the command makes the window close after starting the TGA_Viewer.exe file.

Code: Select all

	if (Yaf_UseExternalViewer == true) {
		if (Yaf_FileType == 'tga')
			//File.WriteLine(System.GetMainDir() + '\\TGA_Viewer.exe "' + Yaf_RenderFilename + '"');
			File.WriteLine('start ' + System.GetMainDir() + '\\TGA_Viewer.exe "' + Yaf_RenderFilename + '"');
	}

trueBlue · Post by **trueBlue** » 11 Jun 2018, 00:15

Hummm… just tested the default setup.

First run, the MS DOS opened (Even though it was suppose to be minimized) took a while but finally displayed the TGA in the Display. Second run no MS DOS window and displayed the TGA.

Now that I remember, it was when I first installed Beta1 and used an existing TGA file in my Temp directory that was from a previous install.

clintonman · Post by **clintonman** » 10 Jun 2018, 23:59

trueBlue wrote: 10 Jun 2018, 23:53 Up to you. And change the default Setup - C:\Temp\yaf_test.tga to PNG? As that is the biggest problem because the Internal Display is the default presently.

I'm not seeing any problems with the internal viewer at all.
Does the window not display?
Does it open then not show anything?
Do yo have external view also selected when doing internal view?

clintonman · Post by **clintonman** » 10 Jun 2018, 23:57

"When you use the Internal Viewer you have to change the file image type, and does not support a TGA image?
This causes a problem with the default Setup - C:\Temp\yaf_test.tga, the MS DOS window hangs. "

Internal viewer supports formats other than tga so not seeing the first sentence.

Had to do a bunch of testing to see second part. If external renderer is selected, then the Dos windows hangs. Internal Viewer had no hanging DOS windows.

trueBlue · Post by **trueBlue** » 10 Jun 2018, 23:53

Up to you. And change the default Setup - C:\Temp\yaf_test.tga to PNG? As that is the biggest problem because the Internal Display is the default presently.

clintonman · Post by **clintonman** » 10 Jun 2018, 23:38

"Off topic, I do not remember this being an issue, when you use the TGA viewer, you need use a TGA image."

This is verified. Manual run from the command window shows error message from TGA Viewer. It can open other formats but only accepts tga on the command line.

As it is now there is code in truespace is stopping it from even attempting to start TGA viewer.

Possible solution:
We can add a warning for this case, something like "TGA Viewer will only open tga files. You will have to open the file manually, do you wish to continue?"
If they say yes, they will get the error from the TGA Viewer, then theTGA Viewer will open without any open file.

clintonman · Post by **clintonman** » 10 Jun 2018, 23:23

trueBlue wrote: 10 Jun 2018, 21:46 ...

Does Yafaray support DDS?

No. If you use the "..." file button on the Yafaray4tS you can expand the extensions section to see the options.

trueBlue · Post by **trueBlue** » 10 Jun 2018, 21:46

clintonman wrote: 10 Jun 2018, 19:39
trueBlue wrote: 10 Jun 2018, 17:59
clintonman wrote: 10 Jun 2018, 17:12
That may have been something I did, not knowing the limitations of the TGA viewer. I'll load up an old version and see what's up.
It is the Internal Display that I am referring to. I could be wrong but I do not remember it not supporting TGA.

From what I can tell from your code and release notes it has to do with the limitation of the BMP Transmitter?
The TGA viewer and the Optidetctors are separate. If opti is installed it uses that, if not it uses TGA viewer. Opti can display any format truespace can read. TGA I guess is limited to TGA format

Copied from the Replace Thumbnail.RsObj found in the Objects - Tutorial Objects library

Code: Select all

	// RdBitmap flags
	BFILEFMT_BMP = 0 // Save as bitmap file
	BFILEFMT_JPG = 1 // Save as jpeg
	BFILEFMT_TGA = 2 // TGA is not supported
	BFILEFMT_PNG = 3 // Save as PNG
	BFILEFMT_DDS = 4 // Save as DirectX DDS file
	BFILEFMT_PPM = 5 // PPM is not supported
	BFILEFMT_DIB = 6 // Save as Windows DIB
	BFILEFMT_HDR = 7 // Save in HDR format
	BFILEFMT_PFM = 8 // Save in Portable Pixmap format

Does Yafaray support DDS?

trueBlue · Post by **trueBlue** » 10 Jun 2018, 21:45

clintonman wrote: 10 Jun 2018, 21:22 Ok, let's start over.

I do
1.) Install the present Update 4.
2.) Important that you Reset the Default Context.
3.) Open your toolbars and try your scripts without running your Batch Installer for trueSpace7.61

I get the toolbar and the scripts.
what is supposed to happen?

Clinton quote "Explain. I don't see how to live without it. How get the toolbars back if they disappear with reset?"

I guess the confusion for you and myself is if the toolbars should be opened after a reset.
It has always been since day one that the Yafaray toolbar could be saved with a layout or load it from the library.
Also was not sure if you understood if your scripts were being reloaded.
For me with the update, I am trying to respect that maybe some users may not want to install Yafaray4tS and or your C3D toolbar.

So with that said even though they will be included, installed, and availible with the update, the toolbars do not have to be opened when a user Resets the Default Context. The user has a fresh slate and can decide whatever they want to do.

So here is what I was thinking about doing with regards to the Yafaray toolbar.
Create a YafaRay4tS layout that includes the libraries and toolbar.

Your toolbars are already covered as you just have to open them from the Gold toolbox.
And you could certainly save a layout with your toolbars opened where ever you want.
With your PostReset ALL of you scripts will reload the scripts that are available in your CustomScriptsStore folder.

trueBlue · Post by **trueBlue** » 10 Jun 2018, 21:28

Yes this is true.
The top X closes the popup window in Windows Manager.
The bottom X deletes the object in the scene.
It is not necessary to have to reset the default context.
You can delete it in the scene or open a new scene.

Never the less I will add a command that deletes it first before opening it from the library.

Thanks for the heads up.

clintonman · Post by **clintonman** » 10 Jun 2018, 21:22

Ok, let's start over.

I do
1.) Install the present Update 4.
2.) Important that you Reset the Default Context.
3.) Open your toolbars and try your scripts without running your Batch Installer for trueSpace7.61

I get the toolbar and the scripts.
what is supposed to happen?

clintonman · Post by **clintonman** » 10 Jun 2018, 21:13

If I push the red, it wont open anymore without default reset
Push green and can reopen.

trueBlue · Post by **trueBlue** » 10 Jun 2018, 21:07

Totally confused here. The tS761Toolbars and the Yafaray toolbar has nothing to do with my last post.

clintonman · Post by **clintonman** » 10 Jun 2018, 21:01

Yep, steps are:
Reset default
Push Gold Toolbar - get clintons3d toolbar
Push Red Toolbar
Push Red Toolbar inside the new toolbar
Choose YaRayToolbar from the list and push the button - get yafaray toolbar

I still prefer one step
reset default - get clintons3d toolbar and get yafaray toolbar

BTW I think there's a bug. When I close the tS761Toolbars, it won't open again unless I reset default.
Edit: It's the top x that makes it unload permanently. If you use the bottom x it will work again after closing

trueBlue · Post by **trueBlue** » 10 Jun 2018, 20:49

clintonman wrote: 10 Jun 2018, 20:15 I got the latest unofficial and the right click for default reset is in there.
In any case I'll just add a question to the PostReset script, "Do you want to reload the toolbars?"

Clinton, please try this first.

1.) Install the present Update 4.
2.) Important that you Reset the Default Context.
3.) Open your toolbars and try your scripts without running your Batch Installer for trueSpace7.61

Your Persistent install v2 for trueSpace7.61 IS part of the Update 4 for tS761B8 and tS761B8Std
As mentioned earlier some not all of your scripts and ALL of your toolbars are included.
It has been this way for several months now.
Is this not working for you, with regards to your toolbars?

clintonman · Post by **clintonman** » 10 Jun 2018, 20:15

I got the latest unofficial and the right click for default reset is in there.
In any case I'll just add a question to the PostReset script, "Do you want to reload the toolbars?"

trueBlue · Post by **trueBlue** » 10 Jun 2018, 20:02

The issue so far that I can see was mentioned here:
viewtopic.php?t=5446&start=10#p52454

With the YafaraytS installation, if you run the installation after it is installed it throws an error.
To fix that, if you add a check for the file version on the AboutBitmap's attribute 'YafaRay4tS_Version', and create a Question Yes/No/Cancel
Yes = "Would you like to run the Uninstall?"
No = Delete the script
Cancel = Delete the script

And resetting the toolbars.

clintonman · Post by **clintonman** » 10 Jun 2018, 19:42

trueBlue wrote: 10 Jun 2018, 19:33 If it makes easier, was contemplating making YafaRay4tS a permanent part of trueSpace. Maybe even including a YafaRay layout. First need to iron out any installation or uninstall issues.

Let me know what you come up with and I'll conform to it.

clintonman · Post by **clintonman** » 10 Jun 2018, 19:41

trueBlue wrote: 10 Jun 2018, 18:14
clintonman wrote: 10 Jun 2018, 17:19
trueBlue wrote: 10 Jun 2018, 15:11 ...
Also not to crazy about including the GenerateIESprofileScript.RsObj in the Yafaray Folder with the installation, but again just my opinion. LOL, I am trying to get over my OCD(S)
I get why you are doing that, it makes it simple.
...
Yep, you're gonna see a lot of that in the stuff I do. In programming there's a concept called DRY - Don't Repeat Yourself
My programmers OCD won't let me have something in 3 different places when it can live in one place. The Material Converter update posted a little while ago isn't so dry, so that will be dried up and much shorter in the final release.
Been meaning to ask you, is the convert d3d to yafaray script the only thing that changed?
The one that is included with the Material Editor update 4 is changed a little bit. I noticed that the file size of that update was bigger, and the culpert was your included Constant Shader. That image that is included in that shader is 1.5 MB. And it did not look like it was being used by any of your scripts. So I deleted ALL of the included shaders and loaded them from trueSpace instead, as an example:
Code: Select all
//tB
	shader = RsFileIO.LoadObject(System.GetMainDir() + "\\RS Main Libraries\\Shaders - Alpha Shaders\\TextureAlpha.RsMat", d3dmat);
//	shader = Node.Copy(owner + "/TextureAlpha", d3dmat);
I am pretty sure there is a different (Better) way to load them verses from the Library.

Yep, that's the only change and yesp I agree it is better to load in from disk as needed.

clintonman · Post by **clintonman** » 10 Jun 2018, 19:39

trueBlue wrote: 10 Jun 2018, 17:59
clintonman wrote: 10 Jun 2018, 17:12
trueBlue wrote: 10 Jun 2018, 15:11 ...
Off topic, I do not remember this being an issue, when you use the TGA viewer, you need use a TGA image.
When you use the Internal Viewer you have to change the file image type, and does not support a TGA image?
This causes a problem with the default Setup - C:\Temp\yaf_test.tga, the MS DOS window hangs.
That may have been something I did, not knowing the limitations of the TGA viewer. I'll load up an old version and see what's up.
It is the Internal Display that I am referring to. I could be wrong but I do not remember it not supporting TGA.

From what I can tell from your code and release notes it has to do with the limitation of the BMP Transmitter?

The TGA viewer and the Optidetctors are separate. If opti is installed it uses that, if not it uses TGA viewer. Opti can display any format truespace can read. TGA I guess is limited to TGA format

clintonman · Post by **clintonman** » 10 Jun 2018, 19:37

trueBlue wrote: 10 Jun 2018, 17:54
clintonman wrote: 10 Jun 2018, 17:01 Edit: Ok I see you have a toolbar loader. I prefer a one step process instead of reset and load one by one. The right click reset default context doesn't do anything, maybe we can do something with that: right click to reset and load all toolbars.
Not sure I am following you here. It is only an aditional tool to open tS761 toolbars.
The RMB command for the reset is as shown. That is the original command before adding the Question a long time ago per request from Tiles. Not sure why it does not work for you.

I don't have that here. Maybe that's in a later update? Will get the latest and see.

trueBlue · Post by **trueBlue** » 10 Jun 2018, 19:33

If it makes easier, was contemplating making YafaRay4tS a permanent part of trueSpace. Maybe even including a YafaRay layout. First need to iron out any installation or uninstall issues.

trueBlue · Post by **trueBlue** » 10 Jun 2018, 18:14

clintonman wrote: 10 Jun 2018, 17:19
trueBlue wrote: 10 Jun 2018, 15:11 ...
Also not to crazy about including the GenerateIESprofileScript.RsObj in the Yafaray Folder with the installation, but again just my opinion. LOL, I am trying to get over my OCD(S)
I get why you are doing that, it makes it simple.
...
Yep, you're gonna see a lot of that in the stuff I do. In programming there's a concept called DRY - Don't Repeat Yourself
My programmers OCD won't let me have something in 3 different places when it can live in one place. The Material Converter update posted a little while ago isn't so dry, so that will be dried up and much shorter in the final release.

Been meaning to ask you, is the convert d3d to yafaray script the only thing that changed?
The one that is included with the Material Editor update 4 is changed a little bit. I noticed that the file size of that update was bigger, and the culpert was your included Constant Shader. That image that is included in that shader is 1.5 MB. And it did not look like it was being used by any of your scripts. So I deleted ALL of the included shaders and loaded them from trueSpace instead, as an example:

Code: Select all

//tB
	shader = RsFileIO.LoadObject(System.GetMainDir() + "\\RS Main Libraries\\Shaders - Alpha Shaders\\TextureAlpha.RsMat", d3dmat);
//	shader = Node.Copy(owner + "/TextureAlpha", d3dmat);

I am pretty sure there is a different (Better) way to load them verses from the Library.

trueBlue · Post by **trueBlue** » 10 Jun 2018, 17:59

clintonman wrote: 10 Jun 2018, 17:12
trueBlue wrote: 10 Jun 2018, 15:11 ...
Off topic, I do not remember this being an issue, when you use the TGA viewer, you need use a TGA image.
When you use the Internal Viewer you have to change the file image type, and does not support a TGA image?
This causes a problem with the default Setup - C:\Temp\yaf_test.tga, the MS DOS window hangs.
That may have been something I did, not knowing the limitations of the TGA viewer. I'll load up an old version and see what's up.

It is the Internal Display that I am referring to. I could be wrong but I do not remember it not supporting TGA.

From what I can tell from your code and release notes it has to do with the limitation of the BMP Transmitter?

trueBlue · Post by **trueBlue** » 10 Jun 2018, 17:54

clintonman wrote: 10 Jun 2018, 17:01 Edit: Ok I see you have a toolbar loader. I prefer a one step process instead of reset and load one by one. The right click reset default context doesn't do anything, maybe we can do something with that: right click to reset and load all toolbars.

Not sure I am following you here. It is only an aditional tool to open tS761 toolbars.
The RMB command for the reset is as shown. That is the original command before adding the Question a long time ago per request from Tiles. Not sure why it does not work for you.

trueBlue · Post by **trueBlue** » 10 Jun 2018, 17:27

Before the PostReset came into play, the reset.js in the present update 4 included reloading your scripts (that are included in the update, some not all) and all of your toolbars are included in the update as well.
So they were Not lost with a reset.
Maybe you missed that part of the update. It is included in the release notes.

The only caveat is the update only included some not all of your scripts.
With your PostRest it loads all of your scripts that are present in the CustomScriptsStore, so that is even better.

Not a big deal, but it is not necessary to open the C3D toolbar with the PostReset script, thats all.

clintonman · Post by **clintonman** » 10 Jun 2018, 17:19

trueBlue wrote: 10 Jun 2018, 15:11 ...
Also not to crazy about including the GenerateIESprofileScript.RsObj in the Yafaray Folder with the installation, but again just my opinion. LOL, I am trying to get over my OCD(S)
I get why you are doing that, it makes it simple.
...

Yep, you're gonna see a lot of that in the stuff I do. In programming there's a concept called DRY - Don't Repeat Yourself
My programmers OCD won't let me have something in 3 different places when it can live in one place.

The Material Converter update posted a little while ago isn't so dry, so that will be dried up and much shorter in the final release.

clintonman · Post by **clintonman** » 10 Jun 2018, 17:12

trueBlue wrote: 10 Jun 2018, 15:11 ...
Off topic, I do not remember this being an issue, when you use the TGA viewer, you need use a TGA image.
When you use the Internal Viewer you have to change the file image type, and does not support a TGA image?
This causes a problem with the default Setup - C:\Temp\yaf_test.tga, the MS DOS window hangs.

That may have been something I did, not knowing the limitations of the TGA viewer. I'll load up an old version and see what's up.

clintonman · Post by **clintonman** » 10 Jun 2018, 17:01

trueBlue wrote: 10 Jun 2018, 15:11 ...
Not to crazy about loading the toolbars, but that is just my opinion.
Could you live without that?
...

Explain. I don't see how to live without it. How get the toolbars back if they disappear with reset?

Edit: Ok I see you have a toolbar loader. I prefer a one step process instead of reset and load one by one. The right click reset default context doesn't do anything, maybe we can do something with that: right click to reset and load all toolbars.

The button on your load toolbars is really small. I couldn't even tell it was a button at first. I think it needs something to help it stick out from the background, different color, bigger, a label.

trueBlue · Post by **trueBlue** » 10 Jun 2018, 15:11

LOL, could have sworn that I saw the mention of the PostReset before the post got messed up.

Often wondered if one could load a script with the reset.js file. Very Cool!
Still testing the PostReset, the only thing I see is when Yafaray4tS is uninstalled, the PostReset adds the Yafaray render node.
Not to crazy about loading the toolbars, but that is just my opinion.
Could you live without that?
Also in the final release, will need to delete that script upon completion.

With the YafaraytS installation, if you run the installation after it is installed it throws an error.

To fix that, if you add a check for the file version on the AboutBitmap's attribute 'YafaRay4tS_Version', and create a Question Yes/No/Cancel
Yes = "Would you like to run the Uninstall?"
No = Delete the script
Cancel = Delete the script

Also not to crazy about including the GenerateIESprofileScript.RsObj in the Yafaray Folder with the installation, but again just my opinion. LOL, I am trying to get over my OCD(S)

I get why you are doing that, it makes it simple.
Also not a big deal with the Yafaray installation when Vray is present, the installation opens the the Offline renderers, PhotoRender, and the Vray panels. I have seen you change the Combo Control's selection somewhere in your other scripts. Would be cool if you could change the Offline renderers to Yafaray.
And delete the Yafaray render node with the Uninstall.
Since I included the YafaRayBar prototype with the update, would you eliminate deleting it in the Uninstall script?
It is included in my Open trueSpace Toolbars within the Red Toolbox, which causes an error if it is not present.

Off topic, I do not remember this being an issue, when you use the TGA viewer, you need use a TGA image.
When you use the Internal Viewer you have to change the file image type, and does not support a TGA image?
This causes a problem with the default Setup - C:\Temp\yaf_test.tga, the MS DOS window hangs.

clintonman · Post by **clintonman** » 10 Jun 2018, 03:54

Oops, post got messed up. the change to reset.js is 2 lines at the end:

Code: Select all

RsFileIO.LoadObject( rosDir + '\\scripts\\preObjects\\PostReset.RsObj', scene);
ScriptObject.Execute("Project/Space 3D/PostReset");

attached is the node that it loads and runs.

trueBlue · Post by **trueBlue** » 10 Jun 2018, 01:36

Have you tested this in your reset.js file?
If so maybe you can share your reset.js file
Have not tried this yet. See the 3 comments
Not sure how to insert this code into the reset.js file as it is different then a normal script.

Code: Select all

function Execute(params)
{
[b]// tB -  Are you saying to include the above lines in the reset,js file?[/b]



	var fso = new ActiveXObject("Scripting.FileSystemObject");

	//
	//Restore Yafaray toolbar
	//
	var name=WindowsManager.GetWindowsManagerNodeName();
	if(Node.Exists("Toolbar Prototypes Encapsulator/YafaRayBar"))
		WindowsManager.OpenToolbarFromPrototype("YafaRayBar",32,32,0,0);
	Node.Rename(name+"/"+Node.SubObject(name,Node.SubObjectCount(name)-1),"YafaRayBar");
	WindowsManager.SnapFrameToFrameEx(WindowsManager.GetWorkWindow(),name+"/YafaRayBar",19,10,310,-120);
	WindowsManager.SetFrameOwnerFrame(name+"/YafaRayBar",WindowsManager.GetWorkWindow());

	//
	//Restore Yafaray Scripts
	//
	if(fso.FileExists(System.GetMainDir()+ "\\Scripts\\clintonobjects\\CustomScriptsStore\\YafarayScripts.RsObj"))
		RsFileIO.LoadObject(System.GetMainDir()+ "\\Scripts\\clintonobjects\\CustomScriptsStore\\YafarayScripts.RsObj", "/Scripts/CustomCommands");

	if(fso.FileExists(System.GetMainDir()+ "\\Scripts\\preobjects\\Yafaray Folder.RsObj"))
		RsFileIO.LoadObject(System.GetMainDir()+ "\\Scripts\\preobjects\\Yafaray Folder.RsObj", "/");

	//
	//Add Yafaray to offline renderers
	//
[b]//tB - This could be a problem given the different stages tS can be in with and without vray -> See the script I shared earlier.[/b]
	try {
		Node.Create("Clintons3D Package/Yafaray", "/Offline renderers");
	} catch (err) {
		System.Trace("Error: Clintons3D Package plugin should be installed first");
	}

	//
	//Restore Clintons Scripts
	//
	if(fso.FileExists(System.GetMainDir()+ "\\Scripts\\clintonobjects\\ReloadCustomScripts.RsObj")) {
		RsFileIO.LoadObject(System.GetMainDir() + '\\Scripts\\clintonobjects\\ReloadCustomScripts.RsObj', "Scripts");
		Activity.Run("Scripts/ReloadCustomScripts");
	}

	//
	//Restore Clintons toolbar
	//
	if(Node.Exists("Toolbar Prototypes Encapsulator/ClintonToolbar"))
		if(!Node.SubObjectCount("Toolbar Prototypes Encapsulator/ClintonToolbar") ==0){
			var name=WindowsManager.GetWindowsManagerNodeName();
			WindowsManager.CloseToolbar("ClintonToolbar");
			WindowsManager.OpenToolbarFromPrototype("ClintonToolbar",32,32,0,0);
			Node.Rename(name+"/"+Node.SubObject(name,Node.SubObjectCount(name)-1),"ClintonToolbarFrame");
			WindowsManager.SnapFrameToFrameEx(WindowsManager.GetWorkWindow(),name+"/ClintonToolbarFrame",19,10,310,-60);
			WindowsManager.SetFrameOwnerFrame(name+"/ClintonToolbarFrame",WindowsManager.GetWorkWindow());
		}

[b]// tB -  Are you saying to include the next line in the reset,js file?[/b]
}

Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0

Re: Yafaray4tS v0.9.0