Update:

Just reinstalled SR2.0 (i.e the one before) and everything is OK now.

What gives?

Well I don't know about others but I've just installed SR2.1 and now P8 freezes whenever I try to delete anything!

Anybody else having problems?

Hi All

Problem Solved!

Although I had a reply from Smith Micro, I still had some difficulty in locating the required files

Many thanks to Dizzi for the suggestion - they showed up straight away and I deleted the neccessary files and restarted P8 successfully

Thanks to all

Hi Laurie

Thanks for your help anyway.  I've referred it to SM for them to sort out

Hope you feel better tomorrow!

Chris

Quote - You want ui Prefs not library prefs in

c:documents and settings/owner/application data/poser 7 

instead of owner it may be your username

Nope, no good.  Looked under Smith MicroPoser8 - nothing listed

Even tried setting the UI Previous to zero within Poser8.ini file - still no good

I guess I'll have to contact Smith Micro direct unless anyone else has any ideas.

Quote - If you're running an OS Vista or above, go to CUsers"Your Computer Name"AppDataRoaming.
Theres a file there called "Library Prefs.xml". Delete that and restart Poser. I'm using Poser 7, and I'm just assuming Poser 8 puts them in the same place...

Laurie

Hi Laurie,

I'm running on XP under SR2.  Checked all the .xml files in P8 and under windows; no such file exists.  Opened the poser ini file and changed the line: library pallete location - still no use!

Any other suggestions or is it best to contact Smith Micro?

Quote - Your best bet is to go to Preferences and "Launch to Factory State". Sometimes that's the only way to get them back where you can grab them ;). Of course, you'll need to set your interface up like you want it again, but...

Laurie

Hi Laurie,

As per my first post, tha's exactly what I DID do (and first) but I still can't access the window - it still 'appears' to be off screen.

How do I delete my preferences file to remove the errant screen location for this window?

Thanks for your help

Thanks guys for your help

PhilC - tried that but with no meaningful result - I may try this on other .obj imports

geogress - Thanks for the download link - tried Twoface and it appeared to work unitl I rendered the object and then got a chequerboard pattern :-o

so...

Thanks to nruddock for your tip on 'normals forward'  -  did that on the 'twofaced' object and it worked!!  (Incidentally, this didn't give a good result on the original single sided figure!)

Once again, thanks guys!!

Quote - Try to "play" with the "background draw" settings in the preferences. This can make a big difference, especially with this problem.

Thanks wabe - I've already done that and set every slider to fast to redue overload.  I'm just ignoring the camera tracker window now and using the on screen handles to move the camera.

Have you heard of others experiencing similar problems - I've scanned though this (and other forums) with no real result

Best

Chris

Quote - Well, Vue doesn't like Radeon in general, is it a recent one?

What you state really surprises me given that Radeon cards are so extensively used!

Can you expand on what you mean about Vue not liking them?

Thanks for your input

Many thanks guys for your feedback, especially Rutra.

I guess I'm going to have to look elsewhere for a decent renderer for my poser scenes. 

Any suggestions, or is Vue (with it's overly expensive add-ons to make it useful) the best?

Just an update:

On the Vue forums, I've seen reference to a tutorial about importing Poser items into Vue which has some valuable information about reducing texture sizes:

http://www.silverblades-suitcase.com/tutorials/htm/18.html

Well worth the read as it's put my mind at rest about duplicating textures, etc.

Many thanks to all for your valuable insights

Vue Easel here I come (when my credit card has cooled down!)

Many thanks for the responses!

Quote - In my experience with Vue 6 under 32-bit Windows, it was a heavy memory user - when I switched to 64-bit Windows and the 64-bit version of Vue 6 Infinite (I know, different version from Easel) it was MUCH better behaved, effectively ending "out of memory" problems.  Maybe others who are Easel users have more information.  From reading the feature lists it doesn't look like Easel offers a 64-bit version.

I'm running P6 under 32 bit Windows with 2 Gig of RAM (and a pretty large swap file!)  so I guess I might still have problems with Vue Easel.  I must admit the quality of Vue renders I've seen is very impressive compared to even the best P6 (and P7) renders, so I think I'll head that way.

One other point.  I'm using Morph reduction scripts and Mini-Me to turn posed figures into the smallest possible file sizes but I still have render problems.  I would guess this is because of the textures overhead across V3 and Apollo figures when they have several items of attire.   Question: does Vue require multiple instances of these textures across a figure in memory or is one instance shared across figure parts?    I believe this may be part of my memory problem with P6 renders

Quote - You need to edit the file Poser 6RuntimePythonposerScriptsmainButtons.py If you open that file in Notepad it should be self evident what is required. Simply edit the path to the Python script that you want to run when the button is clicked.

DOH!  Of course!  A classic example of looking what's really in the box rather than trying to look and work outside it.

I'll try this over the next few days.  I guess I'm going to have to look at some of the subfolders to see how I can change those as well as creating new ones.  Pity that CL didn't think to put in some form of change menu to do what I am asking for!

Many thanks!

Quote - Vue's renderer crushes all versions of Poser in two major ways:
Global Illumination
Area lights (not certain Easel does that, Infinite does for sure)

Thanks for the speedy response but does it have any 'out of memory' issues like Poser?