WoW:API Model SetModel: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
m (Move page script moved page API Model SetModel to API Model SetModel without leaving a redirect) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{widgetmethod}} | |||
Set the Modelframe to display a certain mesh. | Set the Modelframe to display a certain mesh. | ||
| Line 19: | Line 19: | ||
A side effect of this function is that it seems to preload the specified mesh into some internal cache. When you're trying to load a mesh that's not shipped with the game, you'll might be forced to call a SetModel() at startup or your mesh won't load at all. | A side effect of this function is that it seems to preload the specified mesh into some internal cache. When you're trying to load a mesh that's not shipped with the game, you'll might be forced to call a SetModel() at startup or your mesh won't load at all. | ||
Latest revision as of 04:46, 15 August 2023
← Widget API ← Model < SetModel
Set the Modelframe to display a certain mesh.
Parameters[edit]
- Path - String
- The full path to the meshfile you want to display.
Example[edit]
MyModel:SetModel("Character\\NightElf\\Female\\NightElfFemale.mdx");
Details[edit]
- You will find most of the meshes that are shipped with the game inside of model.MPQ. Theoretically you may also load additional meshes provided through AddOns using this function, although there are almost no AddOns out there that make use of this technique at the time.
Notes[edit]
Notice that WoW adresses its meshes with a .mdx ending, although they have a .m2 ending in the model.mpq. This is probably due to historical issues that emerged while the game was developed.
A side effect of this function is that it seems to preload the specified mesh into some internal cache. When you're trying to load a mesh that's not shipped with the game, you'll might be forced to call a SetModel() at startup or your mesh won't load at all.