I've been away from Poser for years, but I'm thinking of starting up again.  All my figures are based on V2 and M2.  I've purchased V3, V4, etc but have never liked them and in the end and always go back to V2. 

However, V2 and M2 seem like they could be improved by adding more polygons, and if subdivision worked on them I would consider getting PP2014 as part of my relaunch. 

So my question is: has anyone tested whether subdivision works on V2 and/or M2?

Thanks for any thoughts and recommendations

Works with V2 as with any other figure.

Works very nicely with V2 and V2 Low res version as well. Also with M2 and M2 Low res.

There are a few figures where it doesn't work - Poser 5 Judy comes to mind.

For the high res figures like V3, V4 etc it is irrelevant since they have enough poly's already.

Thanks to both for the helpful replies. 

A follow up question, if I may:

If I take the plunge and get PP2014 --and then apply subdivision to all or part of the V2 mesh-- what happens to the texture mapping?  Does the post-subdivision mesh still take the original texture map for the figure, or do you have to re-do the texture map somehow? 

Thanks for any replies...

Texture maps should only be altered if the material zones were somehow changed, which i don't believe subdivision would affect.

Quote - Texture maps should only be altered if the material zones were somehow changed, which i don't believe subdivision would affect.

Thanks.  That makes sense.

Texture map will not be altered at all.  All you are doing is subdividing the mesh in Poser, the material zones remain intact.

Quote - Attached is screencap of V2 side-by-side, the right subdivision of 1 in preview, the left unsubdivided.

Excellent.  Thanks very much for the helpful demo, which gives convincing proof it works for V2 exactly as I hoped it would.  Much appreciated...

Now off to choose between Poser10 and PP2014... hmmm

Notice, left Vicky shows very rough smooth polygons while right Vicky displays better, natural smoothing to it's frame.  The texture mapping is unaffected.  The workflow for using subdivision, load the figure, load it's texture, pose, then have the character subdivided at render.

PP-2014 allows you to weightmap figures which Poser 10 doesn't.

The attached picture shows the old PT-Vicky figure (Same mesh as Vicky-2) with weightmapped joints.

Very good point.  That is the reason I purchase the Pro versions only.  More diversity from the app.

I was helping out with Lyrra's P6 Jessi Fix (available here in the Free Stuff).  In the image (left knee bend) from left to right:

Original P6 Jessi

Jessi Fix

Jessi Fix with Subdivision at 1.

Poser 2012 & 2014 make old figures new again.

Bought Poser10 as a sidegrade from Poser8.  Subdivision of V2 worked fine.  Unfortunately, it crashes on most renders now even with a single subdivided V2 figure. 

I may have wasted my money, though the renders that did work looked fantastic.

Are you rendering as a separate process?

Quote - Are you rendering as a separate process?

Rendering using FireFly within P10.  I used to export to Vue but it was too much hassle since I focus on animations.

Sorry. I meant do you have the "separate process" box checked under your Render Preferences?

Quote - Sorry. I meant do you have the "separate process" box checked under your Render Preferences?

Sorry I misunderstood.  I didn't realize there was a separate process option, but have now checked the box.  I'll see if that helps.  I usually open task manager before rendering and minimize the window for the Poser app.  That bumps the memory load down considerably --though of course it starts surging upward again once rendering starts ... but not as high.  That's the only method I had found to reduce the chances of the dreaded "you are out of memory" crash.  

I'm also about to move the computer I use from WinXP to Win7.  I was goin to install the 32 bit flavor of Win7, but maybe I'll go with 64 bit.  I know Poser 10 is 32 bit (disappointing) but maybe it'll help at least a bit, and perhaps I'll also upgrade to Pro2014 if that's the only way to make it all work... but then only if the upgrade price falls to something reasonable for a hobbyist like me.

Thanks for the insights and advice.

You will be MUCH happier with PP2014 because it IS a 64-bit app. Upgrading to Windows 7 will have little if any impact on your situation as the program is limited to the same amount of memory running 32-bit.

If SubD is taking to much of your system, try the following:
Render without SubD but instead?

Using the free "scenefixer" script to set crease angle on ALL groups of your figures to 180°.
Set Smoothing to "ON" in the render settings.
Render as such.

Remark.

Using SubD will shrink your object file.
Using Smooth Polygons wil expand your object files.

Going from SubD to Smoothed figures "can" provoke clothing poking as the "size" of the figure increases slightly.

Using SubD at level 1, AND using Smooth Polygons in the render settings with crease angle set at 180° in all groups, will +/- maintain the size of soft body objects like figures.
= no shrinking, no expanding, at the cost of some render time of cource.

Use this trick in 64 bit PoserPro that can use all available RAM.

Thanks to everyone who provided advice.  I finished my upgrade to Win7 64-bit and reinstalled Poser 10.  So far, all renders have completed without crashing (yay!) but I haven't taxed it with more than a single subdivided V2 figure yet.  I'll keep the suggested strategies in mind and pursue as needed... including a potential upgrade to Pro2014 some day.

Pro 14 has a lot of characters ,don't know what 10 has.

If 10 has Rex & Roxy ,they was made to be SubDed.

You half to have a 64 bit PC to run 64 bit app's.

You can SubD any mesh,but V4 was the first Vicky that was modeled to be SubDed.
For high end app's. V5,V6 was made to be SubDed in Poser.

Meshes made for SubD are 100% Quads no Tri's.
Some will have a few Tri's ,like Dawn made for eather.

Actually Genesis was the first DAZ figure MEANT to be sub-d.  The reduced resolution V3RR and M3RR are lower poly figures that work well with sub-d despite the trigons in their meshes.