Page 1 of 2
Duel Crash Bug fixed!
Posted: Fri Dec 23, 2005 4:37 am
by jb
In our duel gametype when the player dies we force the PlayerController into specating by calling ServerSpectate:
UnrealPlayer(Killed).ServerSpectate();
We did this so that players go to the back of the line and watch the rest of that round.
This is the cause of the error. As soon as I committed it out not a single crash. I just added the same info from the ServerSpecate() to our Duel code so that in on-line games the player is thrown into the proper specator state. I tested both listen and dedicated servers as well off line games. Not a single crash when I died!!! Ta-da
Sorry it took so long but I really dont see how I would have gotten this right way going by the crash logs run away localmessaging errors (as how does a broadcast message error and ie this was not easy to find so don't nock on me too hard
Now there is no way to really fix this in PR3.6 as I would have to recompile the Us and the dev enviroment has changed so much. I guess we can push really hard to get out something new ASAP! Please I can not make any promisses but we will try to move quickly! Also dont forget the old 3355 patch will work fine with out this crash...
Good...
Posted: Fri Dec 23, 2005 9:35 am
by Finn_bryant
That bug is really annoying, i'm glad that you worked out a fix,
but is there some way for me to implement it myself? If there was you wouldn't have to rush so much on the next release and i could play with 3369 straight away.
I like 3369 for normal ut becaues it fixes a few bugs that i was annoyed with and i dont want to reinstall everything all the time
Re: Good...
Posted: Fri Dec 23, 2005 12:27 pm
by Tim
Finn_bryant wrote:That bug is really annoying, i'm glad that you worked out a fix,
but is there some way for me to implement it myself? If there was you wouldn't have to rush so much on the next release and i could play with 3369 straight away.
I like 3369 for normal ut becaues it fixes a few bugs that i was annoyed with and i dont want to reinstall everything all the time
You can re-code and re-compile yourself..
Re: Good...
Posted: Fri Dec 23, 2005 1:22 pm
by jb
Finn_bryant wrote:That bug is really annoying, i'm glad that you worked out a fix,
but is there some way for me to implement it myself? If there was you wouldn't have to rush so much on the next release and i could play with 3369 straight away.
I like 3369 for normal ut becaues it fixes a few bugs that i was annoyed with and i dont want to reinstall everything all the time
No the only way to fix it is to change the code and re-complie. But to do that I would have to change my version back to PR3.6 and ensure I have everything set up correctly. Way too many chances to make mistakes. We are on the 11th IR (have another mini one out today) so I would plan on a new version sooner than later...
ok
Posted: Fri Dec 23, 2005 2:30 pm
by Finn_bryant
fair enough, i was hopeing the mistake was in some config file but if its code then ill just wait for the next release.
Posted: Tue Dec 27, 2005 12:35 am
by aLi3n
that happens in the PR3.6?
Posted: Tue Dec 27, 2005 3:43 am
by jb
aLi3n wrote:that happens in the PR3.6?
Yes using the new 3369 patch will cause you to crash the first time a human player dies. This was something new that was caused by the change in the 3369 patch. Ealier versions dont have this issue..
Posted: Wed Mar 15, 2006 12:32 am
by General_Sun
Posted: Wed Mar 15, 2006 5:52 pm
by Tim
Why the hell don't you just relase a patch??? Just make a 3.6-3.6b, not the whole file!
Posted: Thu Mar 16, 2006 12:46 pm
by jb
Tim wrote:Why the hell don't you just relase a patch??? Just make a 3.6-3.6b, not the whole file!
As I said I dont have an enviroment for 3.6 anymore, I would have to basiacally install every over again, ensure that I have the source code for 3.6, add in the fix and do lots of testing to ensure that something new (ie some dependency on other files did not get mixed in). Had things worked out better, you all would have had the release by now... We did not expect this delay
Posted: Thu Mar 16, 2006 4:24 pm
by Tim
jb wrote:Tim wrote:Why the hell don't you just relase a patch??? Just make a 3.6-3.6b, not the whole file!
As I said I dont have an enviroment for 3.6 anymore...
Send me the source!
You already have, but I'm not sure that's 3.6. If it is, please tell me - and tell me what was fixed and how do I fix it.
Posted: Fri Mar 17, 2006 2:40 pm
by Shadowstar
Maybe if more coders would join the team it wouldn't be neccessary to tie up our one main coder with this kind of stuff. You all do realize that every moment he spends working on the next release and not the last one, the sooner it will be released, right?
Posted: Fri Mar 17, 2006 9:44 pm
by General_Sun
Well for most of us, having 3.6 working again in a week is much better than having 4.0 in a month.
Posted: Sun Mar 19, 2006 1:06 pm
by jb
So does rolling back to the old Epic patch break other things for you? Just was curious...
Posted: Sun Mar 19, 2006 3:51 pm
by General_Sun
I can try that if I get some instructions on how.
