12-08-12 Lego Blocks

So the last couple of hours (or at least since last post) I've been working on make some Lego Blocks for the app.

Yo soy Alberto y ese ha sido mi post. Happy Codding!

12-08-12 New Lego Model

With the Model Loaded finished in DirectX mode (There is no entry for that and I just realized it) I decided to take a break on programming, and redo the Lego Guy with more accurate measures, the result after all sunday work:

The new Lego guy is the one on the right, do you notice the difference? Yeah aside from looking fatter next to the old one there is none... still now the measures are accurate as I said, and he would be able to interact in a better way with the other Lego pieces I'm going to make for the test program.

Yo soy Alberto y ese ha sido mi post. Happy Codding!

12/08/05 Specular Mapping and Transfer Mapping

Its 3:30 in the morning so I'll be brief.

I just finished normal mapping and transfer mapping, this lets the shader draw specular highlights given a map, and Transfer Mapping lets the shader has two textures combined in a single one in accordance to a 3rd texture description, that is, when white, the first texture is draw for a pixel and when black the second one, and all shades in between.

I also improved the way the shader is called on each draw cycle so its mo efficient.

I'm almost done with the Direct X part.

Yo soy Alberto y ese ha sido mi post. Happy Codding!

12/08/03 Vectors

So I was avoiding vectors at all cost... but decided to try them... for the sake of trying them, the result: 100 Model running on the screen at real time, The thing is... even-though vectors tend to be slow for accessing data... in my engine data is only saved as reference in the structures, everything is run from the GPU and therefore there are no bottle necks as often.

Here is an image:

Yo soy Alberto y ese ha sido mi post. Happy Codding!

12/08/02 Instances, Textures, Scripting

Lots of changes for this version, not that it is very noticeable still, but I changed all the Texture manager settings, now the Material Manager Class will load once all the textures that run on the program and use them along the whole program, models sharing textures wont be compromised if an instance change the texture it is applied to them, in the Lego example there wasn't any problem as the textures where not shared, and that generated extra materials, textures and therefore waist of memory.

I also started the reading of the configuration file along the program, It will run on the beginning with the settings specified on it and if there is no file, the program will create it on the first run with default settings.

Here is an example of instancing and texture swapping, I found the model online, and I don't know where is it from or if it has any copy rights... but as this is just an image and it wont be released with the dll I don't see myself being sued... Hopefully...

Yo soy Alberto y ese ha sido mi post. Happy Codding!