[Geoff Vane]

I have got it to work again.

Procedure:

-Deinstall
-Computer off
-Install
-computer off
-Run

Not turning the computer off, results in errors.

[Geoff Vane]

Thanks for the standard method.

I’ve created an emitter from hell.
It contained a full color avi of 2 minutes.
That will mess up things quite nicely.
I have deleted it now.

Hence my question how to go to the limit of PI, with some calculations to avoid serious problems.

I was thinking, working with software rendering from the start, could that give more room for my evil experiment?

[Geoff Vane]

I have found the cause.

My attempt to push an emitter to the memory limits, has resulted in an emitter which disturbs PI completely. By renaming it, PI could get over this bump and startup correct again.

A question emerges: How can I get rid of a buggy emitter in a library? I now did this with the library manager with the particles disabled and I was very lucky no crash occured. Is this the best way to do it?

[Geoff Vane]

Thank you so far Elvis,

But I need your help to really push PIL3 to the limits in terms of emiter size and length.

Looking at the taskmanager I find under physical memory the total memory, the available memory and the system cache.

Could you -for example- tell me which percentage of which memory count, the size of an emiter avi can be? (say 80% of the available memory or so)

If I know how to calculate things, I can push the limits without having to try many options.