Stop caching images / purge G-Force memory
Moderators: BTT, andy55, b.dwall, juxtiphi
-
Guest
Stop caching images / purge G-Force memory
I'm trying to fool G-Force into accepting Live video input by using a program called imagecaster. It is designed to take stills from a firewire DV video camera and upload them to an FTP site or local folder for web viewing. I pointed the program to the sprites folder and set it to re-load every 4 seconds. It save an image from the camera to the same name repeatedly. Then I set up a script in G-Force to use this file as a sprite. Since I have the boot file set to not cache images, I figured G-Force would re-load this image fresh every time I ran the script. No Go. Each subsequent time I run the script it displays the image set at start-up. Is there a way to purge G-force memory while running or really no cache images? Of course if some one has a way to run live video into G-Force another way PLEASE let me know (macintosh OSX)
-
Guest
Re: Stop caching images / purge G-Force memory
On a winXP machine I made a sample script that runs when I press a key that's simply this:
------------------------
PurgeFileCache();
StartParticle( "YourPic" );
----------------------
Every time I press the key bound to the script it reloads the file and shows the new pic. Now I just need that imagecastersoftware, can't wait to try it
------------------------
PurgeFileCache();
StartParticle( "YourPic" );
----------------------
Every time I press the key bound to the script it reloads the file and shows the new pic. Now I just need that imagecastersoftware, can't wait to try it
FAQ item
From the FAQ...
How do I edit configs while G-Force is running?
G-Force caches its files as it goes alone, so file changes won't always take effect until you restart G-Force. However, if you'd like to edit a config "on the fly" (ex, edit a text particle via the LAN then have a preset script call it) you can tell G-Force to load the file from disk each time it goes to use it. If a sprite, script, or particle's filename starts with a '$', then G-Force will not cache it. The other method is to load a fresh copy of a config from disk is to use the key that "reloads current configs" (U by default). Pressing this key will cause G-Force to reload the currently running configs from disk and delete any running particles. This second method is really only useful as tool for config development and testing. For example, you'd making some changes to a config, save the changes, and press 'U' to tell G-Force to reload it from disk.
How do I edit configs while G-Force is running?
G-Force caches its files as it goes alone, so file changes won't always take effect until you restart G-Force. However, if you'd like to edit a config "on the fly" (ex, edit a text particle via the LAN then have a preset script call it) you can tell G-Force to load the file from disk each time it goes to use it. If a sprite, script, or particle's filename starts with a '$', then G-Force will not cache it. The other method is to load a fresh copy of a config from disk is to use the key that "reloads current configs" (U by default). Pressing this key will cause G-Force to reload the currently running configs from disk and delete any running particles. This second method is really only useful as tool for config development and testing. For example, you'd making some changes to a config, save the changes, and press 'U' to tell G-Force to reload it from disk.