Author Topic: ERROR: SV_SetConfigValueForKey: overflow  (Read 2001 times)

Offline -RDX-Leftless1

  • Rank: Private
  • *
  • Posts: 83
ERROR: SV_SetConfigValueForKey: overflow
« on: February 06, 2009, 01:50:34 pm »
I'm getting this error when starting the server with a mod running, tried the x5 lite and the open warfare mods and got the error with both. Any ideas Joker ??

Offline Joker{eXtreme}

  • Rank: Private
  • *
  • Posts: 6108
    • http://www.mycallofduty.com
Re: ERROR: SV_SetConfigValueForKey: overflow
« Reply #1 on: February 06, 2009, 01:55:26 pm »
Not at home so can't really help on this one yet.

I have recieved numerous reports that fs_game folders and usermaps folder are not working or causing problems or crashes.

Will know more once I get home and can work on it, then will post results and tut if it works

Offline -RDX-Leftless1

  • Rank: Private
  • *
  • Posts: 83
Re: ERROR: SV_SetConfigValueForKey: overflow
« Reply #2 on: February 06, 2009, 01:58:01 pm »
Thanks Joker, will check back later. :D

Offline OLDPHARTSHaiPing

  • Rank: Private
  • *
  • Posts: 47
Re: ERROR: SV_SetConfigValueForKey: overflow
« Reply #3 on: February 06, 2009, 05:08:04 pm »
Had same problem and I changed the command line back to gameservers recommended config.  Server now works but i can't change the hostname.  maybe patch 1.3 will just send us all a gun to shoot ourselves with.

Offline Joker{eXtreme}

  • Rank: Private
  • *
  • Posts: 6108
    • http://www.mycallofduty.com
Re: ERROR: SV_SetConfigValueForKey: overflow
« Reply #4 on: February 06, 2009, 05:09:25 pm »
The use of mods and maps are BROKEN right now, can't run anything but a stock server

Treyarch is aware

Offline Marc

  • Rank: Private
  • *
  • Posts: 59
    • http://www.wildcardonline.nl
Re: ERROR: SV_SetConfigValueForKey: overflow
« Reply #5 on: February 06, 2009, 06:00:24 pm »
Quote from: "{PST}*Joker";p="24682"
The use of mods and maps are BROKEN right now, can't run anything but a stock server

Treyarch is aware

not entirely true, smaller mods run fine but the bigger ones like ours wont (how fubar is that....specially when on 1.1 they ran without breaking a sweat)

treyarch is aware..also true....so now lets wait another 3 months for them to get this fixed

Offline flash313

  • Rank: Private
  • *
  • Posts: 33
Re: ERROR: SV_SetConfigValueForKey: overflow
« Reply #6 on: February 06, 2009, 06:03:23 pm »
I JUST FOUND THIS POST ON CODHQ

We have just released a new mod.ff containing the necessary fixes for the mod to run under 1.2.

I posted a detailed message about what we did at CustomCOD.com:
http://customcod.com/community/index.php?topic=1067.0

t3chn0r,
OpenWarfare Project
http://openwarfaremod.com/

Offline -RDX-Leftless1

  • Rank: Private
  • *
  • Posts: 83
Re: ERROR: SV_SetConfigValueForKey: overflow
« Reply #7 on: February 06, 2009, 06:57:36 pm »
Quote from: "flash313";p="24694"
I JUST FOUND THIS POST ON CODHQ

We have just released a new mod.ff containing the necessary fixes for the mod to run under 1.2.

I posted a detailed message about what we did at CustomCOD.com:
http://customcod.com/community/index.php?topic=1067.0

t3chn0r,
OpenWarfare Project
http://openwarfaremod.com/

I just tried the fix for the open warfare mod and still got the same error.?

Offline PvtWhoOkid

  • Rank: Private
  • *
  • Posts: 425
    • http://www.tya-clan.com
Re: ERROR: SV_SetConfigValueForKey: overflow
« Reply #8 on: February 06, 2009, 07:13:14 pm »
I don't know about you guys but this pissed me off!  I will not use any other mod unless its ace5 or x5.  So then this would make this patch pointless!  Its always nice to see them fix one thing and break the other.

