WoW:API Model SetModel: Difference between revisions
Jump to navigation
Jump to search
SetModel -Documentation by DerGhulbus-
mNo edit summary |
({{widgetmethod}}) |
||
| Line 1: | Line 1: | ||
{{widgetmethod}} | |||
<center>'''SetModel''' ''-Documentation by [[User:DerGhulbus|DerGhulbus]]-''</center> | <center>'''SetModel''' ''-Documentation by [[User:DerGhulbus|DerGhulbus]]-''</center> | ||
| Line 19: | Line 21: | ||
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. | ||
Revision as of 12:18, 10 June 2006
← Widget API ← Model < SetModel
Set the Modelframe to display a certain mesh.
Parameters
- Path - String
- The full path to the meshfile you want to display.
Example
MyModel:SetModel("Character\\NightElf\\Female\\NightElfFemale.mdx");
Details
- 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
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.