|
For general (non-technical) questions or comments, click here to send an e-mail. For help with technical problems, please see the rest of this page.
If you need help installing InterAx in a multi-user Windows environment, click here.
If your problem is accompanied by an error message, please see the Error Message section below. If you do not receive an error message (or receive an error message not listed below), please see the links at the bottom of this page.
Windows Vista Notice: As shipped, Windows Vista does not support the older Windows help file format used by this software (.hlp). Because of this, you may not be able to view the included help file if you are using Windows Vista. Microsoft has released a free update that will allow help files in the “.hlp” format to be viewed on Vista. To download the free update (for Windows Vista only), click here.
Error Messages during installation:
"Error in compressed file - Bad CRC" - This error can occur if you have a “bad download”. When Setup is run, it checks the integrity of the Setup file itself. This error is generated if it is determined that the Setup file has missing or corrupted data. To fix the problem, you simply need to try downloading again. Following the steps below should increase your chances of being successful on your next download attempt:
- Delete the Setup file that contains the error.
- Empty your Temporary Internet Files folder. In Internet Explorer, click on the ‘Tools|Internet Options...’ menu, then click on the [Delete Files...] button, then click [OK] to delete the files. You will not lose any important data by doing this. The Temporary Internet Files are files that Internet Explorer creates and uses as you surf the internet.
- Try downloading the file again.
- Try to refrain from downloading too many other things at the same time.
"Could not modify the registry..." - This error would only occur on computers with multiple user profiles. In order for InterAx to be installed correctly, it must be installed while logged on to Windows as an Administrator (or with administrative privileges). This error is generated because Setup is attempting to write to a part of the registry that the current user’s ”permissions” settings do not allow. When this error occurs, Setup is attempting to create the InterAx Project file association, which allows InterAx Projects to be opened by clicking on them from Windows Explorer. Note: This error occurs in Setup for InterAx 2.0.0 or older. Starting with the next update, this error will be explained better, and it will not cause Setup to abort.
Error Messages in Editor and/or Player:
“Error 76 - Path not found”
- Occurs in a game I downloaded: Please ensure that the game was unzipped properly. Games created with InterAx have sub-folders within the main (root) folder. This sub-folder information is stored in the zip file. After unzipping, if the game's main (root) folder contains many files and has no sub-folders in it, then the following will solve your problem: In WinZip, be sure that the "Use folder names" option is checked before you unzip the file. This option is visible in the window that appears after you click on the 'Extract' button. When unzipped properly, there should be a "Resource" folder under the game's main folder. Within the "Resource" folder, there should be two more folders: "Gfx" and "MMedia". This error occurs when either the Editor or Player tries to access a file in one of these sub-folders, but it doesn't exist.
- Occurs in a new project I created: If you receive this error while running a new project you created in the Player, the most likely cause is that no image was chosen for Scene 1's 'Scene Image' property.
“Error 28 - Out of stack space” - This error occurs if the InterAx code get’s stuck in an infinite loop, and is the result of a flag problem. The problem occurs if a flag change causes one or more other flag changes which comes back to a previous flag change in that series of flag changes. Sounds a bit confusing, yes. Here is a basic example of what can cause this: A responder is set to trigger when Flag 1 = 2. The responder is set to change flag 1 to 2 when triggered. When flag 1 = 2, the responder takes action. When the action calls for changing flag 1 to 2, the responder is triggered again. This repeats itself until the error occurs. Note that the above example is basic, in that the problem lies solely in one object. Many times the problem is the result of several flag changes in several objects that ultimately come back to a previous flag change in that series of flag changes. The flag changes could be something like: Flag 1 = 3, which changes Flag 10 to 12. This causes Flag 17 to change to 8, which changes Flag 1 to 3 (note that we are back to the beginning of the series of flag changes). The best way to figure out the cause is to 1) Keep the ‘Debugging/Notify Window’ turned on, which lists all flag changes as the game is played. 2) Examine the properties of all objects in the scene in which the error occurs. Pay close attention to any flag properties (setting or checking of flags), and look for a situation that can cause a looping condition. 3) If you can’t find the problem just by looking at the properties, go through each property with a flag and UN-CHECK the governing checkbox, thus disabling the flag check or change. Do this for all flag checks or changes in the scene except for one. Run the game and check for errors. If none occur, go back to the editor and one by one, re-enable the flag properties until the error occurs. This should at least narrow the problem down to a particular flag. In versions 3.1 and higher of the InterAx Player, this error will have a better description and hopefully make it clearer as to exactly which flag caused it.
“Runtime Error ‘##########’: Automation Error” - Automation errors have no specific cause, but are generally due to a driver problem or problem with DirectX. Try the following to fix this error:
- Be sure you are running the latest version of DirectX (click here for more)
- Click Start>Run then type dxdiag into the box and click OK. Once this app starts, click on each tab at the top of the window to examine each part of DirectX. At the bottom of the window for each tab, you will see a list of problems found (if any). Fixing any problems listed in this app is a good place to start! Often the errors listed can be fixed by doing the next suggestion.
- Be sure you are using the latest drivers for your sound and graphics cards. You can usually find driver updates by going to the website of the company who makes the card (or sometimes the company who makes the processor that the card uses). If you are unsure of their website, try doing a search on the name of your card.
"A required .DLL file, xxxxxxx, was not found." - The system files required by InterAx were not installed correctly, are missing, or have become corrupted. Please re-install InterAx. This can sometimes occur after "un-installing" another application. When given the option, you should never allow an un-installer to remove DLL or OCX files from your Windows\System folder.
"Component 'xxxxxxx' not correctly registered: file is missing or invalid." - The system files required by InterAx were not installed correctly, are missing, or have become corrupted. Please re-install InterAx. This can sometimes occur after "un-installing" another application. When given the option, you should never allow an un-installer to remove DLL or OCX files from your Windows\System folder.
"Error initializing DirectX 8" - Please be sure that you have DirectX 8.1 or higher installed on your computer. The latest version of DirectX can be found at Microsoft's website. It is a free download. See the downloads page for more information and links to DirectX at Microsoft's website.
"InterAx could not access the Windows Registry." - This error would only occur on computers with multiple user profiles, particularly Windows XP and Windows 2000. InterAx needs to write data to a portion of the Windows Registry, but the current Windows User Profile does not have permission to do so. This error may occur in InterAx 2.0.0 or older. It will be fixed in the next version. In order to correct the problem until then, you need to either run InterAx from an Administrator User Profile, or edit your user permissions. Starting with version 3.0, InterAx will work correctly in multi-user environments. Until then, it is impossible for InterAx to run on user profiles that do not have administrative privileges.
If you did not find help on this page, then you may want to make sure your problem hasn't already been addressed in an update patch. Click here for the Updates page. If you still experience the same problem after installing the latest update, please use the appropriate link below
Click here to contact Tech Support.
If you think you have found a bug, click here to send an e-mail. Please include which version of InterAx you are using, and be as specific as possible about the bug.
|