YOUR ACCOUNT

Login or Register to post new topics or replies
westdale

Posts: 60
Filters: 7
I discovered this issue when testing v11
I have Studio V10 running on Pc and laptop, I have a local NAS drive ( and also some public cloud ) which enables me to share work.
I went to open a trial project in v11 and it told me that an image in App Data \ Local \ Temp could not be found - it then hung completely needing task manager to kill it.
Repeatable hang.
Sudden realisation --- Filter Forge is saving shareable data in App Data \ Local --- consequences are obvious.
Images for a project should be stored in the project file , no? Accepted that caches can be in App Data but not the actual images or filters.
Further investigation ongoing ....

Ed. Possibly the beta 11 is allowing me to work with projects which should be sharable but is storing the information in an unsharable way because the beta licence is not flipping some switch somewhere to use shared storage. ?
  Details E-Mail
GMM
Moderator
Filter Forge, Inc
Posts: 3491
westdale, we're unable to reproduce your issue. Please send the failing project file to the support team.
  Details E-Mail
westdale

Posts: 60
Filters: 7
EDIT - thought I had found one cause ....
If I leave a FF running on one computer, the temp files on C: are not tidied away in to the project files so opening the project on the other computer fails when trying to access them as it obviously has a different C: drive smile:-)

But Edit -- this issue only needs one computer.....as I found this morning
FF10 created project on the NAS drive - including a picture from C: desktop.
double click the project and it opens in FF11 and reports the missing temp file and hangs

Please advise how to send the project file as I cannot attach it here and the normal reporting mechanism doesnt take attachments.

The cause appears in both cases to be incomplete closure of FF so the temp files are not rolled into the project.
Not easy to reproduce!
However there is an issue in FF11, in that it hangs completely (needing Task Manager abort) if it attempts to open a project file in this bad state.
  Details E-Mail
GMM
Moderator
Filter Forge, Inc
Posts: 3491
Thanks westdale, this makes things much more clear.
The cause of this behavior is not FF running on the other computer but that your project is open on that computer. You don't need to terminate FF, just select File > Close Project.

This is generally expected behavior. You can open a Microsoft Word file on the first computer, then try to access it on the other computer: you will get a message the file is being used, and Word will refuse to open it.

The issue with FF is that we don't perform this kind of checks, and FF just keeps loitering around waiting for the file handle to close smile:) We'll do something about that, someday.
  Details E-Mail

Join Our Community!

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

33,710 Registered Users
+17 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:

17 unregistered users.