19 réponses à ce sujet

[Jenna WSI]

So... I have a working base mod with PRC, but importing my areas gets me this error. I'm importing one at a time for these larger areas and they're still not wanting to import... help please. -.-

[Failed.Bard]

That's something to do with a placeable set outside the map area, isn't it?
If that's the case, you might have to manually check placeable locations in all the maps in question, then re-export them.

[Zwerkules]

Out of bounds means that the number of tiles in the tileset don't match the number of tiles given in the [TILES] Count=xxx line in the set file.
The numbering of tiles starts with 0, so if the last tile is 199 you actually got 200 tiles. Apart from tile 199 never showing up setting the tile count to 199 instead of 200 wouldn't cause any problems.
What causes problems are tiles that aren't numbered correctly. If you have a tileset with a tile 0, tile 1, and tile 3, and set the count to 4, you'll get the out of bounds error, because even though the last tile has the number 3, there aren't 4 tiles present because tile 2 is missing. Gaps won't be filled in.
What is an even more likely cause for this error is if you made your area with a hak version that has say 110 tiles and now you overwrite the hak with an older version that has only 100 tiles but the same filename. The hak will be loaded, but ten tiles are missing which might be needed to load your area. So you'll get an out of bounds error.

[WebShaman]

Hmmm...PRC does not include tiles.

I think this problem may be being caused by something else.

You may have to remove the haks, import, then put the haks back in to be able to do this.

[Zwerkules]

It doesn't have to be related to tiles. I guess if you had a hak which had 200 placeables and it was overwritten by an older version with only 180 placeables, you might get the same error.
In general the out of bounds error message means that something is referencing a resource with for example the number 200 while there are only 199 resources of that kind. It could be tiles, placeables, creatures, etc.
To have the actual filename of every resource in the area data instead of a number would make the area data a lot bigger, so I guess that everything is referenced by number.

Modifié par Zwerkules, 18 septembre 2011 - 09:08 .

[Jenna WSI]

We're using CEP, custom haks, and PRC though. We took the original module, removed the areas, saved, then added prc for testing... now I'm trying to re-add the areas.

Also I think Zwerk's post is going to make my brain bleed. >.>

Modifié par Jenna WSI, 18 septembre 2011 - 09:05 .

[Birdman076]

Are you using CEP 2.4 by chance? Reason I ask is I updated my Rhun mod from 2.2 to 2.4 and did a butt ton of other updates only to get an index of of bounds on an already existing area that had been in the original module all along. I had added some CEP content to that area when I originally added 2.2. So, I made a copy of the mod as I didn't want to lose my work, I tried going back to CEP 2.2 as I hadn't used any 2.4 content yet. Didn't work, so I tried deleting the area altogether, saving the mod and reimporting the original area which had no CEP content. Didn't work. In the end I lost all the work I had done and had to go back to the 2.2 version which is where I am at now.

[Jenna WSI]

No we never updated from 2.3.. still there.

[Master Jax]

I get the same error in many, many, many module areas. It is related to custom content, and my NWN is a disgusting, over-modified monster. What it is and why it is should not concern us. As I've always said: Don't waste time thinking why something got frakked, where was the error; just fix it.

So, what do you do when the out of bounds message appears? Place the mouse arrow on the Yes button and then press Enter, and hold it till a zillion more similar messages appear in rapid succession. Eventually, they will all be gone, and your area will be available as always. It doesn't cause any other issue. How do I know this? Because I've extensively modified every module I play, that's why, you un-believer!

[Jenna WSI]

Thanks, but mine aren't fixed by doing that.

[Failed.Bard]

Are you using the same top hak as before? If that's been changed, maybe you could try using the previous top hak until the areas are added in again.

[WebShaman]

You need to remove the PRC, add in your areas, then re-add the PRC afterwards.

[Jenna WSI]

The toolset has some silly hoops for me, these days. >.<

[Master Jax]

This may sound silly, but, have you actually tried emptying the module of all haks, and then adding each one by one, making tests at each stage? It's a little tedious, but the best way to find out what's causing the issue. Or you could always drive your fist through the monitor and with a wet and swollen face swear never to touch NWN again. Been through both already, so I would know...

[WebShaman]

I have had this problem before, with the PRC. It is a known "issue"...

[Alex Warren]

WebShaman wrote...

I have had this problem before, with the PRC. It is a known "issue"...

I didn't knew something like this may happen ;p

[WebShaman]

Well, I remember having these issues with PWs that I worked on with the PRC included.

One would have to do building, etc without the PRC haks attached, then re-add them afterwards.

It was one reason why we had a basic building mod - without the PRC attached.

There really is no reason to have the PRC attached when building, tbh.

[Calvinthesneak]

True that, but I too didn't know that you had to reattach PRC after. That's gotta be ouch on build time... of course if you build in mod without PRC and just import them into such a mod.....

[Jenna WSI]

Alex Warren's fix seems to have worked.Add dummy haks without the usual prc info in them, Import areas, Add normal prc haks back in... voila. No errors.

[Jenna WSI]

Correction, this is not fixed. Some of LoW's tilesets are still out of bounds when I try to open them, but all others are fine. Example... the underwater tile opens fine but the fantasty interior does not. These are also heavy with placeables and npcs, the areas that won't open now (but would in our other mod).