Texture atlas list?

[MunkDev]

I was just curious whether there's an actual complete list of the texture atlas that Blizzard uses nowadays? Dumping individual atlas entries with GetAtlasInfo is fairly cumbersome when you're looking to do bulk work efficiently. I'm also trying to use some of the newer textures found in the beta texture repo and would ideally avoid having to use Photoshop to crop out individual parts, since pretty much all new textures in Legion use the atlas system.

This is what Rygarius said about where the information comes from:

The system doesn't support creating your own; it's tied to our internal database and editors. You only need to know about our atlas if you reuse our textures.

Is there any way to get a hold of this data without cobbling together code to scan the whole interface for atlas textures and dumping the data into a saved variable?

[MunkDev]

I put together an addon for this purpose on live servers, although it obviously won't help with Legion textures until addons are enabled on the beta client.

http://www.wowinterface.com/download...asScanner.html

[ykiigor]

All legion atlas list in lua table
http://pastebin.com/qpEHYhrj

[MunkDev]

Thanks! Mind if I ask how this data was procured?

[ykiigor]

From WoW DB files. You need FileDataComplete.db2, UiTextureAtlas.db2 and UiTextureAtlasMember.db2

[galvin]

Is there anyway to find the texture file that the atlas uses?
I used the pastebin link, but the addon never put pathnames in the saved lua file.

[MunkDev]

The addon does put path names in the saved variable and the pastebin has a list of every single texture that's referenced. Maybe you misunderstood the output?

This is what a texture path looks like.

[[Interface\PETBATTLES\PetBattleHUDAtlas.blp]]

[galvin]

I got something like this after scanning

AtlasScan = {
	["Insanity-Tentacles"] = {
		1252243, -- [1]
		129, -- [2]
		30, -- [3]
		0.00390625, -- [4]
		0.5078125, -- [5]
		0.68359375, -- [6]
		0.80078125, -- [7]
		false, -- [8]
		false, -- [9]
	},
	["UI-Character-Info-Title"] = {
		1400895, -- [1]
		196, -- [2]
		40, -- [3]
		0.0009765625, -- [4]
		0.1923828125, -- [5]
		0.6982421875, -- [6]
		0.7373046875, -- [7]
		false, -- [8]
		false, -- [9]
	},

[TOM_RUS]

Originally Posted by galvin I got something like this after scanning

And that makes sense, since client knows nothing about file names. You can still use names, but they are simply getting hashed, and file lookup performed by that hash internally.

[MunkDev]

This is the format I get in my scan:

AtlasScan = {
    ["minortalents-backplate"] = {
        "Interface\\LevelUp\\MinorTalents.blp", -- [1]
        418, -- [2]
        169, -- [3]
        0.001953125, -- [4]
        0.818359375, -- [5]
        0.46484375, -- [6]
        0.794921875, -- [7]
        false, -- [8]
        false, -- [9]
    },
    ["QuestDetails-RewardsBottomOverlay"] = {
        "Interface\\QuestFrame\\QuestMapLogAtlas.BLP", -- [1]
        287, -- [2]
        46, -- [3]
        0.283203125, -- [4]
        0.5634765625, -- [5]
        0.7783203125, -- [6]
        0.8232421875, -- [7]
        false, -- [8]
        false, -- [9]
    },
}

[TOM_RUS]

You two just run that addon on different client versions :P

[Resike]

What does the 8th and 9th paramerer means?

[MunkDev]

Originally Posted by Resike What does the 8th and 9th paramerer means?

Horizontal and vertical tiling.

[MunkDev]

Originally Posted by TOM_RUS And that makes sense, since client knows nothing about file names. You can still use names, but they are simply getting hashed, and file lookup performed by that hash internally.

How does this affect browsing or attempting to dump texture paths? Is this still doable?

[TOM_RUS]

Originally Posted by MunkDev How does this affect browsing or attempting to dump texture paths? Is this still doable?

None of the API's return texture paths. They return filedataId instead. Other than that nothing changed. You can convert filedataId to actual file name using information from FileDataComplete.db2 (ofc it can't be done in game, game doesn't even use that db2 file for anything or ever loads it).

[MunkDev]

That's a shame, but if this change reduces overhead then so be it. I was in the midst of developing a texture browser that would let you browse all textures in use in a hierarchical manner, like a file browser. I guess it won't be worth finishing it with Legion right around the corner.