8 réponses à ce sujet

[SteelStallion]

 
Alright, so I've been trying to implement this mod

http://nwvault.ign.c...es.Detail&id=53

With varying degrees of success. What I did was add the necessary paths for the placeables/doortypes.2da included there and merged it with my own, I know I did this part just fine because the appearances are there in the drop down list in a blueprint's properties. What irks me is the actual mdb/dds files. Now, if you follow the link you'll learn this is an older mod that uses overrides to add the new content in. I don't want to use overrides for the placeables, so I just put all of the mdb/dds files into a new custom .hak file, put that in my hak folder and included it in my module. But it doesn't work, the placeables are invisible in the toolset window.

Now here's the odd part; when placing the same exact mdb/dds files into my override folder instead, it works perfectly. I don't understand what I did wrong; they're the same files, the hak file is in my hak folder, and I've included the hak file that's in my hak folder into the module through module properties.

Why does it only work when I place the mdb/dds files into the override folder? Shouldn't this achieve the same exact thing? 

[Vekin101]

I had problems with it myself. 
I know it sounds strange but when using the hak version with your toolset have you checked that the blueprints have the correct appearence?  Only other thing I can think of is your using other custom haks that have the same names and the mdb/dds files?

[SteelStallion]

Nope, pretty sure I'm not. I've double checked everything.

Ultimately it's not a big deal because it works in game without the override files, meaning it won't affect players at all and will only affect builders of the module. It just means we have to include some override files.

Not a HUGE issue, I'm just still learning the toolset and trying to understand why something like this is occurring.

[Morbane]

does the name of your hak have any spaces - fill them with _ if there are

[Alupinu]

When you installed the files in your hack did you remember to delete the original RAR file? If I remember correctly that might had something to do with it. Because I have the same content in my hak and it works fine.

The second possibility is that it’s all part of a grand conspiracy to ******-u-off. But that’s highly unlikely and hard to prove.

[SteelStallion]

Nope, no spaces in my haks. And I don't think there really was an original RAR file. The mod in the link is old and uses the override method (irony) so it's just a RAR of mdb/dds files, I merged the 2das with my own and created a hak for it.

Again, i've moved past this issue. It's just a curiosity at this point, but I'm just curious as to why this issue happened but all the other custom content seems to work just fine.

[Morbane]

[wonderful duplicate post]

Modifié par Morbane, 15 août 2012 - 09:40 .

[Morbane]

You're doing something wrong.

I installed the set just now and it is all there - except for the doortypes.2da the hak version is short a column - just copy each column by hand (its only one row) and make the last column be a 1

Some of the placeables are really big and situated very high - also remember to click on the blueprint every time you change the appearance or you'll never see your new models.

[johnbgardner]

I've had the same problem. I am pretty sure it has something to do with the placeables.2da file processing. I can't swear to this, but I think a blueprint is stored with the LINE NUMBER of the placeables.2da, not the "LABEL" which is what is in the dropdown list. Therefore, unless the line numbers of your placeable.2da and the author's placeable.2da are identical, the blueprints will show up without an assigned appearance. I know it may be a pain, but what I do is place the .mdb, .utp, and .dds files in the override directory, fire up the toolset, assign the correct appearances, then save the blueprint as a global blueprint, overwriting the one in the override. Then, I add the files to a zip file in the <installation>/data directory and delete them from the override directory. This, in effect, makes the model available to all game sessiions.