Been working on houses for the past few days. Modelling, texturing and previewing.
This is Fishermans house model I’m refactoring now, optimizing polycount, covering holes and fixing proportions.
Now house area can be set from GUI, with handy chechboxes.
P.S. Fixed a couple more bugs in the games code, for smooth in-game previewing.
For the last 2 months I’m completely occupied with RecastNavigation – porting and bugfixing, with addition of rigging now, which goes slowly .. very slowly.
On the brighter side – here’s a little glimpse of whats going on behind the scenes (aka Krom bought a color laser printer)
Majority of Recast Navigation code has been finally ported to Delphi.
Now I can switch back to more NG-related things. Plan is to make a test tool that will load NG map and try to build a Recast NavMesh on top of it, much like the demo above, but with an NG map instead of demo level.
Here on the screen is the first step of it – making a polymesh to feed into RecastNavigation navmesh generator.
This thing is monstrous! Luckily it’s simple and does not use any advanced data structures or C++ trickery.
State of the ported code:
Pathfinding and unit interaction (PUI) is a subsystem in the game responsible for most of the unit movements and interactions.
Today’s houses got more data-driven. Now it’s XML that governs which units can be trained in School/Fort/Barracks. Neat when you want to rebalance it 🙂
Spent this weekend coding the new wares handling for the houses. Now all the houses (except Market) store their wares in the same manner. This allows to experiment with Store/Barrcks/Camp/Fort wares set much more easily then before, without need to worry about special cases like “if ware is wtAll and house is htStore then ..”.
There’s one item I forgot to include into the “1k anniversary” post. I did not made it to the previous post date, but now, a day later, it is ready.
NextGame was born around a year ago. It’s time to summarize a little.
