RHaseltine posted at 1:41PM Sun, 14 January 2018 - #4322197

You must not install Michael 4 to the application folder, modern versions of Windows will block you from writing the necessary files there. None of your content should go in the application folder.

What RHaseltine said:

Ever since Microsoft introduced the UAC this has been a major problem with installing content "the old way". Simply because Windows won't allow write access to any files in the "applications" folder, and it gives a flying fart about where the write request comes from.

The problem we now have is that a DAZ installation of M4/V4/whatever needs to be installed into Poser's own "root" runtime, which is the "runtime" folder which can be found here: "DRIVE:/Program Files/Smith Micro/Poser Pro 2014/Runtime*.*"

If your files aren't in the "Poser Pro 2014Runtime*.*" folder but somewhere on your "C:/" drive anywhere, you're in trouble.

Because any workarounds to fix this would be quite complex and error-prone, I'd simply sugest the "radical" method:

UNINSTALL Poser. Reboot your machine.

Then install Poser again, **BUT NOT ON "C:/" DRIVE! ** Choose "D:/" or whatever you like. When you're asked about your Library Location, always choose "External". Remember it's paramount to keep your libraries (- any libraries! -) OFF the "C:/" drive to prevent the UAC to get it's greedy control over your libraries!

Once you have Poser installed like this, you can install M4/V4 into the "DRIVE:/Program Files/Smith Micro/Poser Pro 2014/Runtime*.*" Then run the EXP batch files and all the other "DAZ initialization rites" as described in the readme s. That should get it all to work properly.

DISCLAIMER:

It's late here and I'm tired. This how-to was written from memory because it's been a while since I last installed Poser, so some advise given might be inprecise. I hope others can help me out here about the exact procedure. Sorry if I made any errors, or when I wrote complete nonsense. I tried to do my best.

Karina

First of all, take a DEEP BREATH and calm down...

Opening new threads and jumping to new ideas in each one will only scatter the topic and the support you get will trickle at random bits.

One bit here: If you can't properly install M4 in your runtime, I doubt that you will be able to get Genesis and the "DSON" (not Dyson - that was an astronomist) to work properly!

If your Volkswagon doesn't start it's not a good idea to install a Ford engine and hope that all will be well then... Oh, and don't ask the FIAT people either! :)

Best idea would be to continue this HERE:

https://www.renderosity.com/mod/forumpro/?thread_id=2920839 and then HERE:

https://www.renderosity.com/mod/forumpro/?thread_id=2920835

Then we have ONE thread where we can try to help you, instead of several scattered ones. Thank you.

Karina

Nevermind, just let us know what worked for you. -K-

Dang it!\ But it gets swallowed when you edit your post\ so you must add those \ double backslashes \ manually again
I really hope I have my \Kalashnikov\ with me the day I meet the guy who had this \absolutely brilliant idea\.

You're right about the creation of channels:

Until PP2014 Poser couldn't create valueParms "on the fly" in a ready loaded figure. It had to be done while the inital figure is loaded: Load geometry, load body parts, load channel groups, create valueParm and targetGeom channels, load data for these, assemble the final figure.

That's also the way the SASHA-16 Setup works: A script preloads the geometry and some basic channels, and then, depending on the "elements" you click, the figure is built .

It's like building a LEGO figure, brick by brick. But once you've assembled the figure it's almost impossible to add more bricks right in the middle of the figure without breaking it.

However, in PP2014 I can already create "targetGeom" injections to be added anytime. There's also limited support for "valueParm" creation, though only via a Python script. What's still missing is full control over the creation of both channel types in both BODY and body parts. Then we could finally do away with all those cumbersome methods: Take a bare base figure, and inject whatever morphs you need, later, anytime.

We're almost there. Almost!

K

Thank you WandW,

that's about what I expected. Now I only need to find out what those people were smoking when they devised these installation routines... (and why the Dickens this caricature of a "forum software" did eat the backslashes from the file paths in my previous post)

K

**Well, since this is an ever recurring theme:

Is anybody able to determine what exactly this "Initialization Rite" does?

Any of the batch files only call a program called "DzCreateExPFiles.exe" with the parameter of the figure attached, e.g. DzCreateExPFiles "Victoria 4" "V4"

But what sort of "Voodoo" does it do? I mean, Poser has no sort of registry for library content, so maybe the only thing that this .exe does is copy the DAZ files to the correct location??**

Trying to solve this user's problem:

Since Generation4 figures came out I've updated Poser to a couple of new versions. Because V4 (now: SASHA-16) is still my main figure I, theretically, would have to "initialize" her for every new version of Poser.

I didn't do that.

