I created an new file at 400 X 400 at 72DPI, made some
layers filled the with random nozzle images and the same thing
is happening. Is anyone else experiencing this sort of behavior?
Richard
the same thing happens on the mac. i noticed this on the original
painter 6 also, and with all subsequent updates the problem remains. i
just icq'd a friend about this same issue last night. as far as i can
determine it looks like a layer management prob. when multiple layers
are open and a layer somewhere in the middle of the hierarchy is
filtered painter may become confused as to the actual layer being worked
and thus shuts down. i had a similar 'blurring' effect crash the other
day that happened in exactly the same spot twice. the image was 15MB @
200dpi, 10 layers active and visible. i finally decided to render all
layers invisible (shut the little eye) except for the layer i wanted to
filter. no problems. even the preview moved around with no delay. i've
used this workaround in the past.
ghi stecyk
Thanks for the tip. It makes sense. I wish I had
thought of it earlier. At least there is a work around
so I don't have to use KPT 5's Blur filter; which isn't
as responsive as the new Gaussian in 6.1.
Richard
Are you referring to the Painter 6.1 patch?
Jin
____________
Sorry, I should have continued reading messages <G>.
By the way, don't recall if you were on the lists/groups where this was
discussed, but can you explain the number found in the upper left corner
of the Canvas/Resize dialog box? I'd like to get an accurate answer as
to what this represents, or confirmation that it's the amount of memory
used to display the image in Painter (I think that's what someone said..
still confused).. if that's possible.. and figure if anyone knows,
besides the developers.. you would.
Not that it's critical... just curious about it.
Thanks,
Jin
__________________
Richard
Richard
Thanks, someone must know.. unless it was just put there like a rose
stuck behind the ear. <G>
Jin
_____________
As I think someone else pointed out in one of these forums, that number
is the _in-memory_ requirement that Painter will use for the image after
the resize. (Note that how an image is organized in memory is going to
be different than what it would be when written to disk.)
It very likely got placed there during program development, and was left
there because the information is useful to the user as well. Since
Painter is used for professional work, large image sizes are expected,
and knowing what will be required is potentially useful.
Doug Frost