hi,

just adding my dime to the debate. Poser is sensitive indeed to the videodriver, but having an older one usually leads to random-like weird behaviour in the design phase, and in the User Interface arena. 
Since you're in a 32-bit OS environment, it might be worthwhile starting TaskManager (right click your taskbar), look into Processes and check whether the Poser memory usage comes close to 2Gb. If so, you've got to activate the 3Gb-switch in Windows. If not, there is no memory issue. 

Note that each CPU does one thread at a time, each thread addresses one bucket. Having a bucket-size larger than your image just turns the renderer into a one-thread system. Having small buckets generates some overhead due to bucket-overlap-calculations (portions of the scene effecting each other). Life is one big trade off.

The thing that really wonders me if that you only get a portion of the result. I would say: small buckets, multi-thread and render in Poser, so you can see what it's doing. That might you give some clue.

I use windows MovieMaker, for cutting large videos, and to combine small animation footages with music. It outputs to wvm in some standard sizes, and works well. Avi's are uncompressed, a real nightmare.

Pinnacle Videospin is second, as it can handle other formats. I just found it, so it might promote to #1.

Wax, from http://www.debugmode.com/ , comes third at this moment. It handles multiple videotracks, I just haven't used it that much yet. Looks great though, and can run as a plugin too. Deals with Avi.

Go http://www.prvsoft.com/ for great converters and other free tools, love them.

have fun.

 hi all,

I have split my runtimes in chunks like Girls, Beings, Scenes and DazPoser, the latter takes the standard runtimes. Each folder contains the Runtime as well as the Daz Studio content, and so on.  I do not use PZDB since it deals with poser only, I use P3dO instead. Next to Poser content it handles Daz content as well (which requires separate lighting sets, camera setups and sometimes materials too), and deals with a secondary structure (and substructures) using favorites (for clothes, hair, etc). This way I have some pack of clothes plus all accompanying textures and props in one place, whatever the source.

