XeNTaX

jayko wrote:

RandomTBush wrote:And another progress report! (Yes, this means that all four of the recent games should be supported in the next update!)

Once I've made sure things are working alright, I'll go back and fix up a few of the other importers now that I have better knowledge of the header information, hopefully fixing up those problematic models that wouldn't import beforehand.

Awesome job, man!

Would the problematic models include those old TWD2 and TWAU location models where the UV Mapping is a bit buggy, or does the header information apply to the models like Felix from TFTBL where an error message would come up while importing? (I've also found the ANF ep3 textures don't convert correctly but that might just be me like last time instead of the BMS Script.)

Just curious either way (and definitely not meaning to pile on the work) - looking forward to the update!

Almost certainly, yes. The way I was reading it before used just the vertex sizes as a reference point, which is actually incorrect. There's actually a section just above the polygon information which I've got set up for Batman/TWD3/TWDM/GotG which dictates what kinds of things are stored in those vertex buffers. With any luck, the older formats will be set up the same way, and I can transfer the coding over to those to fix the importing issues for good.

RandomTBush wrote:And another progress report! (Yes, this means that all four of the recent games should be supported in the next update!)

Hah you're awesome! although now that means I'm going to have to buy the games for the PC! *shakes fist*

Figured I'd give the importer a new look since I'm overhauling a lot of things.


Personally, I think it's way better than the way it was before.


(Don't get excited about the Back to the Future importer being there yet, it's a placeholder until I can get the 30th Anniversary Edition's rigging bullcrap figured out, it'll be removed before release.)

It looks cool are they both optional? Also, will this still work for the 2009 version of 3ds?

Tydeus wrote:It looks cool are they both optional? Also, will this still work for the 2009 version of 3ds?

The "disable" options on the bottom? Yeah. Vertex colours are disabled by default since it makes most models pure black, and LODs (which only apply to Batman, TWD3 and GotG) I don't think most people would be interested in (and make things take longer to load), but both can be re-enabled by unchecking their respective boxes.

And yeah, it should still work in 2009, I don't have it installed on my computer (I'm using the next one up, 2010), but I don't think I've added anything that's not already in 2009's MaxScript setup. And it should also work properly in 2012 and 2015 and such since I'm rewriting a bunch of things to accommodate their... er... "quirks" (bugs).

RandomTBush wrote:

Tydeus wrote:It looks cool are they both optional? Also, will this still work for the 2009 version of 3ds?

The "disable" options on the bottom? Yeah.

I meant the two versions of the interface, one with just text and the other with icons but I was going to ask about those options at the bottom.

The second picture looks pretty much like the one we have now but blue, but I kinda like it

Tydeus wrote:

RandomTBush wrote:

Tydeus wrote:It looks cool are they both optional? Also, will this still work for the 2009 version of 3ds?

The "disable" options on the bottom? Yeah.

I meant the two versions of the interface, one with just text and the other with icons but I was going to ask about those options at the bottom.

The second picture looks pretty much like the one we have now but blue, but I kinda like it

Ah. Well, the colour scheme will actually vary, mine there's blue since I customized the colours of 3DS Max's UI (I prefer looking at that over longer periods of time compared to the default grey), but I suppose it wouldn't hurt to include both UIs, just in case people prefer the text-based menu options instead (or the icons don't work).

Oh my God! Amazing tool!

It's just my luck that as soon as we enter what seems to be the home stretch, my 3DS Max decides "a license error has occured."

This is what I get for updating my PC.

EDIT: Fixed it, but hell if I'm ever letting Windows update again after that hassle.

When the new version of the tool gets released I'm gonna do an edit for TWD2 Kenny with TWDM Randall's clothes.

Edit: I'm having trouble extracting the ttarch2 files from The Walking Dead Michonne. I get this error. What do I do?

Don't use 24 since it's for a different game.

https://mega.nz/#!qkR0nJCZ!ImhNfUDaxL0n ... F1WjadV-Eg

Since it's gonna take me another week or two to rewrite all my older, frankly-hackish-at-times importers, I thought I'd set up a separate script with just the new stuff for now. So yeah, the script above will work with Batman: The Telltale Series, Marvel's Guardians of the Galaxy, The Walking Dead: A New Frontier and The Walking Dead: Michonne... but nothing else for now. Just use the old script for those until I get 'em brought up to standards. There's one bug that I know of that I'll have to address later -- any models that have over 65,535 vertex points (eg. adv_virginiaRailroad_meshesD in TWD3) won't import because Telltale thought it'd be a good idea to use short values for those polygon faces with an extra modifier (a crapton of long values that are either "-1" or "0", which don't seem to match up... what?!?) instead of just extending it to use long values. I don't understand why, they do have a value for face buffer lengths in the headers...

I've also fixed up a miscalculation with my .D3DTX QuickBMS script, so the textures from TWD: A New Frontier's third episode should extract now:
https://mega.nz/#!T0gnCBCK!ZDMRxZTrTFeq ... aLqKDAvFow

Still haven't found out how to get the "gobo" and "lightprobe" textures to extract correctly yet, but I'll work on that after I've got the MaxScript fully updated.

As always, lemme know if something's broken with the new stuff.

Awesome!

Done a little bit of testing - TWD3 models seem to be working fine, but TWDM's UV mapping seems a bit dodgy. Some work okay with the use of a bit of UVW Unwrapping (which is inconvenient but still workable):



While others appear a bit more difficult:



I'll do a bit more research and find out if it's specific models or if this extends to a lot/all of them and then maybe that will help identify the issue.

jayko wrote:Awesome!

Done a little bit of testing - TWD3 models seem to be working fine, but TWDM's UV mapping seems a bit dodgy. Some work okay with the use of a bit of UVW Unwrapping (which is inconvenient but still workable):

*image*

While others appear a bit more difficult:

*image*

I'll do a bit more research and find out if it's specific models or if this extends to a lot/all of them and then maybe that will help identify the issue.

Whoops! Seems I accidentally labelled the wrong kind of UV formats used for those, they should've been read as short signed integers, not short unsigned integers as they were there.

Re-download the script, should be working now. Thanks for letting me know!
https://mega.nz/#!qkR0nJCZ!ImhNfUDaxL0n ... F1WjadV-Eg

RandomTBush wrote:

jayko wrote:Awesome!

Done a little bit of testing - TWD3 models seem to be working fine, but TWDM's UV mapping seems a bit dodgy. Some work okay with the use of a bit of UVW Unwrapping (which is inconvenient but still workable):

*image*

While others appear a bit more difficult:

*image*

I'll do a bit more research and find out if it's specific models or if this extends to a lot/all of them and then maybe that will help identify the issue.

Whoops! Seems I accidentally labelled the wrong kind of UV formats used for those, they should've been read as short signed integers, not short unsigned integers as they were there.

Re-download the script, should be working now. Thanks for letting me know!
https://mega.nz/#!CpoUyCqL!r3fAturSXwYt ... Jm3piSi7p4

Thanks for the speedy fix! Tremendous work you've done here, man -- can't commend you enough. I'll be sure to shoot you a donation or something for your hard work when some cash comes my way. All that work deserves reward, I'd say : )