💬 kaizagidoraʹs Feedback

[faint robin]

are you sending client animations to the server via remote or smth
it'd be more smoother to handle all animations on the client

[tardy stratus]

They aren’t animations

There literal calculations

Tail and neck / terrain alignment

They get sent to the other player to reconstruct it on there device

Server does no calculations

It just helps send data

Through the network

With verification checks

[faint robin]

isnt that literal animations 🫃

[tardy stratus]

[faint robin]

you can still have all of this be ran on the client rather than replicate it on the server

[tardy stratus]

Sorta but they aren’t premade

[tardy stratus]

the server isn’t replicating anything

It’s just sending data

[tardy stratus]

^

[faint robin]

why are you sending data....
still sending information to the server......

like i get you cant get the camera position from a client but that'd still be a security flaw if you're sending the camera position to other clients

[tardy stratus]

you don’t know what I’m sending

All I said was math calcs

You don’t know how the framework is made

You know nothing about the system

So why do you keep assuming

First

[faint robin]

get this guy on the top 10 delusional list 🫃

just common sense rlly
if you want it smooth have it ALL be handled on the client
don't send information to the server to then relay it to the clients (UNLESS ABSOLUTELY NECESSARY)

only have the server validate things 🤷‍♂️

that and you can get remote data with just a remote spy

https://devforum.roblox.com/t/tired-of-remote-spoofers-lets-fix-it/2577431
smth good for you tho

[tardy stratus]

Mind explaining to me your solution to redoing this so no data gets sent to the server while still keeping it accurate

And also working with graphic quality and distance of players if they are streamed out

Like a list

[faint robin]

movedirection...
velocity..

animate accordingly similar to how the client does to itself

[tardy stratus]

Okay well tail is understandable

But what about neck rotation

[faint robin]

i mean you could probably make it dependant on other player distance, whether or not have the neck face towards nearby players and if not just have it face in the facing direction 🤷‍♂️

might be a little over the top but that's a suggestion 😭

that orrrrr
get the general facing direction of the camera (not position or orientation)
and send it to the client from the server at intervals to prevent server lag

but overall the whole handing everything besides the neckmovement on the client is more preferable over server lag

[tardy stratus]

Okay and terrain alignment?

[faint robin]

raycast down the legs and use the kinematic chain algorithm 🤷‍♂️

[tardy stratus]

So fire a raycast for every other player on your device

[faint robin]

i guess yeah

unless you want to use a single raycast to get the surface normal

but then again i feel like the max players of a dinosaur game is abt 20/30 players
and raycasting is rlly cheap if you use it the right way

[tardy stratus]

There are 2 raycasts being fired a hip height one so they don’t clip into the ground ( moves with the rotation of the dinosaur) and one that gets a Angel ( doesnt move with the Dino rotation. 2 of them also help with jittery ness so they don’t move back and forth when on rock terrain or on 2 angels close together

So 10-20 to 40 raycast you’ll be calculating for other players if they’re all together in a good render distance

[faint robin]

not too bad 🤷‍♂️

probably have the raycasts update every 0.5-1 seconds only whenever they move

i don't think it'd be too much of a performance impact
i'm just rlly worried abt the server

[tardy stratus]

How much bytes of data would you think is okay to send through the network if you’re worried about the server

?

[faint robin]

smth absolutely minimal

garbage collection is a horror 😭

as minimal as it gets

[tardy stratus]

Do you got a size ?

[faint robin]

nothing more than 1mb atleast

i usually sit around 40 kb