rec.autos.simulators

Does anyone know what all the available settings are that you can put in the
core.ini file?

I like to know what all I can mess with.

Vintook

Randy, can you help?

There aren't that many that are overly (or even mildly) interesting to
play with.  I'm sure you've probably seen the bandwidth and port
settings that VROC uses.  There are several others that control
bandwidth on a LAN and between a client and its local server (via
shared memory).  Aside from that, you can try

[ Rasterizer ]
fullScreen = 0

if you have a Rendition card (this might also work with OpenGL, I'm not
sure off hand).  This will cause GPL to run in a window.  Useful if
you're debugging something, but not particularly so otherwise.

You can also try

[ Communications ]
log_server_connect_status = 1

which will cause messages to be sent to the host's chat pad that are
similar to those displayed in the connecting-to-a-server dialog box for
a client.  Again, useful for me to debug some things, but rather
annoying to a host.

Most things that might be considered 'interesting' aren't compiled into
the released program (they'd just make it bigger and slow it down, and
we don't need that, do we?)

Randy

Thanks, for your response, Randy. A couple of additional quick questions...

Does this work for 3Dfx, as well? If not, is there any way to run GPL in
3Dfx mode in a window?

Speaking of the chat pad, is there anyway to capture chat text aside from
screen shots?

Thanks, again!

Eric

It's not directly possible on Voodoo I or II boards because of the
pass-through setup they use.  I believe there's something called
winglide floating around that circumvents this.  I've never used it,
but from my (very limited) understanding of how it works, I suspect it
would hurt the frame rate quite a bit.  I don't know how the Rush and
Banshee setups work.  Whenever we've needed this capability while using
a 3Dfx board, we've just hooked up one monitor to the 3Dfx board, and a
second monitor to the 'normal' video card.

Nope.

Randy