CS1.6 dedicated server halts with podbot
 

I have a Windows XP dedicated server running CS1.6 that runs fine without podbot. After adding podbot the server stays up for a few hours then halts. I have included 3 screen shots that I'm hoping someone can help me with.

The first screen shot shows a mismatch statement at startup.

The second screen shows my list of mods.

The last screen is from the Windows application event viewer when the server halts.


Any help is greatly appreciated and thanks in advance...

http://www.geocities.com/kungfuchris1/screen1.JPG



http://www.geocities.com/kungfuchris1/screen2.JPG
http://www.geocities.com/kungfuchris1/screen3.JPG

Re: CS1.6 dedicated server halts with podbot
 

Try to test which map it crashes on. What is that [xbot] in that console log I can see?

Re: CS1.6 dedicated server halts with podbot
 

Thanks and I'll go through the logs to see if I can determine if a particular map may be causing the problem or try and reproduce the problem...funny thing it never happens when I'm playing. Anyway the "xbot" you see is just part of the custom name I've given the bots on our server.

Re: CS1.6 dedicated server halts with podbot
 

KWo,

Thanks for the tip...it does appear to be with a specific map namely:

cs_assault_apc_b2

I've removed the map and hope the problem does not reoccur. BTW on my first screen shot do I need to be concern with the Podbot "mismatch" statement near the bottom?

As always I appreciate the help. All the time goes into making my 11 yr old very happy.

:chinese:

Re: CS1.6 dedicated server halts with podbot
 

Are there some breakable glasses or something like that? Try to find another pwf file for that map and let me know if it still crashes on You with the new pwf.
Note:
When You replace map_name.pwf file by another one , You need to delete map_name.pvi and map_name.pxp files.

No - don't worry about it. It's because podbot mm has been compiled against metamod 1.17.4 and currently You are using metamod 1.19.p28 - but - as Bailopan (one of curent mm developers) said me - there is always backward compatibility. The interface of mm has been expressed to 5:13 and podbot mm has still 5:10 (because of compilation with mm 1.17.4) - that's why You can see that message.