I/We can only hope a work around is found for this buggy problem, if not then like marc said time to wait another 3 months!!

Offline Joker{eXtreme}

  • Rank: Private
  • *
  • Posts: 6108
    • http://www.mycallofduty.com
Re: ERROR: SV_SetConfigValueForKey: overflow
« Reply #9 on: February 06, 2009, 07:14:55 pm »
Had to remove some features from X5 Lite to apply this fix to get X5 to work :(

So some recoding is in order for us here

Offline flash313

  • Rank: Private
  • *
  • Posts: 33
Re: ERROR: SV_SetConfigValueForKey: overflow
« Reply #10 on: February 06, 2009, 07:19:18 pm »
I agree the ace5 or x5 i was just trying to help.the ow mod did run on my pc with the fix.

Offline PvtWhoOkid

  • Rank: Private
  • *
  • Posts: 425
    • http://www.tya-clan.com
Re: ERROR: SV_SetConfigValueForKey: overflow
« Reply #11 on: February 06, 2009, 07:19:29 pm »
Quote from: "{PST}*Joker";p="24701"
Had to remove some features from X5 Lite to apply this fix to get X5 to work :(

So some recoding is in order for us here


You heard him guys, bring on the beer.

Offline Joker{eXtreme}

  • Rank: Private
  • *
  • Posts: 6108
    • http://www.mycallofduty.com
Re: ERROR: SV_SetConfigValueForKey: overflow
« Reply #12 on: February 06, 2009, 07:21:50 pm »
2 files where I had to remove things from which result in no custom hardpoints anymore, and the minimap controlled settings don't work anymore either.

Offline PvtWhoOkid

  • Rank: Private
  • *
  • Posts: 425
    • http://www.tya-clan.com
Re: ERROR: SV_SetConfigValueForKey: overflow
« Reply #13 on: February 06, 2009, 07:41:47 pm »
Hardpoints was a given, might need recoding. Mini map could be related to the same thing??

Offline -RDX-Leftless1

  • Rank: Private
  • *
  • Posts: 83
Re: ERROR: SV_SetConfigValueForKey: overflow
« Reply #14 on: February 07, 2009, 08:53:36 am »
I found this post by JD at callofduty.com concerning this problem.


Hi all,

It is clear that some of you are experiencing problems with the 1.2 patch. First, we apologize for any additional inconvenience this has caused. After some time reviewing the feedback, it is clear there are two main issues.

Audio Problems:
A select number of Vista users are reporting that all sound in the game is no longer audible after patching to 1.2. We will be including a permanent solution in our 1.3 patch. In the mean time, a work-around fix has been discovered, and instructions are located at this post: http://www.callofduty.com/board/viewtopic.php?f=29&t=101457

Mod Problems:
While HTTP Redirect is fixed (so you can download custom maps + mods from the web, in-game) it appears some mods may no longer be functional after patching to 1.2. At first glance this would appear to be a new bug, but after some digging we determined this problem is actually with the mods themselves, and here is why:

In the process of addressing issues for Patch 1.2, we had to add new DVARs to the game for development purposes. Modders, you know what we mean when we say DVARs. =) There is a hard limit to the number of server DVAR’s that can be used, for network latency (lag) reasons. So when you run a mod, the game DVAR’s load first, then the mod DVAR’s come second. If the additional mod DVARs exceed that hard limit, it will not load. That was the problem in a nutshell with today’s 1.2 compatibility. Since we added additional DVAR’s, the mods spilled over that max limit.

The solution for modders – use server DVAR’s sparingly. When possible, set client DVAR’s. There is no guarantee we won’t add more DVAR’s in the future as these are a core component to our development process, so you want to prune down your DVAR’s as much as possible to avoid future compatibility hassles. We support and maintain our mod tools – however, we are not able to maintain compatibility with mods, nor is this our responsibility. By definition, a mod is user-generated content and must conform to the technical limits of the game.

We have already begun work on a 1.3 patch which is slated to release this month as well. Along with /record, we will include a more permanent fix for the audio issues.

More update will follow.

Regards,
-JD