Forums » Suggestions
Add a command, /view invite "name", or some command along those lines, that allows you to invite someone else to see the same 1st person view as you.
The invited person would need to also type in a command, /view accept "name".
pvp vets could share a 1st person view of a dog fight, so that noobs could see what it looks like from the vets perspective.
noobs could share their view with vets, so that the vets can see what the noob is doing wrong in a dog fight.
noobs asking stupid questions like: "how do i kill this queen" can share their view, so vets can see what queen, what sector, what mission, etc...
The command could work from any where in the galaxy, with anyone else, anywhere else, with no inherent risk to the person invited.
Sharing someone else's view while you float in sedina b8 is not an inherent risk, it is a chosen risk. Sharing someone else's view does not time out your ship, or otherwise offer you any protection or immunity. If you take damage while sharing someone else's view, you receive a system message saying that you are taking damage.
You should be able to leave the view at anytime, by using your activate key, and cancel your invite with /view quit, or /view uninvite "name".
There should be no limit to the number of people invited, and sharing a view.
The invited person would need to also type in a command, /view accept "name".
pvp vets could share a 1st person view of a dog fight, so that noobs could see what it looks like from the vets perspective.
noobs could share their view with vets, so that the vets can see what the noob is doing wrong in a dog fight.
noobs asking stupid questions like: "how do i kill this queen" can share their view, so vets can see what queen, what sector, what mission, etc...
The command could work from any where in the galaxy, with anyone else, anywhere else, with no inherent risk to the person invited.
Sharing someone else's view while you float in sedina b8 is not an inherent risk, it is a chosen risk. Sharing someone else's view does not time out your ship, or otherwise offer you any protection or immunity. If you take damage while sharing someone else's view, you receive a system message saying that you are taking damage.
You should be able to leave the view at anytime, by using your activate key, and cancel your invite with /view quit, or /view uninvite "name".
There should be no limit to the number of people invited, and sharing a view.
+1
+1
+1
This is more than reasonable and WELL worth the dev time. Can someone add some more words and reasoning to back this so that the devs take this suggestion serious?
This is more than reasonable and WELL worth the dev time. Can someone add some more words and reasoning to back this so that the devs take this suggestion serious?
Good suggestion, but I'm going to have to -1 this because I want to see a revamped dynamic economy first.
+1
+1 to excellent idea - would be interesting from a training perspective if one could cause control/fire inputs to be displayed on the shared view as well.
-1 to anyone thinking +1ing any one idea will somehow result in more delays to any other specific idea.
Not to mention the fact that you'll see a revamped dynamic economy in VO around the same time you'll see a resurgent Lehman Brothers crowned top firm on the Street.
-1 to anyone thinking +1ing any one idea will somehow result in more delays to any other specific idea.
Not to mention the fact that you'll see a revamped dynamic economy in VO around the same time you'll see a resurgent Lehman Brothers crowned top firm on the Street.
+1 and +1 to lecters idea
+1 from me too
This is a variation of the ride-along suggestion, and as such I'm in favor of even a partial implementation, but I'd rather we have an actual reason the view is being shared, which ride-alongs accomplish, while opening up other gameplay mechanics.
"I'd rather we have an actual reason the view is being shared"
Yeah, because people totally would never set up live streams of their ship's dash cam! :P
Yeah, because people totally would never set up live streams of their ship's dash cam! :P
If you're just talking about sharing a view without any in-game consequences (like moving a player to another station) there's already things that exist to do that and don't require the devs to implement anything.
I like this idea. Both parties are protected by the one having to invite and the other having to accept. Also I see no reason the RP aspect is a problem. There is already faster than light communication, why not video imaging? It might be hard to implement though, what with the image processing done outside the main game server. The ride along thing probably makes more sense from a development point of view.
+1 to however it works out.
+1 to however it works out.
"It might be hard to implement though, what with the image processing done outside the main game server. The ride along thing probably makes more sense from a development point of view."
Not really. The main added complexity of remote viewing vs. ride-along is that the server would have to persist the viewer's ship (if they weren't docked) and possibly notify them about it if it takes damage. The graphical element, however, is identical to ride-along -- the client would just pretend to be riding along, but without any option to disembark into whatever stations the ship they're watching visits.
@Arf: Yeah, but those methods interfere with performance, and viewing them requires either having an extra screen/device, exiting the game, or switching to windowed mode. Now, if the devs finished the built-in "video" system they started a few years ago that recorded network data or events or whatever instead of actual video, and then added a way to transfer those recordings in-game, it would then be possible for people to record combat without combat-disrupting performance losses and then send those recordings to their trainees in-game after the fact. That would be fairly handy, although it wouldn't be live. (Obviously making it live would be a terrible idea, since unlike the OP or doing it non-live, it would impair performance on the recorder's part by increasing bandwidth use.)
Not really. The main added complexity of remote viewing vs. ride-along is that the server would have to persist the viewer's ship (if they weren't docked) and possibly notify them about it if it takes damage. The graphical element, however, is identical to ride-along -- the client would just pretend to be riding along, but without any option to disembark into whatever stations the ship they're watching visits.
@Arf: Yeah, but those methods interfere with performance, and viewing them requires either having an extra screen/device, exiting the game, or switching to windowed mode. Now, if the devs finished the built-in "video" system they started a few years ago that recorded network data or events or whatever instead of actual video, and then added a way to transfer those recordings in-game, it would then be possible for people to record combat without combat-disrupting performance losses and then send those recordings to their trainees in-game after the fact. That would be fairly handy, although it wouldn't be live. (Obviously making it live would be a terrible idea, since unlike the OP or doing it non-live, it would impair performance on the recorder's part by increasing bandwidth use.)
Having a view command independent of passenger transport is more useful than have a shared view that is depended on passenger transport.
The two ideas are neither mutually exclusive, nor necessarily interdependent. The view command can be implemented without concern for passenger transportation concerns, and passenger transportation can be implemented without concern for sharing views.
If shared views and passenger transport should happen to both be implemented, there would be nothing preventing people from using both features to effect a "ride along". But neither feature should be dependent on the other feature. Each would be useful in it's own right.
The idea of transporting passengers should be presented as a separate and independent suggestion, without dependency on shared views, and in it's own thread.
The two ideas are neither mutually exclusive, nor necessarily interdependent. The view command can be implemented without concern for passenger transportation concerns, and passenger transportation can be implemented without concern for sharing views.
If shared views and passenger transport should happen to both be implemented, there would be nothing preventing people from using both features to effect a "ride along". But neither feature should be dependent on the other feature. Each would be useful in it's own right.
The idea of transporting passengers should be presented as a separate and independent suggestion, without dependency on shared views, and in it's own thread.
+1
Some one double check my ability to count.
By my count, I see 10 players in support of this idea, and 2 opposed.
By my count, I see 10 players in support of this idea, and 2 opposed.
+1, this would be great.
+1 (Bump)
+1