Viewport viewmodels or traditional viewmodels?

Recently, I’ve been thinking about some viewmodel stuff and came up with the idea of using viewport frames to make viewmodels instead of traditional “teleport to camera” viewmodels. Both of them are quite similar, though the viewport one has following capabilities:
-Viewmodel doesn’t clip with the environment
-You dont need to make a separate collision group to prevent being flinged
-Ability to change the viewmodel’s FOV and transparency.

Some downsides I can think about:
-More lag (probably)
-A bit more scripting
-Viewmodel cannot interact with environment directly

Non-roblox FPS games that I played always use the viewmodel one, so I’ve been thinking if using it in roblox can be a good idea. What would the performance cost be? Are there any other pros/cons you can think about? Please give some feedback below

1 Like

I actually do this frequently, the biggest con for me is the lighting. ViewportFrames have terrible lighting. Honestly just do whatever you want, if you want it in a viewport frame then go ahead, whatever fits your game.


Viewports are good as long as your game has basic lighting…
I guess the pros to having viewport viewmodels is that they don’t clip through things.
But overall I prefer traditional because they’re overall just more reliable.

1 Like