Since I've gotten P7 I haven't used P6 since. Actually, my P6 is pretty well stripped out with the exception of Jame and Jessie everything else was moved into external Runtimes. But parts of me just can't seem to uninstall it yet.

I guess not. Sorry it was such a hard question to ask

I still have 4,5,6 and 7 still on my pc
too lazy to uninstall and set up the runtimes

Everybody is laughing too hard to reply. ;) So I take it you can export a large jpg render (3 or 4 characters, 1200x1000 or so) from P7 and it ends up being more then 60-70kb? Do a comparison render with P6 and P7, same pz3. When you export/save the image use the "max quality 100" compression setting in P6, use whatever compression setting you want in P7 - it doesn't matter what you put because the setting doesn't appear to change anything in P7. Then compare the images, my P6 still produces better images, the same image out of P7 is just not very clear. Universal poses, that's cool. Multiple undo's is cool too. I guess the putty tool is alright. But... the bottom line for me is I just can't get P7 to output the quality of image that I can with P6. I also tried exporting TIF's and PSD's and saving the final from PShop, the resulting image still lacks depth or real clarity. Somebody set me straight if I'm wrong, maybe I've just totally missed some crucial P7 render setting - but I don't think that's the case.

I have 6 and 7 both up. I still like 6 better, but that could be because I'm not completely comfortable with 7 yet. 
Isn't there an update coming out soon for 7?

I still have P6 installed, got rid of P4 and 5 though.   I work in P6 where all my python scripts work and save and render in P7.   I export as .tiff and use an image editing prog to compress as much as I want to.    Sometimes though I might work in P7 with the new morph tool and because the new python menu is much easier.   Unfortunately, because I have large directories in my linked runtimes I can't let P7 Build folder menus when it asks to since it will crash.   I'm hopeful the issues I and others have with P7 will be addressed in the first SR.   

i still have 6 installed because i haven't copied my runtimes over to 7 yet. lazy me.

I have 5, 6 & 7 installed because I test my products in all three.  I no longer support 4 or the ProPack.  All of my content, with the exception of native, is on external runtimes and has been since I first got P5.

I uninstalled P6 after putting my files in P7 runtime. I still use PP but uninstalled P5. needed disk space. For an export workaround I export as PNG and work in Photoshop to edit, then save as jpg. This also gives me a transparent background when just rendering a figure. And no white or gray edges to have to edit out later. I love working with the morph brush.

I still have P6SR3 on board although I use P7 now. 

Some of the python apps I bought previously, are only good for Poser6.  Not that I'm fretting to much about that.

I have the same problems as Ben_Dover. COmpression artifacts in final render in Poser 7. Too bad, because the render engine doesn't crash like Poser 6.

Regarding the lack of clarity in P7 (Ben_Dover's comment)... have you checked your texture filtering settings in the material room? Rather than one single setting in the render settings (which was turned off by default on P6), each texture map used by P7 can be individually selected for texture filtering; it's now a choice on the image map node settings. Annoyingly for some, it's default position is now 'on'... and this can lead to blurry, ill-defined images and loss of clarity in the details.

jonthecelt

My poser6 runtime is stripped to the barest minimum as well, but I have linked all my runtimes into it including the Poser7 runtime.

Quote - Regarding the lack of clarity in P7 (Ben_Dover's comment)... have you checked your texture filtering settings in the material room? Rather than one single setting in the render settings (which was turned off by default on P6), each texture map used by P7 can be individually selected for texture filtering; it's now a choice on the image map node settings. Annoyingly for some, it's default position is now 'on'... and this can lead to blurry, ill-defined images and loss of clarity in the details.

jonthecelt

before you get mad at texture filtering check your Min. shade rate. it should be 0.2 or smaller for good detail... i believe it defaults to 1 in P7 where it defaulted to 0.2 or 0.5 or something like that in P6.

also remember texture filtering in P7 is not only in a different place than P6 but is implemented in a different way. so the fact that it is on in P7 does not lead to exactly the same issues as having it on in P6.

thats not to say you shouldn't turn it off when you feel you need to. just don't jump to the conclusion that this will solve your problem. although it might

Quote - So I take it you can export a large jpg render (3 or 4 characters, 1200x1000 or so) from P7 and it ends up being more then 60-70kb?

Never export a render as jpg from Poser, any version! The compression method is bad. Export your render as tif, psd, png, or bmp, then take your render into Photoshop and save it as jpg using "Save to Web". If you don't have Photoshop, use whatever paint program you have and save as jpg from it. You'll get much better results and it will be free of artifacts unless you save it at very low quality.

I've ordered P7 and will keep P6 on my system for quite a while. When I upgraded from P5 to P6, I kept p5 for over a year before removing it, to use as a backup in case I ran into problems with P6. When I upgraded SR3 had been released so I don't think I ever had to fall back onto P5 but it felt secure to have it there just in case.

I still mainly use P6 because P7 won't let me do print size images and won't export properly to Vue6Inf, until those 2 crucial things are fixed I'm sticking with P6!
Don't get me wrong, I like P7 especially the increased render speed but for my current work load it's just unusable except for images for here and only then if I'm not going to take the scene into Vue which is unlikely because Vue's lighting is better!

Dumped version 6 a week after I got 7........ combined the runtimes, moved out a lot of products rarely used and forgot about 6. It crashed too often on my Mac to enjoy using it. I have 6 on an external backup hd but not missed it once. On the quality issue I ALWAYS export my rendered images in tiff format..... yes I do a lot of postwork but it's not to fix the quality of the render. I usually render out at roughly 2000x2000 and 300dpi. I also only use jpg to save ( save for web) a copy to upload other than that I keep my images as tiff or psd format. A jpg loses quality every time it is opened ,or so I was told when I first got into cg. Whatever, I rarely use it , certainly not as a working mode for Poser or Vue . I also lower the texture filtering in the render settings window down to about .02 . I did it once following someones tute settings on getting a reflective floor prop to work and liked the results . I haven't the patience to fiddle with them individually in the mat room. O.0

I still have 6 on as well as 7 for testing products. As for quality of renders, I have found 7 to be superior by far in realistic results. I use the settings most have mentioned and export as .tiff always. I also render out at over 1200 by 1024 for all images.

I've done comparative renders with P6 and P7, same image, same size [9" x 6"] at 300 dpi

Size of image in P6 =  40Meg  As it should be!
**Size of image in P7 = About 1Meg ** Totally wrong!!

Poser 7 doesn't save out at more than 75dpi, it's a known bug so I don't know how you guys are doing 300 dpi images.
That's why I don't use it yet, I do images for book covers and the publisher wants 300 dpi, if I do it in P7 they don't get it and they get mad at me!

maybe I'm missing something but I believe from other posts that this is a known bug but if you guys have some pointers I'd be glad to hear them!! 

@ thefixer; Ok, on the point of Poser only rendering at 75 ppi I stand corrected.... I do however end up with 300ppi images at say 8x8 inches without resizing UP in Photoshop. I checked something I did the other day. In Poser the render dimensions I put in were' 2400x2488' at '300dpi' I exported that as a tiff. When opened in Photoshop the document dimensions read at 33.33x34 INCHES and yes, at 72ppi. However it's 32 megs in size ! To fit on my monitor I have to zoom out to 32%. I can zoom in to 300% where the figures entire face fills the screen to work on small details........... a bit jaggy at the edges but still very clear image. What I can do then is go to the resize assistant under the Help menu and resize that down to 7.5x7.6 inches at 300ppi and move the quality slider so the 17213k it indicates for the original image remains the same. In PShop the new resized doc dimensions now read as 7.5x7.6 at 303ppi. That is what I would send to someone requesting an image 300ppi . I can print that out on A4 and it looks great. Really I dont have to do that resize stuff at all .... I can just print it out from the 33x34 inch 72 ppi ....and what I will get when I set my printer to do it at 300ppi is a very good quality 7.5 inch print. Well , all I'm saying from my understanding of resolutions an' stuff is that this is my method of dealing with it, works for me ..... everyone please form an orderly queue to kick it to pieces now ; D http://graphicssoft.about.com/gi/dynamic/offsite.htm?site=http://www.digitalmediathoughts.com/articles.php%3Faction=expand%2C5812 "The quick way is to take the largest pixel value on the image (in this case, 2272) and divide it by the longest print side of the page size you're going to print it on. So if you were printing an 8" x 10", you'd divide 2272 by 10 and get 227 PPI. No quality problems with that PPI! At 11" x 14" you'd have 162 PPI. Still ok there, and at 16" x 20" you'd be at 113 PPI. This is pushing the barrier of acceptable quality, but I think it would still look decent - especially since the larger the image the further away people tend to view it. So what's the painful way of calculating PPI? If you're a math person, you won't find this painful, but I'm not, so I did find it moderately painful. The formula for the data above would look like this: (2272 x 1704) / (8.5 x 11) = x. In this instance, we'd get 41,406 and change. We'd then take the square root of that number and get a PPI value of 203. This is the most accurate method of calculating PPI (the quick method above gave us 227 PPI), but it's more involved. If your software gives you the PPI value, all the better, but if it doesn't you can safely use the quick method to crank out a PPI value before you waste valuable ink and paper."

thefixer_: I did a bit of testing to see what the end sizes would be: In render dimensions window my inputs were- 1st)- 9"x7" @72 dpi: 3min render. While rendering the render window itself had this as 534x648 . The tiff I exported was a wopping 128 k. Lol. Postage stamp. At 300 ppi that will print me a 1x1 inch image @300 or 9x7 @72 . 2nd)- 9"x7" @300 dpi : 22 min render. The render window reported 2225x2700. When opened in PShop it was noted as 20inchesx27inches @72ppi. But this prints out as a 9x7 inch print at 214ppi or a 4.5x6 inch @ 333ppi. So to get images your publishers can use, ie. 8x10 inches @ 300ppi it seems in Poser 7 you do need to set the image size to what your final print would be and the dpi as it should be, don't leave it at the default 72. What you will get is a very ! large image ( prolly a bit bigger than the 30x36 inches I cite in my previous post ) at 72ppi............ but that will give you a 8x10 print at 300ppi & happy publishers Please try in Poser7 and let me know if works for you.

