"List index out of bounds" error

[Legacy_Grani]

               I've tried importing a prefab area to my module (this one: nwvault.ign.com/View.php?view=Prefabs.Detail&id=48705&id=1232) but when I try to open the imported area in my module, I get the "List index out of bounds" error and the loading bar freezes somewhere on the beginning.

I tried opening the demo module of this prefab in the toolset and it opens without problems. It is a CEP module, but so is mine, so I dunno why I can't open that imported area in my module.

What is this error? And how can I repair it?

Thanks. '>

PS: I do, however, have an additional hakpak placed over the CEP's top hak. It consists of merged 2da from 1.70 community patch and two additional tilesets. I don't know if it could be the source of the problem, but maybe it is.
               
               

               

                     Modifié par Grani, 14 juin 2013 - 07:34 .
                     
                  

            

[Legacy_Fester Pot]

               Usually is content within the module still in a specific area you're trying to load, that is no longer available - such as removal of a HAK from the module list but not the removal of the content in the module (placeables, area additions, etc.).

Any .2da files in this hakpak over CEP's, that conflict and have not been properly merged, will cause problems. Placeables may go missing, doors, creatures, etc.

A placeables.2da in your most top hak, would be used instead of CEP's placeables.2da if you have not taken the time to merge them together.

Thus, errors occur.

FP!
               
               

               
            

[Legacy_Grani]

               Hmm, alright, guess I will have to check the hak once again. Thanks.
               
               

               
            

[Legacy_Grani]

               Well, I removed this hak I was talking about (it was above the CEP haks in the list) and instead, I've placed some other haks under the CEP ones. So, CEP has top priority now, but the error still occurs.

I'm pretty confused.

Edit: I think I might have found the problem, but it doesn't mean I know how to solve it.

Even though supposedly both my module and the demo module of this prefab area use CEP 2.4, there is a difference between haks (and their order) used in our modules.

CEP haks in my module go as follows:

cep2_top_v24
cep2_add_phenos5
cep2_add_phenos4
cep2_add_phenos3
cep2_add_phenos2
cep2_add_phenos1
cep2_add_sb_v1
cep2_add_doors
cep2_add_tiles1
cep2_add_tiles2
cep2_core7
cep2_core6
cep2_core5
cep2_core4
cep2_core3
cep2_core2
cep2_core1
cep2_core0
cep2_crp
cep2_crp_s


The CEP haks from the demo module, on the other hand, are:

cep2_top_v24
cep2_add_phenos5
cep2_add_phenos4
cep2_add_phenos3
cep2_add_phenos2
cep2_add_phenos1
cep2_add_tiles2
cep2_add_tiles1
cep2_ext_tiles
cep2_add_doors
cep2_core7
cep2_core6
cep2_core5
cep2_core4
cep2_core3
cep2_core2
cep2_core1
cep2_core0
cep2_crp
cep2_add_sb_v1
cep2_crp_s


In both cases "cep23_v1" tlk file is used.

Well, I'm sure that's the source of the problem, but I still don't know if there's anything I could do to import this area. I'd rather not mess with my CEP haks (I've based my module on CEP 2.4 starter module, so I trust it) but I know it might be impossible to lay my hands on this prefab otherwise. '>
               
               

               

                     Modifié par Grani, 17 juin 2013 - 12:05 .
                     
                  

            

[Legacy_meaglyn]

               Maybe the area in question uses tiles that only show up in cep2_ext_tiles? It should not hurt your existing module to add that one.
               
               

               
            

[Legacy_Grani]

               It finally worked! '> Thank you!