Zitat von Karina

---

I indeed expected users to install SASHA manually (just because I do so too with ANY content).

---

I've never installed content any other way than manually, because I like to know exactly what I'm getting and where to find it (and of course I like to put Library items where *I* want them to be). But when I started making freebies last year, I knew the zips I shared would need to be set up to work if a user chose to "Install from Zip" or took the approach of "merging folder contents." So I studied Renderosity's documentation on how to set up a Runtime (for products or freebies), and I also studied a ton of runtimes I'd downloaded. That's what my recommendations to you are based on.

I wouldn't worry about the fact that people are sometimes advised to reinstall the Poser application. If a user does that without first backing up their Python scripts folder, then they risk losing a LOT more than your scripts! Every Python script I've ever gotten (freeibe or purchased) is installed in my Poser Application's runtime, as per the installation instructions. I don't have Python folders in any other Runtime except for that one, and I was under the impression that was how it was supposed to be.

Because the Python folder lives in a different Runtime from all other Poser content, content creators whose products include scripts always have to include separate zip files -- one for the content and one for the Python scripts. But each zip file, when unzipped, should exactly mirror the structure of its target runtime, from Runtime on down -- which means you don't need to know the path above Runtime (so it doesn't matter that you don't know where the user's Application folder is.) That way a user could, for example, drag the poserScripts folder from your unzipped Runtime onto their existing poserScripts folder (in their Applications folder) and have the OS "merge contents."*

That's why I set up my sample Runtime hierarchy for FOLDER 2: Items for the Poser Application runtime the way I did: b/c it mirrors the structure of the target runtime. That way it works no matter what method you use to install. That's also why I didn't use the original names for the PoseWriter Ignore files, so that any existing files wouldn't get over-written.

* Using the OS's ability to "merge contents" of folders (including subfolders) is probably the most common way people install new content for Poser. As I undesrtand it, on a Windows system, if you drag a folder onto an existing one of the same name, you get the option to "merge" or "replace." On a Mac, you don't get that option by default. To get the "merge" option, you have to hold down the option key while dragging. If you forget to do that, you risk having the new folder replace the old one instead, so not many Mac users go that route, understandably. However, there IS a much safer way to get the "merge" option on a Mac, and that's to always install from a separate drive, like a USB thumb drive or a network drive. When you drag a folder from a separate drive onto your internal drive, you always get the option to "merge" or "replace."

Zitat

---

- (6) I kept a "My Own Presets" folder in the >character >SASHA-16 >SETUP, and the >materials >SASHA-16 libraries.
--> Albeit Just to remind people again and again that it's very convenient to save presets instead of starting over from scratch again and again.
You won't believe how many people still follow the old drill:
Load figure - inject morphs - apply texture - apply character morph:
JUST to have the same character they made yesterday, and the day before, ad nauseum...

---

I'm not suprised that some people would be that clueless. (I mean, come on, they could just open the same .pz3 file they were working on yesterday to continue using the character!!) But I'm not sure any of us actually have any idea what the "typical Poser user" does. We're all just guessing, based on the kinds of questions we see on forums and maybe our knowledge of how less tech-savvy folk tend to operate.

However, I think it makes sense to include a folder for Sasha users to remind them that they can save customized figures there. Those who have no need for such a folder can just delete it! I do wonder, though, if this name for the folder might be more helpful: "My Customized Sashas" or "My Sasha Characters" or something like that? Because technically, a CR2 file isn't a preset, at least not the way light and camera files are.

Zitat

---

- (7) Still struggling with this.
I can't preview where people will install S-16 to, and because a shortcut to the manual needs an absolute path, there's no easy run.
I could maybe write a text file saying "Look in this and that folder, but that's already the best I can do.

---

You shouldn't need an absolute path if you're referencing an item within a runtime structure. That's actually kinda the point of a runtime structure

The default content Runtime that gets installed with Poser has a subfolder called ReadMe, and every additional Runtime I've ever set up for use in Poser also has that same subfolder. It's on the same hierarchy level as the Geometries, Textures, and Libraries folders. So if you provide the manual in that folder as part of all the content installed with S-16 (excluding the Python scripts), then your library shortcuts to the manual don't need an absolute path. They just need to reference: :Runtime:ReadMe:YourManual

At least that's how it's supposed to work!

Zitat

---

ADDENDUM:
You said some scripts have duplicates with different version dates:
You could do me a big favour if you could tell me which scripts in which folder are affected.

---

Here's a screenshot that shows the modified dates. Hope this helps!

[attachment=267]

Zitat von Karina

---

I indeed expected users to install SASHA manually (just because I do so too with ANY content).

---

I've never installed content any other way than manually, because I like to know exactly what I'm getting and where to find it (and of course I like to put Library items where *I* want them to be). But when I started making freebies last year, I knew the zips I shared would need to be set up to work if a user chose to "Install from Zip" or took the approach of "merging folder contents." So I studied Renderosity's documentation on how to set up a Runtime (for products or freebies), and I also studied a ton of runtimes I'd downloaded. That's what my recommendations to you are based on.

