Because I want to keep this forum active...

[+JuggerNaut+]

first of all, it's fkn great and if you've not tried it, do so.

i have a Qlive question:

i've not seen a force model option. i have a 24" monitor and it's too big on that, but i think that windowed it defaults to 1024x768 (wish i could get that bigger), but problem is with rail - i can't see some of these models from a distance and i don't want zoom (right mouse button is walk for me).

any config setting(s) i could tweak?


thx

[^misantropia^]

Can't test it right now, but can't you set r_mode to 5 or higher and do a vid_restart?

[DTS]

Get a mouse with more than 2 buttons.

Edit: Actually I use a keyboard key for zoom but whatever. Just find a key you can reach easily and bind that to zoom.

[4days]

i've not seen a force model option.

the config's buried in your windows profile. create an autoexec.cfg in "C:\Documents and Settings\juggs\Application Data\id Software\quakelive\home\baseq3" and put something like this into it:

seta cg_forceenemymodel "tankjr/bright"

[+JuggerNaut+]

Can't test it right now, but can't you set r_mode to 5 or higher and do a vid_restart?

i will try that tomorrow when i am unburied from work, thanks

Get a mouse with more than 2 buttons.

i've never gotten used to zoom, so i refuse to use it. also, my g5 has plenty of buttons, thx.

the config's buried in your windows profile. create an autoexec.cfg in "C:\Documents and Settings\juggs\Application Data\id Software\quakelive\home\baseq3" and put something like this into it:

seta cg_forceenemymodel "tankjr/bright"

you may be getting flowers in the mail. i'll try this one tomorrow firstly. thanks!

[MKJ]

"never gotten used to it so i refuse"

wouldnt it be the other way around?
kindof circular logic there, sir

[DTS]

You don't need to create an autoexec file, you can use the console in QL

I also think the command is cg_forceenemymodel (different from Q3).

[+JuggerNaut+]

"never gotten used to it so i refuse"

wouldnt it be the other way around?
kindof circular logic there, sir

oh, you fucking ferret. i couldn't get used to using zoom and there wasn't a map that i played regularly that needed it.

[+JuggerNaut+]

You don't need to create an autoexec file, you can use the console in QL

I also think the command is cg_forceenemymodel (different from Q3).

i'll take a look, thanks

[4days]

You don't need to create an autoexec file, you can use the console in QL

I also think the command is cg_forceenemymodel (different from Q3).

that's true. i just chopped down my q3 autoexec.cfg and copied it to the QL folder.

and the "seta" part is just because it's in a config, you wouldn't need it in the console.

[+JuggerNaut+]

You don't need to create an autoexec file, you can use the console in QL

I also think the command is cg_forceenemymodel (different from Q3).

that worked, thanks. since green keel is a standard model in Qlive, any idea how to add that particular one? i just put cg_forceenemymodel keel

[4days]

cg_forceenemymodel "keel/bright"

[+JuggerNaut+]

you secksi man you

[menkent]

you could also decrease the default FOV with rail.... like if you normally use 110 just add "fov 90" to your rg bind. sort of a semi-zoom. it's not ideal, but i remember seeing configs with different fov for each weapon (higher for shotty and rl, lower for lg/rg).

edit: assuming that QLive lets you mess with fov, that is

[Unisaw]

i've never gotten used to zoom, so i refuse to use it. also, my g5 has plenty of buttons, thx.

I find that zoom in a CA or FFA leads to death for the most part.

[Zyte]

you could also decrease the default FOV with rail.... like if you normally use 110 just add "fov 90" to your rg bind. sort of a semi-zoom. it's not ideal, but i remember seeing configs with different fov for each weapon (higher for shotty and rl, lower for lg/rg).

edit: assuming that QLive lets you mess with fov, that is

Do you know if this would require you to also add fov values to all your weapon binds, also for the ones you want to keep using with your cg_fov value, in order for it to switch between the different field of views?

e.g.:
bind r "weapon 7; fov 90"
bind e "weapon 5; fov 120"
bind f "weapon 6; fov 120"

would be required or could i leave the 120's away if cg_fov is already 120.

Can't try it here.

[menkent]

you'll need to add cg_fov 120 to your other binds to reset it. i never really did this because i found it messes with my movement too much... changing fov also proportionally changes your sensitivity and i'd run into walls and miss jumps.

on the other hand, holding down a zoom button is even worse. my solution was to make a sort of toggle with two configs:

Code: Select all

//z2.cfg
bind alt "exec z1.cfg"
cg_zoomfov 100
sensitivity 8
bind r "weapon 5"
bind a "weapon 3"
bind v "weapon 6"

//z1.cfg
bind alt "exec z2.cfg"
cg_zoomfov 50
sensitivity 5
bind r "weapon 5; exec z2.cfg"
bind a "weapon 3; exec z2.cfg"
bind v "weapon 6; exec z2.cfg"
//so switching to RL, SSG, or LG will pop me out of zoom, as will hitting alt again. you'll notice that both are using "zoomfov" instead of "fov" because I was using a thinshaft config "cg_fov 300; cg_zoomfov 100;+zoom"

[Zyte]

looks like an inventive solution menkent thanks. Ill try and see if it's something for me.

In osp i used to have ctrl as a zoombutton but i never really got used to it. Thus i practically never zoomed.

[menkent]

yea, it's pretty useless except in CTF where the maps are much bigger.