[disawar1]

Code works fine few time ago but now I got a rubbish. I just can't imagine what is wrong here. I suspect that problem is encoding. Anyway my attempts to convert to another encoding not given result. I want to understand how to fix it, anyone can give an explanation?

PHP Code:

#include <sourcemod>

static const String:g_sMannequinModel[][][] =
{
    { "hello", "world" }, // WHEN I COMMENT THIS LINE CODE WORKS FINE WTF?
    { "models/survivors/survivor_namvet.mdl", "bill" },
    { "models/survivors/survivor_teenangst.mdl", "zoey" },
    { "models/survivors/survivor_biker.mdl", "francis" }
};


public OnPluginStart()
{
    new size = sizeof(g_sMannequinModel);

    for (new i; i < size ; i++)
        PrintToChatAll("[%s %s]", g_sMannequinModel[i][0], g_sMannequinModel[i][1]);
} 


OUTPUT:

[hello world]
[models/survivors/survivor_namvet.mdl urvivors/survivor_namvet.mdl]
[/survivor_namvet.mdl r_namvet.mdl]
[.mdl bill]

[Powerlord]

A few questions:

• Does this still happen if you specify the dimensions of the array manually, such as static const String:g_sMannequinModel[4][2][64]
• Did you recently switch the SourceMod version being used to compile the plugin, such as changing from 1.6.2 to 1.7.0?

[disawar1]

Thanks!
1. I manually set the array size and it solved the problem, such as static const String:g_sMannequinModel[][][56]
2. Nope

I thought that the compiler specify the array size automatically, it not absolutely so, right?

[Powerlord]

Originally Posted by disawar1 Thanks! 1. I manually set the array size and it solved the problem, such as static const String:g_sMannequinModel[][][56] 2. Nope I thought that the compiler specify the array size automatically, it not absolutely so, right?

It's supposed to infer the size when you specify it during creation, but it sounds like it isn't for some reason.

Might be a bug in SourceMod, I'd have to wait for psychonic or asherkin to comment on this to know for sure.

[Mitchell]

simple side solution until they reply is to have two variables that has one containing file path, and the other containing the name.

[asherkin]

Originally Posted by Powerlord It's supposed to infer the size when you specify it during creation, but it sounds like it isn't for some reason.

The problem here is differing sizes at the innermost dimension (which is invalid, for obvious reasons). Manually specifying it removes the ambiguity, and lets the compiler correctly infer the others.