I'm getting this error when testing in coop. Single player works fine. The map goes to load and seems to load immediately, then:



I am told I spawned too many strings in gsc, but removed most scripts and it still does it, plus don't quite understand what that means.

I been 5 years with the mod tools and never i see this error, something new everyday with this

Check your _zombiemode to see if youre still calling:

	maps\_zombiemode_timer::init();

allong the init functions? I had this error pop up out of nowhere on Oil Rig i think, the 'zombiestopwatchneedle' is a shader used in that .gsc that's how i tracked it down i think..
Been a while though. Try commenting that script out, and see if that helps. Think that magicly fixed it for me back then..

Check your _zombiemode to see if youre still calling:

	maps\_zombiemode_timer::init();

allong the init functions? I had this error pop up out of nowhere on Oil Rig i think, the 'zombiestopwatchneedle' is a shader used in that .gsc that's how i tracked it down i think..
Been a while though. Try commenting that script out, and see if that helps. Think that magicly fixed it for me back then..

Yeh it does, JBird had the same thing and I told him to comment that call and it fixed it for him too.

Super duper awesome! Thanks!.

Anyone know if I will get this error again, or one related to it? And what I should avoid to not have that happen?

edit: and if I needed that script, lol. don't think i did.

Personally i'm not sure what the actual cause is tbh. It seemed to pop up out of nowhere on Oi Rig, and never came back after removing the script.

EDIT: from the looks of the script it's the stopwatch hud being used in der-riese i think, so you can prob miss it

Hmm, thanks. Seems it did that to me also, out of nowhere. All I can think that I have done since the last successful coop test was add some shaders, pecached from zombiemode, and updated scripts and adding scripts, and a lot of mapping. Updates were just making some thread on spawned things to fix players death issues, and I took the ones out I added, but that didn't work. I can't image it was the additional shaders, I've added more than this before I think...

But commenting that out did fix the issue with two players at least, lol. Hope I do not see it again. 

Thanks.

G_FindConfigstringIndex has a limit that's defined by the parameter it's passed from.

configStringIndex = G_FindConfigstringIndex(string, 515, 1023, 1, origErrorMsg);

      if ( i == max )
      {
        Com_Printf(15, "G_FindConfigstringIndex: overflow...\n");

Edit:
Areas used (in bo1 at least)

I got this error again, but it was a different place this time. It pointed me to a specific shader I was using. I ended up have to reduce the amount of shaders I was precaching by one and then it worked. I decreased it by 10 to be sure, I found extra, but it only gave me the error in coop, so it could have been one per player... not sure, didn't test anymore than that.

I got this error again, but it was a different place this time. It pointed me to a specific shader I was using. I ended up have to reduce the amount of shaders I was precaching by one and then it worked. I decreased it by 10 to be sure, I found extra, but it only gave me the error in coop, so it could have been one per player... not sure, didn't test anymore than that.

It's more related to hud elements than anything else. Like you have a setText on a loop.

It's more related to hud elements than anything else. Like you have a setText on a loop.

Really? I do use an old version of my hud hint string script in this map where it does do that. Perhaps I should update it and see if I still have that issue. I've modified that script do only set it once now while close to/touching the trigger in my latest version of it.

It only happens on load though. Not while in game. But I had another issue with that and trems bank combined before, so it prob would be a good idea for me to update it in this map then. Thanks.

Really? I do use an old version of my hud hint string script in this map where it does do that. Perhaps I should update it and see if I still have that issue. I've modified that script do only set it once now while close to/touching the trigger in my latest version of it.

It only happens on load though. Not while in game. But I had another issue with that and trems bank combined before, so it prob would be a good idea for me to update it in this map then. Thanks.

And by loop I mean like 0.05 and have 4-6 other elements running with the same thing.

And by loop I mean like 0.05 and have 4-6 other elements running with the same thing.

Cool, thanks. I'll play it safe and isolate any instance like that.