rocketships racing 3d

[Ricky]

therefore we use a skybox, or spheres (at the appropriate sizes) attached to a skybox.
this way, no need to have big shapes or to have entities at big distances.

  ...or you can do like the geniuses at "Starfield" and replace the 3D entity with a nice 2D sprite who always looks at the camera.
  R.-

[RemiD]

As a suggestion, I recommend you start thinking about a good tutorial about your game and how it relates to cryptocurrencies.

my goal is to make a simple 3d racing game (with rocketships, from the earth, to the moon !)

and have gameplay elements (competitors, obstacles, friends, enemies, events, money (tokens), fuel, items (and associated powers) ) which help to understand the important concepts and factors which can influence the financial markets (especially the fiat currencies market and the crypto currencies market )

of course the vision i have about it will change during the development (as always).

we will see how it goes 👀

[RemiD]

or you can do like the geniuses at "Starfield" and replace the 3D entity with a nice 2D sprite who always looks at the camera.

sure, i can use only a textured skybox with 2d shapes, or i can use 3d spheres for the earth and for the moon, and a textured quad (=textured sprite) for the sun.

but this does not change the problem that i have to know the sizes of the sun, of the earth, of the moon, and their positions in the 'sky', depending on where the rocketship is between the earth and the moon (on the zaxis) and depending on its lateral offset (on the x axis and y axis).

fortunately there is chatgpt to help me to find the formulas to calculate this 📝🤓

[Baggey]

Wouldn't a simple pythagoras do the trick 

https://www.google.com/search?q=pythagoras+theorem+formula&client=firefox-b-d&sca_esv=f189ccc98951b8a3&ei=VRhVaOSLKP-8hbIPu63eiQU&oq=pythagoras+theorem&gs_lp=Egxnd3Mtd2l6LXNlcnAiEnB5dGhhZ29yYXMgdGhlb3JlbSoCCAAyChAAGLADGNYEGEcyChAAGLADGNYEGEcyChAAGLADGNYEGEcyChAAGLADGNYEGEcyChAAGLADGNYEGEcyChAAGLADGNYEGEcyChAAGLADGNYEGEcyChAAGLADGNYEGEcyDRAuGIAEGLADGEMYigUyDRAAGIAEGLADGEMYigVIoDhQAFgAcAF4AZABAJgBAKABAKoBALgBAcgBAJgCAaACDZgDAIgGAZAGCpIHATGgBwCyBwC4BwDCBwMzLTHIBwo&sclient=gws-wiz-serp

Just solve for a which would be the dimension of the object. Once b is over a certain distance "switch/Case" graphic for simple blob? or different images?

Hope that gives you an idea to simplify the model abit?

Baggey

[Krischan]

the good news is that i can use 384 zones of 1,000,000 width (x axis), 1,000,000 height (y axis), 1,000,000 depth (z axis), without problem, and always keep player and the camera and the relevant entities, near the origin (0x,0y,0z).

It must also not be physical accurate because as we know from Hitchhiker's Guide to the galaxy:

"Space is big. Really big. You just won't believe how vastly hugely mind-bogglingly big it is. I mean, you may think it's a long way down the road to the chemist, but that's just peanuts to space"

For a game it is sufficient if it is "believable big" but even here you'll run into technical limitations soon. I've made a lot of experiments and Tech Demos for a space game that I haven't shown yet because it was never finished. For the size problem I've always used two approaches in combination:

- use a simple 1.0/distance scaling factor
- keep the Camera in a small box

I wrote this function years ago for the latter problem:

Code Select Expand

Global localx:Float, localy:Float, localz:Float
Global globalx:Float, globaly:Float, globalz:Float
Global simx:Float, simy:Float, simz:Float


