💬 znimatorʹs Feedback

[cyan chasm]

how did u get the skeleton its like unity and what does it do it shows the possible calculations?

[swift slate]

https://devforum.roblox.com/t/ceive-imgizmo-a-debug-gizmo-library/2470790/31

[swift slate]

blue ones shows the surface normal and direction, the green one its actually characters velocity, the longer it gets, the faster

[cyan chasm]

w

[cyan chasm]

so what can i use this debug for

can i use it to visualize raycasts?

and what are other debugging tips u got

bc i wanna understand optimization more

[swift slate]

debugging not equals optimization

debugging helps understand the process, what happens inside your code/logic

[swift slate]

yes

it also comes with different shapes like Cube, Sphere, Capsule

[cyan chasm]

what r optimization methods u know

[swift slate]

KISS, SOLID

learn these principles

[cyan chasm]

whaths that

[cyan chasm]

ommg

[swift slate]

KISS (Keep It Simple Stupid)
SOLID (Single responsibility principle; open/closed principle; Liskov substitution principle; Interface segregation; Dependency inversion principle)

SOLID its basically a standard for programming, after learning that you dont need to worry about optimization

[cyan chasm]

what about abserving server and client memory and how to know what resources ur script will use

[cyan chasm]

u know a video on this i would need to play with the debugging first but i just wanna see it before

or would it be easy to do once i understand the gizmo

[swift slate]

Its simple, Client stuff for client only, Server stuff for server stuff only.
for example, why the hell would you make visuall effects on server?! The server doesnt need to see or calculate that, thats a waste of resources
All effects should be on client
On other side Server is used ONLY to manage Data, nothing more.

[swift slate]

there is no documentation for Gizmo sadly

[cyan chasm]

hmm true so u came to this conclusion bc of SOLID? so solid is just the process of thinking

[swift slate]

@cyan chasm

        gizmo.AddDebrisInSeconds(0.25, function()
            gizmo.PushProperty("Color3", Color3.new(0.0117647, 0.701961, 1))
            gizmo.Arrow:Draw(downRay.Position, downRay.Position + downRay.Normal, 0.5, 1, 5)
        end)

the only thing you need to use its .AddDebrisInSeconds(), .PushProperty() and :Draw()

https://jakeywastaken.github.io/CeiveImGizmo/api/Arrow
there is some docs, but they are poorly written

[swift slate]

no, thats how game development works in general

[cyan chasm]

i want ot know the logic of gizmo

[cyan chasm]

hm

[swift slate]

this idea also comes to any other software programming
for example imagine you made own YouTube.

You have a huge database of videos, descriptions somewhere on the Earth

you dont want the server that holds all that huge data, render videos by itself

instead Client (The User) is making requests like - "Man i want to watch that video, load it for me"

and the YT goes - "Cant render full video, cuz i will die, so there is a encoded chunk of it"

and it sends small pieces of video every time when it can, depends on your internet connection

Its also shows why KISS works

no need to overcomplicate things just to show off
its your code, your game, your logic

[cyan chasm]

true