Forum:Model Viewer Discussion

Forums: Index > Wiki discussion > Model Viewer Discussion

First off, hey all! I've been "missing" for a few months or so - but mostly I've been doing mad scientist stuff.:p Which brings me to the topic at hand. If you haven't been checking Twitter, or haven't talked to Jspoel, I'd like to point your attention here. If you click on the infobox, and your browser supports WebGL, you should see the progress of my current project. For those of you who can't see it - it's a model viewer, that's no different in concept than what you'd see in the GECK or NifSkope - only, in this case, entirely web based.

But before I progress any further on this project, with the intent on adding it to Nukapedia, I need a course of action. And to get that course of action, I need your opinions and suggestions on the matter. After all, most of you have put in a lot more time and effort into this site, than I have. If anything, I'm just a glorified interior decorator. :p

What follows are a few key points I need input on, so we can all discuss, and come to agreement on them.

Importance/Focus

To put it simply: This is a wiki covering the Fallout universe, which exists almost entirely in the games that have worn its title. The last two of which, and undoubtedly future releases, have been made in true 3D.

So the question is, how much value - how much importance to the readers, would the addition of this feature have? In other words, how would the ability to see the items, objects, and (eventually) clothing/NPCs, as they appear in game, from the comfort of Nukapedia, affect the popularity and traffic on the site?

This should dictate the necessity, accessibility and notice-ability of the feature in question.

Method

Currently this feature works on the test site, by overriding the larger view of the infobox image. The consensus so far, one that I ultimately agree with, is that this isn't very viable. So the question remains, what would be a good method for accessing the viewer window?

One method, would be to have it work off of a gallery thumbnail - this wouldn't require the need to find a place for something; but on the downside - it would be suffering from the same issues the infobox image did. Namely - when a user clicks on a thumbnail, they expect a larger version of that image - and not completely different media. That's why video thumbnails tend to feature a "play" icon on them.

Another, would be to add a button, somewhere on the page, that simply states "View in 3D". While this would require figuring out a place to put it, on the layout, it's purpose is immediately clear, and takes up less layout space in general, than another thumbnail.

But those are just two options - I'm sure there are other possibilities, so if you think of one, please share. Otherwise, please state your preference. Displaying the viewer directly on the page however, is not a valid option. Too much of a performance hit, to force it on anybody who visits the page. Regardless of the method of accessing it, the popup window, is likely the best overall method of viewing it.

Data Storage/Organization

The original plan of this project, was to create not just a model viewer; but one that could be run "natively" within the confines of a Wikia site. The downside is, that there's quite a few limitations on everything from page size, to accessing images that were uploaded to the site.

In order to compensate for these limitations, I was forced to store the actual .nif file, and its textures (in png format), in (base64) text format, on individual pages. The downside of this, is a bunch of pages that look similar to this. Now, obviously this isn't something that would have a point to be seen by the users.

So, in the interest of keeping things organized, and having a bit more control, I'd first suggest a custom Namespace for these things. Something like "Data:" or "ModelData:". That way, (hopefully), these things could be kept out of the public eye, and not hog up the "recent changes" feed.

Beyond that - is naming conventions. Currently on the test site, they're merely stored using names that are "flat paths". For instance, the above nif file, would be located at /Meshes/Weapons/2handrifle/plasmarifle.nif in the game's data, and on the test site, the page name is Meshes-weapons-2handrifle-plasmarifle.nif. So one option would be storing the page like:

/wiki/ModelData:Meshes-weapons-2handrifle-plasmarifle.nif

But, since pages support paths, this should also work:

/wiki/ModelData:Meshes/weapons/2handrifle/plasmarifle.nif

Doing things like this, will reduce bloat a bit, by allowing multiple models to use the same textures, as they do in game. At any rate, some form of consensus is needed - to make sure that sanity and organization prevails.

