LucidX1235 wrote:

Stupid question on how you make these, do you have a base engine you can edit to make games, or do you make a slightly different one from scratch every time>

GL00B wrote:

No, i make every game from the very scratch. That way, I can change the way it works depending on what i need for the game. take the tekken 4 game and nfs 3 game, why would i need such a complex wall render for a fighting game? same goes for the car game, the car model is super simple and doesn't need a rotating vertex render

For Each []in ()

End

kittygamer8997 wrote:

@GL00B I saw your profile comments were closed so I have to type here but I have something maybe you know about that will improve some stuff. Its the For Each block, it is compatible with scratch and runs loops 10x faster its in a extension of turbowarp. Your games do a lot of calculations so it will still be laggy but it could possibly run better. Im using it for my 3D space game, possibly the best space simulation on scratch because I havent seen anything better yet. Idk if this format works in scratch blocks

for each [i] in (100)

end

kittygamer8997 wrote:

kittygamer8997 wrote:

@GL00B I saw your profile comments were closed so I have to type here but I have something maybe you know about that will improve some stuff. Its the For Each block, it is compatible with scratch and runs loops 10x faster its in a extension of turbowarp. Your games do a lot of calculations so it will still be laggy but it could possibly run better. Im using it for my 3D space game, possibly the best space simulation on scratch because I havent seen anything better yet. Idk if this format works in scratch blocks

for each [i] in (100)

end

Idk how to make the block look like a repeat loop but its just a different look of a repeat block

kittygamer8997 wrote:

@GL00B I saw your profile comments were closed so I have to type here but I have something maybe you know about that will improve some stuff. Its the For Each block, it is compatible with scratch and runs loops 10x faster its in a extension of turbowarp. Your games do a lot of calculations so it will still be laggy but it could possibly run better. Im using it for my 3D space game, possibly the best space simulation on scratch because I havent seen anything better yet. Idk if this format works in scratch blocks

For Each []in ()
end

GL00B wrote:

kittygamer8997 wrote:

GL00B wrote:

kittygamer8997 wrote:

I always wondered how I could do something like line intersection raycasting because I don't know how that works. how does it detect collisions like that? I only know step by step or DDA. how does it know where the collision is??? please teach me or give me something to tell me how it works.

Glad you're interested! Since you know how to code a DDA raycaster, I'm really sure that you use vectors for it. Your Line intersection raycaster will have the same code as your normal DDA raycaster up until the actual loop. there, you will be checking a list that has your map data, cycling through it. you won't be using a voxel list, or a tile list, nope, just a list that has your data in certain packets that you can cycle through by the length of the packet. so simply:
( Wall_index * ( Packet_length ) + Wall_attribute [ this is where you store the x1,y1,z2,texture,height,anything you can think of. ) of

then you will use a line intersection formula, to find the intersection between 2 lines. one will be your ray, and the other will be the wall in the list. you cycle through the list and you will have checked intersection with the rays. the formula i use is this one :

https://www.youtube.com/watch?v=bvlIYX9cgls

You will use the alpha and beta to determine the Distance and the U coordinate in the texture of that wall. Thats all

****note****
you will realise the walls are NOT sorted, so you will need to use a z buffer, which will limit the y axis's resolution too. it will also greatly reduce the performance, so code it right and avoid extra calculations as much as possible!

Too much stuff. i am very very very confused and how would you even make the map?

Okay, lets simplify it. imagine the ray in a normal raycaster as a bullet that keeps moving till it hits something. right?
well, in our line segment raycaster, there is no bullet. there is just a laser beam, that instantly shows!
this laser beam checks if any lines are touching it. forget about making the map now, just tell me, is this clear? you are not moving till you hit a wall, you already hit the wall ever since the “beam” spawned, which is just a really long line that starts at your camera's position and it's end is a point that's equal to your vector + camera position.

matthewpanop wrote:

GL00B wrote:

kittygamer8997 wrote:

GL00B wrote:

kittygamer8997 wrote:

I always wondered how I could do something like line intersection raycasting because I don't know how that works. how does it detect collisions like that? I only know step by step or DDA. how does it know where the collision is??? please teach me or give me something to tell me how it works.

Glad you're interested! Since you know how to code a DDA raycaster, I'm really sure that you use vectors for it. Your Line intersection raycaster will have the same code as your normal DDA raycaster up until the actual loop. there, you will be checking a list that has your map data, cycling through it. you won't be using a voxel list, or a tile list, nope, just a list that has your data in certain packets that you can cycle through by the length of the packet. so simply:
( Wall_index * ( Packet_length ) + Wall_attribute [ this is where you store the x1,y1,z2,texture,height,anything you can think of. ) of

then you will use a line intersection formula, to find the intersection between 2 lines. one will be your ray, and the other will be the wall in the list. you cycle through the list and you will have checked intersection with the rays. the formula i use is this one :

https://www.youtube.com/watch?v=bvlIYX9cgls

You will use the alpha and beta to determine the Distance and the U coordinate in the texture of that wall. Thats all

****note****
you will realise the walls are NOT sorted, so you will need to use a z buffer, which will limit the y axis's resolution too. it will also greatly reduce the performance, so code it right and avoid extra calculations as much as possible!

Too much stuff. i am very very very confused and how would you even make the map?

Okay, lets simplify it. imagine the ray in a normal raycaster as a bullet that keeps moving till it hits something. right?
well, in our line segment raycaster, there is no bullet. there is just a laser beam, that instantly shows!
this laser beam checks if any lines are touching it. forget about making the map now, just tell me, is this clear? you are not moving till you hit a wall, you already hit the wall ever since the “beam” spawned, which is just a really long line that starts at your camera's position and it's end is a point that's equal to your vector + camera position.

I know I did not ask the original question but is it like a very long sprite that detects if a wall is touching it

kittygamer8997 wrote:

-snip-

for each [ i v] in (10) {
do something with (i)::custom
}::control

23mConnor wrote:

I’ve tried 3d elements, but the most I got was a 2d rectangle that created it’s shape sl o w l y.
Still, it’s a cool ambition, I might return to racking my brain around such things before the end of this year!

thomasito101 wrote:

https://scratch.mit.edu/projects/1064911854/

Does this use the Raytracing method? And how do the textures “warp”? Or are they individual pixels changing color? I want to know please!

N8_D_GR8_1 wrote:

kittygamer8997 wrote:

-snip-

I think you mean this:

for each [ i v] in (10) {
do something with (i)::custom
}::control

It was a block that was removed from scratch a while back, but is still supported. You can use it in a program by using the opcode “control_for_each” or backpacking it from a project that has one. I've only noticed very small changes in performance with this block, but it can come in handy for simplifying code a bit.

https://en.scratch-wiki.info/wiki/For_Each_()_in_()

magicsponge321 wrote:

I'm trying to make a raycaster, like you recommended, but I'm stuck on making FOV and making it.. ya know, 3d.
Here's the link: https://scratch.mit.edu/projects/1189288628

ajspeckhals wrote:

magicsponge321 wrote:

I'm trying to make a raycaster, like you recommended, but I'm stuck on making FOV and making it.. ya know, 3d.
Here's the link: https://scratch.mit.edu/projects/1189288628

griffpatch has a yt tutorial on that