I am planning on using Unity’s Network View to create a Dual Device game, this is a game which will be using a PC for an FPS with a mobile device to control equipment. The mobile device will be required to render allot and I feel it won’t be able to render the entire world if required, however the PC should be able to easily. I want the mobile device to recieve the view from a camera in the PC FPS and then use that as the viewport on the mobile device. The mobile device will also send input back to the PC. I feel making the PC do all the work is the best approach, unless someone has a better idea. Any advice would be greatly welcomed.
Are you saying you want the PC to render the view, and then upload its screen buffer to the mobile device, so the mobile device doesn’t have to do rendering? That sounds like it would be much less efficient, and laggy, than simply having the mobile device do its own rendering. I would start making your game and find out if the mobile device truly can’t handle the art assets you’re using; and in that event, use simpler, easier to render assets on the mobile side.
i dont need to read everything to answer this
ITS NOT EFFICIENT TO SYNC THE ACTUAL SCREEN DATA
essentially this is basically sending a texture file over the internet every single frame. Now you might think hey streaming videos can do it, they cant both generate a unique frame and then send it.
now compare sending an image file to sending vector coordinates of your object and camera
its like a millionth the size
the only way to get any degree of realism that you are seeking
is SUPER low poly models and a masterful use of textures
(id say normal maps and the works but youd have to use the works sparingly too)
then it comes down to the laundry list of optimization tricks for mobil which youd have to look up because people literally write books on the matter
THERE IS NO work around for this
short of making your own engine and then somehow doing so better than the UNITY DEVS whose sole career is based on making the engine.
-edit: I notice that my advice sort of sounds a bit centric on bandwidth, which certainly it is but, it still applies to the phones processor, by the time the server renders a frame its already after the action took place then there is the time involved in sending that data and the time it takes for the phone to re render the image
by the time all that happens the character is massively behind temporally (would look laggy as a cheerleader in a math class)
and because of the way you did it there is no way to compensate for the latency with code on the client side
plus the fact that you would max data plans mercilessly in addition to the high premiums youd be paying just to meet the bandwidth requirements.
I hope that this is adequate enough to deter you from this idea completely, if it isnt, then by all means prove me wrong an good luck to ya.