koobas.hobune.stream
Network Rendering from PC to Android Mobile
Dear all
Hello everyone, I'm not good at English, please forgive me.
I'm a student and our team doing a project which is that people can use an android mobile (an app) to understand our school's library, like Google map, but using 3D models , not using a camera with sphere photo.
Is it possible that using a PC to be a rendering server (the project at the PC) and using Android Mobiles to control the first person camera and get the picture on the mobiles screen (using WiFi, 3G, 4G) ? The PC render the picture and the mobile just need to download the picture.
Our teacher give some hints that requires us to search "remote rendering" at Google but I can't find anything about the term. Is there someone know the term? Please give me more information about it.
Thanks for reading this question.
I'd say that would be a very bad idea:
It's not scalable. Imagine having a server render 3000 active connections each perfor$$anonymous$$g individual rendering. All running on graphics cards, all having to send uncompressed data because otherwise your servers would overload.
Oh god the delays... Assu$$anonymous$$g you have a server powerful enough, imagine the amount of shitty laggy video you would have if you weren't on the same network as the servers. Firstly you'd have varying delays, so occasionally it would speed up and slow down, you'd have packet drops, so you'd either need a lossless connection or endure endless amounts of broken images.
Yes, I'm exaggerating a bit, maybe a lot, but the fact remains, unless you're doing non-real time rendering, you should never use servers for rendering. Theres a reason mobile devices have graphics cards!
Also, "remote rendering" comes up with a ton of stuff in a single google search.
Thank you about your opinion. Should I rebuild the project with lower polygon models and import it to the mobile? We are afraid the mobile can't handles the project as the library is too big and it included many objects (3D models).
There are a ton of optimisations you can do to make your application run faster on mobile, but thats for another question (and one you can answer in a google search)
"We are afraid the mobile can't handle the project", the biggest problem here is "we are afraid". Why are you trying to fix a problem you're not even sure you have? Get some phones and do some testing and see how well it runs. If you have a problem, then you can start doing optimisations.
Also it seems like this would be a project much better suited for the web, but thats just my opinion.
