YOUR ACCOUNT

Login or Register to post new topics or replies
SpaceRay
SpaceRay

Posts: 12302
Filters: 35
I have Windows 7 64 bit and when installing Filter Forge 2.011 I have installed it in the C: root folder that belong to 64 bit applications so I thought that Filter Forge 2 was an 64 bit compatible software and was optimized to 64 bit.

Then when I installed FF 3.0 beta I was forced to install it in the Program Files x86 folder because it seems that it is a 32 bit application

So I thought that the FF 3.0 Beta was only made in 32 bit, and there would be a future 64 bit release when the FF 3.0 final version was released.

But the great surprise came when GMM wrote the following in another thread

Quote
GMM wrote:

We don't have (and don't plan) a 64-bit version of Filter Forge. It can work as a plugin under a 64-bit host application but it still remains 32-bit.


I am sorry but I do not understand how could I install FF 2.0 in the 64 bit application side if it is NOT a 64 bit version, and then why FF 3.0 is not the same and needs to be in the 32 bit compatibility folder. I suppose that the FF 3.0 is because is still a beta and not the final version.

I must be missing something or having wrong knowledge about how the 64 bit application compatibility works or what can be installed outside of the Program Files x86 folder.

Please, could you explain more about this ?

SO, the FF 2.0 plugin can work under 64 bit host application but the FF 2.0 standalone version is 32 bit ?

Thanks very much
  Details E-Mail
GMM
Moderator
Filter Forge, Inc
Posts: 3491
First, short answers to the questions put in the title:

Quote
SpaceRay wrote:
Filter Forge 2.0 is NOT 64 bit ? How could I install it outside x86 ?


No it isn't. You can install to any location of your choice.

Now I guess I should explain some basics. A 32-bit application is one that can address 2^32 bytes (4 GB) of memory. (Actually in Windows a single app can only address 2 GB but that's another story). A 64-bit application is one that can address 2^64 bytes of memory. Filter Forge is designed to never consume more than 1.5 GB of memory, so we don't need a separate 64-bit version of Filter Forge.

Actually a 64-bit Windows doesn't prevent you from installing Filter Forge to C:\Program Files. Our installer would still suggest C:\Program Files(x86) that is normally reserved for 32-bit software but you can change the location manually. Moreover, if you've got a previous Filter Forge version installed in some location, an update will detect it and prompt to install in the same location.

Quote
SpaceRay wrote:
FF 2.0 plugin can work under 64 bit host application but the FF 2.0 standalone version is 32 bit ?


Yes, both 2.0 and 3.0. In fact the plugin is just a tiny loader that calls the main application and then transfers the rendered result back to the host.
  Details E-Mail
Kraellin
Kraellin

Posts: 12749
Filters: 99
"Filter Forge is designed to never consume more than 1.5 GB of memory, so we don't need a separate 64-bit version of Filter Forge."

i've heard that before, gmm. why the limit there, especially since we now can have more effective ram in a machine?
If wishes were horses... there'd be a whole lot of horse crap to clean up!

Craig
  Details E-Mail
GMM
Moderator
Filter Forge, Inc
Posts: 3491
Quote
Kraellin wrote:
why the limit there, especially since we now can have more effective ram in a machine?


I guess it will require years to rewrite. Maybe Vladimir or onyXMaster could explain this in detail.
  Details E-Mail

Join Our Community!

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

33,715 Registered Users
+5 new in 7 days!

153,538 Posts
+7 new in 7 days!

15,348 Topics
+72 new in year!

Create an Account

Online Users Last minute:

18 unregistered users.