[MoJoPz]

Fixed

[Weasel]

I hadn't checked on my CS:S server in a few weeks. Today I tried to join and it crashed my client to the desktop shortly after joining my server.

If I move the sm_skinchooser plugin into the "disabled" folder and restart, the server runs fine (sans the custom models of course). I tried updating to these MM:S and SM builds:

• Metamod:Source to the "stable-branch" snap-shot (ver 1.10.6, git 940).
• SourceMod to the "stable-branch" snap-shot (ver 1.7.3, git 5210).

I also tried re-compiling the plug-in after upgrading SM. However, problem persists (as per log quoted below):

L 06/05/2015 - 17:46:50: SourceMod error session started
L 06/05/2015 - 17:46:50: Info (map "fy_kittybuzzy") (file "errors_20150605.log")
L 06/05/2015 - 17:46:50: [SM] Plugin encountered error 15: Array index is out of bounds
L 06/05/2015 - 17:46:50: [SM] Displaying call stack trace for plugin "sm_skinchooser.smx":
L 06/05/2015 - 17:46:50: [SM]   [0]  Line 1006, sm_skinchooser.sp::LoadModels()
L 06/05/2015 - 17:46:50: [SM]   [1]  Line 235, sm_skinchooser.sp::OnMapStart()
L 06/05/2015 - 17:47:21: [SM] Native "KvGotoFirstSubKey" reported: Invalid key value handle 0 (error 4)
L 06/05/2015 - 17:47:21: [SM] Displaying call stack trace for plugin "sm_skinchooser.smx":
L 06/05/2015 - 17:47:21: [SM]   [0]  Line 305, sm_skinchooser.sp::BuildMainMenu()
L 06/05/2015 - 17:47:21: [SM]   [1]  Line 819, sm_skinchooser.sp::Command_Model()
L 06/05/2015 - 17:47:21: [SM]   [2]  Line 764, sm_skinchooser.sp::Timer_Menu()
L 06/05/2015 - 17:48:16: Error log file session closed.

I haven't changed the models in a very long time (1 year)? or done much in the way of any configuration changes since probably the beginning of this calendar year. So, not sure what is up. Going to double-check that the configuration files have been "dos2unix'd" (since this is on Debian 8 Linux) - just to be sure. But, can't think of anything that would mess this up.

meta version
Metamod:Source version 1.10.6-dev
Built from: https://github.com/alliedmodders/metamod-source/commit/e14b479
Build ID: 940:e14b479
Loaded As: Valve Server Plugin
Compiled on: May 10 2015
Plugin interface version: 15:14
SourceHook version: 5:5
http://www.metamodsource.net/
meta list
Listing 5 plugins:
  [01] SourceMod (1.7.3-dev+5210) by AlliedModders LLC
  [02] CS Tools (1.7.3-dev+5210) by AlliedModders LLC
  [03] SDK Tools (1.7.3-dev+5210) by AlliedModders LLC
  [04] SDK Hooks (1.7.3-dev+5210) by AlliedModders LLC
  [05] SteamTools (0.8.3) by Asher Baker (asherkin)
sm version
 SourceMod Version Information:
    SourceMod Version: 1.7.3-dev+5210
    SourcePawn Engine: SourcePawn 1.7, jit-x86 (build 1.7.3-dev+5210)
    SourcePawn API: v1 = 4, v2 = 6
    Compiled on: Jun  2 2015 15:02:47
    Built from: https://github.com/alliedmodders/sourcemod/commit/a8d7242
    Build ID: 5210:a8d7242
    http://www.sourcemod.net/
sm plugins info sm_skinchooser
  Filename: sm_skinchooser.smx
  Title: SM SKINCHOOSER (Skin Menu)
  Author: Andi67
  Version: 2.7
  URL: http://www.andi67-blog.de.vu
  Status: running
  Reloads: Map Change if Updated
  Timestamp: 06/05/2015 17:45:45
  Hash: fa485d6d0377deeacc8d1d41a0c2bbf7

[freak.exe_uLow]

Originally Posted by andi67 http://www.sourcemod.net/newstats.ph...0&addon_id=692 Seems like you don't know what you're talking about , I use it every day to check if models I made work ingame. So first check if you use the latest STABLE versions of SM and MM , than check your modelfiles and your ini-files.....

Dont forget, i use this Script for Counter Strike Global Offensive not Counter Strike Source

i have no idea why this not work....i think i have no errors in the Script....:/ Can i send you private my folder (sm_skinchooser and models) ? its that okay?

[Weasel]

i have no idea why this not work....i think i have no errors in the Script....:/ Can i send you private my folder (sm_skinchooser and models) ? its that okay?

I thought the only games supported by this plug-in were Counter-Strike:Source and Day-of-Defeat:Source? Then again, I gave-up on CS:GO some time ago - so maybe I am mistaken.

[andi67]

Quote:
I thought the only games supported by this plug-in were Counter-Strike:Source and Day-of-Defeat:Source? Then again, I gave-up on CS:GO some time ago - so maybe I am mistaken.

Surely it works on CSGO....

[Weasel]

Still haven't been able to figure-out why it stopped working on my CS:S server (related post here).

[andi67]

Maybe you have deleted or changed files or not uploaded all skinchooser files from the package.....

[freak.exe_uLow]

lol the guy Weasel have the same error.

can i send you the files? I dont see the error.....

[Weasel]

Originally Posted by andi67 Maybe you have deleted or changed files or not uploaded all skinchooser files from the package.....

I will try re-installing sm_skinchooser plugin from srcatch (again).

[Weasel]

After re-installing the plug-in from the zip file from the top of this thread (but using my existing configs that match the custom models actually loaded obviously), I get this in the error logs:

L 06/07/2015 - 18:33:24: [SM] Plugin encountered error 15: Array index is out of bounds
L 06/07/2015 - 18:33:24: [SM] Displaying call stack trace for plugin "sm_skinchooser.smx":
L 06/07/2015 - 18:33:24: [SM]   [0]  Line 1006, D:\e\Plugins Sourcemod\sourcemod-1.5 neu -windows\addons\sourcemod\scripting\sm_skinchooser.sp::LoadModels()
L 06/07/2015 - 18:33:24: [SM]   [1]  Line 235, D:\e\Plugins Sourcemod\sourcemod-1.5 neu -windows\addons\sourcemod\scripting\sm_skinchooser.sp::OnMapStart()

I cleared all the custom downloads from my client (i.e. deleted the "download" folder) and tried again. When I connect from my client, it crashes right to the Windows desktop. I do get into the game briefly (a few seconds) before the client crashes. Basically enough to see that the custom models do not actually get displayed (although they did download successfully). But it does not display the generic "Error" model either. It's like all the bots/players are invisible. The server does not crash, just the client.

Going to try ripping all the custom models out except maybe one to test with. Maybe a VTF file is corrupted or something. I can see that causing a client-side crash, but it would not explain the server-side error messages in the logs.