Making some good progress.  Updating visuals/adding some new gameplay elemeents.  Here are some more images from the second level.





I've also recently started a twitter account for those that are interested in following (I'll follow any fellow devs here back as well):

https://twitter.com/FuzzyWuzzyGames

Going to also order a Wii U dev kit soon.  Good times!

Congrats for wii u game !!

where i can find some videos ?

Thanks!  Here are some videos:

Our most recent trailer:




Our video dev log announcing the Wii U release:




The game also now looks a lot better than what appears on those videos since we moved to Unity.

Been a while since I've posted here!  Been updating the game quite a bit, but my wife recently gave birth to our second son so it's been pretty busy.  But here's a screenshot of the most recent progress:

Working on a new HUD.  This HUD hides each section when necessary, keeping the game field minimal.  One thing I'm doing is removing the score.  The score will now be tabulated after you finish the level, also keeping information more focused to the game.

Been playing a bit with some texturing effects/post processing stuff in Unity.

Details maps are awesome.  Our level maps are like 4096x2048, which is already at max size on Unity.  It ends up blurry if we zoom in, so detail maps hides the bluriness.  Left is without any detail maps zoomed-in, right is with a simple 512x512 repeating detail map.



Also got some glow working on the rails in-game:

How I would do it is to create a global state machine script (in C#), and attach it to a single game object that's going to live in the scene.  I would then tag that game object as a "StateMachine".

If you ever want to access that state machine from other game objects, then you can use GameObject.FindGameObjectWithTag("StateMachine").GetComponent<StateMachineScript>(), where StateMachineScript is your class name.  Using Find functions in Unity can sometimes be slow, so try caching wherever possible.

If you're lazy like me, I would attach that state machine to the Main Camera, and access it through script from other game objects using Camera.main.GetComponent<StateMachineScript>().

Another option is to get Play Maker Unity plugin.  It's a popular visual scripting engine that I've used at a company that I work under contract.  It works really well:

http://www.hutonggames.com/

I've personally used Unity's own manual to learn unity.  Their main page is broken up into sections, so it's easy to pick and choose:

http://docs.unity3d.com/Documentation/Manual/index.html

We're now official Nintendo developers!

Armillo is coming out to the Wii U eShop!!

http://www.nintendolife.com/news/2013/01/fuzzy_wuzzy_games_is_rolling_armillo_onto_the_wii_u_eshop

Now working on a dynamic weather engine.  Got some rain & lightning working:

Still needs a monitor, some vinyl lettering (Ackk Studios/Two Brothers branding) and a whole for the controller cable... it's getting there!
Only 3 more to go

Which color should I make next... Green, Blue, or Yellow?

Wow!  That looks awesome.  Love the dedication and hard work you guys are putting into this.

What color to make next?  Well, I vote green.  I suppose it doesn't matter too much as it looks like you guys are going to make all four.

Bonus stage is working now as well (minus the blast-off effects).  Here's an on-the-moon shot:

Working on the new menu system now.  Focusing this updated system on using 3D widgets with a much better presentation.  Also trying to get the player straight into the game a lot faster.

Love it, Keep it up!

Thanks!

Looks like it's going well.  Got the block physics, trapper, and critter routines in. 



So next I'll be working on getting the bonus stage working as well as game entering/exit camera panning transitions.

Alright!  Parallel universe works well now in the Unity port.  Missing a bunch of effects that the original version has, but those and hopefully more will be added in eventually.



Next, going to add some physics to the bashable blocks, work on porting over the trapper (the enemy that grabs you into a glass cage), then adding new critter behavior routines.

Looks pretty good so far!

Thanks!!


Unity port is coming along.  I've got a good chunk of the gameplay elements in (re-writing a bunch of them in the process) and Level 1 can now be played from start to end with all the game elements except for the parallel universe.

As for getting the parallel universe to work, I'll be taking advantage of Unity layers:



Using layers, I can basically spawn all the objects (both main and parallel universe) in the scene, then tell the camera to only render objects in the main universe, then switch over to the parallel universe when needed.

Only thing about layers that kind of annoys me at this point would be that lighting doesn't seem to work in layers.  This kind of messes up my plans for multiplayer as a light follows each player and should only be visible on that player's viewport.  I'm thinking of just baking light positions in the world for multiplayer maps as a work-around.

Alrighty.  The world is nicely populated now.  Now going to start implementing the gameplay logic and visual effects of the missing game elements of level 1.



Just some of my initial thoughts about the porting:

- Overall porting of the code syntax was straight forward.  Some namespace changes (Math to Mathf).  Some missing math functions such as Vector * Matrix (replaced by Inverse(Matrix) * Vector).
- x axis was flipped for me, so I had to negate it when parsing my level data
- Model transformation in Unity follows strictly scale-rotate-translate.  So some of the squishy effects of Armillo wasn't ported as a result as I used a good series of matrix multiplications as a result.
- I've avoided using Quaternions in XNA.  Quaternions are now everywhere in Unity, but they're straightforward to use.  (Just not straightforward to me when working with the math logic behind them!)
- I love Unity's game object, component, and runtime tuning system.  Makes things a lot easier.

I had to also scrap the entire XNA coded rendering engine in favor of Unity's built in.  Much easier to work with and shader support seems pretty good.  I don't get any full screen effects or dynamic shadows with Unity Free, so I'll have to upgrade to Pro later on once I'm ready.  Other things I've scrapped: the HUD (I'm debating whether I should go NGUI or OnGUI.  This game doesn't have a complex HUD, so I'm leaning the latter), the Front-End, and the main game logic loop.

So the decision was made to port over to Unity.  One of the reasons is for better cross-platform support.  The main benefit of sticking with XNA is that we would be able to release Armillo on XBLIG, but that market seems like it's going nowhere at this point.  

The other path that we could have gone to would be to go with Mono.XNA which is the most easiest alternative as it uses the same XNA development interface.  But Unity seemed to be the best fit - I'm pretty familiar with it, plus it allows for some awesome iteration times (runtime previewing of assets, tuning of values, ease of use, etc.).

This means that we'll be releasing Armillo on Windows, Linux, and Mac.  And further down the road, on iOS and Android.

So the past couple of weeks, I've been testing out the feasibility of porting.  It's a bit of a pain - going to have to re-write about 60% of the code (a decision that I reluctantly made), and doing an incremental port (ie. porting the code piece by piece).  But so far, it's shaping up:



Just working on getting level 1 back in the game, which is starting to look a bit nicer with normal mapped procedural models (eg. the guard rails & doors).  I've also purchased a nice FX tuning tool / library called fxmaker, so the visual effects should also start to look a lot better as well.

Bye bye XNA....  Hello Unity!! 

So everything's installed on my new laptop.  Now back to development!

Here's a rough initial pass of the texture map:



In-game it looks like this:



At this point, it still looks a bit bland, with some of the textures a bit too much on the realistic side.  Another thing that's missing is props, but those will come at a later time.

Oh I think I see, the "pole" aren't the stretch edge line but are "inside" the UV. Or something like that. He's clever :O

Ah I think the black part are the unused texture space, there are none in the rendered sphere, so it show the uv projection, I think I get it now!
Thanks for the explanation

Keep up the good work

Thanks!!