![]() |
![]() |
|
#1
|
|||
|
|||
|
Anyone seen that one before.
Had the new Bridges_of_Druzhina_B1 running fine. Lots of people in and running it fine. Map changed to Gumrak Station, again everything fine. Then back to Bridges_of_Druzhina_B1 and everyone gets this error. Solution anyone? |
|
#2
|
||||
|
||||
|
Romano had the same thing. Super weird.
Quote:
|
|
#3
|
||||
|
||||
|
It happens with all the Customs.
Any news on this matter? Last edited by Mike_Nomad; 07-31-2012 at 08:41 AM. |
|
#4
|
||||
|
||||
|
It doesn't Mike, i run Kursk followed by Ogledow,and i've never seen it, my files aren't in the cache right enough,so it may have something to do with that.
__________________
|
|
#5
|
||||
|
||||
|
Quote:
It does happen and its totally reproducible. It was happening with every custom and the only way to correct the trub was a Server re-boot. That's my experience when trying to run ONLY Custom maps. The most reliable work around at this time is to alternate between a stock map and a custom map in the rotation. It is a bug intro'ed since the new patch "that's being looked into". |
|
#6
|
|||
|
|||
|
so what do the logs say?
|
|
|
||||
|
||||
|
An option update to address this has gone out for servers.
__________________
![]() Pretty, what do we blow up first? - Myn Donos |
|
#8
|
||||
|
||||
|
Nice to hear there's a fix now.
|
|
#9
|
||||
|
||||
|
For the longest time we did not experience this behavior with customs. But recently, it began to occur with daily regularity. We are seeking a solution. Where can I find information on the option update?
Last edited by G_Sajer; 08-16-2012 at 04:00 PM. |
|
#10
|
||||
|
||||
|
Just UPDATE your server files.... or, have your provider do so.
|
|
#11
|
||||
|
||||
|
Quote:
![]() I did just that. Keeping my fingers crossed. ...no lock-ups in a couple of days. This is a very good sign. Thanks, Tripwire. Last edited by G_Sajer; 08-18-2012 at 01:55 PM. |
![]() |
| Thread Tools | |
| Display Modes | |
|
|