!!! WMP Contest Discussion !!!

[Postal]

Im happy to hear all this discussion. Unhappy since my ISP sucks, and as soon as this contest is over, I am switching services.

 

[soldat]

searched for those strings in the *.uc and *.u files... no luck

but it seems you get those errors on maps anyways regardless of your weapon. so hopefully its not your fault if you are concerned, try swapping out your meshes for other ones, one by one. hunch says it might be a mesh problem.

 

[Donator]

Happy news: subclassed the Disruptor directly under weapon (instead of LinkGun) and changed those small green flames that are attached to players' bones from xEmitters to Emitters. Couldn't crash the game since then and I've already been playing 45 minutes...

 

[Postal]

That was probable the problem. Something linkgun that you changed was conflicting.

 

[Donator]

Unlikely. That was my firts idea too, but even after leaving out the LinkGun code the game would still crash occasionally. I think the problem originates either from attaching several xEmitters to the same bone, or from the "if (!AttachToBone...) -> Destroy.xEmitter" paragraph, since the problem disappeared the moment I used the Emitters' native "Kill" function instead of the xEmitters' "Destroy".

 

[Donator]

This version should be bug free. It's a code-only version, so only useful to those I've sent the first beta with the new textures included. Just replace the old .int and .u file.

 

[Parser]

Hey Postal, we're still allowed to use the SpecialButton exec function in our weapons, aren't we? I've managed to make mine more interesting in doing so.

If you want a description, head over to http://fraghouse.beyondunreal.com - latest news post.

 

[Postal]

Yup a special exec allright. but I would like permission that if several weapons uses execs, to change the names so they all use the same button.

 

[Parser]

Mine's currently using SpecialButton, like you specified on page 2.

 

[Postal]

Actually it was Doc idea, but it is a good one.

 

[soldat]

disruptor.... usually to destroy the xemitters you set mregen=false. this, coupled with the xemitter lifespan, ought to exterminate it. but if you fixed it, cool. i'll test it out.

also, do you hurt yourself when you fire disruptor primary blasts? not the explosion, but just by shooting? i think i killed myself that way. hmm.

parser, your underslinger sounds lethal... i like it!

 

[Postal]

9 days left. I do hope I get 9 more entries.

 

[Donator]

Per se, it's possible. The Disruptor primary projectiles perform a constant HurtRadius every 0.1sec, so even a graze shot will hurt you slightly. But even with the speed combo activated you're too slow to actually hurt yourself with it. It is possible though, if you jump from a high spot, gather some falling speed and fire downwards.

 

[Postal]

I will someone to send me an entry.

 

[Parser]

I think mine's more or less done now. Got the damage types in, finalised it, but I just need to give it a quick test online. Hopefully it'll be in your inbox by tomorrow.

 

[Postal]

WooHoo

And look, Kangus has another whimpy avatar again.

 

[Donator]

Same here. All I need is the ok from the beta testers and you can have it.

 

[Postal]

WooHoo <<--Cheap Excuse to boost post count-->>

 

[Parser]

Damn, problem. Uh, the exec function doesn't work online at all. No client message, no change in firemode properties. I'll see if I can't fix this.

 

[Parser]

Ok, I got it working. Just needed to turn the exec function into a simulated function then replicate it clientside.
If anyone else is having problems with their exec commands working clientside in netplay, do this:

[*]Turn exec function SpecialButton() into exec simulated function SpecialButton()

[*]Now add some server to client replication:

replication
{
  	reliable if ( Role < ROLE_Authority )
    		SpecialButton, bAlternateFire;
}

The bAlternateFire bool is just my toggle for switching between the two alt fire modes.