Instead I just copied the DAZ folders from "GeometriesDAZPeople" and "Libraries!DAZ" to the basic runtime of the new Poser installation (that is: the runtime that is inside the Poser program folder - let's call it the "Native Runtime"), and all DAZ figures worked flawlessly in the new version.

The only thing I made sure of is that none of the basic DAZ Generation 4 are present as duplicates in any of my external runtimes. This makes troubleshooting a lot easier because if Poser can't find V4 files the problem must be within the Poser "Native Runtime", unvariably.

So before you continue, search all your external runtimes for these folders:

• "RuntimeGeometriesDAZPeople"
• "RuntimeLibraries!DAZ" and ->move the content of these folders to the "Native Runtime": "{Your drive}:Program FilesSmith MicroPoser {yourVersion}Runtime*.*"

This "Native Runtime" is the first where Poser looks when searching for content! Only if it isn't in this one, it will continue searching in the other runtimes. And the more files are scattered over various runtimes the more prabable it becomes that Poser gets confused, and the problems start. (That's also the reason why Python scripts should always go into the Python folder of the "Native RUntime"; if you want them to be added to the "Scripts" menue this is mandatory anyway because otherwise they won't show up.)

My assumption: The basic DAZ V4 as it came from DAZ uses a hell of a lot of scripting to reload code which reloads code which again reloads code until the figure is completed. Now imagine some code files aren't exactly where Poser is looking for it? YEP, Poser won't be able to find it and thus some morphs are missing or not working because of missing morph data.

QUOTE lelek240:

** Any V4.2 i have saved with those morphs is working,but if i want them to sue on new V4.2 chararcter,they wont load,[...]**

That's the logical consequence: Once the morphs were loaded OK by the scripts, they become part of the .cr2 file and will continue to work. Each "new" V4 character you try to create will again try to call the scripts, with the results as decscribed above.

Karina

SamTherapy posted at 12:04PM Mon, 04 December 2017 - #4319321

[...] Unless he's Scottish, then it'd be Duncan Disorderly. [...]

LMAOROTF!! That made my day Sam, thank you!

On the name: It should be a name that most cultures on this planet could speak and write easily (remember Poser's large userbase in Japan! And please also don't forget us Slavs...

Someone also should remember to check whether the prospected name doesn't have a dirty meaning in another language. Example car names: https://www.oddee.com/item_93544.aspx

I don't know whether the Issue with "Eve/Eva" is still valid (which I think is stupid anyway: "Eve" isn't a protected brand name!)

But I could imagine "Pretty Eve" being quite catchy for people and would also make a perfect acronym to "PE" (and in Russian, "красивая Ева" sounds nice too! )

Karina

(and with "PE", make it clear that the two letters are spelled separately: "Pe---Eh", not contracted )

The bus is going to the left side. The doors are on the other side, where the people would get in and out at a bus stop.

As @pikesPit already stated I did replace the .RAR files with a .ZIP version.

I wasn't aware that .RAR isn't a well-established standard already because it offers many improvements vs. the "ancient" ZIP standard. I'm sorry if I caused you any trouble.

If you want to learn more about SASHA-16, or keep updated with fixes or new features, or want to help improve SASHA please visit my forum at sasha-16.forumprofi.de/index.php

Thank you, and take care

Karina

EClark,

I followed that thread at the Hive too, and IMO what you posted were words of good reason. Nothing wrong with them. But you just can't help it if certain people want to misunderstand your words just to stir up a fight.

As Boni already said we all know the usual trolls and troublemakers. In an ideal world we all would just ignore their posts, and without any response to their posts they would soon leave. "Don't feed the trolls!" Unfortunately this isn't an ideal world, and at some point someone will reply, and then the shit hits the fan again.

However, I have a saying for you that I first read a really long time ago, on one of the old BBS boards:

Don't let the bastards grind you down!

Print that out and hang it right next to your screen. It helped me!

Finally, I'd just like to thank you for being you.

Take care, and "Don't ... !" ;)

Karina

Try 7zip: http://www.7-zip.org

It can read and write an impressive amount of archive types, and it's free.

Generally speaking, no.

png and tga are lossless file formats, whereas a jpeg gets it's higher compression ratio by omitting minute details in the picture information. Depending on the amount of compression this can be from hard to notice to obvious.

Packing them in a rar or zip file will compress the png and tga files where possible, but it will keep thee data 100% intact.

Archiving jpg which are already compressed to the maximum and reduced in file size due to the compression ratio of the jpg will result in near zero extra compression.

So you'll always get larger archives when they contain png or tga files.

HTH

Karina

AmbientShade posted at 12:50PM Wed, 02 August 2017 - #4311232

RorrKonn posted at 1:24PM Wed, 02 August 2017 - #4311196

Anyways the ones with the red eyes are all most identical & the 4th .the first is just more muscular. but REX never got near amount attention as the other. why ?

Because he didn't have boobs.

My pleasure!

Hi all, Karina here :)

I just checked at shareCG and it's still there.

However you can also download SASHA from her web forum at

http://sasha-16.forumprofi.de/index.php

Enjoy SASHA