Crossfire Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CF: Crossfire Client Noise
On Oct 10, 10:46pm, Darren Benham wrote:
> Subject: CF: Crossfire Client Noise
> At the very least, the client seems noisy. Is this something I/we should
worry
> about???
>
> Example, when I'm holding a key down to go east, I get a bunch of:
>
> Wont send command east - window oversized 10 255
> Wont send command east - window oversized 10 255
> Wont send command east - window oversized 11 0
This can safely be ignored. BAsically it means that it won't send the command
you just pressed so that the client doesn't get too far ahead of the server.
>
> Or I see a few:
>
> Got update_item command for item we don't have (215279)
> Got update_item command for item we don't have (215279)
> Got update_item command for item we don't have (215165)
I believe I have fixed most of those in the next version of the server. They
are also fairly harmless.
> Since there is no install command in the client's make file.. are the
following
> files necessary to run the client? Are they even config files or are they
only
> used for building the client:
>
> deb_keys sounds the pixmap directory.
The client binary is self contained. the def_keys and sounds are used as
defaults and compiled in. Images in the pixmap directory are also compiled in.
All you really need is just the client binary itself.
On Oct 11, 5:18pm, Christian Stieber wrote:
> def_keys, probably.
> YOu can copy this to ~/.crossfire/keys. Note that the
> up/down/left/right keys won't work on Suns (assuming a 0.94.3
> server/0.94.4 client; I don't know any 0.95.0 servers to try): you
> have to rebind them whenever you start the client.
Keybindings is completely client. By default, the client uses the same
keybindings the server used to use as its default. Note that different
keyboards could actually be more relevant than the system type.
You should only need to bind the stuff once in the client. After that, it
should save the keybindings so future times you run client it should all work.
>
> > sounds
>
> Only if you want to play with sound. Not recommended --- the sound
> sucks. :-(
You obviously need hardware that has sound to use sounds in any case. You
will also need to download a copy of the sounds and install them someplace and
modify the sounds file as needed. The sounds can certainly be improved -
however unless they actually annoy you, the bandwidth to transmit what sounds
to play is pretty minimal.
--
-- Mark Wedel
mark@pyramid.com
References: