In the ask the devs-thread, Rarebit answered a question about charatcer
customization. The answer was that it would be very difficult to
implement this without lag, as the server needs to send all kinds of
information to all the clients that view the character. So, my
suggestion is this:
When changing something other than clothes, it would be done from the
loading area. And when the change is made, let's say a new hairstyle,
the client makes an image of the new RSI. When you then jack into the
matrix again, this image is sent to the server, which then sends it out
to the other clients viewing the RSI in the world.
Example: You make a new wallpaper in photoshop. It has many layers,
matrix code, many cut-out RSI's, blur on some places, grids, matrix
text and so on. You save the file as a .psd file (or .pspimage in paint
shop pro). Now the file is very large. So let's make the file into an
RSI. It's sent to the server, and then from there out to the other
clients. Now you change soemthing in the .psd file. You add some more
code. Now the RSI data that is sent out to the server is chnaged, and
the server looks for the new part in the database, and compiles the
RSI, and sends it out ot the other clients. But, now you save your
wallpaper as a .jpg file. All layers, everything, is compressed into
one one image, and a quite small filesize.
This is what would happen when you change the hairstyle on your RSI.
The image would update. Now, as far as i understood, the server has
every clothing piece stored, and just dresses the RSI, and sends it out
to the other clients. The complication was that when modifying bodies,
all kinds of body parts would have to be stored on the server. But with
this idea, nothing like this needs to be stored in the server, except
clothes, that would work like it does now, the RSI body comes fro the
client. And when changing from the loading area, the client has even
more time to make the image and upload it to the server.
Hopefully you understood the messy text! Merry christmas :smileytongue:
customization. The answer was that it would be very difficult to
implement this without lag, as the server needs to send all kinds of
information to all the clients that view the character. So, my
suggestion is this:
When changing something other than clothes, it would be done from the
loading area. And when the change is made, let's say a new hairstyle,
the client makes an image of the new RSI. When you then jack into the
matrix again, this image is sent to the server, which then sends it out
to the other clients viewing the RSI in the world.
Example: You make a new wallpaper in photoshop. It has many layers,
matrix code, many cut-out RSI's, blur on some places, grids, matrix
text and so on. You save the file as a .psd file (or .pspimage in paint
shop pro). Now the file is very large. So let's make the file into an
RSI. It's sent to the server, and then from there out to the other
clients. Now you change soemthing in the .psd file. You add some more
code. Now the RSI data that is sent out to the server is chnaged, and
the server looks for the new part in the database, and compiles the
RSI, and sends it out ot the other clients. But, now you save your
wallpaper as a .jpg file. All layers, everything, is compressed into
one one image, and a quite small filesize.
This is what would happen when you change the hairstyle on your RSI.
The image would update. Now, as far as i understood, the server has
every clothing piece stored, and just dresses the RSI, and sends it out
to the other clients. The complication was that when modifying bodies,
all kinds of body parts would have to be stored on the server. But with
this idea, nothing like this needs to be stored in the server, except
clothes, that would work like it does now, the RSI body comes fro the
client. And when changing from the loading area, the client has even
more time to make the image and upload it to the server.
Hopefully you understood the messy text! Merry christmas :smileytongue:
