"Array Index is out of Range"

[VR_Dev]

What can you guys tell me about this. It gets thrown a whole bunch of times for my Iron Man. Google search shows one other topic about this that apparently I don't have permissions to view.

It doesn't break anything or seem to slow gameplay down.

Any info is helpful.

cb

[stupid_chris]

that's pretty vague.

[VR_Dev]

that's pretty vague.

Yeah sorry I know. I just don't even know where to look. It's obviously because of one of my custom parts.

Is it something in a .cfg, or have something to do with one of models? When I get home I'll post the debug.

I was just curious if someone could point me in the right direction.

[nli2work]

try the output_log.txt

usually it'll say what is throwing the error. Won't tell you which part, but can tell you which plugin and from there you can narrow it down to parts associated with the plugin

[VR_Dev]

try the output_log.txt

usually it'll say what is throwing the error. Won't tell you which part, but can tell you which plugin and from there you can narrow it down to parts associated with the plugin

Now this is super lame, but it proves how much I don't know about debugging. But where do I find output_log.text? Quick search says its in KSP_data. But I can't find that anywhere in my KSP folder

Edit: I assume KSP.log is the same thing

Edited September 15, 2014 by clown_baby

[raidernick]

I have gotten this error before. It is always related to the part animation and happens when you either have the animation named incorrectly in the CFG, have an animation module added to a part cfg that doesn't have one or or have the animation frames in unity set beyond what they were in autocad/blender

[VR_Dev]

I have gotten this error before. It is always related to the part animation and happens when you either have the animation named incorrectly in the CFG, have an animation module added to a part cfg that doesn't have one or or have the animation frames in unity set beyond what they were in autocad/blender

This is incredibly helpful. Thanks a lot.

[NathanKell]

The READ FIRST sticky in modded support has all sorts of useful info, like how to get your log.

That error is going to be because, let's say there's an array of 10 items (int[] arr = new int[10] or whatever) and the program tries to access, say, arr[12].

[VR_Dev]

The READ FIRST sticky in modded support has all sorts of useful info, like how to get your log.

That error is going to be because, let's say there's an array of 10 items (int[] arr = new int[10] or whatever) and the program tries to access, say, arr[12].

Whoops sorry. I should have read that first. I assume if google couldn't find it it hadn't been discussed.

And that explanation is a little over my head. But it doesn't seem to be a problem. I'll drop it