Thanks for NOTHING New Version!

Nice, I'm in the middle of a huge project, go to apply a filter and Filter Forge tells me that it's out of date, download a new version. Fine and dandy BUT, you idiots lock up Photoshop by doing that and now I've lost a good hour and a half of work. How about giving me a popup saying "There's a new version available... download or continue with your old version for now?" instead of just killing the whole process and locking up the application. Extremely poor programming. Oh, and I've downloaded the version on the website and it's identical to what I have already so how do I move forward? Get rid of the date sensitive release betas! It's Memorial Day too so I'm sure nobody will be actually getting around to releasing the new version until tomorrow. Nice way of doing things.

I don't have a problem with releasing a new beta, thats fine... what's WRONG is just shutting it down mid stride and killing my PS app... VERY WRONG. Filter Forge should NOT have control over the app, the app should have control over FF. This can't be the first time this has happened... if it has, I'd call this a MAJOR bug in the 2.0 Beta.

Yeah, that could have been worded more nicely, but the sentiment is one I can share: FF suddenly deciding to kill itself and hang PS in the process? Not. OK.

I was thinking about that too. If it were autodesk, and they were causing me to break commitments, I would be extremely unpleasant to be around.

Well, time-sensitive it's not BUT I had tweaked a few things just right along the way. Each element of the design is saved seperately, I just have to re-assemble. The filter I wanted to apply just happens to be a 2.0 filter. I still have 1.0 installed and working and had it been one of it's filters, I wouldn't have known or cared about this issue. A beta ending is one thing... but a beta ending and disabling an app is a whole other thing.

And I meant "idiots" in a warm, fuzzy, "what the hell were you thinking" kind of way.

Quote
tigerAspect wrote: On the other hand, why are you using Beta software for a time-sensitive project?

QFT,

that said, I'd like to see a "update later" option for FFv1, I too have been pretty annoyed by the "required updates" when I want to just quickly hop in to check something out.

Quote
Vladimir Golovin wrote: The update extending the beta will be released later today (we're compiling it as I write this.) Additionally, it will include two minor features that were intended for the final beta stage.

Cool...Thanks Vladimir....

Thanks Vlad, sounds great

I'm not in the middle of any critical project or anything, but as a regular FF addict I'm starting to shake, cold-sweating and what not.. , and yes its me causing dos attack like behaviour on your server by hitting F5 on beta page every ½ second..

Quote
Thrash wrote: I don't have a problem with releasing a new beta, thats fine... what's WRONG is just shutting it down mid stride and killing my PS app... VERY WRONG.

This shouldn't happen -- at least, that's definitely not the way we intended it to be. Most likely, this is caused by incorrect handling of the beta shutdown date in the plugin DLL. We'll look into this after the programmers have finished the code for Beta Stage 4.

Quote
Sphinx. wrote: as a regular FF addict I'm starting to shake, cold-sweating and what not.. , and yes its me causing dos attack like behaviour on your server by hitting F5 on beta page every ½ second..

LOL..... I haven't stopped clicking my FF V2 desktop icon.....pretending that it's just some minor glitch in my machine temporarily preventing me from my daily FF fulfillment..... .....

Quote
Vladimir Golovin wrote: The update is out:

Thanx Vlad and FF team!!! Just in a nick of time.....I almost lost it.....can't go more than 24 hours FF-less.....

Thanks Vladomir for the resolution and explanations. I have the latest beta in and it's working flawlessly so far and a BIG THANK YOU for adding the CS5 option on the build folder menu! WOOT!

Please read before you delete this string. I've just installed the FF2 beta version downloaded today (2.006, I think) onto my squeaky-clean, new, Win7 64bit with PS CS5 Extended machine. No problems at all -- until I manually copied across all my saved "Favorites" and "My Filters" from the old machine with FF1, plus one or two other settings. The standalone and plugin were incredibly slow despite my 12Gb RAM (time to make a coffee while waiting for the standalone to open), and downloading the first new filter gave me time to drink the coffee and wash up the cup, but by then the libraries had all updated. I rebooted and everything is fine now -- running quickly as both standalone and plugin. This suggests to me that it may be either that the most recent beta has resolved an earlier problem, or as described above, individual computer configurations are somehow at fault. I think I'm probably saying "don't despair", which is unusual, because if something can go wrong for me it usually does ...

Thanks Vlad and FF team for the update.

Vlad, what does the "Diagnostic" stand for? I mean, the AA zone/ AA edges, for what can it be useful? Is there some component that does the same behavior? Is there some thread you guys have discussed about it to read more about this subject?

Thanks in advance.

Thanks Vlad, I'll check this out.