TrekkieGrrl: If it does not crash without IDL and crash with IDL - where is everything located in the scene (so I can create exactly the same one).
You have one point light. What is its location and what are the properties (color, falloff, shading rate,etc). And what are your render settings for the scene? And which camera do you use and its postion.

I tried several render settings and point light postions, but it renders fine with IDL

Trekkiegrrl: I thought I had the same problem as you had, but it was (probably) a different one.
The "crash" message which I had was in fact a "program not responding" error. Once the program responds it will go away. It almost looks identical to the crash message - except that one does not go away. These messages seem to be a windows 7 problem which occurs when you load textures/objects/etc from a network drive and it takes too long.

So in effect - I use the same props as you did and I do not have the problem with it. So I do not think the props or textures itself are the one causing the problem.
If you load the props in an empty scene and - without changing them - render, do you then have the problem you described? And if you render with IDL on?

It is not the model itself or the textures. I had the same problem, but for some reason it is gone now.
I had a reproducable scenario where ffrrender would crash if you rendered the scene for the first time after starting Poser. After I ran the "collect all inventory to a folder" python script all problems with the scene disappeared. The new (collected) scene does not have the problem nor does the original scene.
I tried the scene on another machine and the ffrender crash did not happen there either.
Since the texture names remained the same and the nodes in the material room are the same it must be something else

During preview (and maybe draft rendering) not all textures are loaded - bump, displacement, normal and specular maps These are loaded when the rendering engine needs them. That is why you sometimes get a texture not found during a render and not when you load the object.
It could be that the texture loading mechanism during the renderfase is different and under certain conditions causes this error. But this is just speculation

There does not seem to be anything special - standard texture maps with some of them a reflection node.
It could very well be that the OS (in my case windows 7) thinks ffrender has crashed while in fact it has not and when windows 7 detects that, it removes the message and the render continues.
Renderspeed or choking the processors is not really an issue here (I think). The whole render with IDL calculation takes about 45 seconds.

I tried the same scene with the same props.
The first time I rendered, I got a ffrender crash as well but it kept rendering the entire scene. This was with IDL off. Each render after that rendered fine (without crash) - even with IDL on.
If I save the scene and restart Poser, the same thing will happen - 1 ffrender crash and after that no more crashes
I could be that it is one of the materials which is choking ffrender.
 

Esther: For the girls I used Roogna's schooluniform (shirt), Kobamax's FlareSuit (skirt, blazer is great too!), AdamTwaits Schooldays (Tie, Stockings, Shoes). For the boys I used 3 piece suit from DAZ.

Wim

Why it does not work in your case I do not know. In my experience Advanced Hardware Shading makes things slower and the texture size for preview also has a big impact on memory usage.
Can you see how much memory in Poser is taken up in your scene?

One thing which might help to discover the source of this problem is to turn on logging for texture loading. You can do this by setting WRITE_FILE_SEARCH_LOG to 1 in Poser.ini .
It will write a file in (Vista) "c:usersYourNameAppdatalocaltempposer8.0.
The file is called debugFileSearch.log.

Look at the file when Poser reports the "Texture not Found" error and look at the end of the log file what actual filename it looks for. This might provide a clue what is going on.

The only problems I have had with Texture not Found is a bad reference, but this has been the case in all versions of Poser. I use the logfile often to find which file is missing.

Set texture preview size to 256 or lower in Preview Render settings. This will enable you to load more characters in the scene.

**NoelCan, your attitude leaves much to be desired. I state my personal feelings
**

They are trying to make things easier for the inexperienced user who does not have a clue how things work.
The problem is that they are making it much more tedious for the experienced user and they forget that every inexperienced user tends to get more experienced.

My favorite example is the hidden scale dials in the latest generation of DAZ figures

Bagginsbill is right.
We get what we ask for. There are a lot of people (including me) who want to work with bloated runtimes and be able to manage these runtimes. I want to be able to find, pick and use props/clothing/hair and other stuff as best suits my needs/ideas. Yes, I can model them, but that takes a lot of time which I rather spend on composing and detailing a scene. That is what I like  to use Poser for.
Sometimes I want photo realism in my renders but often I only want it to look real and not necessarily be a fysical perfect representation of it. A 3D application allows you to create real and not so real scenery which you are unable to do in the real world. Here you want the illusion of reality and not necessarily the real thing.

And yes, I also want all the goodies mentioned here in this thread and more....
 

Turning off Enable Hardware shading in the render settings for the preview might improve the speed in preview mode as well.
 

My join date is feb 25, 1999, number 316
I am one of those people who usually lurks - unless I have something useful to say. After I got burned in the early 80's on alt.sf-lovers on usenet I seldom joined forum conversations.

I did a search on my hard drive to see what the oldest poser freebie was which I ever downloaded.
It is Poser 3 poses - RockstarPoses.zip from Daniel "DD" Nichols file dates 14 feb 1999

Anyone remember anything earlier?

Wim

Adding new items took about the same time with the update as the first time (about 4 hrs).
Crossreferencing took only a few minutes. (luckily the factorization of 3x10^25 is not the case...)
I did get two errors though - the one with the icons and another one after adding the new items. Is there a way to log these errors?

Trailing spaces do not work as a filter, it is cut off at data entry level. Preceeding space does work.

I am curious about other users with a 1M item list and the performance updating new items with multiple runtimes.

Wim

]