The WIP Thread

[Captain J]

Looks healthy and smooth, i guess! Although the head detail shows a lot of difference than body itself.

[TrebbyTrebuchet]

Messing around in blender, experimenting with weapon animating. Turned out pretty well, I think

[Captain J]

Smooth! And are those casings actually functional projectiles?

[sonic_HD87]

Messing around with GZDoom after all this time. Since my HDD died sometime ago, most of the stuff I had for GZDoom vanished, so I replicated some of my works. This is one of them, using Survival Doom's tricks for pre-rendering. Although the method is old, still looks neat.

[TrebbyTrebuchet]

The casings are 3d models, just tryna get their physics right

[potetobloke]

*cool video showcase thing*

Can't wait what this turns into!

[jazzmaster9]

More Innocence X3
Ivory Keep (WIP name)
[imgur]https://i.imgur.com/rHjAhvI[/imgur]

[Captain J]

Hellishly wonderful blood pool.

[Clownman]

[MartinHowe]

Who needs World in Conflict

3 ... 2... 1... Calling down the airstrike!

[InsanityBringer]

So in the programming thread I mentioned I was experimenting with GMod's exposed nextbot AI. At the time there I was working on some simple state based behavior system where all state changes are managed manually by me, lamenting that I didn't fully understand the fear ai paper. Well, I gave it a second readthrough today and suddenly got struck by a bout of inspiration, and I've coded up a relatively simple planning system. This new system is insanely flexible now and I don't have to manage any transitions at all, just weights of individual actions. Its extremely impressive and I'm loving working with this new code base.

One limit I'm unaware of how to solve at the moment is that there can only be one goal active in a single frame. Imagine if this was AI for something like Team Fortress 2, where a bot would be expected to stand on a point and fight off dudes. Having a simple FightOffDudes goal and a simple CapPoint goal won't work 100% right since only one can go. They're either fighting off dudes or capping the point. However, firing is an autonomous system, all I need to do is tell the bot to start firing and they will if the target is in sight. Presumably, then, some basic fighting logic can be an action that sates CapPoint, so long as the actual staying on the point action gets some time to run, or something of the sort. Maybe the stand on the point action will fire at nearby targets? It could flee the point and put priority in smartly attacking if staying on the point is too dangerous.

If I can get my dumb nav stuff improved for gzd I'll take a stab at this sort of shit in zscript I think. It's really fun to work with and easy to manage.

EDIT: charple model is way too good

[GreenLegacy]

---

Evolution of mugshot(2017-2018)

This means I improved my pixel art skill a lot

[Captain J]

Original to Crystal Clear HD! Tho looks unnecessarily large for a mugshot. I like 2nd one the most. But i guess bigger face means more characteristics!

EDIT: The work must go-on.

[Pixel Eater]

Making an alternative translucency type for Desolate Spectrum:

Off

On

[leodoom85]

WIP of a Heretic map....