YOUR ACCOUNT

Login or Register to post new topics or replies
Iam Nemo
Posts: 13
I get this nagging persistent problem with FF 1.014 Pro when used as a filter plugin in Photoshop CS3 under Windows XP Pro SP3 with 4GB RAM and 8GB swap space and plenty of free disk space:

Whenever I am trying filters (any) in FF on one of my images (any size) FF crashes (and freezes Photoshop in the process) and gives me this error message box:

"Failed to Create Event" followed by another box with "...X86 SSE2 Fatal Error".

I cannot pinpoint the exact conditions. Seems to happen ALL the time these days. I reinstalled FF and PS CS3 with same result. Could it be caused by trying another filter before completion of the preceding one?

Any idea please??? Thanks Iam Nemo
  Details E-Mail
CFandM
ForgeSmith

Posts: 4761
Filters: 266
I am not on the staff for FF but my guess would be exactly that reason...It like most plug-ins is always best to let the effect finish doing what it is doing before applying another one..Or in this case running thru Filter Forge again....
Causes confusion within the plug-in and ultimately lock-ups, freezes and crashes...
Stupid things happen to computers for stupid reasons at stupid times!
  Details E-Mail
Iam Nemo
Posts: 13
Sorry I didn't see your reply before. Thanks for replying. BTW I sent the same question to FF tech support and never received an answer so you're way ahead of them on support smile;)

I also suspected this to be a problem but FF also crashed while I was changing parameters on the first filter I tried. How can one prevent FF from starting calculations as soon as a parameter is changed ever so slightly? Waiting for each parameter change to be effected completely, IMHO, would limit FF's usefulness as a filter.

Thanks! Iam nemo
  Details E-Mail
Carl
c r v a

Posts: 7289
Filters: 82
One thing to speed it up is to turn the antialaising off [ Defaults to 5 ] while you fine tune the parameters, then turn it back on when you want the final render smile;) smile:)
  Details E-Mail
CFandM
ForgeSmith

Posts: 4761
Filters: 266
Quote
Iam Nemo wrote:
Sorry I didn't see your reply before. Thanks for replying. BTW I sent the same question to FF tech support and never received an answer so you're way ahead of them on support Wink


hehe smile;) smile:)

I agree with Carl..Turning off the antialaising will speed up things a bit..
Stupid things happen to computers for stupid reasons at stupid times!
  Details E-Mail
GMM
Moderator
Filter Forge, Inc
Posts: 3491
@Iam Nemo: The developers say the bug is almost as old as Filter Forge itself. Unfortunately we haven't yet been lucky to reproduce and locate it.
  Details E-Mail
Iam Nemo
Posts: 13
Thank you guys; I will try turning the AA.

@GMM: thanks for your reply. I have used FF extensively with PS CS3 before and never had this problem (at least never that bad for sure). It seems it has appeared with my upgrade to the last couple of minor versions.

Any suggestion from the developers? Should I revert to an older version or move on to using PS CS4? Thanks! Iam


  Details E-Mail

Join Our Community!

Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!

33,711 Registered Users
+18 new in 30 days!

153,531 Posts
+39 new in 30 days!

15,347 Topics
+72 new in year!

Create an Account

Online Users Last minute:

18 unregistered users.