HELP regarding colors

[Darxus]

> >Have you tried running the game, disconnecting and then reconnecting to
> >the machine running it? That will help indicate where the problem is.
> <James "Wez" Weatherall>
> <<Derrick Shearer>>
>
> I can't do otherwise. :p Starcraft, like many games, resizes the screen,
> and
> changes its color depth. When such happens, existing VNC connections
> are killed, and so must be reinitiated. An extension for quick protocol
> renegotiation might be nice. I don't, however, see a need for adding such
> to VNC in any immediate timeframe, unless resolution change induced
> disconnects are more common than I believe them to be. (very uncommon)

Okay, I've been wondering why this question hasn't been posed before --
*why* are you trying to play a directx accelerated game on a remote
desktop ??

You know what directx is for, right ?  direct access to the hardware...
speed.  

So go you and give it *the* slowest interface possible... you try to get
it to draw on another computer over a network ???  what were you thinking?

> Your thinking turns out to be right with regard to DirectX and its lack of
> reliance upon GDI in full screen mode. As such, no amount of enabling
> or disabling DirectX hardware acceleration has any effect upon VNC's
> use of GDI hooks. I might as well leave DirectX fully accelerated. :p
> Ach well, unless VNC expands to include support for sound, then I see
> no reason why DirectX support should be addressed, or otherwise
> hooked.

Both of these things I'm sure are possible, but anything that requires
directx support is probably going to work very poorly, as it is, by
definition, going to want the fastest possible connection to the
display hardware... as opposed to the slowest possible access to the
display by putting the displayo on another computer over a network.  And
sound is going to require streaming audio over your network, and a whole
nother set of messy protocols.  

> VNC would definitely be better with the following:
>
> *Multi-user, multi-sessioning, with consideration given to the distinction
> *between shared and independently viewed client/server relationships.
> *Furthermore, multiple logon types entailing multiple permission sets.

As has been said before, this can be done with one of the following:
1) expensive licensing from microsoft
2) rewriting half the operating system

#1 will not work, ever, as this is GNU stuff.
#2, hey, feel free to implement it yourself....

> *Effective multi-casting to large audiences.
> *Repeaters/sub-multi-casters?

I say again:  *WHY* ??

No, wait, lemme guess... you wanna broadcast your starcraft games across
the internet ?  <cringe>

The last time I heard anybody talk about repeaters & multicasters of
anything like this, they were discussing broadcasting online quake games. 
I think I was around to witness the 1st spark of this thought, and I think
they've actually pulled it off to some extent (go find MPOG, or visit
#clanring).  This, I would say, is only anywhere near practicle on a
*much* lower level, hacking the game's protocol itself, and rebroadcasting
its data packets, and having every viewer run a client that renders the
data locally.  *Not* transferring bitmaps of every entire frame all across
the internet. 

> *"Drag 'n Drop" file transfers with NO command line or menu capability.
> *Modular file transfer protocol.

Could be useful, but would probably require too much coding to be
practicle.

> *Modular modes for display. (Hextile, CoRRE, RRE, Raw, and others)

Why ?

> *Encryption; modularly integrated.
> *Compression; modularly integrated.

Compression, encryption, sure.... modular ?


Yes, it's good to look at all possibilities, and consider the best way to
implement all things.  I encourage you to try implementing these things
yourself.  You've got the source code, that's what open-source is all
about.

> Would VNC be more aptly described as VND (Virtual Network Display),
> allowing for VNA (Virtual Network Audio), or VNS (Virtual Network
> Sound), with VND and VNA|VNS being components of VNC?

No.

> Derrick Shearer
> dls2 "at" Lehigh.EDU


________________________________________________________________________
***PGP fingerprint = D5 EB F8 E7 64 55 CF 91  C2 4F E0 4D 18 B6 7C 27***
               darxus "at" op.net / http://www.op.net/~darxus 
                           You do not exist.


---------------------------------------------------------------------
The VNC mailing list     -   see http://www.orl.co.uk/vnc/intouch.html
---------------------------------------------------------------------