| Q: Some things aren't working right since I installed. - (0 comments) |
AKA Panama Jack on 04-03 8:37PM |
Make ABSOLUTELY sure you have upgraded every single one of my scripts you are using. Older versions do not work with newer versions.
If you don't have the Auto DSO Delete option enabled in the General Options you MUST delete every single DSO file in the Tribes 2 directories. In windows use the Search for File option to search for *.dso. When they are all found delete them.
I recommend that the Auto DSO Delete be enabled at ALL time. Tribes 2 will take longer to load but the game will be far more stable and you will not run into weird problems when you upgrade ANYONES scripts.
|
| Q: I am UEing what happened? - (0 comments) |
AKA Panama Jack on 03-26 10:41PM |
Usually you have installed scripts that do the same things as other scripts. IE: Multiple Chat Hud script, Multiple Weapon Hud scripts, ect...
If you have Uberchat installed and install my Super Chat you will more than likely have problems.
If you have installed GUI replacement packages from other people (Brigadier, Anakha, Onazz, Ilys, Canadian, DaTimsta, ect...) they WILL cause T2 to UE because those packages have scripts in them that CONFLICT with PJ Compass Hud, PJ Objective Hud, PJ WepInv Hud and Super Chat.
Do NOT install any of my scripts listed above if you are going to use those GUI replacements. If you want to use GUI replacements you should check the Full Hud Replacements that are designed to work with my scripts. They are simple and easy VL2 files you drop into the base directory.
Many of the GUIs that are created by others will be converted to my Hud System. If you have a special one you want converted just point me to it and I will convert it for you.
Also, if you have Tricon2 installed you will almost ALWAYS UE when you host a server because Tricon2 does not like working with client side scripts.
|
| Q: What happened to the Kitty and Animations? - (0 comments) |
AKA Panama Jack on 03-02 5:02PM |
Well, they had to go away. 
They fell prey to the script limitations I mentioned in another FAQ. I basically ended up removing all extras that were not needed for the minimal operation of the regular scripts. Kilroy, Kitty and the Animation system tipped too many people into the script limit area. Heck it eventually pushed me into the script limits after I added a couple of other scripts from other scripters to my setup.
So basically all of the little extras like that are now gone for good so everyone can install more scripts.
|
| Q: I need to reinstall T2 how do I save my PJ settings? - (0 comments) |
AKA Panama Jack on 03-02 4:57PM |
All of the settings my scripts use are stores in the prefs directory and there is a panamajack directory that has a few other minor things.
Both of those directories are in Tribes 2 base directory. Copy both of them to a safe place. When you are done reinstalling Tribes 2 copy both of the saved directories back to the base directory. Now install all of your client side scripts and graphic files.
If you were using Super Huds to convert all of your main graphics you should go to Super Huds options and reinstall the graphics again. Super Huds will say they are installed but they really aren't yet. If you don't reinstall the graphics you might run into problems. The worst one might be a UE.
You are finished and ready to go.
|
| Q: How do I delete PJ Scripts? - (0 comments) |
AKA Panama Jack on 03-02 4:52PM |
Go to the base directory in Tribes 2 and delete any file you find that starts with PJ. This will completely delete all PJ scripts.
If you just want to delete a script or two find the script you want and delete it. The names are just like the script names. If you want to delete Mega Faves look for PJMegafaves.vl2 in the base directory and delete it.
|
| Q: How do I set the options on the PJ Scripts? - (0 comments) |
AKA Panama Jack on 03-02 4:47PM |
You will find that you can set script options in the same place you set your graphics resolution, sound and controls. A SCRIPTS tab was added to the Settings screen in Tribes 2.
Click on the LAUNCH bar and you will see SETTINGS on the bar that pops up. Click on SETTINGS. The settings dialog will open and you will see a SCRIPTS tab at the bottom of the tabs. Click it and you will see a list of all client side scripts. You can double click on any script in the list and if it has an option screen it will be displayed so you can set your options. Some scripts will even let you enable or disable them. You will see an ENABLE button on the right side of the dialog. When it is GHOSTED you cannot disable the selected script but when unghosted you cah enable or disable it. There is also a READ ME button that will unghost if there is a read me file for the selected script. Just click the button to read all about the selected script.
|
| Q: My new graphics won't show on my new script. - (0 comments) |
AKA Panama Jack on 03-02 4:41PM |
If you have used Super Huds to change all of your default graphics you must go to the options screen on Super Huds and set your Main Graphics again when you add a new script.
This will cause Super Huds to scan the new script and update the huds and graphics (if it can) to the new graphics you have set everything. Sometimes they might have their graphics settings imbeded in the CS file with their own graphic settings. If that is the case then Super Huds cannot convert the hud to the new graphic but in most cases this doesn't happen.
|
| Q: Is there a bug in Tribes 2 Packages? - (0 comments) |
AKA Panama Jack on 03-02 4:35PM |
There is a small bug in the T2 Package system that can cause a potential problem with both servers and clients.
A simplified explanation of packages is this...
Packages in Tribes 2 is a way for scripters to add new abilities to existing routines. All of the gametypes and almost all client side scripts use packages to add more functionality to the game.
The package system was slightly patched with the new patch so it can retain all of the packages if some is removed. In the old system if you had 3 packages and deactivated the second one it effectively deactivated the third one as well. This was a very bad thing that caused all kinds of problems for scripters. The packaging system was patched to prevent this but a bug crept in.
If you try to deactivate a package that isn't there the first package in the package list is deleted. The package isn't deactivated but it is deleted from the list. If a script tries to deactive a package multiple times that doesn't exist it could remove all packages from the list. This is when problem arise.
Example...
MyPackage1
MyPackage2
MyPackage3
Say a script tries to deactivate a package called "Junk" two times. Since junk isn't in the list MyPackage1 and MyPackage2 are removed instead. Both of those packages are still active even though they are not in the list.
Now if another script deactivates MyPackage1 both MyPackage1 AND MyPackage2 will be deactivated as they are not in the list of active packages. MyPackage2 SHOULD be reactivated but it isn't since it isn't in the package list. This can cause things that need that deactivated package to stop working or a worst case cause T2 to UE.
Here is the fix for the problem.
This is for both Servers and Clients. For windows load console_start.cs, located in the gamedata directory, into a text editor like notepad. For linux load console_start.cs, located in the tribes2 directory, into a text editor.
Fine a line that looks like this (line number 42/43)...
function DeactivatePackage(%this)
{
And add the following line right after it...
if(!isActivePackage(%this))
return;
Save the script. You are fixed.
If you are only running as a Client and don't want to edit the above script just install the script below in your autoexec directory.
Peace Out...
PJ
(If you are viewing this from the F.A.Q. page click on the Question to go to the download page for the mentioned file.)
|
| Q. Is there a script limit for Tribes 2? - (0 comments) |
AKA Panama Jack on 03-02 4:31PM |
Unfortunately yes.
The limit doesn't seem to be in how many or the size of the scripts. It is all based upon what are called packages.
Packages are a way for scripters to add extra abilities to functions inside Tribes 2 without having to completely re-write everthing and cause incompatabilities with other scripts. Tribes 2 has a limit on the number of packages and the number of unique functions that can be packaged.
For non-scripters this means that things can start to go wrong when you reach that limit. What you will see happen is some scripts start failing after you install some new scripts. Or even worse you start to UE (Unhandled Exception error and Tribes 2 crashes).
To find out if you hit the script limit for your machine just removed ANY 2 or 3 scripts (don't remove the ones you just installed) and try running Tribes 2. If the problems you were having go away then you reached your script limint and the scripts you installed were not faulty. When this happens that means to have to decide what scripts you want to keep and what scripts to get rid of. There isn't any way around this problem other than removing some scripts from Tribes 2.
You are most likely to experience this problem while hosting a game to test out your new scripts than joining a normal server. The reason for this is because when you host a server the act of hosting activates alot more packaged functions than non-hosting.
|
|
|
