"While it may be feasible to work *Arial* or similarly simple fonts into the mesh, it would not be so with *Hurricane* or other flowery cursive fonts.  In general, florescences and such organic shapes are very expensive in terms of poly count."

Here is "Rage Italic". It's 33000 polys with the hi res cube and 12000 with the lo res cube. (The "roughness" is actually part of the font and not a render error.)

Render time 22sec.

---

As for RAM use, sorry, but even laptops are 64bit and have 4 to 8-GB RAM these days on average. My 3 year old Acer is definitely not a high end machine.

There comes a day when you simply have to stop worrying about users with 10 year old gear and copys of Poser that are several versions behind.

So everything I write about refers to PP-2014 and "average" computers, only.

I often cursed Poser in the past for freezing when I tried to import a wonderfully detailed high res model that was made in Max.

And wished for a low res version with a displacement map instead.

But that problem is gone at least since PP-2012, and now polygons are no longer a problem.

That's my point: People are still stuck in the past because once lots of polygons were bad for Poser and they adapted to it.

But now it's the other way round and textures are the bottleneck.

Of course there are always extreme cases where one is better than the other.

But this is exactly what I try to find out.

 

:-)