One final note: since all files involved are "translated" in the same manner, and the result is the actual file data - anybody that has access to the games files, should be able to contribute, using a site similar to this. The general rule of thumb, similar to the result of Bot-Rewrite, will be to wrap "pre" tags around the data itself. This way, regardless of the file size, it will only appear as a single line on the page itself. For the textures, currently only png are supported - so the .dds textures would have to be converted first to that format. Some additional modifications would be needed for normal maps - as the game uses the alpha channel from those files, as a separate texture type.

Comments, Questions, Concerns, and Opinions

All are welcome, and desired below.

I would like to see this on the wiki ASAP. I think it should be in the Gallery, maybe taking up about 1/2 of the standard page width, inside a template box with a link to a page outlining known tech issues and explaining what it is (for those who cant' see what is supposed to be there. Agent c (talk) 15:54, January 12, 2015 (UTC)

This is all very impressive, Digital! I've never seen anything like it on any other wiki, and it could become a major feature of this wiki. People will be very interested, and what you've done with the plasma rifle is one great example! (You've just improved its quality to the extreme by adding a few more .png textures files right?). I'm glad you see our point, that clicking on it in the infobox shouldn't straight away show a 3D model, because people expect just the larger 2D-model. But the idea of a small 3D thumbnail gave me an idea. The gallery is a good option and it may be the way to go, but I was thinking of an alternative and see if we could add an icon in the top left corner of the infobox, similar to the Pip-Boy icon you see in the right top corner. Or somewhere else slightly below it using a new parameter line. That would give it more profile. For overview pages with more items like similar clothing, the gallery can be used. For the organisation we sure can use a new namespace, ModelData is a good name. For the nif files I wouldn't use a deep branch, but give it a good name like FNV plasma rifle.nif and place it in a well named category, f.e. Category:Fallout: New Vegas weapon 3D models. Its .png texture files can be named f.e. FNV plasmarifle#.png‎, FNV plasmarifle alpha.png etcetera, and store it in a category below that. Jspoel 17:08, January 12, 2015 (UTC)

It does need testing though I think to see how it works on different browsers and mobile, and more detailed instructions for us less tech savvy users, in order increase the workforce getting the .nif and texture files uploaded. Jspoel 17:19, January 12, 2015 (UTC)

Looks awesome. I have easy access to all the models and textures everything in NV and F3 so I'll happily upload as much as needed. One question I have is about the legality of this. Would we actually be allowed to upload the models and textures to the wiki, as it places them in very easy access of the general public.JASPER//"Do you like hurting other people?" 17:54, January 12, 2015 (UTC)

I don't see a problem with it. We've uploaded many soundfiles, dialogue files and images from the GECK. We are all crediting it and that should be good enough. Bethesda only is profiting from this. Jspoel 18:11, January 12, 2015 (UTC)

This is AMAZING. You just keep blowing my mind with unbelievably nice improvements to the visual side of our wikia. I absolutely love this. If this is legal (I'm no expert in US copyright stuff) then i think it would be super to add this to our wiki. My thoughts on how to get to the view would be to add a button on the top left image (like the pipboy one on the top right) with just a fancy "3D" icon, or a seperate line in the infobox with "Click here to view in HD", a bit like we added the dialogue files in link. - ^Greets Peace'n Hugs (talk) (blog) 18:34, January 12, 2015 (UTC)

Wow, all of a sudden tons of comments! :P Let's see if I can break these down a bit. First off, method of viewing it. I was playing around a bit, and came up with this idea - the menu drop down, would be used on pages that cover weapons with mods. For instance, in this case, clicking the button would show the standard plasma rifle, while there would be one for the magnetic accelerator version as well. Since it seems that each mod combination has a different model, it's one way of handling these things. Not too crazy about the color of the button in contrast to the infobox, but../shrug. Having a inset icon on the infobox image would work (modification choice could be moved to the viewer itself), I'm just concerned too many insets would start covering up the main image itself.

As far as support goes - I should have a pretty good test already enabled for checking whether or not someone's browser supports WebGL. Performance of course will vary from device to device - computer to computer, testing of course will be ideal, but there shouldn't be any issues other than slowness for those devices that don't have the performance.

And with naming conventions - it would make things a lot easier if the paths are kept the same way they are in the game archives themselves. See, the textures referenced in the .nif file, also include the paths (relative to the data folder), and this is important as the nif files themselves share textures. For instance - the Magnetic Accelerator Plasma Rifle and the normal Plasma Rifle, both use the same textures for the base. So making separate textures for each model, would just increase bloat. So it doesn't have to be deep - but then the "path" should be part of the name itself (i.e. textures-weapons-2handrifle-plasmarifle01.png)

Finally, the reason for the quality increase since the first time I shared it, was because the textures default to the 3rd person textures (i.e. what you see in the world, or in another character's hands), I merely just changed the image data, with the 1st person textures - which are about 4x the resolution. :p Digital Utopia (talk) 22:29, January 12, 2015 (UTC)

Isn't that an overkill? Sounds like a very interesting idea, but also quite much work, which only users with GECK editor can do. And not only that, they also need to know how to add these things. Energy X 18:37, January 12, 2015 (UTC)

Overkill? It's a major asset if we can get it to work over here. I'm willing to spend hours on it and motivated to add it to the wiki. I hope others as well, though I know it's timeconsuming. We'll just have to see who is willing. Anyway, any new image is already a good improvement. We start with the weapons, they are clearly the most popular. Digital can create a sort of guide with more detailed instructions. Jspoel 18:49, January 12, 2015 (UTC)

Most of the work will be the parsing and viewing code for the viewer itself - adding the images/models, won't be much different than adding the dialogue - in fact, might even be easier, since dealing with the GECK won't be necessary.Digital Utopia (talk) 22:23, January 12, 2015 (UTC)

I don't immediately see any legal issues beyond what we're doing already vis-a-vie images, but I have sent a message to Gstaff @ Bethesda, I will report back if there is a reply. Agent c (talk) 20:20, January 12, 2015 (UTC)

A couple of questions/comments: Users that don't have graphics cards, browsers or operating systems that support WebGL will not see this if clicked, but it won't alter their page view in any way, correct? Two: I believe there are a some typically unused infobox parameters, e.g. image caption, that we may be able to insert a clickable button directly beneath the main infobox image to take them to the 3d model viewer. I'll have to check and see which ones are not used. If this is so, they can be added to the infobox without overriding the main 2D image. The Gunny   21:07, January 12, 2015 (UTC)

The current test site, already includes cross-browser detection of WebGL support, if you click on the infobox image in a browser that doesn't have WebGL support active, you should just see the normal image viewer instead of the model viewer. For whatever method ends up being used to access the model viewer, similar checks would be used, either disabling, or outright hiding the button.

Currently, the test site uses a slightly modified version of the infobox templates - that do exactly that. If you go and edit the plasma rifle page on that site, you'll see that it has a field named "model" for the infobox. Beyond that, the only other major addition was the javascript to the MediaWiki namespace, that includes the javascript libraries for the WebGL wrapper, and the parser itself, along with - of course, the script that actually ties everything together. My focus was to do as much as possible with what already exists on Nukapedia, without having to make huge changes to layout or templates just to support it. I'll likely have to do more template modifications to handle any additional buttons in the infobox. But those too should be relatively minor.

Digital Utopia (talk) 22:23, January 12, 2015 (UTC)

How about creating the button as a template itself and we just transpose it into the empty image description parameter of the infoboxes on pages themselves? I'm checking a bunch of pages to see if image description is used at all, but so far that parameter seems to be empty on every page.

Edit: I think if we do this, we should make every attempt not to bury it down in the image gallery. If there's a way to add it to the infobox as a button without replacing the main image, I think that's the way to go. The Gunny   22:55, January 12, 2015 (UTC)

It's possible, but I didn't want to step over an existing field, just in case - modifying the template really isn't a big deal, just so long as I make sure I do it right :PDigital Utopia (talk) 23:10, January 12, 2015 (UTC)

One thing I do need to add- I'm pretty confident that most Fallout 3/Fallout: New Vegas, objects, items, and weapons should be supported with the existing code. However, some kind of method for reporting any bugs will be necessary. Perhaps, if it has its own page for instructions/requirements, the talk page could be used to report any display bugs. Editors adding models, and adding them to a page, should probably check first to make sure everything looks good before publishing it.

Creatures, and clothing will come later, as well as animations (idle by default, a drop-down box to choose any additional ones). NPC support will probably come last, as it will require figuring out how facegen works, and how I can apply it to the WebGL wrapper I'm using for the viewer (Three.js).Digital Utopia (talk) 23:10, January 12, 2015 (UTC)

My concern about the infobox is the size, it would only give a postage stamp sized place for it, whereas in the gallery, the display would be bigger. Agent c (talk) 08:36, January 13, 2015 (UTC)

I'm starting to think that a thumbmail - regardless of location, would be more trouble, and less effective than its worth. I mean, ignoring the extra time it would take to prepare, upload, and edit the page to add it, it would still have a tendency of blending in, and getting lost among the other Gallery images - considering the Gallery's location, and the fact that its purpose isn't immediately apparent to the user. Plus, on top of all that, a thumbnail would have to be added for each variant. However, if it's done similar to this, then not only would its function be readily apparent, but enabling it be as simple as enabling the infobox image (i.e. adding a line to the infobox parameters), and the drop-down could contain any number of the different versions described on the page (i.e. mods, other visually different variants not notable enough for their own page, etc).Digital Utopia (talk) 13:54, January 13, 2015 (UTC)

See, my main goal with this project (outside of the viewer itself, of course) - is to make it as easy as possible to maintain and contribute to. So anybody that has access to the game files themselves, can convert and make pages for them, and simply edit the infobox params on the related item's page, to make the viewer available. Currently, I'm working on testing out some code that will allow the model viewer to use the native .dds files, without having to first convert them to png. So that everything it uses, will be directly from the game data. When this gets closer to being ready - I'll work on some tools to make the process even easier. Hopefully I can make them work with just Javascript/HTML - so the tools can be actually be on the site itself. Digital Utopia (talk) 13:54, January 13, 2015 (UTC)

(←)  I like what you've done with placing a "View in 3D" button below the main infobox image, working with a dropdown menu to display more models if they are there. Color is fine for me, and it has a prominent place. It's better than adding a small icon in the top left corner, which tends to overcrowd the 2d model space. I can go along with the naming convention. You will know what will work best. We should keep the image desc parameter, it's used quite a bit. We'll see later on where it should be placed, below or above the 3D button. Good work! Jspoel 17:36, January 14, 2015 (UTC)

I looked on a bunch of pages for image description being used. Couldn't find any. Any chance you can link a few that use it? Either way, adding another line to the infobox should not be that big of a deal. The Gunny   20:24, January 14, 2015 (UTC)

I meant the image description is used in general. You're right you hardly see it on weapon pages. But I would just create a new (or a few new) parameters for the 3D images. Jspoel 22:48, January 14, 2015 (UTC)

If we can't have the image on the page itself, then having a view in 3D button below the infobox image seems good. Agent c (talk) 23:10, January 14, 2015 (UTC)

No sense, in my opinion, of reusing existing infobox params for it - considering it's going to require some template tweaking anyway to get that button to show. I'll get it worked out on the test site first.Digital Utopia (talk) 09:07, January 16, 2015 (UTC)

Updates

This section will provide a log of progress, and other streams of consciousness in the process of getting the viewer and page integration, finalized.

(1/16) - There's a known bug dealing with the display in IE, as well as some issues with getting the window to show up properly; but I'll get to that after the infobox. That being said, I've done a bit of work on the loading process itself. First and foremost, it's now using the actual .dds files (converted to text of course), from the game data. So, now, no conversion will be required, and it should use a bit less memory on top of it. Second, textures are now pre-loaded, with a progress blurb - right after parsing, and before generating the model. At this point, it's back to using the default (3rd person) textures, until I figure out a good way of checking if the high-res ones exist for a particular texture. That's probably going to be the next step, and then I'll start working on the infobox on the test site. Digital Utopia (talk) 09:07, January 16, 2015 (UTC)

(1/17) - Texture loading change seems to have fixed the display issue in IE. Work on parsing the .esm format has begun, with the goal of creating a dictionary of sorts, to tie model files, texture files, texture replacements/sets, and mod info, to the items FormID/EditorID. Not only will this allow for the display of 1st person (high res) textures without hassle; but it will also do the same for modifications, as well as items that simply use a different texture, for the same model (like Q-35_matter_modulator). Digital Utopia (talk) 16:11, January 17, 2015 (UTC)

(1/20) - Initial Esm parsing is complete - covering all GECK sub-categories under "Items", Texture Sets and Statics. Testing was successful on all NV and Fo3 ESMs (including DLCs). Not all of these will be supported in the viewer initially (esp Armor/Armor Addons); but I'm thinking ahead a bit. Next steps are to combine everything, and export the necessary information into a format JavaScript can use (i.e. JSON). Digital Utopia (talk) 19:42, January 20, 2015 (UTC)

(1/21) - Weapon data conversion to JSON is complete, which is the most complex, and can potentially have the largest amount of data attached to it (i.e. mods, first person models, texture replacements for all), for the main New Vegas ESM data. Output is around 300kb. Next up will be the rest of the categories, and then finally, before final output - "merging" the ESM data, adding items by editor id that don't already exist. Order will be FalloutNV -> New Vegas DLCs -> Fallout3 DLCs -> Fallout 3. Since stats aren't really important, this will make sure that only models/textures that aren't already used in the newer game (and thus, potentially better quality/more options), will have to be added from Fallout 3.

Currently, the viewer works like this: nif file is referenced in the infobox, which it then loads and parses, then scans through the resulting data looking for unique textures to load, preloads the texture data, and then converts the nif data for use in the viewer. Once the JSON dictionary is complete - the editor id will be referenced in the infobox, and the option chosen via the button/menu will both be used. Once a choice is made, it will grab the information for the chosen editor id, and load the .nif file based off of any options. When it gets to the point of loading the textures, it will look for any texture replacements, and override the nif-referenced texture with the replacement, and load that instead. A similar process will be done when actually applying the textures as well.

The "View in 3D" button itself, will load the basic model for the given item. When armor is supported, it will load the male variant, and if there is a female variant, there will be a menu. For weapons, the menu itself will contain the basic model, and all mod combinations. Each entry will also have a "First Person" button, to load that version as well. My initial plan of using the 1st person textures on the basic model, had to be scrapped after noticing that a lot of the first person models, differ from the base model - and the first person textures are actually defined in that model's nif instead. Which means, in order to make it standardized, and load firstperson textures by default, I'd have to parse not one, but two nif models before being able to show it. The first of course, being the base model - the second, the 1st person model, just to get the texture names. So, for a matter of compromise, I've decided to just run with the idea of a "first person" button for each entry that has one.Digital Utopia (talk) 15:48, January 21, 2015 (UTC)

Just wanted to make sure you knew at least some people are reading these and watching your progress. Give us a heads up when you update the systems at the test wiki so we can try them out (and bug check, I guess).  The Gunny   20:48, January 21, 2015 (UTC)

Thanks for all your updates on the progress! When we can chip in you'll let us know, allright? Jspoel 23:10, January 21, 2015 (UTC)

I hope to get the esm data output integrated into the page/viewer by the end of the day, and then comes the page work itself - so within a few days, I should have something close to the final layout/method set up. Main reason I've been giving updates, is to show that work on it is still being done and progress is still being made, even if it's not immediately obvious to someone visiting the test site. When there's actually something visibly done - I'll create a new section here, to let everybody know.

Current plan is, once the page/template stuff is done - I'll start working on a utility that will make adding models/textures a lot easier. I'm going to try my absolute best to make it pure Javascript, so that it can be done completely in the wiki itself; but I can't guarantee anything quite yet. The idea currently, would allow someone to drop a nif or dds file, from the proper path (i.e. Data/textures/... or Data/meshes/...) on the page, and have the page automatically convert the file to base64 (with pre tags), display the output, and provide a link to the page where it should go, based off the file path.

What I'd like to happen, is once everything is set up, that anybody here, can get in some practice with the process of adding model assets, and adding the model property to the infobox for an item/weapon. That way I can get some feedback on ways to streamline the process, and of course, addressing any issues with the display of the model itself. This of course, would be at the test site - any weapon or item page someone wants to try out, can be copied over to the test site. I believe I have most of the templates/add-ons set up, that this site uses. Obviously pictures won't show up in that case, but those aren't really important for the purpose at hand. So yeah, it won't be too long before I'll need as many people as possible to help :p.Digital Utopia (talk) 16:02, January 22, 2015 (UTC)

(1/23) - Parsing and formatting is essentially finished - still working out some small format issues with the JSON right now. Should be fixed and ready for usage shortly. Once that's done, work will begin on the test page itself - so if you head over there today, don't be surprised if things are broken. Goal for today is to at least get the viewer to work with the data, off of the editorid value for the model parameter of the infobox. Once that appears to be working, I'll be moving ahead with adding the button/menu, and some kind of alert for any missing textures or models - to alleviate any guesswork when it comes to adding things. Digital Utopia (talk) 21:51, January 23, 2015 (UTC)

(1/24) - A few setbacks ended up turning that "shortly" into an all day affair - however data is finally up. Integration with said data is also complete -including the use of texture replacements, and loading a specific model via an index. The latter will be used in coordination with the button/drop-down. At the time of writing this, the viewer on the test site is essentially off-line, as it will stop at 11% when loading the textures. This is due to still working on a way to create a list of missing textures, without impeding the loading of the model. I will update this, when this issue is resolved. Digital Utopia (talk) 23:00, January 24, 2015 (UTC)

Alright - model will now completely load, regardless of whether all the textures are present. If they are not, a gray texture is used as a placeholder, and the missing files are added to a list. When any files are missing, an exclamation button appears in the bottom right corner of the viewer. Clicking this will display a box immediately above that button, listing any assets that are missing, and encourages the person to add them. Eventually, it will contain a link to a page with instructions on how to do so. Now that the viewer code is handled, it's time to move on to adding the button/menu. Digital Utopia (talk) 03:28, January 25, 2015 (UTC)

(1/25) - Infobox template modification is done for the magic button, menu is populated and styled, and both are linked to code, albeit that code doesn't really do anything yet, except print the selected index to the browser's developer console. Further adjustments will likely be necessary with the menu text, to balance readability, appearance and clarity - especially with weapons that have 3 mods. The next step will be re-creating the lightbox, to be able to use it on demand, instead of having to hijack the one wikia creates. A couple of notes about the button. As soon as the modelviewer script loads, it checks for WebGL - if it fails that check, it makes the entire row/button disappear. Otherwise, it will initially be disabled, with the text of "Loading...". Once the data is loaded, the button will be enabled, and the text will change to "View in 3D". Digital Utopia (talk) 23:28, January 25, 2015 (UTC)

I like the design of the button. Subtle and clear. - ^Greets Peace'n Hugs (talk) (blog) 23:51, January 25, 2015 (UTC)

Thanks! I'm really trying to keep within the theme as much as possible. I feel it would take away from the benefit of the viewer, if everything else about it looked like crap :p Digital Utopia (talk) 05:21, January 26, 2015 (UTC)

(1/25 pm) - Viewer is now tied exclusively to the button/menu itself, and everything from the infobox template, to the viewer code, has been divorced from the infobox image. Viewer is also completely functional with the button/menu choices - missing textures and models aside. As mentioned earlier, the viewer now uses its own "lightbox", independent of the wikia system. This eliminates the errors and quirks from the original method of hijacking Wikia's, plus gives me a little bit more flexibility. For instance, instead of picking one size, or nothing at all, the viewer should automatically fill up 80% of your browser's window - regardless of screen resolution. While it won't change the size once it's open, neither does the Wikia one - so /shrug.

Next order of business is the converter tool, and on that subject - I've discovered some good news. HTML 5 has a native file upload API, which means that can be handled entirely within a wiki page! Well, for people with browsers that support it anyway - which should cover the majority of users. So, that's the next step - to work on a nice, user-friendly converter, to expedite the amount of assets available. Digital Utopia (talk) 05:21, January 26, 2015 (UTC)

(1/27) - There is currently a bare-bones demo of the loader/converter here. Simply drop a nif/dds file in the pretty box, and if everything goes well, you'll see the filename, link to the page it's supposed to go on, and - most importantly, the base64 encoded data, already surrounded by pre tags. Simply copy, go to the page, edit it, paste and publish. As I said though, it's bare-bones, and merely a demo. A better appearance, support for multiple files at once, and better feedback/ease of use features are forthcoming.

The method has deviated a little from my initial plans - mostly due to the fact that, for security reasons, only the filename itself is available when uploading files. So it's impossible to get an idea of where a particular file is supposed to go, just from the upload itself. To compensate for this, I proceeded to extract every Fallout 3 and New Vegas texture and nif file from the game archives, and exported the file name, folder path, and size for each one, and formatted it for use with javascript. So when a file is dropped in the drop zone, it first checks the file extension, then the file name and size are compared to the information in the array - if it finds a match, it generates the proper page name and displays it - before proceeding to upload. Once that's done, it encodes the file data, and spits it out to the text area.

In order to further test the process of adding a new model to a new page, I copied over the 10mm Pistol. Despite having to make a few tweaks to the parsing code, everything else worked perfectly, after only adding the model param to the infobox, with the its editor id as a value. That being said, you can certainly tell that the drop-down needs some better formatting. Currently I'm leaning towards adding a number in parenthesis after the mods i.e. (1), (2), (3), and listing combinations by simply showing something like "Mod 1 & 2", "Mod 1 & 3", "All Mods". That way I'm not trying to cram a ton of text in such a small area. Digital Utopia (talk) 15:58, January 27, 2015 (UTC)

(1/28) - The AssetLoader is now fully operational, with a new look and a bunch of additional features and/or improvements.

• A new look that fits in better with the existing theme
• Support for multiple files at once
• Significantly faster file matching
• Descriptive, and color coded status messages
• A check for, and a warning when an asset already exists
• The ability to post an uploaded asset, directly from that file's "block"
• A check for whether or not a user is logged in
• Response error handling, when posting a new asset - to inform of any permissions issues.
• A larger drop area.

So, feel free to give it a spin, and let me know what you think! Digital Utopia (talk) 21:20, January 28, 2015 (UTC)

(←)  Asset loader works great, couldn't be better. I do have a question though. Maybe I'm missing something, but there are many editor ids, nif files and textures files that have the same name in Fallout 3 compared to New Vegas. Probably plenty are the same and can be used for both, but I can imagine there also with the same name, but with different contents. How do you solve that? Jspoel 23:24, January 28, 2015 (UTC)

These 3D models are looking fantastic guys! Check this out for an example! (click on the eye icon in the 3D button). Jspoel 23:51, January 28, 2015 (UTC)

Bethesda Response

Response from Gstaff is they think it's a "cool idea". He's also mentioned some have used "sketchfab.com" for similar effects. Agent c (talk) 11:36, January 16, 2015 (UTC)

Glad to hear that we have their support! Digital Utopia (talk) 17:54, January 16, 2015 (UTC)

Awesome. JASPER//"Do you like hurting other people?" 23:23, January 21, 2015 (UTC)