"Porting Fallout3 objects

[NotErich]

Considering how asset-intensive the GECK is, I figured the more there is access to, the better. I suppose the easiest way to do so would to be to introduce a .esm with just the assets inside of it. Would I be fine in just getting the fallout3 .esm, and deleting all the maps and such. Would this be a valid approach? Also, how would I go about getting all of fallout 3's DLC into that .esm?

 

Any guidance would be appreciated.

Edited August 27, 2011 by NotErich

[avianrave]

This sadly would be using content without the authors permission. If you can get the ok from Bethsenda, then it would be possible. Or if you run your own website and don't mind getting in hot water with them. As far as I know, the nexus does not want to deal with this issue.

 

Now if you want to make such a file for your own personal use, it should be easy. Just extract the meshes and texture bsa into a new folder. Then extract the meshes and textures from all of the DLC bsa, and put it in the same folder as the FO3 assets, with meshes and textures in their respective folders. Then make a FO3Resources.esm, and add all of the meshes from FO3 and create new static objects. Then lastly, you put all the meshes/textures into the bsa archive, and you have only 2 files then.

 

If you just want to make the esm with the resources referenced, then I think that might be alright. Whoever you share the esm to would have to extract the bsa archives from their own FO3 directory.

[PowderdToastMan]

If you own fallout 3 u can get the mod - requiem for the capital wasteland - http://www.newvegasnexus.com/downloads/file.php?id=41480