|
 |
 |
|
|
|
|
- Why isn't G-Force showing up in my media player?
- Each media player detects plugins differently, so the best general guidance is to ensure that you're using the latest version of your media player and that you followed the installation instructions carefully. Beyond that, try a fresh restart and running the installer again.
- Why doesn't G-Force respond to my keystrokes or mouse clicks?
- Some media players don't pass keystrokes or mouse clicks to visual plugins, leaving you completely unable to use G-Force's hot-key commands. iTunes for Windows does not pass CTRL keystrokes in a specified way (such that they can be decoded) nor does it pass mouse clicks. You are encouraged to email the creators of these media players and request they add proper keyboard and mouse support for visual plugins.
- Why do I crash, get extremely low frame rates, or have other strange problems?
- Out-of-date video drivers or OS extensions are known to cause problems when using full screen mode, so check for updates and remove unnecessary background tasks. Also, try deleting your "G-Force Prefs" file in the case that it's become corrupted (an endless number of bad things can result from a damaged prefs file). See the following question to generate a fresh prefs file.
- How do I generate a fresh (or "factory") preference file?
- To create a fresh "factory" set of prefs, first ensure G-Force is not running (for some media players, you must exit the media player as well). Next, find and delete the file named "G-Force Prefs". The next time G-Force runs, it won't find its prefs file and will generate a new prefs file containing the default (or "factory") settings.
- Why don't my changes in the prefs file have any effect?
- The prefs file is read when G-Force starts and overwritten when G-Force exits, so any changes made to the prefs file while G-Force is running will be overwritten. Note: some media players internally do not exit G-Force even if you turn G-Force off via a media player command or control (so you must exit the media player in order to cause G-Force to exit and write its pref file).
- Why does G-Force run slowly, stutter, or run in spurts?
- If you're running other processes that use your CPU intensively (such as sound filters/equalizers, virus scanners, file sharing apps) then you will observe skips and/or decreases in frame rate. Quit other processes, disable intensive extensions, disable extra sound processing, and use a clean environment (ie, reboot) whenever possible in order to maximize your frame rate. Also, many laptops have energy saving features that reduce processor speed when they believe that the user isn't using the computer—review your energy saving control panel and disable appropriate features and/or background tasks.
- Why does G-Force stutter or "burp" when it goes to load a config or sprite?
- Unexpected disk access can result in an unsightly visual "burp" or stutter (which is what happens if you manually load a sprite or config that hasn't been recently already read-in). As the media reads a requested file, G-Force must halt because it cannot proceed until it has the file (also known as "blocking I/O"). Hence, if the file is large (such as a lagre image or video file), this stutter can be very noticeable. G-Force uses a cache look-ahead to prevent this (causing the file to be asynchronously read-in about a second before its needed), leaving only manual user actions that result in disk access capable of causing stutters.
- Why does full screen mode look strange or have poor color quality?
- G-Force in full screen mode runs fastest when host display device is in 8 bit mode. Sadly, not all media players and OS environments support 8 bit full screen mode, so G-Force's factory settings are set to use the depth mode best for the player and OS environment. You are encouraged to experiment which full screen mode is most preferable to you using the M and SHIFT+M keys (for players that support keystrokes). Also see the following item and the FAQ for more.
- Why does G-Force look pixelated on my display in full screen mode?
- LCD display devices can only display at the resolution they're built at (ex, 800x600, 1024x768) while CRTs can have several resolution modes. This is because LCD displays by nature have a set physical number of pixels while CRT devices can focus and scan their electron beam differently in order to achieve different resolutions. Graphics hardware is able to support resolutions other than LCD's hardware resolution by using an intermediate frame buffer (of the dimensions requested by the software) and scales it to the actual hardware's frame buffer each frame. For example, Apple G3 PowerBook displays are 1024x768, but Mac OS supports applications that switch to 640x480 by scaling each 640x480 frame to 1024x768. Since 640x480 isn't an integer multiple of 1024x768, the image on the LCD display appears pixelated. You should experiment with different full screen modes in order to find a mode favorable for your display device and personal preferences. Typically, you'll want to choose a small resolution mode (640x480, 800x600 or 1024x768) and use 8 bit mode whenever it's available in order to maximize the frame rate.
- Why doesn't the standalone version respond when I play an audio CD?
- Your computer has to be set to play the CD digitally (ie, not set to play through the CD player's onboard analog player). Many PC systems play an audio CD by passing the analog (ie, non-digital) output of the CD-ROM directly to your speakers, bypassing your digital hardware. So if you don't see any output, your system is playing the CD digitally but you're visualizing the CD-ROM's analog output, or your system is playing the CD analogly but you're visualizing the CD-ROM's digital output. Also see the following question.
- Why doesn't the standalone version respond to any sound?
- Your default sound-in may be not set properly. The standalone version uses your default recording channel as audio input. Go into your control panel and verify that your audio input/recording source is selected correctly. It's also possible you're reading the source correctly but it's not powerful enough to see any activity. Increase the signal level to see if a signal is there (the - + and [ ] keys scale the post-filter and source level respectively). See the G-Force as an Application section for more.
- Why isn't the visual response from G-Force in sync with the audio that I'm hearing?
- Your audio player is probably buffering enough audio that by the time it gets to the speakers it was already passed to G-Force a while ago. Try experimenting with smaller buffer sizes in your audio player to decrease this time delay. Also try consulting your audio player's support resources. Running a large output frame size that maxes out your CPU can put the audio player in an abnormal state of playback, so try reducing the G-Force frame size.
- Why do I hear crackling and/or stuttering whenever G-Force is running?
- G-Force is CPU intensive software. If your system isn't fast enough, then G-Force's CPU demand may compete with your audio player, not allowing your audio player decode audio at a fast enough rate. An audio player's equalizer or third party software that digitally filters audio are also large CPU loads and are common causes for jumpy video in G-Force or audible crackles. Try making G-Force a lighter CPU load by either reducing the size of its window or by decreasing the 'FPS' field in the preferences (FPS is described in the customizing section).
- Why does G-Force say "Factory Default" when it tries load my config?
- G-Force falls-back to an internally stored "factory" config if there's a problem loading a config. Double-check that your config has no missing/extra quotes or comment delimiters and also make sure it's not open in another application.
|
|
|
-
|
|
|
|
 |
|