Non-Steam v19+ closes and quites into OS.
 

[Whistler]
You wrote very good bots.
Nice AI and relatively(at least to [e]pod and pod-mm) clean code.

But where is some big trouble.
When playing with bots under non-steam v19+(v19,v20,v21,v22) after playing some time(maybe 2 hours,10 minutes,hour) game quit's to operating system without any error/warning message.
Tested BOTH with GF2 and Radeon 9250 graphic cards so i sure it's not drivers problem.Memory has been tested with memtest86(linux) for 4 hours without errors...
And the most importand fact is where is NO this problem whith non-steam v17/v18.
It's maybe protocol interaction problem(buffer overflow or another mem leak) cause after each quit to OS Steam*.mdmp process memory dump file appears in CS installation dir.I not diagnosed dump files cause i not acquainted with structure of Steam protocol.

Tested on Win2kSP2/Win2k3 SP1 With 2 different Video Cards and multiple driver versions/different heapsize parameter values/Different bot_quotas(8-20) and different RAM size(256/320/512) and Swap sizes.
Heap parameters in registry set to automatic allocation by OS.

I'll hope you can check this problem out and hopefully fix that.
This BUG exists only when bots loaded.
When i'm alone or playing on net/inet where's no problems.

Re: Non-Steam v19+ closes and quites into OS.
 

Sorry - at this forum non-steam is not supported. It's warez - banned by Valve as the cracked version of their game (they lose money because of this the people use cracked version). We can't help You. Buy a legal steam version of CS and then we can talk again about the problem (if it will appear with legal CS, too).

Re: Non-Steam v19+ closes and quites into OS.
 

this doesn't seem to be related to the "non-steam CS 1.6".

I'll check it out and see if it's a bot problem.

btw - Valve does not "lose" money, they just make less money. Also there are also many people who already have a valid license of original CS, but they just don't like the DRM facility like Steam (which is just annoying).

Re: Non-Steam v19+ closes and quites into OS.
 

[KWo]
"It's warez - banned by Valve as the cracked version of their game (they lose money because of this the people use cracked version)"
You right in some points...But cracked stuff not always malfunctioning...
For now non-steam is 95% compatible with latest Steam updates and you know why?Because Non-Steam is derived from steam.You think all Steam CS is legal?
Where is no such a problem to get steam-cs from da net and regging your own steam account...
I think Valve will not ban you for helping IDF soldier who has salary which not enough for buying 2 WinRAR copies...I need to eat something too ;)
[Whistler]
"I'll check it out and see if it's a bot problem."
Thank you
"but they just don't like the DRM facility like Steam (which is just annoying)."
Right

I think what may-be this is derived from original Count-Floyds Podbot 2.6 source cause some people on the net have this problem on Podbot 2.5.
Anyway forgot to write something in the original post...
I have a some(maybe untested by you operating system):Windows server 2003 Ent SP1 but i don't think this should be a problem.Anywhay it's something with a bot's for sure.
Even if you will be unable to find the source of this problem
i will continue to use your bots anyway cause they are the best bots from all ;)

Re: Non-Steam v19+ closes and quites into OS.
 

well, sorry but please don't mention the "non-steam CS 1.6" anyway, as if Valve guys see there are too many things about warez on this forum we will just get into trouble (although I _personally_ don't think disobeying the developers is "theft", bad, wrong or anything)... so please don't do it, okay? After all it's still a violation of our forum rules and I think you won't get too much help

Re: Non-Steam v19+ closes and quites into OS.
 

[Whistler]
No problem. ;)
Thank's anyway for such a good bot.

Re: Non-Steam v19+ closes and quites into OS.
 

Mhh...
It's not YAPB problem.
It's problem of ALL podbot based midifications(yapb,mm,...).
JoeBot works fine.
[Whistler]
Can you check up engine interoperation code?