Why does this happen? Is it a glitch? Has this been fixed?

Any info on this would be great.. Thanks:)

I haven't had it happen yet, even on OBJ of 500K polys.

What size and what program used to make OBJ?

Which OBJ? I've been creating heaps of OBJ files in Blender, and the only time I've ever had an issue was when the OBJ itself was dodgy. PhilC kindly helped me out with that.

I believe there are tools available to verify an obj's integrity.

Yes. If all other .obj files inport then your model is wonky.

You might try MeshLab (trying to remember the name earlier) - just to make sure the OBJ is squeaky-clean.

Hi,

I've the same problem only with PP2012. I can import the obj file (exported from Cinema 4D with Riptide Pro) in Poser 8, In MeshLab and also in Vue 10 Inf, but not in PP2012 - it crashs like the screen.

Please take a look at the screens

http://s7.directupload.net/images/user/120220/4az6wvsy.jpg

http://s14.directupload.net/images/user/120220/3c4gdb39.jpg

http://s14.directupload.net/images/user/120220/chjl368z.jpg

Did someone know a reason?

Greetings Amigo

Quote - Hi,

I've the same problem only with PP2012. I can import the obj file (exported from Cinema 4D with Riptide Pro) in Poser 8, In MeshLab and also in Vue 10 Inf, but not in PP2012 - it crashs like the screen.

Please take a look at the screens

http://s7.directupload.net/images/user/120220/4az6wvsy.jpg

...

Not sure, but if i forget to assign a material to the obj in the modeler, poser will crash, too. Not when importing it, but when saving it. This is based on poser2010, though, but something similar might be the case for 2012 (the screenshot with the white dress gave me the idea).

I also got this after I installed SR1. All objs even the perfect ones crash Poser. I get around it by importing in Poser 7 instead which I have kept for compatibility purposes but it is annoying. The problem is reported to SM several times.

That's interesting... because it never happens to me unless the model is wonky. And I've made all the models that crashed PP 2012.

"because it never happens to me"

Because it never happens to most people. Nevertheless, a bug was introduced in SR1 that affect us unlucky ones.

I am thinking the problem is connected with "localization".

The problem seems to occur on systems that use a "," (comma) where the standard version uses a "." (period)

vintorix,

I meant no disrespect... I honestly found it interesting and am wondering what causes it.

Sorry about that.

No problem. I will test Medzinatar's suggestion later - I cannot retart just now perhaps I dont have to restart but haven't time to find out..

Funny enough..my poserpro2010 imports any obj without any issues. Daz imports the exact same obj without any issues. It's just with poserpro2012 it crashes. So for now I have to import it through pro2010, save scene and then work on scene in 2012.

Do you use a comma   ,    as a delimiter?

I changed to using a period but i didn't help, even after restart.

Why should we have to change anything if the obj opens in all other programs and previous versions of poser? What makes poserpro2012 so special? It is an inconvenience end of story. 

Wasn't a response to what I asked, but that's okay. You shouldn't have to change anything, V01f.

I read on runtimedna that one of the poser developement members is looking into it. There were complaints that side as well. Robynsveil my response was not directed at anybody. Just stating that having to change anything should not be needed and that it should just work, like before.

I see that the Poser users are spoiled. That is the advantage coming from Vue. We Vue users are hardened. For every Poser bug there is least 10 Vue bugs, usually much worse.  I mean no disrespect but Poser users are tenderfoots..

really..

I see your point of vue, BUT if something used to work and doesn't in a later version, does that make any sense?

 V01f my dear fellow the right attitude to have is one of timid optimism, like "Perhaps today there will be no problem?"

Are you familiar with Marcus Aurelius, the roman emperor and author? No?
He adhered to stoicism, a philosophy I warmly recommend. For instance observe how he handled annoying people. (You think that if you are a Roman Caesar you don't have to meet annoying people but obviously you have to..) Every morning Marcus said to himself, "Today I know that I will meet at least one unreasonable person". Then the day roll along and then, lo and behold comes the unreasonable person. Do Marcus got angry? No no, he just said to himself. "I was right again!".

i had this same issue after installing sr1.

i had poser installed to a external drive, i then reinstalled poser to c drive default directory and only put runtimes in external location.

no issues sinc, all working as should.

hope this helps

have "poser [installed] to c drive default directory and runtimes in external location"

That is the way I always have  it so I can't try that. Even if the comma thing didn't work it has probably something to do with localization. This is my punisment because I was too lazy reinstalling to an english version of Windows, which I normally alwys do, sigh.

@Vintorix

"I was too lazy reinstalling to an english version of Windows"

Do you use a swedish version of Windows?

Im a fellow Swede and i use Swedish Windows 7 Home Premium SR1 (64-bit) with Poser Pro 2012 SR1 (64-Bit), got curious and imported a few random *.obj´s and they all worked fine.

Maybe we can compare system/installation paths?

(skriver på engelska för att inte stänga ute övriga forumdeltagare)

Hi jonny nice to meet another fellow citizen. Normally I always use an English version of OS less problem that way.  But now we know it isn't that, hmm starting to get curious! ;)  Usually when you lay down your problem in a forum with as many users as the Poser forum the solution should arrive pretty fast. But not this time!