Thanks. "Modern versions of MacOS" is a little vague, but the rest is there. Just need to figure out whether my present system will hack it...

(...and the detail is now on the store upgrade page too. :) )

The Poser 13.1 upgrade page has Mac in the headline but only mentions Windows in the description.

If it is available for Mac, what are the system requirements now?

I have the same problem with order number 112760165 and Paypal transaction 6RY09754X04242528.

Ah! I knew I'd got those CopyHairSettings scripts for something... Then I went away on holiday...

Any progress on an updated version of Furred Cat, Tiny?

Quote - Yes, unfortunately every hair group need to be changed.

Now I'm confused. The cat has a "Fur" material and a "Whiskers" material. I'm guessing I missed a whole bunch of material settings for the fur that aren't under the cat...

Quote - But there is hope! :biggrin:

I think I might wait for your fix. Sounds like much the easiest (and safest) solution for me. ;)

Thanks. Does it need changing on every material, or just particular ones?

I'm working with the furred cat, who shows the same grey hairs.

Fur already has "None" selected on its image map. This is the one I'd have expected to need to change, but it seems it doesn't. All the other image maps are set to "Quality", but they only seem to relate to particular body parts...

Quote - Set the texture filtering to none. Doh...

Dumb question time: Set which "texture filtering" where?

I'm guessing it's a setting on nodes somewhere in the Material room?

It sure helps when problems with the software are presented in a reasonable and informative manner without mud-slinging rants and general animosity. I'm interested in learning where the problems are, but not at all in how angry this makes anyone.

For the record, I've found that SR2 does seem to have improved IDL render times at least some of the time, but it also seems to produce slightly brighter renders for the same settings (I generally start at IDL RT: 3, IC: 25, ILQ: 3, PS: 3, MSR: 0.5) than SR1.

SR2 has not fixed the way "Save" sometimes remains greyed out after Material Room changes are made, and mimimising Poser while it is rendering still doesn't always work properly.

(All these based on Poser 8 running on an iMac with OSX "Tiger".)

(Edit: remove quote from deleted post.)

Cumulative lists are all very well, but sometimes folks want to know what's changed this time... ;)
Is there an accessible official list of things fixed in SR2 since SR1 was released?

I guess that means there'll be an SR3 sometime. Is the list of fixes in the SR2 ReadMe a cumulative one of everything fixed since the original release, or is it just those things that have been fixed since SR1 was released? (It looks like a cumulative list to me, but my memory could be flakey.)

...and if your files contain relative paths, where should they start? I've seen files taking these possible options:

1) Starting with :Runtime:... like this:

   figureResFile :Runtime:Geometries:...
   reflectionMap ":Runtime:Textures:...

2) Starting with the directory inside Runtime:

   figureResFile :Geometries:...
   reflectionMap ":Textures:...

3) Sometimes even taking it one level further:

   figureResFile :Creator:...
   reflectionMap ":Creator:...

In my experience, the third case almost always causes problems, and the second case sometimes does. If I ever find troublesome files I always edit them to use the first case (which might, I suppose, be what's meant by "absolute path" in this thread?).

Of course, very occasionally full absolute paths like "C:......Runtime...." turn up, and they always cause trouble... ;)

Did you try (say) downloading the copy from the forum here and checking to see whether it still misbehaves on your system?

If there's a problem with that image then it's a problem in the specific format of your copy.

Once it's been through whatever mangling this forum uses to tidy up images for posting it is called "file_440349.jpg", is "JPEG image data, JFIF standard 1.01", is 242163 bytes long, and works fine as a background, at least in my copy of Poser 8.

Quote - I run Poser Pro  .  All is fine until I start rendering,  then things start going wrong..

I QUIT Poser.  Things continue in the wrong position until I shut down..

Ok. Open a Terminal window and run a command like this: **top -s 5 -F -o cpu -O vsize
(I'm on Tiger, but I hope Snow Leopard has "top" installed as standard.) It will display (and then update every 5 seconds or so) a table like this:

** Processes:  61 total, 4 running, 57 sleeping... 208 threads            16:19:53
Load Avg:  1.04, 1.05, 1.05     CPU usage:  49.8% user, 3.0% sys, 47.3% idle
SharedLibs: num =    0, resident =    0B code,    0B data,    0B LinkEdit
MemRegions: num =  8242, resident =  632M + 17.8M private,  204M shared
PhysMem:   293M wired,  219M active,  928M inactive, 1.41G used, 1.59G free
VM: 7.94G +    0B   41784(0) pageins, 0(0) pageouts

  PID COMMAND      %CPU   TIME   #TH #PRTS #MREGS RPRVT  RSHRD  RSIZE  VSIZE
  471 Poser 8    100.1%  2:17:28  11   157  2290   412M- 99.1M   438M-  962M
   63 WindowServ   1.1%  2:45.82   4   324   594  10.5M+ 71.7M- 67.4M   278M
  499 top          1.1%  0:00.23   1    18    20   996K   796K  1.45M  27.0M
  486 Terminal     0.8%  0:01.24   6   136   178  2.81M  12.9M  21.4M   237M
  197 firefox-bi   0.7% 11:03.75  11   192   952   139M  45.2M   165M   432M
    0 kernel_tas   0.4%  2:13.58  47     2   444  5.62M     0B   213M  1.44G
..... and lots more .....

There'll be a list as long as the window, probably. Interesting values are: - the CPU usage on the second line

• the PhysMem and VM lines which tell you how your memory is being used and whether there's a lot of pageing happening.
• the process by process CPU use in the %CPU column
• the process by process RSIZE (real memory used) and VSIZE (total virtual size) values

This is much what the Activity Monitor is doing, but in a much handier cut-n-paste-able form. In my example above you can see that Poser 8 is being very busy on one CPU (at near enough 100% - it's running Wardrobe Wizard) but that the other CPU is more or less idle, and that there's plenty of spare memory.