[Build a Killer Linux Gaming Machine for $430]

I'd say "adequate" rather than "killer". But if you are on a budget then this would probably do the trick for now and then upgrade parts later. The power supply is what worries me the most about this build with regard to safety (of your PC) and longevity rather than performance.

 

Re. PC vendors -> agreed, never buy a PC already made... ever!

[A Red Letter Day]

I think the sucess of SteamOS amongst console gamers relies a lot on whether they can put out a standard SteamBox machine which is garunteed to play all the games… just like a console. It has to be affordable too. Without that it's no different to hooking up a PC to the TV.

 

Many console gamers say they like console because they put the disk in and it works garunteed...

 

I think the major advantage here is that you can share all your games between your console and your computer without ever having to buy them twice. You get to enjoy the best of both worlds at low prices... i.e. relaxed on the couch and hardcore at the PC. If I were to buy all my Steam games on Console (which isn't possible) it would probably cost me $10,000 + (at least in Aus)

[Teaching Leadwerks]

It might be a little advanced for most people, but I would love an article about shaders.

 

Best way to learn shaders is to read some OpenGL tutorials. Even if you aren't interested in OpenGL itself, you will very quickly learn how shaders work and how to use them.. Then adapt that

[Open to the Public]

Of course you don't..... well, let me expl... ah stuff it

[Open to the Public]

I can't think of a worse way to learn than from a full example game. It's a good way to get your brain stuck in a box... learning the tricks and never really learning the concepts.

 

@YouGroove: Have you ever noticed that when you buy a new car then you often notice the same model of the car on the road a lot more often.... same thing happening here......

[One Little Thing]

I can't stand typedefs like that. I don't see why its necessary to typdef variable types that are already short. Its a little more understandable when they get longer.

[One Little Thing]

Ok I'm not "bikshedding" here I'm just asking out of personal interest. If you are copying the argument... wouldn't it be quicker to copy something of a smaller size.. It just seems logical that it would be faster to copy something smaller in memory than something bigger.

 

And yes I do realize that this isn't the only thing relating to speed but I'm just wondering about this aspect specifically.

[One Little Thing]

Also if I recall correctly the memory size of a pointer / reference is the same size as a float and bigger than an int so there is no real gain in using a reference / pointer with these native types.

[The Art and Viability of Independent Development]

To me making a good game is always better than making the best selling game. So be it if I am never rich... So long as I can survive and slowly expand doing what I love most.

[One Last Thing]

Hey I'm not saying I don't believe you when you say it's a recast limitation. Doesn't change the facts....

[One Last Thing]

That's just the way Recast works:

 

Well that is just very sad considering recast claims to be world class....

 

Are we at least able to set this one and only size? or is that completely fixed?

 

I have to really think about this now. I don't know if I can even make my game on LE3 anymore .

 

Will there be any way to turn off the LE pathfinding?

[One Last Thing]

Controllers are all the same size, due to their use of the navigation mesh and crowd avoidance. If you were doing something special like a giant boss, I would skip the character controller altogether, because it's a special case and something like that would stay in the same area. It's a limitation, but everything good has constraints.

 

This sounds more like a shortcut than a "good constraint". This means we're limited to human or very humanoid characters in the game.

 

This screws me up a lot tbh... I don't have any giant robots but I have a lot of things with different sized controllers. If they aren't different sized they would look stupid intersecting with each other or colliding with things that don't exist...

[One Last Thing]

Ok cool. So physics is run on a different thread right? That's pretty good.

[One Last Thing]

What about a mode for having no physics body?

 

Not sure whether I like this or not because it seems restrictive... However, I can't really tell until I try it.

[Happy New Year]

Packaging manufacturer? Are you going to be selling LE3 in hard copy as well?

[Seventh Crystal Of Theia (S.C.O.T.) - Latest progress/ingame video.]

Graphically it looks really nice. I like the look and feel My only biff with it would be how the speed she runs doesn't match the animation.

 

One way to get around needing a hairbrush thing is to have a standard idle animation and then a list of emote like animations. Every time the idle animations ends you have a certain chance that a random emote will be played. It seems to work pretty well.

 

Good work. Keep it up.

[Ubuntu is probably the future of PC gaming]

You may be right. It may just be the best thing for the industry. I wouldn't ever have problems again going to a LAN and no one can play a game because they can't use DX10 on XP.

 

I think it will take a bit of time but Heck if that is where the games are then that is where I will go...

[The Adventures of Ken & His Trusty NPCs]

I have finished the standard patrolling behavior for the mobile NPCs. I can now set up a mobile NPC in the editor and give it a pre-determined patrol pattern in the editor that utilizes the path finding grid that I made. That is all working well now.

 

Now it is on to the attacking behavior. I want the units to pause for about 0.7secs or so and simply look at the target before sounding the alarm and then pursuing the target. It will change to a retreat state if it looses too much hp and a seek state if it loses sight of the target. To facilitate these movements I added two new functionalities to the Controller Module including:

 

int TrackEntity(LE::TEntity tgt)

int ChaseEntity(LE::TEntity tgt, float proximity)

 

These functions will automatically track and chase the target entity from the character controller module without the behavior states having to do any more than just call these functions once to initiate the appropriate movements.

[Path Finding: It's Not Actually AI]

HAHAHA lulz always a funny one MG....

[Path Finding: It's Not Actually AI]

Nice one MG XD..... Though do you sleep with one eye open? Just in case something happens along the way and you have to make a quick decision XD

[How to be a great programmer (or whatever)]

http://www.leadwerks...led/#entry48802

 

Evidently its not working too well Josh. Maybe you should go back to what you were doing before ::giggles::

 

[Leadwerks 3 begins closed beta test]

Oh well, I guess I will beta test it when it comes out then, like always. Testing is my speciality, I test everything, over and over again.

 

Flip the switch Igor!

[Leadwerks 3 begins closed beta test]

Well for future consideration. Macklebee, Marley Ghost & DaDonik. All three very honest and very capable.

 

Sometimes the silent giants do the best work.

 

Of course I'd like in as well but I'm not about to sing myself praises.

[Path Finding: It's Not Actually AI]

Thanks guys. Appreciate it all.

 

@Paul: Yes I agree AI is more about behaviors and decision making. Movement along the path is just another step by step algorithm without any decisions to make.

[Path Finding: It's Not Actually AI]

Fixed the problem where the character goes backwards to the closest / first node in the path list.