I'm thinking of splashing out on it.

CHK2033 posted at 10:18PM Sat, 13 June 2020 - #4391542

Thats new (or just not released) EZScene/EZSkin4 ?

Unreleased. Untested. Undocumented. Sadly, I no longer have enough time or the necessary support network (testers etc.) for major new releases.

It'll be all I can do to update the existing stuff, so that's where I'll concentrate my energies.

LaurieA posted at 10:16PM Sat, 13 June 2020 - #4391793

You're a good man, Snarly ;)

Oh, stop it now! I have a reputation to keep up, y'know! Snarlies are ebil. Everyone knows that.

This is EZScene, the Poser addon I've been developing recently.

I can assure you it is neither redundant or merely a spillover script :)

hborre posted at 6:10PM Mon, 06 April 2020 - #4385587

I don't, just my opinion. But if you could elaborate on its purpose, I'm all ears.

Fair enough. A Poser addon is a Python script, and as such is subject to the same considerations as any other script with regard to the move to Python 3.

By virtue of its location in the special addons folder (and its adherence to certain conventions) it benefits from (a) automatically loading when Poser starts, (b) its user interface being managed by Poser, including its docked status and its location in each room and (c) access to parts of the Poser python API not readily available to regular scripts

It's certainly not perfect (addons can interfere with each other far too easily), but it's still a neat feature that I use a lot.

hborre posted at 5:06PM Mon, 06 April 2020 - #4385578

To be honest, I feel that the addon folder is just a redundant location for spillover scripts. There are scripts that simply need to be recompiled but who has the time, skill, and software to do that.

I don't think you know what Poser addons are…

false1 posted at 5:06PM Mon, 06 April 2020 - #4385570

Are addons considered scripts? That’s what I’m mostly concerned about.

Yes. Yes they are.

KarinaKiev posted at 8:24AM Wed, 25 March 2020 - #4384416

Great work, and your Python skills are what I strive to achieve, but probably never will.

Well I've forgotten so much it's quite possible I never will again either :-D

Maybe one day we'll work on something together, as I'm a huge fan of Sasha!

Cheers, Snarly

The Snow Machine code was incorporated into my EZMat script as a plugin.

Before:

After:

Kon, of course

Retrowave posted at 7:48PM Mon, 09 March 2020 - #4383023

Thanks a lot, Snarly, but which directory should I put the .py file into, and which directory for the .pyc file?

Anywhere you like - it will run from any location. If you put it into the main scriptsMenu folder (Poser Software\Poser 11\Runtime\Python\poserScripts\ScriptsMenu)it will appear in the Poser menu which will make life easier, but it isn't necessary to do so. You only need the .pyc OR the .py - the .py is just the source code for the compiled .pyc

hborre posted at 6:31PM Mon, 09 March 2020 - #4382993

There is an extensive forum discussion on VSS posted years ago when BB introduced it. There might have been a similar one at RDNA but that is entirely gone now.

@ Snarly: Will EZMat and MATHelper work with the current Poser 11? I was contemplating installing EZMat but there maybe scripts in there that no longer work with Superfly.

They do work, but I wouldn't recommend using them. I still use them, but I know how to do so safely.

They only work with Firefly shaders. They are liable to delete Superfly shaders without warning, if they are connected to a Cycles root node (it thinks they are orphans) They assume that there is a PoserSurface node and that it is the first node in the shader tree.

If you can work within those constraints then the scripts may still be useful. Otherwise, steer clear of them :)

I've been working on some new P11 scripts, and P11 versions of old scripts, but as I no longer have sufficient time to support them it's unlikely that they will be released. However, we'll see what the future holds.

MATHelper has been uploaded…

I did notice, however, that you left a message there saying to ask for any other stuff needing to be uploaded. So here's sending some friendly snarly noises at you, asking you to upload MATHelper so that I can download it!

I can (and shall) upload MATHelper when I get home tonight. This reason it's not there at the moment is because I incorporated all of its functionality into the more powerful EZMat, which I think you already have?

Retrowave posted at 9:05PM Sun, 08 March 2020 - #4382796

Thanks both, but I did read the instructions

I'm wondering if it has something to do with Windows and that damned UAC thing. The instructions said to put it in the same Runtime Scripts folder destination that was installed along with Poser itself. Unfortunately, that is in the UAC area of Windows, and it's a problem that stopped the DAZ Install Manager from working the other day, so it might be stopping this from working as well.

I'll reinstall, but I'm pretty sure I followed the instructions correctly. If it doesn't work next time, I'll just have to see if it works by installing the script to a Runtime that is not located in the UAC area of Windows.

EZSkin 3 is not designed to run in Poser 10 - you need EZSkin 2 for that. The 'RendererRootNode' function didn't exist in Poser 10, which is why you are getting the error. BB's VSS is a great tool, or you can use my MATHelper (see bottom left panel of the attached screen shot).