I'm using Poser Pro 2012 and TerraDome 2.

I've been building several exterior desert "sets" for a graphic novel and everything has been working just fine -- even though I'm loading many objects and set dressings into them.

However, on one particular desert set I've created that is actually simpler than others I've built, I simply cannot smoothly move my camera around in Open GL mode and have to use SreeD instead.

Now if I have the scene loaded with objects I can understand why things might slow down but, as I said, this set is actually less complicated than others I have no problem with.

So, I can't help but think that something in the scene data has gotten corrupted in some way. This started to happen as I was adding dressings to the set.

Any ideas on what's going on on?

What is the texture resolution of the scene objects? I have seen Terradome2 promos boast 8000x8000 pixel texture resolution which I think is a little too high. Try switching to wire mesh when rotating the scene or camera. I had the exact problem with a detailed tank prop in PP2014. Switching to a different display solved my problem.

Hi ya. Just guessing here.... This is fairly typical behavour when Poser is operating at the top end of your system's capabilities.
And some items are much larger than others. A fully morphed V4 is something like 4 megs, but the un-morphed version is a couple k! And you can't tell them apart by looking! So... Things that help. Save your scene and reboot.This will clear any memory leaks you may be suffering. If you have programs that open on boot, like mail or skype, close 'em. Now launch Poser. Things should be better.

If it's still slow you'll be reduced to double clicking the dials and manually adjusting the values to get your items properly placed.
Wire frame, if you can stand it (I can't) and you're not already using it, is said to reduce the demands on the PC and allow more responsive behaviour.

Another option is to delete/restore items until you find out what is causing the slow down and replace that something with a lighter weight version. I don't have the patience to actually follow that advice, so it comes completely unencumbered!!

I'd plan to render to the background in this case. If I were proactive and remembered where I left that serious number.....
Best of luck!!! Andy!

Thank you so much for your prompt responses, hborre and donnena-Andy.

I have tried most all of that -- including gradually eliminating dressings from the set -- and the problem still remains if I try to work in Open GL mode. In SreeD, the display's camera movement is fine. Usually no other programs are running in the BG, other than MS Security Essentials and MalWareBytes. I can try killing them to see if that helps.

Since I have more complicated sets I've built that do not display a problem, I am wondering if the issue might have been introduced when I "changed" the TerraDome2 A-Zone material. Surely, the old material is purged from the scene when you do that, right?

I don't mind working in SreeD if I have to, though it doesn't show the skydome texture.

I'm using Poser Pro 2012 64bit on Windows 7 Pro x64. I have two E530 quad-core processors in an Intel Skull Trail Motherboard, 8GB of Ram, and a AMD FirePro V7900 graphics card.

It is a bit befuddling because, as I said, other (even more complicated) sets I've built will display in OpenGL mode with no "sticking". I may try swapping-out a different material on Terradome's A Zone to see if that helps, but I've used the same one on a very similar set that has no issues.

Will let you know what I eventually discover.

Open to other ideas, too, of course.

hborre: I'll check the material map size on the A-Zone next time I open the program.

It's the PC, not Poser...... You can bog down machines with 3 times the ram... it just takes longer! Do you have the means to reduce the physical size of the textures?

I'll look into that, Andy. I may be able to.

I can't remember whether PP 2012 has these options. It may not. But just in case it does: Go to Render>Render Settings> Preview (tab). At the bottom right, there's a slider called "Preview Resolution". Lowering that may help. I have 12 gigs of RAM, but my vidcard isn't OpenGL optimized, and I sometimes have trouble with the display. I have my preview textures maxed at 512. If you don't have those options, you may have to resort to creating a reduced set of textures yourself.

But sometimes the sheer amount of geometry can slow things down, and morphs count, even when not used. First, check out the scene in "Smooth Lined" document mode. Are there any areas of very dense mesh? If there are, that may give you an idea of what you might need to optimize. Next, look at the terradome figure -- how many morphs have you loaded on that thing? Remove all the ones you aren't using. That may help too.

galaxiefilm posted at 8:49AM Tue, 20 October 2015 - #4233696

Since I have more complicated sets I've built that do not display a problem, I am wondering if the issue might have been introduced when I "changed" the TerraDome2 A-Zone material. Surely, the old material is purged from the scene when you do that, right?

Actually, no. Not until you close and re-open Poser. Swapping out a whole lot of textures can fill your cache very quickly. Check out your memory usage with task manager. Then save, exit, and re-open. There is often quite a difference.

If you do a lot of testing with a scene -- for instance, trying every skydome texture to find one you like -- Poser will slow down to a crawl after a while. Closing and re-opening should fix it, though.

@ moriador:

Thanks for all of the excellent suggestions.

As a rule, I have not used more than one morph on a Terradome zone so far. I have experimented with a few combos but really didn't like the results. For this particular set that I've built and am having the display slowdown on, I have closed & reopened the scene & the program several times and still have the issue.

Yes, Poser Pro 2012 does have the preview texture display slider, so I will give that a try and let you know how that works. That sounds like a very likely solution. Mine has been set at 512, which I presume is a default.

Thanks, again!

Well, moving the texture detail slider downward didn't change a thing.

In fact, the performance of the entire program started to freeze-up -- just on this one scene alone, not on any others.

So, I simply deleted the scene entirely and completely rebuilt the set as close to the way it was before as I could -- and the display & program perform just fine on this new scene file.

So, go figure.

I tried everything else.

The only thing I can think of is that something simply got corrupted in the scene file -- somehow, somewhere.