Camera, cockpit, etc settings?

[nara]

Hey can someone point me to the camera, cockpit, and zone(?) settings that people have shared? I know those resources are somewhere, but searching on the forum gave me too many results, and I couldn't find it on the wiki. I'm looking for custom camera settings, settings for a mini map on screen, and settings to change the zone circly things (they're getting in the way). Directions on how to implement those custom settings would also be appreciated. Thank you!

Also, where is the new version of tron located? I hear there is a version 0.4, but the download on the wiki for mac is still 0.2.8 I think.

[Durf]

Minimap is a feature available on 0.3 and 0.4. It is on your screen by default when you use those versions.
For customizing the minimap (and other HUD options), you will need to look at the cockpit tutorial on the wiki (note: for 0.4 only).



For camera settings:
I'm not sure, there may be some more options for 0.4 clients, but here is where you can reference the settings:
List of console commands - Search the page (F3) for "CAMERA_" and it will highlight ALL the related settings (all camera settings).
Note, some of the settings are for SERVER cameras only (tbh, I never tried fiddling with the camera settings client side - so good luck).




Zone settings (with their default values):

Code: Select all

ZONE_SEGMENTS 11 #number of segments in the circle
ZONE_SEG_LENGTH 0.5 #the length of each segment (1 means the segments are connected)
ZONE_HEIGHT 5 #height of the zone (1=cycle height, 4=default rim height)
ZONE_ALPHA 1 #transparency from invisible to full intensity (0.0 - 1.0)
# the following are more like extra settings you can ignore:
ZONE_BOTTOM 0 #adding values to this raises the entire zone off the grid (you can't pass "under" it but it looks like you can)
ZONE_ALPHA_SERVER 1 #server controlled alpha setting
ZONE_ALPHA_TOGGLE 0 #"This is XORd with ALPHA_BLEND to determine the way to draw zones"

Here are some suggestions:

Code: Select all

# SUMO:
ZONE_SEGMENTS 32
ZONE_SEG_LENGTH 1
ZONE_HEIGHT 0.5
ZONE_ALPHA 1
# plus any other custom settings you might want, like axes_indicator or something
# this makes the sumo circle actually look like a sumo circle + increases visibility

Code: Select all

# FORT:
ZONE_SEGMENTS 32 # or 11 if you really prefer
ZONE_SEG_LENGTH 0.95 # disconnected segments to show the speed of the zone rotation
ZONE_HEIGHT 2 # whatever your preference is for this
ZONE_ALPHA 0.4 # visibility inside and out
# plus any other custom settings you might want, like axes_indicator or something

Code: Select all

# RACE:
ZONE_SEGMENTS 32
ZONE_SEG_LENGTH 1
ZONE_HEIGHT 1
ZONE_ALPHA 1
# extras that I've mentioned
HIGH_RIM 0
AXES_INDICATOR 1
EXPLOSION 0
FADEOUT_NAME_DELAY 0
GRID_SIZE 4

But maybe you don't like to have to remember all this.
There is a tool available that can assist you in making CFG files like the ones above ^.
The tool is located at http://durf.tk/tool-2 (The link says "Color Codes" because that's what it's mainly used for, but it can spit out CFGs like these)

Visit the link, and click "Show/Hide" for Miscellaneous Options (make sure you uncheck "Ignore Misc Options").
There's a brief form for you to fill out, and once you're done getting the settings you want, click the button "Finished, gimme the CFG" to get your custom file.

You can save that file as anything you want: fort.cfg, sumo.cfg, race.cfg, nara.cfg, anything!
Where do you save it? In one of tron's many configuration directories (tbh idk where that is on mac - but it should list it in tron's ABOUT menu)
(if anyone on mac, or that knows mac, knows where these directories are, please help out)

Once you save the file in a configuration directory, tron will have it available for use.
Say you connect to a fort server, you can do "/console include fort.cfg" to set all the settings you want to be ready to play fort.
Connecting to a sumo server would be the same way: "include sumo.cfg" when you join, and you're all set.


Hopefully that helped you; certainly better than manually setting each setting anyway.


Plus! This is what I found regarding 0.4 on mac.

[vov]

For some settings that exist already:
http://wiki.armagetronad.org/index.php/Cockpits_List
http://wiki.armagetronad.org/index.php/Custom_Camera

Concerning zones, I don't know of any lists. Durf's sets are probably fine there (to put in autoexec.cfg, or paste directly into the console to test ).

[Phytotron]

There was a PM exchange you and I had years ago about setting up your custom cam. If you didn't delete them, you may want to search your old messages to see if they're still there. I don't remember if it was helpful, though. In fact, it seems I might have pawned you off on sinewav, heh, so look for those too (if you did indeed go to him for help).

[nara]

Pawned me off to sine wave sounds kind of objectifying/degrading. Since it's been a few years I don't remember, but maybe it's in my inbox somewhere. Thanks.

Also, thanks Durf and vov for the help - I have not attempted to change my settings since those things are usually an ordeal for me, but I'll sit down sometime and attempt it!

[/dev/null]

I can give you amazing settings if you want to stomp face. If you prefer to wait for it, my setting are crap.

[nara]

You should share those settings as I'm interested in stomping (tron)face! (Who isn't?)

[/dev/null]

this is off the top off my head, but I think they were 6.5,6, -.5 and then set whatever the turn follow delay was to 0.

As I said, its off the top of my head, and the numbers listed are in the order they appear in the console when you search for the variables needed. Ill actually go look later and get exact numbers.

[vov]

Quite possibly these:

CAMERA_CUSTOM_BACK 6.5
CAMERA_CUSTOM_PITCH -0.5
CAMERA_CUSTOM_RISE 5

[/dev/null]

You missed a number, but mostly right.

[/dev/null]

haha, I just checked my settings, you were right with the negative. Did you bastards copy my old settings? I notice they are damn close to the new custom ones, and that didnt used to be the case. I would advise dropping he back more so you can better, and turning off the follow lag.

[Phytotron]

Pawned me off to sine wave sounds kind of objectifying/degrading.

Well, then you misunderstood the idiom.

(In fairness, I used it somewhat facetiously. To be precise, "pawn/palm off" usually implies either deception or that the activity in question was unwanted. Neither was the case then. It was just a matter of "he knows Windows directories and uses custom cam and I don't, so ask him." I was just passing you off and letting sinewav deal with the work. )

[Lucifer]

Pawned me off to sine wave sounds kind of objectifying/degrading.

Well, then you misunderstood the idiom.

(In fairness, I used it somewhat facetiously. To be precise, "pawn/palm off" usually implies either deception or that the activity in question was unwanted. Neither was the case then. It was just a matter of "he knows Windows directories and uses custom cam and I don't, so ask him." I was just passing you off and letting sinewav deal with the work. )

Punted. I like that one.

The idiom can be objectifying/degrading, depending on the reason it's being used. In this case, it's not, because Phytotron was sending you to someone more knowledgeable than he in order to provide you with the help you were looking for.

I'm sure you can imagine times when it might be degrading, so I won't give an example.

[/dev/null]

Pawned me off to sine wave sounds kind of objectifying/degrading.

This should greet all new players. Dont be pussy, use awesome.