Hello,
I have read that the Page File is very important and needed for the seamless flowing work of Filter Forge (as it happens with most applications) BUT I think that in this case FF could be more important and could demand special requirements.
HOW Filter Forge works with the Paging file ? Is very important that it is inside the C: drive or it can be in another different drive ?
HOW Filter Forge makes and works with it´s own "temporary files" ? Are they located inside the C: drive where the software is installed ?
Could it be that FF is 32 bit only, and even using it in the Program X86 folder, could have problems in a 64 bit Windows 7 ?
AND MORE IMPORTANT does the paging file required by Filter Forge works in the SAME WAY for BOTH VERSIONS either plugin or standalone ?
And as a plugin is the same if the host is Photoshop or any other compatible softare?
I have taken out and transfered the paging file from C: drive (system drive) to E: drive and now have 32 GB of Page file Size in E: and 0 GB in C:
This was because I have seen that it was recommended to move the pagin file out from a SDD drive as it could be a problem for the life of the SDD drive.
All the applications I have does not care that the page file is in E: instead of C:, and I do not get any error from other application in reference to memory problems.
The only apllication I have a "bad allocation" error problem is in Filter Forge 3.06 Pro
From the text below from onyXMAster I wonder HOW Filter Forge works with the Page File and the temporary files
| Quote |
|---|
oniXMaster wrote:
"bad allocation" means that you ran out of available memory.
Please try the following:
1) ensure your paging file size isn't lim ited by a setting in Control Panel->System->Advanced->Settings(Performance)->Advanced->Change (ideally it should be System Managed and you should have enough space on disk, I recommend several tenths of gigabytes)
2) reduce the amount of memory Filter Forge uses for it's internal computations (go to Tools->Options...->Rendering and set the Maximum RAM usage slider to something like 60 instead of the default 75)
Also please ensure that you have enough disk space for both paging file, you can check it in the same location as 1) ) and Filter Forge temporary files (available in the same location as 2) ).
P.S. Test With 10000 x 5000 image sizes with properly set up paging file. The fact that other filters render fine makes me think that you're running out of disk space (there are two bitmap-based components in there, with such resolutions the temporary files alone might take from 3 to 6 gigabytes |
