Initial script startup screen

[Guest]

Archived from groups: alt.games.quake3 (More info?)

Is there any way of slowing, or ideally step-by-stepping the very
first blue script screen that comes up when you start Q3 (and STV:EF)
so you can see what it's saying & processing?



--
Face down in the gutter

 

[pop]

Archived from groups: alt.games.quake3 (More info?)

add the following to the command line in the shortcut that starts Q3:
+set viewlog 1
( toggle the display of the startup console window over the game screen)
after Q3 starts, put it in "window mode" (alt-enter) and the blue screen window
is still visible and can be scrolled. not much more in the blue screen than can
be captured in the Q3 log: ...\baseq3\qconsole.log (with set logfile 1 in your
autoexec.cfg file):
HTH
--
pop is Mark
I'm lost. I've gone to look for myself.
If I should return before I get back, keep me here.
--
"talented_drunk" <no@no.again> wrote in message
news:mbofe0pcag91iubsgv1ap4em0so8gofir9@4ax.com...
> Is there any way of slowing, or ideally step-by-stepping the very
> first blue script screen that comes up when you start Q3 (and STV:EF)
> so you can see what it's saying & processing?
>
>
>
> --
> Face down in the gutter

 

[Guest]

Archived from groups: alt.games.quake3 (More info?)

or just use

/condump nameoffilehere.doc

pop wrote:

> add the following to the command line in the shortcut that starts Q3:
> +set viewlog 1
> ( toggle the display of the startup console window over the game screen)
> after Q3 starts, put it in "window mode" (alt-enter) and the blue screen window
> is still visible and can be scrolled. not much more in the blue screen than can
> be captured in the Q3 log: ...\baseq3\qconsole.log (with set logfile 1 in your
> autoexec.cfg file):
> HTH

 

[Guest]

Archived from groups: alt.games.quake3 (More info?)

On Sun, 04 Jul 2004 12:07:42 GMT, "pop" <p_o_p@hotmail.com> wrote:

>add the following to the command line in the shortcut that starts Q3:
>+set viewlog 1
>( toggle the display of the startup console window over the game screen)
>after Q3 starts, put it in "window mode" (alt-enter) and the blue screen window
>is still visible and can be scrolled. not much more in the blue screen than can
>be captured in the Q3 log: ...\baseq3\qconsole.log (with set logfile 1 in your
>autoexec.cfg file):

Cheers y'all - the +viewlog captured what I wanted.

Any ideas why the following commands are not recognised by Q3 1.32?


Unknown command "bot_minplayers"
Unknown command "bot_nochat"
Unknown command "cg_tracerchance"
Unknown command "cg_tracerlength"
Unknown command "cg_tracerwidth"
Unknown command "cl_motd"
Unknown command "g_enableBreath"
Unknown command "g_enableDust"

They're all valid calls, according to Commander Keen's Q3 console
page.

http://www.planetquake.com/q3console/variables.htm




--
Face down in the gutter