mpevmvp VS procedural-gl-js

Well I did build this: https://github.com/eamonnmr/mpevmvp which leans more towards EV than endless sky. Not that it's caught any attention.

I tried to play this but I think i'm doing something wrong? went to here, downloaded everything including the pck file (windows user), launched up a game hosted a server 26000 (allowed all connections through firewall), launched up a 2nd instance of the game, successfully joined the server but all I see is stars. Am I jumping the gun on being able to play this or am I doing something wrong here?

Multiplayer EV clone: https://github.com/eamonnmr/mpevmvp

Started out as sort of an experiment in 'can you do multiple levels with godot's high level multiplayer API' and the answer turned out to be yes. On the way I ended up finding that loading data via CSV was a pain point so I spun out a project to load CSV rows into classes... All the work I did at work with a Python ETL framework is probably showing through there.

Nice writeup, I always like it when the shaders are highlighted like this. I got started in a similar way 7 years ago and have been making 3D terrains with THREE.js & WebGL since.

The real fun begins when you need to implement some sort of Level-of-Detail system and streaming in data to give the illusion of high detail everywhere without sacrificing performance.

Last year I released an open-source framework (https://github.com/felixpalmer/procedural-gl-js) for creating 3D terrains for web applications, you can see Uluru here: https://www.procedural.eu/map/?longitude=131.036&latitude=-2... (unfortunately the aerial imagery from our default provider isn't as high resolution as other places in Europe)

Great visualization and approach with compressing the tile data. Do you have a comparison of how much smaller the payload ends up being compared to simply sending PNG files?

I use PNGs to encode elevation data in my 3D mapping library (https://github.com/felixpalmer/procedural-gl-js/) and this does a pretty good job of compressing the data, for example in the ocean the PNG files are also very small as the image is mostly black. Different use case I now as your data is much more sparse, but I wonder how close the PNG compression would be compared to your approach.

Yeah, the React parts of this are very minimal. I'm not really sure what using it gets you, since it just manages a single div.

The _actual_ library that does all the work is here: https://github.com/felixpalmer/procedural-gl-js

- Tiny filesize means library is parsed fast. Package size is less than THREE.js thanks to code stripping

Check it out on Github: https://github.com/felixpalmer/procedural-gl-js/

The imagery comes from the Orthofoto dataset on https://www.basemap.at/ - the actual texturing is done by the Procedural GL JS library https://github.com/felixpalmer/procedural-gl-js