Not sure, though what file type are you using for the model, because .glb is the most compatible with Godot.

While I have no experience with shaders, in Godot any variant can be converted to bytes by using var_to_bytes and bytes can be converted back again to variant using bytes_to_var

For example,

var v3array : PackedVector3Array = [Vector3.ZERO,Vector3.ONE,Vector3.LEFT] print(v3array) # To convert it into bytes var v3array_bytes : PackedByteArray = var_to_bytes(v3array) # To convert it back again from bytes to PackedVector3Array var convert : PackedVector3Array = bytes_to_var(v3array_bytes) print(convert)

Hope it helps :gok:

I'm not too well-versed in the Godot engine thus far, but my best guess would be to check that the texture's filter is set to "Nearest" as opposed to anything that blurs the pixels like "Inherit" or "Linear"

I'm not sure whether or not you've figured it out by now, but for mobile devices you need to use buttons as your controls, as it's the only feasible way to interact with the Godot engine at the moment (besides tapping the screen). As for tutorials I would look to the Godot documentation on UI elements, or watch a tutorial on buttons.

Man, I need to start solving my own problems, because at the expense of around 10 hours of my time and a little bit of sanity, I've finally fixed it! For any of you trying to make a movement FPS in Godot for whatever reason, you can use this as a base. It's klunky, but it works:

if (velocity.x <= 0 && -velocity.x <= max_speed || velocity.x <= 0 && velocity.x * direction.x < 0): velocity.x += direction.x * air_accel * delta; if (velocity.z <= 0 && -velocity.z <= max_speed || velocity.z <= 0 && velocity.z * direction.z < 0): velocity.z += direction.z * air_accel * delta; if (velocity.x >= 0 && velocity.x <= max_speed || velocity.x >= 0 && velocity.x * direction.x < 0): velocity.x += direction.x * air_accel * delta; if (velocity.z >= 0 && velocity.z <= max_speed || velocity.z >= 0 && velocity.z * direction.z < 0): velocity.z += direction.z * air_accel * delta;

I have officially found the issue, and it seems to be that as soon as I enable autoload on literally anything, that's when the node system stops working, so for those of you who are seeing the same issue, I would avoid autoload because it seems to be VERY buggy.

I recreated this thing in different project so I can share project file if needed
image.png

Try usibg move and collide instead of move and slide for your characterbody, otherwise tou could use an area 2d to detect the collision

It is not a method it is a property of the atlasTexture
Please remember to make the texture an atlasTexture
I have made a video to show this, Pleas take not I am using godot 4.1 but it should not matter

Video demonstartion

You can use AnimationPlayer's "Add Track -> Call Method Track" in animation API ,

It will excue the the func you set after "attack1" finished .

Maybe try this plugin?
This can convert AnimtedSprite's animation frames in an AnimationPlayer.

GitHub - poohcom1/godot-animated-sprite-2-player: A Godot addon to convert animated sprite frames to animations in an animation player.

A Godot addon to convert animated sprite frames to animations in an animation player. - GitHub - poohcom1/godot-animated-sprite-2-player: A Godot addon to convert animated sprite frames to animations in an animation player.

favicon

GitHub (github.com)

Hi! And welcome to the forum!

In general the answer to your question is "yes" but specifically the answer is that nobody can tell without looking at the specifics.

I suggest you go ahead, get a free anti-virus program, for example a trial, and check your system and the files you expect to be malicious in particular.

If the files are small you can also upload them to a site like virustotal.com

Sorry, could you elaborate on what you want to do.

When you .pack() scene all the children that do not have that node as the owner not being saved, same with all variables that do not have export in front of them, maybe that's the issue?