Deleted4363562User Posted August 4, 2016 Posted August 4, 2016 Which is better for performance? I recently have been toying around with making mesh mash ups and was worried about file size. I'm putting clutter on furniture and sometimes just use static objects with the WorkshopStackedITEMKeyword, so that I don't have to utilize more standalone nifs, Once a user deletes a table, for example, all the items stacked on it get deleted.
Ethreon Posted August 4, 2016 Posted August 4, 2016 Single nif of combined meshes. Preferably passed thru any 3D editing software to unify the meshes using same material.
Deleted4363562User Posted August 4, 2016 Author Posted August 4, 2016 On 8/4/2016 at 2:01 PM, Ethreon said: Single nif of combined meshes. Preferably passed thru any 3D editing software to unify the meshes using same material. That was my thinking. NifSkope and Outfit Studio aren't good enough?
Ethreon Posted August 4, 2016 Posted August 4, 2016 Nifskope is ok to mash them together . I think you're better off using CK to make static collections. Not sure, I usually move them all into MAX and do my job there.
Deleted4363562User Posted August 4, 2016 Author Posted August 4, 2016 On 8/4/2016 at 2:33 PM, Ethreon said: Nifskope is ok to mash them together . I think you're better off using CK to make static collections. Not sure, I usually move them all into MAX and do my job there.Thanks, I am mostly concerned about file size for when I release my mod on consoles. If it were just PC, I'd just go with all custom nifs for all the clutter etc. It's just a Home Plate overhaul mod. My first iteration had all individual static objects via the CK, and I never heard about or noticed any related issues. The new version, however, has a basement and almost double the objects. I'll go with the CK statics for now, and wait for feedback later.
Ethreon Posted August 4, 2016 Posted August 4, 2016 Well if you are building spaces then you should just use individual items. Allows for later modifications easier :)
Recommended Posts