A Christmas present for ZDoom

Chilvence · Post by **Chilvence** » Sat Jan 08, 2005 6:43 pm

There is a second type of state that takes two parameters for x and y offset, but I dont think decorate weapons have access to it?

I havent really experimented much with this stuff yet, since I've been doing my own weapons in the source itself.

Some random thoughts:

It seems any given actor always contains several different pointers to lots of other actors, and I have been using these to do some intresting things.

Since these pointers are saved within the objects, how about extending certain specials like A_SetInvulnerable, etc to read these pointers as one of their parameters? For example A_SetInvulnerable(lastenemy) would read whatever pointer is in lastenemy and make it invulnerable(ok, crappy example), or even new ones such as A_CopyPointer(lastenemy, target)

Its far from being the most comprehensive way to manipulate an actors behaviour, but it is a start. For example a few pages back I suggested a pointer to set the actors tracer to the actor that spawned it, but this idea is far more flexible and generic.

Perhaps you could take that one step even further, eg a totally generic A_SetActorProperty([object_pointer], [property_name], [new_value])

eg :

A_SetActorProperty(target, angle, angle_t ANG45)
A_SetActorProperty(lastenemy, health, int 50)
A_SetActorProperty(tracer, flags4, |MF4_FIRERESIST)

Of course, I understand if that overcomplicates the parser too much, but I dont know how it works

Post by **Graf Zahl** » Sat Jan 08, 2005 6:49 pm

They have. Add OFFSET(x,y) after the state duration and before the code pointer. I haven't tested it myself though so it may not work.

Cutmanmike · Post by **Cutmanmike** » Sat Jan 08, 2005 6:59 pm

randy wrote:I'm stickying this for the time being so that it doesn't get lost.

I don't think it will with the reply rate

The Ultimate DooMer · Post by **The Ultimate DooMer** » Sun Jan 09, 2005 6:23 pm

deathz0r wrote:new weapon stuff

Hang on...how can you be playing with new weapons if they haven't been implemented yet?

Chilvence · Post by **Chilvence** » Sun Jan 09, 2005 6:24 pm

Go to page 4

deathz0r · Post by **deathz0r** » Sun Jan 09, 2005 10:31 pm

Well, I got a friend of mine to compile a build with Graf's code, so it's a "clean" version of ZDoom without Chilvence's hacks. Enjoy:

http://deathz0r.unidoom.org/junk/96weapons.zip

Your Name Is · Post by **Your Name Is** » Tue Jan 11, 2005 6:08 am

WOW! An early christmas present for me!

Post by **TheDarkArchon** » Tue Jan 11, 2005 3:18 pm

deathz0r wrote:Stuff about a railgun he made

Can I get that, please? Send it to my MSN adress if you do.

deathz0r · Post by **deathz0r** » Tue Jan 11, 2005 4:32 pm

TheDarkArchon wrote:Can I get that, please? Send it to my MSN adress if you do.

You want a do-tims beta, or just the railgun graphics?

GeeDougg · Post by **GeeDougg** » Wed Jan 12, 2005 12:18 am

Sounds like he just wants the railgun. But who wouldn't want the DO-TIMS beta? You'd have to be an idiot not to want that. No joke.

Edit: Unless the only reason you don't want it is because you're waiting for the full release....

Chilvence · Post by **Chilvence** » Wed Jan 12, 2005 12:43 am

Graf Zahl wrote:
Chilvence wrote:Hmm, I just had a look at the existing blast radius code, and it seems like it checks through every actor on the map (!) to see whether it is in range and blastable... this doesnt seem to make sense. Surely there is a more efficient way to do this, eg just checking through objects that occupy nearby blockmap blocks?

Of course there is. But that's one unavoidable part of commercial game programming. If the hack works it is unlikely to be removed. There are always more important things to do.

I have a followup question; it seems they only coded it like this because of the fact that you cannot scan for missiles in the blockmap. But I think being able to scan for missiles is actually quite desirable, for one you could implement some intresting monster defenses with it. Lets say hypothetically that all missiles were linked to a blockmap block (but still obeyed the existing collision behaviour). Do you think that would impact performance much? (I'm asking this before I start mangling my zdoom source in a bizzare experiment...)

Otherwise, is there a way to find all sectors that occupy a given blockmap area, and then look through those sectors for missiles? If there is something that is similar to this in the source already, can you point me to it?

Post by **Graf Zahl** » Wed Jan 12, 2005 4:12 am

Chilvence wrote:
I have a followup question; it seems they only coded it like this because of the fact that you cannot scan for missiles in the blockmap. But I think being able to scan for missiles is actually quite desirable, for one you could implement some intresting monster defenses with it. Lets say hypothetically that all missiles were linked to a blockmap block (but still obeyed the existing collision behaviour). Do you think that would impact performance much?

In 1993 it mattered. With today's computers the performance impact is irrelevant.

Otherwise, is there a way to find all sectors that occupy a given blockmap area, and then look through those sectors for missiles? If there is something that is similar to this in the source already, can you point me to it?

That would be much more calculation intensive. The blockmap has been invented to avoid having to do it this way.

Finalizer · Post by **Finalizer** » Wed Jan 12, 2005 6:11 am

I had the same problem with weapon offsets going all over the place, the knife in my game goes way up on the screen for some reason whenever custom punch is used, as if it's supposed to be a firing frame... I don't have any screenies with me, sorry.

Heh... this might as well be 2.0.96a!

Post by **TheDarkArchon** » Wed Jan 12, 2005 12:00 pm

deathz0r wrote:
TheDarkArchon wrote:Can I get that, please? Send it to my MSN adress if you do.
You want a do-tims beta, or just the railgun graphics?

Just the graphics. I just want something to experiment with.

Post by **Graf Zahl** » Wed Jan 12, 2005 12:21 pm

I just looked at the state offset issue. It appears to be a bug (state.Misc2 is left uninitialized.) I'll fix it ASAP. This obviously means I have to update the attachment to the first post.

Since I won't have any time for 4-5 hours anyway to do something about it I think it's a good chance to add stuff anybody here has done with this code. Feel free to send them to me by email and if it's good I'll add it.