' keeps the player in a given distance While the world can Move far away
Function Home(target:TEntity, world:TEntity, homesize:Int = 100)

    ' store Local player Position
    Local localx:Float = EntityX(target)
    Local localy:Float = EntityY(target)
    Local localz:Float = EntityZ(target)

    ' Check X axis
    While localx > homesize
    
        globalx:+homesize
        localx:-homesize
        PositionEntity target, localx, localy, localz
        MoveEntity world, -homesize, 0, 0
        
    Wend

    While localx < - homesize
    
        globalx:-homesize
        localx:+homesize
        PositionEntity target, localx, localy, localz
        MoveEntity world, homesize, 0, 0

    Wend

    ' Check Y axis
    While localy > homesize

        globaly:+homesize
        localy:-homesize
        PositionEntity target, localx, localy, localz
        MoveEntity world, 0, -homesize, 0
        
    Wend

    While localy < - homesize

        globaly:-homesize
        localy:+homesize
        PositionEntity target, localx, localy, localz
        MoveEntity world, 0, homesize, 0
        
    Wend

    ' Check Z axis
    While localz > homesize
    
        globalz:+homesize
        localz:-homesize
        PositionEntity target, localx, localy, localz
        MoveEntity world, 0, 0, -homesize
        
    Wend

    While localz < - homesize
    
        globalz:-homesize
        localz:+homesize
        PositionEntity target, localx, localy, localz
        MoveEntity world, 0, 0, homesize
        
    Wend

    ' store simulated player Position
    simx = localx + globalx
    simy = localy + globaly
    simz = localz + globalz

End Function

I've uploaded a demo with the full source here:
Quattest_Homekeeping

It is basically a huge boring starfield but it demonstrates how the camera "moves" through a really big starfield but never reaches the outer limits. This also avoids the common Z-Fight problems if your Camerarange extends 1,10000. And Objects that are further away than 10000 units can be often rendered as a pixel or small Sprite if they are not too big.

[RemiD]

Space is big. Really big. You just won't believe how vastly hugely mind-bogglingly big it is.

indeed

For a game it is sufficient if it is "believable big" but even here you'll run into technical limitations soon.

yes

i have my ideas to manage this, which should work. i am not going to look at your code now because don't want to confuse my mind... maybe later...

[Krischan]

No need to hurry, as I wrote this code is 10+ years old But keep us up to date with your ideas and solutions.

[Ricky]

i have my ideas to manage this, which should work. i am not going to look at your code now because don't want to confuse my mind... maybe later...

  The closer you are to a paradigm, the harder it becomes to create new standards and ideas that aren't related to it.
  The baker on the corner who hasn't done it before is more likely to create an "original" video game than someone who has been doing the job for years... Which is truly strange and paradoxical.
  Conclusion: I recommend you hire the baker as an advisor .
  Maintain your inspiration.
  R.-

[RemiD]

some news :
my idea of having 384 zones of 1,000,000width (x axis) * 1,000,000height (y axis), * 1,000,000depth (z axis), which makes a 3d world of
1,000km (x axis) * 1,000km (y axis) * 384,000km (z axis), works well. 🙂

and the sizes and positions of the sun, of the earth, of the moon, change depending on where is the rocketship between the earth and the moon and depending on the offset of the rocketship on the x axis y axis, this works well also. 🙂


now i am working on the rocketship controls and physics / movements. 🌍🚀🌑

[RemiD]

Space is big. Really big. You just won't believe how vastly hugely mind-bogglingly big it is.

i see what you mean now. 😅

i have managed to achieve what i wanted, with 384 zones of 1,000,000m * 1,000,000m * 1,000,000m, and a skybox of only 1,000units * 1,000units * 1,000units, which moves with the spaceship, and the sun, the earth, the moon, sizes and positions are automatically adjusted in the skybox, depending on where is the spaceship between the earth and the moon (in which zone and at which position in the zone).

but i realized that for a racing game it is important to give the impression of fast movement, so it is pointless to be accurate with distances and sizes, but this was interesting to do.

so now i have reduced the size of each zone ( 100,000m * 100,000m * 100,000m ) and it looks / feels a little better. but i may reduce it even more...

http://rd-stuff.fr/blitz3d/rocketships-racing-3d-20250630.mp4

all these big distances, and big sizes, reminded me of this scene from a movie :
https://youtu.be/vP_OSWdIrXw?si=I3LjqX2F6zKHlgft