The Birth of Stormbringer!

[Jherrith]

It usually takes my system longer to beat up on the HD's looking for and gathering up its needs for rendering the scene than it does for yours to DO it.  And then I get to watch mine render it.  Watching grass grow, paint dry, the life cycle of a bug.  Long time.   

McG.

Well, since you an Cookie showed me the errors of my render and light settings indeed things are much faster.

The bonus of now running a 64 bit version of Poser on a 64 bit OS helps considerably too.

Incidentally I recall you saying there was issues with file associations via that UAC folder and Poser, which might have been similar to what I was seeing when I was installing the legacy characters V4, M4 and so forth. Once installed they did not show up in the Poser default runtime in their folder. I did figure out the solution to that if you are interested.

[McGrandpa]

That should make it easier!  And, should also make it harder to misplace it!

McG.   

[Jherrith]

Indeed

[McGrandpa]

Well, since you an Cookie showed me the errors of my render and light settings indeed things are much faster.

The bonus of now running a 64 bit version of Poser on a 64 bit OS helps considerably too.

Incidentally I recall you saying there was issues with file associations via that UAC folder and Poser, which might have been similar to what I was seeing when I was installing the legacy characters V4, M4 and so forth. Once installed they did not show up in the Poser default runtime in their folder. I did figure out the solution to that if you are interested.

Sure I'm interested!  Although  I recall mentioning two issues:
1) UAC restricting a Users ability to write stuff to a HD and it *STICK*!
2) Defender  putting a Users stuff in PROGRAM DATA somewhere because Windows is being told that stuff is unsafe.  Poser never looks in there.
I first ran into this in Vista.  The business and government users had this to deal with since NT I think.
McG. 

[McGrandpa]

Another thing I learned and do USE to my benefit is to get the DAZ Figure Installers and Figure Updaters to work, using the Runtime of your choice, is to have a file named "Poser.exe" in the top folder where you want the installer to put the Figure and Morphs.   I also discovered by experience that having a PoserPro.exe won't work.  The DAZ stuff is expecting Poser.exe.   That file can be a text file named Poser.exe, the installer check is a simple name check.
If I go to install say M4 in a new folder, and I forget the Poser.exe, I get the warning and exit of the installer.  Shucks. 
But J., I am not encouraging ANYONE to do what I do.   After all I do refuse to install content to the programs own folder set.  I don't think of scripts, pythons, to be "content".  ALL scripts, pythons go into the Programs own folder set.  There is no other place the program executes code from.  Code, like scripts and pythons. 

McG.   

[McGrandpa]

Well, since you an Cookie showed me the errors of my render and light settings indeed things are much faster.

The bonus of now running a 64 bit version of Poser on a 64 bit OS helps considerably too.

Incidentally I recall you saying there was issues with file associations via that UAC folder and Poser, which might have been similar to what I was seeing when I was installing the legacy characters V4, M4 and so forth. Once installed they did not show up in the Poser default runtime in their folder. I did figure out the solution to that if you are interested.

J.? 

McG.   

[sidherose]

Another thing I learned and do USE to my benefit is to get the DAZ Figure Installers and Figure Updaters to work, using the Runtime of your choice, is to have a file named "Poser.exe" in the top folder where you want the installer to put the Figure and Morphs.   I also discovered by experience that having a PoserPro.exe won't work.  The DAZ stuff is expecting Poser.exe.   That file can be a text file named Poser.exe, the installer check is a simple name check.
If I go to install say M4 in a new folder, and I forget the Poser.exe, I get the warning and exit of the installer.  Shucks. 
But J., I am not encouraging ANYONE to do what I do.   After all I do refuse to install content to the programs own folder set.  I don't think of scripts, pythons, to be "content".  ALL scripts, pythons go into the Programs own folder set.  There is no other place the program executes code from.  Code, like scripts and pythons. 

McG.   

Poser.exe is the executable file inside the program folder that opens it up and loads it.

Why would anyone who only uses Poser use a DAZ installer at all? It installs everything in a Content folder that sits in your runtime and your runtime can't see it even if you did install it there because Poser doesn't have a Content library folder.

We use zips. They unload to the right places in whatever 'runtime' we pick to load them into..unless they're packed for DAZ in that Content folder which has the Runtime folder inside of it. Then you still have to remove it from there and put them in the right places.

[dRaCX]

Creating ANY text file with a false .exe extension is a "Hack" that comes with it's share of troubles. I for one CAN NOT endorse such actions due to the possible harm that can result from it! It would be wise when discussing any kind of hack, to do it outside the public eye.

-Reader BEWARE!-
creating txt files with false extensions are methods used to create viruses! Do so at your own risk!

[Aelin]

I have already changed .txt in .pz2 or .mc6. But before the save of the document, and because I'm working in my own codes; or trying to change an mc6 in a pz2to use them at least in part between Poser and DS.
But an .exe The only terme "virus" is enough for me

[sidherose]

I have already changed .txt in .pz2 or .mc6. But before the save of the document, and because I'm working in my own codes; or trying to change an mc6 in a pz2to use them at least in part between Poser and DS.
But an .exe The only terme "virus" is enough for me

It's okay to change the .txt documents of .mc6's to .pz2 . That is acceptable to Poser.