An issue with custom models is that you have to make a model which supports both Alex and Steve models, which can be difficult for certain model designs, for example wrist worn objects or shields. An option which could fix this is a predicate option (similar to the already existing lefthanded), which could be called something like playermodel. Using this, the model could be different depending on whether you have the Steve or Alex model, to allow for these issues to be bypassed. It could be handled similarly to lefthanded in that Steve is a 0 value and Alex is a 1 value.
An example of how this could be utilized specifically is a watch model to replace the clock, when held in third person there would not be visible gaps between the band and watchface and the player arm (similar to the gaps visible in the shield model in-game).
(I'm not fully sure if this should go in Scripting or Graphics, but I've put it here as there is another predicate based suggestion here)
2 Comments
Please sign in to leave a comment.
Post a new comment: