XiNAVRO

Site interface and images uploaded under files seem fine; the Media - Image section is lagging. New Vegas Nexus for example: https://www.nexusmods.com/newvegas/images/ Images on the first page are mostly fine. Second page and beyond start to struggle, and going further back (10-20 pages) really becomes spotty.

I'm at my wit's end. Been trying to solve this issue for the past few days now. http://i.imgur.com/6i0sfwz.jpg As shown in the picture above, the wrist on the glove mesh is being enlarged -- problem is, the mesh itself has the same size. I did have to divide the mesh at that point, but only because the glove NIF file doesn't have anything beyond the Forearm bones. http://i.imgur.com/5RoKSJu.jpg Already checked the bone node sizes to make sure that this wasn't the NIF file acting up. Bone scales are all set to 1.0000 AFAIK. I don't get it. What could be the issue here?

That was indeed the case - as stated in the wiki linked in the OP, it was showing up as invisible due to unused VGroups. To be more precise, I had a suspicion that it might be the vertices where the bone weight was less than 0.020; weight squashing and normalizing solved this issue. After taking a look at every VGroup and removing anything that seemed insignificant enough, the armor is now showing up in-game properly. Either figment's 3DS import / export plugin is making an issue handling the file, or Blender NIF plugin is unable to handle such fine print (as the original was working fine, must be the process of import/export). Made it myself. Used the mesh mod Asian Face Enhanced with a slightly modified variant of my custom Skyrim face texture.

Screenshot attached to show the issue. http://i.imgur.com/weH9Fuz.jpg So I started fiddling with Blender last week. As I have stumbled upon a new method that uses 3DSMax and Blender 2.49 on the Nexus wiki, I decided to give it a shot. Rather than creating a new file from scratch and wondering where I went wrong, the approach I took was to modify an existing item first and see how it works in the game. The candidate I chose is DixiePig's Slooty Vault Suit, as I wasn't too happy with the proportions but did not like how Bodyslide skewed the clothing part either. Most of the process went fine, and while I was testing the file I was able to see it in the game performing as I intended; problem is, only a specific part of the clothing was showing up. The vault suit part was showing, but nothing else - no skin, no belt, no boots. I did not touch anything in the ESP file, and copied all the material properties from the original file to minimize any chance of making a mistake. I have went through Blender to make sure no orphaned VGroups were remaining, and made sure all vertices had been weight painted as well (not that I would assume this is the culprit, as all I did was change the proportions of the original mesh keeping its weights intact). Not sure what I am doing wrong. The file in question is here: http://www.mediafire.com/?voficp0d25gql5r

Read the Bethsoft blog, and glad that this whole fiasco is over. That being said... The blog may have pointed out a few interesting points, but ultimately made me scratch my head even more. If what they state is true, then this system was being "under development" since as early as 2012, with possible legal issues needing up to three years to have been solved out by Valve. While they very much could have tried to establish an understanding and find a working solution with the modding community, they decided to pull a few select modders, made them sign an NDA to know about an "exciting new change" and rolled it out as a surprise for most. Then Gabe Newell had to visit Reddit and conduct a quasi-AMA for damage control, all the while stating as if he did not know what had been planned under the hood and how the community reacted. (Also interesting to note that Robin, you were there asking him questions and Gabe left most of his answers as vague as possible - while he was able to state exactly what drink he got from Starbucks. Quite frankly, I found that a bit insulting). Also the blog states that they had been with the modding community since 2002, and also that opening up a market is full of problems. So they knew exactly what sort of issues modders would point out in the course of THREE DAYS. Copyright infringement, no protection in case of mod theft. unable to share a common denominator plugin and/or script, etc. Yet they still thought this was a good idea, and proceeded nonetheless. "While others in the industry went away from it, we pushed more toward it." That may have been true for over a past decade, but somehow every decision they made with this incident points the other way. At least they decided to listen to the community and shut the program down without further ado, that is respectable from both companies.