I feel the same way as thefixer.  I don't like the way Poser 7 is acting so I will never get rid of Poser 6 yet until they come out with a fix for 7.  For some reason, Poser 7 can't save a good render if it wanted too.  I like Poser 6 where it's at for the meantime.  I don't understand why we have to jump through hoops in order for Poser 7 to save a good image.  It's a simple bug that they can fix pretty easy, so it seems.  Ever since I installed Vista Ultimate, I don't even have Poser 7 on my computer yet.  
Adrian

Gini: I actually do set my render dimensions by hand, i.e. under Render dimensions I will input 9" x 6" or whatever and change the dpi from the default up to 300, select a full quality render and it doesn't do a 300 dpi render and never will until SR1 render at 300 dpi.

If your method works then that's great, I really mean it,  but I want/need a bit of kit that will render at what I want it to, I paid enough for it.

Fortunately, Poser 6 does give me that so while I will "play" with Poser 7 to get used to it, any commercial stuff I do will still be done in 6 for now until hopefully SR1 fixes this particular bug which let's face it should never have got past the Beta testers!!

P7 collapsed quickly for me (Firefly rendering died entirely) so I'm
skipping it until it's fixed. 

Also the texture filtering needs to be off by default.  Stewer insists
that on-by-default is mathematically correct, and I understand his
point mathematically, but good math and good pictures aren't
necessarily the same thing!

P4/5/6 still installed, to test all my stuff. but I think it's time to toast 4 and 5. I have the runtimes all setup to P7 and I have P7 runtime linked to P6. I use P7 most of the time but once ibn a while Carrara 5Pro complains and I use P6 for that and some of the python scripts.

I final render my stuff in Vue6I or Carrara5Pro most of the time.

Uninstaled all posers and instaled 7 on new system, but just copied 6 and put onto other comp without reinstaling again, thats the fun lot's programs you dont need reinstal.
The only problem is all characters saved i have to buger about reload each 1 and save again, and trying to find all the bloody stuff on them because the Homer Simpson trained programers on p7 never used thier bloody brain's.
To put an external runtime searcher in p7, no wounder america has to keep poaching the best programers from around the world, to show the Homer Simpson trained programers how to code properly.