Fri, Nov 22, 2:42 PM CST

Renderosity Forums / Poser - OFFICIAL

All Forums

Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 21 6:06 am)

Poser Gallery - Poser Freestuff

Subject: Parmatic error in Poser 7 Pro

PapaBlueMarlin opened this issue on Apr 30, 2008 · 10 posts
Back to Forum Print
PapaBlueMarlin ( ) posted Wed, 30 April 2008 at 4:21 PM · edited Fri, 22 November 2024 at 2:20 PM

I copied parmatic from my poser 7 runtime into my poser pro runtime.  I have gotten a parmatic updater error message with a traceback error.  Has anyone else had this problem?


nruddock ( ) posted Wed, 30 April 2008 at 5:36 PM

Quote - I copied parmatic from my poser 7 runtime into my poser pro runtime.  I have gotten a parmatic updater error message with a traceback error.  Has anyone else had this problem?

What's the error message ?

PapaBlueMarlin ( ) posted Wed, 30 April 2008 at 5:42 PM

It's a trace back error - I didn't save the message.  I'm getting the same problem with real skin shader so I think it's an issue with Pro and old python scripts.


bagginsbill ( ) posted Thu, 01 May 2008 at 8:07 AM

I need to see the error. Might be easy to fix.

Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)

semidieu ( ) posted Thu, 01 May 2008 at 3:03 PM

Intersted to know too...

PapaBlueMarlin ( ) posted Thu, 01 May 2008 at 3:58 PM

I'm trying to figure out how the parmatic error occurred.  Once it occurs again, I will be sure to save the error and post it here.  On a side note for python scripts, I've found that there is a problem with the real skin shader sets, but stewer's turn off texture filtering still works.


PapaBlueMarlin ( ) posted Thu, 08 May 2008 at 8:57 PM

These are the error messages that I'm getting:

Traceback (most recent call last):
  File "C:Program FilesSmith MicroPoser ProRuntimePythonparmaticparmaticUpdater.py", line 131, in ?
    ParmaticCameraUpdate()
  File "C:Program FilesSmith MicroPoser ProRuntimePythonparmaticparmaticUpdater.py", line 118, in ParmaticCameraUpdate
    for mat in materials:
TypeError: iteration over non-sequence

Traceback (most recent call last):
  File "C:Program FilesSmith MicroPoser ProRuntimePythonparmaticparmaticUpdater.py", line 131, in ?
    ParmaticCameraUpdate()
  File "C:Program FilesSmith MicroPoser ProRuntimePythonparmaticparmaticUpdater.py", line 118, in ParmaticCameraUpdate
    for mat in materials:
TypeError: iteration over non-sequence
Traceback (most recent call last):
  File "C:Program FilesSmith MicroPoser ProRuntimePythonparmaticparmaticUpdater.py", line 131, in ?
    ParmaticCameraUpdate()
  File "C:Program FilesSmith MicroPoser ProRuntimePythonparmaticparmaticUpdater.py", line 118, in ParmaticCameraUpdate
    for mat in materials:
TypeError: iteration over non-sequence


bagginsbill ( ) posted Thu, 08 May 2008 at 9:15 PM

Ah yes. I remember this. It's easy to fix.

The problem is that there are occasionally certain wierd "actor" props that are not really body parts, but they seem to be, according to the rules as stated by EF or SM or whoever.

Anyway, there are such objects that should have a material list, but when you ask for it, it barfs and gives not an empty list, but instead a "None" object.

This is becoming more and more annoying as more and more of these show up. One of the other Python script gurus (philc maybe) showed recently how he had to check like 20 exceptional cases to get this business to stop breaking one of his scripts.

It's happening a lot more with Poser 7 than it ever did with Poser 6.

I'll get an update out to you soon. Hopefully tomorrow.

Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)

PapaBlueMarlin ( ) posted Fri, 09 May 2008 at 4:09 PM

Thanks for looking into it :)


semidieu ( ) posted Fri, 09 May 2008 at 4:12 PM

I have the same problem with those 'special' props.

Didn't tested it, but couldn't be possible to use the 'Visible In render' ? I think most of the problematic actors aren't visible in renders...

Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.