Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent behavior with viewmodel overrides #77

Open
sr229 opened this issue Sep 3, 2021 · 5 comments
Open

Inconsistent behavior with viewmodel overrides #77

sr229 opened this issue Sep 3, 2021 · 5 comments

Comments

@sr229
Copy link

sr229 commented Sep 3, 2021

There are times that Outfitter can use the workshop model's viewmodel arms but it's mostly a hit or miss with the viewmodel arms overrides.

This was tested with two workshop models, both have viewmodels:

@AmericanEagle1776
Copy link

I'm having the same issue. Both of my listed addons have viewmodels with the first link working but the second one does not.

https://steamcommunity.com/sharedfiles/filedetails/?id=2852693758
https://steamcommunity.com/sharedfiles/filedetails/?id=2908317736

@Python1320
Copy link
Member

Since we can't use the lua that tells which viewmodel is for which outfit it makes a guess. I could try running the lua to safely extract the mapping in the future. This should really have been handled inside the mdl but I don't think we have any place to store such information easily.

(Alternatively I could make a GUI to let you choose the viewmodel, but that gets strange for players to use.)

For now I can try improving the guessing system because at least the mapping should be easy if you name things correctly:
models/raptors/producer_raptor.mdl
models/weapons/arms/producer_raptor_arms.mdl

@sr229
Copy link
Author

sr229 commented Dec 30, 2022

Since we can't use the lua that tells which viewmodel is for which outfit it makes a guess. I could try running the lua to safely extract the mapping in the future. This should really have been handled inside the mdl but I don't think we have any place to store such information easily.

(Alternatively I could make a GUI to let you choose the viewmodel, but that gets strange for players to use.)

For now I can try improving the guessing system because at least the mapping should be easy if you name things correctly: models/raptors/producer_raptor.mdl models/weapons/arms/producer_raptor_arms.mdl

You could go for a greedy search to look for *_arms.mdl or models containing in a c_arms/* folder but that's probably too expensive and slow.

@Haano137
Copy link

Haano137 commented Oct 8, 2024

(Alternatively I could make a GUI to let you choose the viewmodel, but that gets strange for players to use.)

Please add this as a feature. If people can bother browsing workshop for a model, they wouldn't mind selecting the c_arms themselves.

@sr229
Copy link
Author

sr229 commented Oct 21, 2024

Could probably use the same logic for selecting playermodels.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants