next »

[BrazilianBoy]

 Hi there

From here on, I'll use this to give info ONLY about the game. If I use it for Support, it will become a very big thread, because I love this forum 

I hope to post the very first eye-candy soon!!!


Lucas.

[BrazilianBoy]

The QuadTree implementation is finished Now, I can make huge levels with almost zero performance cost. The object instantiation system also benefits from the quad tree.
Unfortunately, it's very simplistic, and optimized for my game, so it won't be useful into the xith core 

Some gameplay objects were redesigned and look better than ever... I can't wait to make them work as they should


Lucas.

[Marvin Fröhlich]

The QuadTree implementation is finished Now, I can make huge levels with almost zero performance cost. The object instantiation system also benefits from the quad tree.
Unfortunately, it's very simplistic, and optimized for my game, so it won't be useful into the xith core 

How is your QuadTree concept? And in which way is it optimized for your game?

Marvin

[BrazilianBoy]

How is your QuadTree concept? And in which way is it optimized for your game?

Well, the QuadTrees are groups with four children each, wich can be all QuadTrees, or all QuadTreeLeafs. At this point, they behave as normal scenegraph structures, both extending Group, and Implementing QuadTreeElement. You can retrieve the children of a QuadTree, and locate a child deeper in the structure using a set of coordinates. Both classes have an "active" boolean field, used during the traverse.

QuadTreeLeaf owns a set of special fields. For instance: object instantiation definitions, and the collideables of the scene it contains.


If you wat to integrate it to xith, it can be reworked, but I did it entirely today, so it's very simplistic.


Lucas.

[Marvin Fröhlich]

If you wat to integrate it to xith, it can be reworked, but I did it entirely today, so it's very simplistic.

Well, this is indeed very simplistic. So I will create an implementation on my own. But thanks, anyway .

Marvin

[BrazilianBoy]

Wow, I haven't posted here for so long! But the work didn't stopped, in any way
I made springs, launchers, rings, the hud with counters and stuff, graphics for the first level... And much more stuff I forgot to mention. 30% of the engine is ready, I think. I need Collada and physics to work on Sonic's movements. But I can wait. I'm currently working on the menu system and it's design.

I'll post the first (decent) screenshot here:
 

[Marvin Fröhlich]

Wow, I haven't posted here for so long! But the work didn't stopped, in any way
I made springs, launchers, rings, the hud with counters and stuff, graphics for the first level... And much more stuff I forgot to mention. 30% of the engine is ready, I think. I need Collada and physics to work on Sonic's movements. But I can wait. ...

Wow. Apart from the background it looks awesome . You may want to replace the water by Mathias' GLSL water when it's ready.

...I'm currently working on the menu system and it's design.

Are you using the (relatively) new HUD MenuSystem (have a look at the testcase)? If not, what is missing in it?

Marvin

[BrazilianBoy]

Wow. Apart from the background it looks awesome . You may want to replace the water by Mathias' GLSL water when it's ready.

This is the 3D recreation of the first level of the first sonic game, created in 1991. I want to keep the original background About the water... The water in the riginal is almost like this. But it would be nice to pimp it!!!

Are you using the (relatively) new HUD MenuSystem (have a look at the testcase)? If not, what is missing in it?

I'm just making the graphics and planning how will things come and go on the screen. But that menu looks great! If I can mod the buttons, then I'll use it.

[Marvin Fröhlich]

...But that menu looks great! If I can mod the buttons, then I'll use it.

You can.

[BrazilianBoy]

But there are some considerations:

 - I need to move the buttons.
 - The menu should be controllable with the keyboard.

[Marvin Fröhlich]

- I need to move the buttons.

What do you mean? Drag them with the mouse or just place them somewhere different than in the examples? Both is possible. Making them draggable is simple (through a setter). And the example's button placement is just the result of one example of the MenuSystemWidget implementation, which you can do, how ever you want.

- The menu should be controllable with the keyboard.

This is a feature to come. It is not currently possible, but will be.

Marvin

[BrazilianBoy]

What do you mean? Drag them with the mouse or just place them somewhere different than in the examples? Both is possible. Making them draggable is simple (through a setter). And the example's button placement is just the result of one example of the MenuSystemWidget implementation, which you can do, how ever you want.

No, it's an animated effect: I want to slide them into the screen when the menu appears, and slide them off the screen when the menu disappears.

[Marvin Fröhlich]

No, it's an animated effect: I want to slide them into the screen when the menu appears, and slide them off the screen when the menu disappears.

I need to check that. Even if it was not currently possible, it should be and will be .

Marvin

[BrazilianBoy]

I need to check that. Even if it was not currently possible, it should be and will be .

I think it is. Shouldn't I create my own MenuGroupWidget?

[Marvin Fröhlich]

I think it is. Shouldn't I create my own MenuGroupWidget?

Yes, sure. But the HUD currently has no visible button focus behavior. Well, you can do this by catching the onFocusGained and onFocusLost events. So feel free to do so. But it would be nicer, if the HUD would do this for you.

Marvin