#proc.edu.ria

After some time off proc.edu.ria, I started to reboot it using redux. It went 90% good, yet I still need some time to push it further.

All in all, I will switch gear, freeze proc.edu.ria, and start a new procedurally generated content universe project and come back later on proc.edu.ria with better stuff to inject into.

Lately, at work, I used redux & react, and boy, is it cool !

So, I think I’ll push toward reactive programming for Proc.Edu.Ria. I’ve been rather bothered with how to maintain the codebase, along the various rules, stumbled upon some inconsistency with a part of rule_0 (which blocked me for rule_1). 

I must go forward quicker with the rules, but I can only do this without having to revisit rule_0 every time. And also a way to add features simply.

The redux way ensure my codebase will stay solid (because otherwise, nothing will work).

Next:

A proper way to edit variables

React stuff all the way

Rule 0 fixed once and for all (with unit testing and shit)

Rule 1 for connecting blocks made with rule_0

Find what rule_2 should be

A dynamic skybox

A cloudy sky ground

I’m currently trying (and failing) to take a pause on Pro.Edu.Ria.

Making a bad skymap, but it will get better, as I intend to make it dynamic, related to a virtual time clock.

Having done some heavy coding to have a clean project, I’m ready for rule_1 and some eye-candy stuff (shaders).

I was having some trouble with future rules, and yet, I’m confident saying that all rules should be independent.

That said, it only mean Rules should tend to create content, not deeply alter previous content. I’m not 100% sure that rule_9 will not be dependent to rule_8, but I really want to be able to have rules only based on the seed, and only the seed.

The seed

I use any string as a seed, hash it until I satisfy a hash size equal to size^3, or, if the hash is shorter, hash the hash to fill the void.

So, I should be able to apply any rule to any city block, using XYZ coordinate as offset to travel along the hash.

After a lot of time spent on rule_0, it’s done. 

The blocks weren’t properly aligned, so I made a block-grid debug display.

And I add a pilar, because this city should float. Or maybe it should, I’m not sure with all the futurism and all.

For what is my current use of Three.JS, I can tell it’s all but optimised. Mainly because I’m currently at rule_0 (volumetric/spatial density), involved with visual representation of blocks of various sizes. 

Yet, the performances are not here.

And after taking a look at what Babylon.js’s features are, I’m a bit tempted to use it. 

I had to change the laptop I used, and spent some time off proceduria, yet, I needed to be fixed on some architectural “issues”. 

Well, issues is a big word, but to put it simply, I needed to break free from the client/server paradigm, which I did by switching to a node-webkit app.

Then, I needed (and still do need) to have a smooth data pipeline. And for that, I need a generic json data schema (for the whole rule_X description), and a fast data generation (maybe using Rx ?)

Lastly, I overall need to stop wasting time considering whatever could be the best solution for the rule, when I crave to move to the next one.