PlayerModel:SetDisplayInfo

[semlar]

Originally Posted by Resike How can you get the model path then?

You can't, they aren't using paths internally any more.

[Resike]

Originally Posted by semlar You can't, they aren't using paths internally any more.

It makes no fucken sense. We are forced to build a id-path table for 500k models then?

[TOM_RUS]

Why you need path?

[Resike]

Originally Posted by TOM_RUS Why you need path?

I don't need the path specifically, i need some id or whatever based on what i can load a saved model. And since not every model have a id for SetDisplayInfo() and SetModel() requires a path, it would makes sense the path would be the best.

It's like removing GetTexture().

[Resike]

I also have some other questions about other model functions. Why do the models look so blurry on the beta? Also what changed with SetLight()? Seems like the parameters did'nt changes however the same code which runs flawlessly on live drops an error in the beta.

[MunkDev]

Originally Posted by Resike I also have some other questions about other model functions. Why do the models look so blurry on the beta? Also what changed with SetLight()? Seems like the parameters did'nt changes however the same code which runs flawlessly on live drops an error in the beta.

First two arguments are boolean now, instead of 0-1 range.

[TOM_RUS]

Originally Posted by Resike I don't need the path specifically, i need some id or whatever based on what i can load a saved model. And since not every model have a id for SetDisplayInfo() and SetModel() requires a path, it would makes sense the path would be the best.

There's also SetCreature, SetItem, SetItemAppearance, SetDisplayInfo along with SetModel. Those API's cover a broad range of models. Also you don't need any GetXXX API's at all, since that widget only displays whatever you set to it, just store that information yourself somewhere.

[Resike]

Originally Posted by TOM_RUS There's also SetCreature, SetItem, SetItemAppearance, SetDisplayInfo along with SetModel. Those API's cover a broad range of models. Also you don't need any GetXXX API's at all, since that widget only displays whatever you set to it, just store that information yourself somewhere.

The issue is that you won't be able to pair DisplayIDs with their proper model paths like this:

local function ExtractModelData()
    index = index + 1
    print("Model: ", index)
    model:ClearModel()
    model:SetDisplayInfo(index)
    if model:GetModel() and model:GetModel() ~= "" then
        modelData[index] = model:GetModel()
    end
end

Which kills the ability to categorize/use/select multi textured models.