As a result, I can doubleclick to launch an object right into Poser, but into Daz Studio, Carrara etc as well, and all from the same library. It fires scripts too, and the creator welcomes suggestions (that's why it works for Daz Studio now, including non-Poser filetypes). My content library contains about 40Gb and it rocks.

It's great, especially if you spend a dime on the Pro version. But do run the free trial first.

 hi TomHR,

when you loose the top you'll find that the jacket conforms well to Alyson, as you requested.
But as Kalypso mentioned, you want the jacket to follow the top, not Alysson. So that's step one indeed.

Second, the jacket was made for Alysson and not the top, so differences may occur. As a result, you might need additional work, like setting dials or using magnets. This is like fitting Alyssons clothes to Vicky or the WackyWorld Rhino or whatever. Same story. So, first conform to the top, then use dials / magnets.

Third, when you get the feeling things grow out of hand, Poser has PhilC's great Wardrobe Wizard build in. 

All the best.

hi all,

just my dime to the debate.

Please note that moving scenes from one application to another usually means headaches over camera properties, lighting issues and (procedural) materials as well, let alone for procedural objects like terrains and ecosystem details which are generated at render time. Those ecosystems in my Vue scenes constantly break the 2Gb memory limit on my 32-bit system, which gives you some clue on the size of the exports.

Those issues hold for integrating Studio into Carrara of Bryce, and Poser into Vue and Vue into MAX or C4D etc. Anyone who tried to read Poser scenes into Studio knows about this: all cams, light sets and advanced material sets needs either a redo or a serious bodycheck. And Vue volumes are vast.

Vue to VRay is simple, on paper: run xStream, interface to MAX, setup for VRay and off you go... well, good luck with the VRay sun, lights and materials in your Vue scene, then. 

Note that the only thing Lux adds is raytracing, good for reflection, refraction and some GI/IBL. Vue does it well, too. And dealing with light without re-rendering ... is part of Vue 9, as I understood from the Siggraph notes (3DW mag #134, out now).

The real thing I'am waiting for is the ability to deploy GPU rendering, so I can utilise nVidea 480 cards, or stacks of them in renderboxes like The Cube. Same problems though: cams, lights, materials and extreme memory requirements.

 I never made it to 10 types of people, but I do know three: those who can count and those who can't.

Can we do bits too? 1 byte = 8 bits unless you are in networking, so 1MBps will require a 10Mbps line due to start an stop bits, depending on the protocol. Math always was simple until the IT nerds hit the place. Until then, 1+1=2. Now it can be 10 as well.

Running Bryce 6.1 (Poser 7 etc) on Intel Q6600 2.4GHz Quad-core, 4Gb RAM, Vista-32 Ultimate and nVidia 7600GS/512Mb. No problems, as long as you keep your graphics drivers up-to-date when deploying the OpenGL interface.

Note that Vista creates and manages a VirtualApps directory in your Documents&Settings sections which will contain the files you tend to create in ProgramFiles before, like additional presets. This way, backing up is seriously simplified.

regards
aRtBee

ShaderWorks will do the job. See the other "Like to have Library Organisation comments" thread, where Semidieu himself pops in, for the download links etc.
Or ... just don't delete, and go for the 100Gb monolithic runtime as other people seem to like (see the "Can you beat this???" thread).

All the best,
aRtBee

hi all,

thanks for the comments so far, I'll do a wrap-up later on. In the meantime I'm curious:
 - about the comment David Harmon is going to make
 - about the 38 runtimes Jules is (not?) planning to deploy
 - about the current whereabouts of ShaderWorks. All links I can find on Google of runtimeDNA appear dead. The toolkit looks promising though. Suggestions anyone?

regards,
aRtBee

hi,

I just started a thread yesterday on library organisation, people are putting tips and tool references in there, so have a peek.
Deleting is tricky since textures (and objects too) etc can be referenced by multiple other objects.

regards
aRtBee

hi all,

I'm just a minor, facing 20 Gb. But my question (in he other thread, just opened) is ... how to get and stay well organised. You all must have an opinion on that, I guess. Please use the other thread to prevent goint OT.

thanks, see you there,
aRtBee 

ziet er uit als een goed begin...

succes,
aRtBee

hi all,

just my humble thought on this. The initial question was: what about lage scale images? Serious printing needs 100 lpi minimum (150 normal) so in the end wejus need more pixels.

Bryce can handle images up to 4000 (x4000) in memory, so up till this size you can do a network render on a still using "tiling". No use on a one-machine network though. For bigger stuff you better stich a UPS (Uninteruptable Power Supply) between the wall plug and your machine, it will pay off.

The smart way of handling things is done in mojoWorld, where tiles of 100x100 can be rendered AND SAVED so when the sky comes down, you can pick up where you stepped out. You can even render at night and work at day. When DAZ failed to pick up this functionality, I do see a new request coming up.

Why someone needs large scale prints is not the issue. My record is 4000x6000 in 254 hours (see Got Her, in my favourites).

regards
aRtBee

:biggrin: 1st: thanks a lot, cool stuff. Extremely cool looking site too.
:crying: 2nd: it takes 87 days (!!!) to download, at max 25 a day, excluding additions in the meanwhile. Am I on candid camera, or what?

regards
aRtBee

hi James (and all others),

I'm subscribed to 3DCreative as well as 3D World both from issue 1 on, and my note is ... it depends.

3DW is better on news, the industry, the schools, the studio's, new hardware and software, presents a CD with demo's and a freebie (half of them can be downloaded from the net as well) and contains basic tut's into the CD software. There is some (understandable) UK/US bias in its contents.

3DC's interviews are much more "on the person itself" from studio bosses to talented newbies, and the articles and tutorials on modelling (cars and creatures) and texturing are brilliant at the advanced amateur / beginning pro level. No CD's, but much cheaper than 3DW.

When you decide for the 3DC option, my recommendation is to get all the back-issues as well, keep the e-mail with the order- and delivery details, and go fot the Jane of Arc tutorials (or ask the staff for access).

regards,
aRtBee