-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transmission of models & textures in MP #7
Comments
Yeah, if this eventually gets a server side backend, definitely. That's what ModelCache is supposed to do. I'm not too sure about uploading models, because well... I'm always a bit paranoid if it comes to uploading something from the client -> server, but well. It would work that way. Not sure how big these files are though. I would throw it at a worker thread and then slowly load the models afterwards. We need a way of identifying a model. |
Is there any danger to loading the model files onto computers? |
@skyem123 Well, it could be a virus ^^ It won't get run, but still. Maybe there is a way to validate the file... |
To ID the model, we just get the hash of the uncompressed-but-packed file(something like a TAR). That's why we need the way the packing occurs to be consistent - so the same data creates the same packed file, which has the same hash. |
so it'll be the same security issues as downloading a texture pack from the server? |
skyem123: What security issues |
Maybe there could be a way to share the animation files, but download the models from the official sources? |
It's no good if we're all the same character...
Here's the general idea:
The server should be able to opt-out from transmitting/receiving files.
Since the client should have a list of models available anyway, the server must still pass the manifests - the clients will then search their local model directories for a PMX file that matches and try to use that.
The text was updated successfully, but these errors were encountered: