problem with mean

[Hot-Doc]

Just had quick look on the new version of podbot_mm. Finally no more slomo-effect - Thank you very much!

But the server would crash a few seconds after loading the first map if I used meanmod too. Since the last version of podbot_mm worked fine with mean (v. xxx.13) it could have something to do with the recent changes, so I post it here. Any ideas?

And by the way, the waypoint for cs_siege had a little problem. A ct bot tried to jump on the ledge of the house number "01" but couldn't reach it from the box below this number.

Anyway thank's again for this well working bot! :)

[SoUlFaThEr]

ok i fixed this waypoint of cs_siege for you Hot-Doc

theres a demo of the bot making this jump in the demo section for pod2.6 in the filebase, and i uploaded all the waypoints to the filebase waypoints section for pod2.6, its titled beta3 now

go go go

[Pierre-Marie Baty]

when you guys post about a crash, please post also whether the crash occurs inside the podbot DLL or inside the mean DLL. That helps...

[Hot-Doc]

@SoUlFaThEr:

Thank you for your fast reaction! I didn't intend to make anybody hurry for this minor glitch, just wanted to mention it...

@ Pierre-Marie Baty:

OK, I will do my very best - but HOW exactly can I recognize this? The HL dedicated server console just dissappeares without a windows crash dialogue, so where can I look for the "guilty" program part? Is it logged somewhere? ???:(

(As you can see, I'm really not a pro...:o )

[SoUlFaThEr]

np thats what i want......help making perfect waypoints for all of you :)

[Hot-Doc]

You get what you want! ;)

[SoUlFaThEr]

btw, i didnt waypoint the lifts in oilrig and siege on purpose because in siege, thats the only route they will take then, and then they get stuck on the elevator(if only 2 or 3 go then its ok......but not ALL of them)

on oilrig the same because the bots that come to the elevator after the first 2...end up getting crushed under it and die.....

hope these are understandable

plus.....humans rarely take the elevator path.....its longer anyway(time wise)

[Pierre-Marie Baty]

@Hot-Doc: indeed, if the game just crashes without a warning and without a single messagebox, I understand perfectly that you're unable to tell us where it crashed. :) There's nothing you can do in that case, so forget my request. Too bad for us...
When it crashes with a windows error messagebox, it says which module caused the crash (ex: "HL.EXE caused an invalid shitty page fault or whatever in module PODBOT.DLL at page 0x12345678" etc etc). That was what I was refering to.

[botmeister]

Another thing to do before reporting bugs, is to run the bot with the minimum needed to run it.

Try and isolate the problem by running just the bot, then try the bot with mean. Try and find out if the problem is reproducable or not and what seems to be causing it.

[Hot-Doc]

@ Botmeister

That is quite exactly what I did. First I tried my normal configuration (hl 4.1.1.1e, cs 1.5, mean 5.50.13 from liblist.gam, metamod from commandline and podbot from plugin.ini) for three times without success. After that I disabled mean (changed commandline and liblist.gam) and it worked well.

Sorry, I really don't know what or how to test else. ???:( Any suggestions are welcome!

/EDIT:
Also tried the updated version of podbot (with modified changelevel). The server runs a few seconds longer but doesn't survive the first autoteambalance. Bots are added and then - nothing, no error message and no more hl console...

[botmeister]

I'll have to try mEAn out with the new podbot_mm to see what's going on. Staty tuned ...

[biohazerd87]

I have this problem and posted the error and no one would look at it>

[Pierre-Marie Baty]

biohazerd, posting an error report, even fully detailed, is for a developer nowhere as useful as experiencing the error himself inside a debugger. Believe me, it's not that nobody looked at it, it's just that this information is -and CANNOT, no matter how detailed you go- be sufficient for a developer to fix the bug immediately. It's useful, but it's not sufficient. It's nevertheless the maximum a tester can do. You reported the error, so now it's known - people will look at it. Just have a bit of patience :)

[biohazerd87]

I know that and i hope i am not coming off the wrong way i just would have thought some one would have posted saying they would take a look at it or something thats all

[botmeister]

Um I said I'd take a look ...