4 réponses à ce sujet

[Bhaal_MA]

Hi all,

 

First of all, thank you for your excellent work on this new CEP version

 

I noticed the following change in CEP 2.60:

 

parts_*.2da

Changed all AC values to match 2da line & model numbers (except parts_chest.2da).

Padded all 2da files to line 255 (except parts_chest.2da).

 

I can understand the padding but the changes in the "ACBONUS" column have nasty side effect on the CEP crafting system: the function ZEP_PreReadArmorPartList of the file zep_inc_craft now add all the 255 IDs for all the parts, there is no way to detect if an ID has a valid model or not.

 

So now, when you try to modify your armour in the game, you have to cycle through the 255 IDs even the one that are not valid :/  

 

Any idea on how to fix this? (without having to manually write the array of valid ID for each armour part...)  

 

Regards 

[meaglyn]

Fwiw, I had the same issues when it first came out.  AD was not willing to reconsider and I have since come around. It is very nice to have the toolset value match the model part.  But coming around to accepting it did require adding a column to all the parts 2das.  I ended making a Model_Src column which holds a non-zero int if the model is valid and **** otherwise so it's easy to scan by eye as well. The ints are 1 == bioware, 2 = cep, 3  = q  sort of thing. Then I changed my crafting/tailoring code to check the Model_Src column.  The same could be done for zep_inc_craft, especially now that it's in an erf and not one of the haks

[Bhaal_MA]

Thank you for reply. I tried a search on this forum but I didn't find anything. 

 

Finally I solved the problem editing the 2das and erasing the ACBONUS of invalid models.  In my case I don't care of the matching of the toolset value and the model parts.

 

And again, thanks to all the people involved in the CEP project.

 

Regards

[The Amethyst Dragon]

I'll do some editing of 2das and scripts (see meaglyn's solution, above) for the next update.

[The Amethyst Dragon]

I've reworked the 2da files for 2.61 to add a column called "HASMODEL". If no model, it's got ****, if there is a model there, it's value is 1. Yup, taken from meaglyn's post in another thread.

 

I've modified a function in two Mil Tailoring Models scripts to account for this (and will put them on the "mil systems" page on the Vault when I do the next CEP update). Now I have to find the script(s) that CEP itself uses and update those as well (in the _sb hak and erf).

 

This update will be out soon. I just want to finish up a few more large shield model overhauls.

 

Edit: Ah, looks like Bhaal_MA already mentioned the script name and function I need to look for. Thanks!