It seems not too bad, on the face of it. It appears to be saying the geometry will be loaded, but I might not be able to apply textures to it. Not to worry, I was using procedural materials anyway; and if UV mapping is required, I still have the OBJ file I imported and I can get the mapping back easily enough.

That error message isn't wholly accurate, as it turns out. Who'd have thought it? :)

What it really means is this, roughly translated: "Your geometry has been removed, and in its place I've substituted a randomly coloured cylinder which can't be deleted, or even made invisible. Have a nice day. :P"

It's a good thing I keep back-ups, huh?

I'm not looking for a solution, by the way. I just wanted to share the weirdness with you. I figure that, where Poser is concerned, there are some things us mortals are not supposed to dabble with. If there's a moral to be taken from this tale, it is that back-ups can be quite useful.

Have a nice weekend, Poser users, and may your texture coordinates never go bad. :P

(Message text, for the benefit of the forum search and text-to-speech users: A geometry being read in has bad texture coordinates - they are being removed.)

Much apreciated. When it's been removed, could it have saved to a different location? Since poser uses a folder under My Documents as well as a runtime in programs.... Also maybe the file was bonked when saving due to another program (anti-virus) scanning the files while in operation? Just grasping at straws to guess.

There's quite a few in there that I've never seen. I must have led a sheltered life.

haha,

you must have found the MakeArt button, and now the machines are taking over...

I, for one, welcome our new digital overlords. :)

Yeah, you always gotta have backups when you're working with Poser.  Sometimes it seems like it was put together sideways, or maybe it's held together with paperclips and sticky tape, for all the weird bugs and odd behaviors it displays.  I keep having this problem when working on projects, which I call the "Just one more thing..." problem.  Work for hours on something, finally make some breakthrough with the project so it represents what you consider the best result you're likely to get.  That point would be where one should save the file and keep that copy as a backup, right?  But Cage keeps deciding, "Let's just try one more quick thing."  Maybe it's a (presumably) quick cloth simulation.  Or cleaning up a couple of the shaders, trying to collapse them into those fancy, new Compund Node thingies.  Something that should be simple and quick, and if Poser is truly stable and reliable and really has the capabilities they advertised when they sold it to you, doing this thing should pose no problems at all.

You know what happens next, of course.  That one last thing crashes Poser, or causes Poser to swap around all the carefully-devised shaders on the figures, or something weird and unexpected.  Work is lost.  Small objects get thrown across rooms.  Usually there is cursing.  The worst part, for Cage, isn't the lost work.  It isn't the loss of trust in Poser, the disruption of the creative workflow, the self-loathing that follows these episodes of seething hate and rage, nothing like that.  The worst part is that Cage knows he's going to have to go talk to the $^#(*%!!!~ Poser Customer Support threshold guardian.  Again.  Tarim's Teeth in a bucket, I hate talking to Poser Customer Support.  :cursing:

Always back up your stuff.  I repeat that here, hoping that I will remember it.

Well, "Just one more thing..." is one of the attractions of Poser, to me. As noted, it does sometimes bite you in the arse instead of providing entertainment.

I always try to remember to save before I do something risky, such as render, run a cloth simulation, or turn IK off. :) Sometimes I forget to save, sometimes the supposedly innocuous little thing I was doing turns out to have been more risky than I expected; but on this occasion, as far as I knew I'd saved a perfectly functioning scene without mishap. How wrong I was...  

Quote - I always try to remember to save before I do something risky, such as render, run a cloth simulation, or turn IK off. :) Sometimes I forget to save, sometimes the supposedly innocuous little thing I was doing turns out to have been more risky than I expected; but on this occasion, as far as I knew I'd saved a perfectly functioning scene without mishap. How wrong I was...

The trouble, I find, with PPro14, is that the range of "risky" somethings has been extended into a wide range of things which were previously always stable and trustworthy.  When in the history of ever has the Materials Room provoked app crashes?  It was always stable.  I just had a crash because I opened the Hierarchy Editor, for Tarim's sake.  Lost two hours of work.  Has the Hierarchy Editor ever, ever been unstable before?  This is getting to be worse than Poser 8 before the third SR made it stable for me.  Grumble.

I'm going to have to start running the autosave Python script again.  I hate to do that.  I don't quite trust Poser's Python callback functions.  I've seen weird things happen with those.  But it may be time for me to resort to that.  Sad, sad.  One wonders what they must be doing to poor Poser, to make it act up like this.  Are the Poser Team jabbing Poser with sharp objects, during development?  Giving it massive trauma and neurosis, I know not what?  It's acting like the freaky, traumatized chihuahua I once knew.  Every now and then it just has to go berserko, because its wires have been all crossed around and mixed up.  :unsure:

Quote - When in the history of ever has the Materials Room provoked app crashes?  It was always stable.

If you want a quick way of shutting Poser down, with none of that tedious asking whether you want to save malarkey, try applying an MT5 that contains animated values. Do not pass 'Go', do not collect 200 local currency units, bam, straight to the desktop.

I'm sticking with Poser 7. Let them scoff. :)

Quote - If you want a quick way of shutting Poser down, with none of that tedious asking whether you want to save malarkey, try applying an MT5 that contains animated values. Do not pass 'Go', do not collect 200 local currency units, bam, straight to the desktop.
I'm sticking with Poser 7. Let them scoff. :)

Poser 7 seemed to be pretty together, nice and stable, IIRC.  I'm sure the dodgy, crash-prone releases didn't start with SM taking over Poser and Poser suddenly being on a bi-annual update schedule, but... it sure seems that way sometmes.  Pretty sure Poser 5 had big problems when it first came out.  :unsure:

Interesting link.  I recall seeing it, some time ago, but didn't pay much attention.  But, see, I might suggest that the crash there is related to Poser's limitations with actor dial handling.  It's not so much the Materials Room crashing as Poser library system bugs crashing the Materials Room.  :unsure:  But it is a Mat Room related crash, so perhaps I quibble.  :lol:

What was the solution you found, for your original problem?  Did you manage to track down the geometry that provoked the error?

Quote - I might suggest that the crash there is related to Poser's limitations with actor dial handling.

Nods

Quote - What was the solution you found, for your original problem?  Did you manage to track down the geometry that provoked the error?

My solution was to recover a very recent backup and work forwards from there. It wasn't a lot of work, fortunately.

I did pry into the PZ3 with an editor, and I found a mis-matched pair of prop statements; the first called up the cylinder primitive, the second was associated with the imported geometry. I tried deleting those but the error persisted; so I gave up. ;)