I wouldn't worry about the fact that people are sometimes advised to reinstall the Poser application. If a user does that without first backing up their Python scripts folder (and/or saving their installers), then they risk losing a LOT more than your scripts! Every Python script I've ever gotten (freeibe or purchased) is installed in my Poser Application's runtime, as per the installation instructions. I don't have Python folders in any other Runtime except for that one, and I was under the impression that was how it was supposed to be.

Because the Python folder lives in a different Runtime from all other Poser content, content creators whose products include scripts always have to include separate zip files -- one for the content and one for the Python scripts. But each zip file, when unzipped, should exactly mirror the structure of its target runtime, from Runtime on down -- which means you don't need to know the path above Runtime (so it doesn't matter that you don't know where the user's Application folder is.) That way a user could, for example, drag the poserScripts folder from your unzipped Runtime onto their existing poserScripts folder (in their Applications folder) and have the OS "merge contents."*

That's why I set up my sample Runtime hierarchy for FOLDER 2: Items for the Poser Application runtime the way I did: b/c it mirrors the structure of the target runtime. That way it works no matter what method you use to install. That's also why I didn't use the original names for the PoseWriter Ignore files, so that any existing files wouldn't get over-written.

* Using the OS's ability to "merge contents" of folders (including subfolders) is probably the most common way people install new content for Poser. As I undesrtand it, on a Windows system, if you drag a folder onto an existing one of the same name, you get the option to "merge" or "replace." On a Mac, you don't get that option by default. To get the "merge" option, you have to hold down the option key while dragging. If you forget to do that, you risk having the new folder replace the old one instead, so not many Mac users go that route, understandably. However, there IS a much safer way to get the "merge" option on a Mac, and that's to always install from a separate drive, like a USB thumb drive or a network drive. When you drag a folder from a separate drive onto your internal drive, you always get the option to "merge" or "replace."

Zitat

---

- (6) I kept a "My Own Presets" folder in the >character >SASHA-16 >SETUP, and the >materials >SASHA-16 libraries.
--> Albeit Just to remind people again and again that it's very convenient to save presets instead of starting over from scratch again and again.
You won't believe how many people still follow the old drill:
Load figure - inject morphs - apply texture - apply character morph:
JUST to have the same character they made yesterday, and the day before, ad nauseum...

---

I'm not suprised that some people would be that clueless. (I mean, come on, they could just open the same .pz3 file they were working on yesterday to continue using the character!!) But I'm not sure any of us actually have any idea what the "typical Poser user" does. We're all just guessing, based on the kinds of questions we see on forums and maybe our knowledge of how less tech-savvy folk tend to operate.

However, I think it makes sense to include a folder for Sasha users to remind them that they can save customized figures there. Those who have no need for such a folder can just delete it! I do wonder, though, if this name for the folder might be more helpful: "My Customized Sashas" or "My Sasha Characters" or something like that? Because technically, a CR2 file isn't a preset, at least not the way light and camera files are.

Zitat

---

- (7) Still struggling with this.
I can't preview where people will install S-16 to, and because a shortcut to the manual needs an absolute path, there's no easy run.
I could maybe write a text file saying "Look in this and that folder, but that's already the best I can do.

---

You shouldn't need an absolute path if you're referencing an item within a runtime structure. That's actually kinda the point of a runtime structure

The default content Runtime that gets installed with Poser has a subfolder called ReadMe, and every additional Runtime I've ever set up for use in Poser also has that same subfolder. It's on the same hierarchy level as the Geometries, Textures, and Libraries folders. So if you provide the manual in that folder as part of all the content installed with S-16 (excluding the Python scripts), then your library shortcuts to the manual don't need an absolute path. They just need to reference: :Runtime:ReadMe:YourManual

At least that's how it's supposed to work!

Zitat

---

ADDENDUM:
You said some scripts have duplicates with different version dates:
You could do me a big favour if you could tell me which scripts in which folder are affected.

---

Here's a screenshot that shows the duplicates, including the ones that have different last modified dates. Hope this helps!

Zitat von Karina

---

->I<- probably would never have discovered it because I never use the "Zero Figure" of Poser!

---

Once I've set up a custom character and memorized the figure, I use the keyboard shortcut for "Restore Figure" rather than "Zero Figure" when I want to get back to the default pose. But when I'm just messing around with a figure, as I was with the S-16 beta, I use "Zero Figure" as a quick way to return to a "blank slate," as it were.

But doing so on the S-16 beta did more than produce wings -- it also made her shrink to near fairy size b/c the "true height" dial got set to something like 7! It's probably a good idea to suggest in the manual that users not use the "Zero Figure" command, but someone will inevitably do so anyway, so now you know what happens!

Unsure if was intentional, but the anus open morph is not working. It's present in the vagina prop, but isn't doing anything. Also the dials are hidden in the hip. The body dials (also hidden/anus open & anus wider) are named EMPTY - not active. This was after the KV was activated.

i am here, but deeply buried in a non-poser project. I can't beta test the new release for at least 4 days.

::::: Opera :::::

Still here. Posted the only thing I had found Everything else I have checked seem to be good.

All seems good to me so far!

Zitat von Karina

---

Where did everybody go?

---

Hi,

All good so far. I have created a new figure based on S16.

Am testing how it works....

Looking good.

LA