Members | Sign In
All Forums > Bridge Crew Comms

Desktop Sharing: "Show My PC" et. al.

posted Aug 08, 2011 15:24:46 by Mike_Substelny
The biggest disadvantage to remote play is that remote players cannot see/hear the main screen, even if they have two PCs and plenty of bandwidth. But with all the cool gameplay features Thom has planned, programming a way to pipe an extra channel of audio/video through the Artemis software might not be the best use of his time, especially if a good desktop sharing service already exists.

Has anyone used Microsoft's remote desktop connection or a service like with the Artemis main screen? Does anyone know a product that would do a good job of audio and video?
"Damn the torpedoes! Four bells, Captain Drayton!"

(Likely actual words of Admiral David Farragut, USN, at the battle of Mobile Bay. Four bells was the signal for the engine room to make full steam ahead).
page   1
6 replies
BarrySmith said Oct 04, 2011 19:08:05
What I'd like to see is the "vis" tab echo the main viewer to each individual console so that you can get a quick peek at the mainscreen, even if you're playing internet. It seems like it might be more useful than a simple external view.
Mike_Substelny said Oct 04, 2011 19:45:24
Seeing the main viewer is good, but I'm also worried about hearing. The main viewer's audio system plays more than the music. It plays the combat sound effects and audio communications, too. Helm and Engineering need to hear weapons firing. In mission scripts everyone needs to hear incoming audio messages.
"Damn the torpedoes! Four bells, Captain Drayton!"

(Likely actual words of Admiral David Farragut, USN, at the battle of Mobile Bay. Four bells was the signal for the engine room to make full steam ahead).
BarrySmith said Oct 04, 2011 20:06:00
Hmm, I have kind of a tentative plan to run a local mumble server for relaying bridge audio to remote players... It definitely won't be possible for all of my bridge crew to be in the same room all the time, because a couple of them live in different cities.

But relaying the important information from audio messages seems like it should be Comm's purview. Indeed, it seems like it might be useful if comms could redirect or echo already recieved messages to specific consoles. (It might be actually. Comms is a station I don't have a great deal of familiarity with at the moment).

Maybe a "server audio" toggle in the options intended for remote players that makes their terminal echo the sounds the server would be playing for those who aren't in the same room as the main viewer?

It wouldn't stream every sound. Just replay any sound the Artemis client already has stored locally. The fact that its not synced with the mainscreen is largely irrelevant if you're not close enough to hear the mainscreen anyway.

I just played a game in a different room from my server. Artemis is definitely a rather austere experience if you're not local - at least the client should echo the end-game statistics to your terminal if you're an internet player - you can see the "game over" if you can see the viewer, but otherwisem, the game just kinds of ends with a whimper.
[Last edited Oct 04, 2011 21:44:34]
wilsontp said Oct 05, 2011 22:07:41
And to answer the OP: I don't think remote desktop software is a good fit for this task. It's slow with arbitrary bitmap data, and it won't work well. We really need a game data stream for this to work well. Using a remote desktop viewer will clog the server's output pipe and really slow down the overall gameplay.
wilsontp said Oct 05, 2011 22:12:14
I would like to see the ability to either run multiple instances of a main viewer, or have the main viewer echo on each console - audio included.

Or both. So single-display people could toggle over to the VIS screen to see what's going on, and dual-display people could just open a second window and attach to the bridge viewer.

In fact, I'd love to be able to instantiate multiple bridge viewers - each with its own display mode. Then we could have an outside view, the tactical view, the status view, and the LRS view all up at once.

That's kind of how I imagine the Real Thing to be.
BarrySmith said Oct 09, 2011 11:38:45
A bit more flexibility might be nice, but it seems like it might be a lot of work, and I'm not sure "nice" is worth that much effort, when it works more than well enough right now.

But as long as i'm dreaming:
Server decoupled from viewscreen, running in text mode for easy virtualisation, porting to OS's other than Windows, and perhaps "indefinite duration" simulations in the longterm, where life in a sector can tick by even when TSN fleet ships aren't online.

A "Captain (Admiral?)" station for each that keeps track of all "clients" logged in, and which manages which console gets which "jobs" from zero (spectator/viewscreen) to all five "working" stations.
[Last edited Oct 09, 2011 11:39:17]
Login below to reply: