ViewportFrame Release


#142

I love this, i can achieve a tardis like effect very easily, although it would be better if i was able to use a shader on a surface gui https://cdn.discordapp.com/attachments/348909182168203264/533053680388407316/Viewport_Frames.mp4


#143

There are so MANY possibilities from this. Can’t wait for this to get released.


#144

I too would like this feature as this could replace the whole need for rendering in my games.


#145

Absolutely love this idea, opens up a very wide window of possibilities from the simplest to the most complex - eager to see what inventions other developers can create from this! :grinning:


#146

I love how many effects I could make with this!
Hopefully it will be added before my game comes out! :grinning:


#147

this is sweet!


#148

Can’t wait to use this for GUI tool icons instead of manually making icons.


#150

Another version of the tardis-like effect :smile:


#151

thats amazing!


#152

Finally, Doctor Who is possible in roblox.


#153

So some things I noticed while using the ViewportFrame is that if you go and copy a players model mid animation and parent the clone to the viewport, the character will statically show itself mid motion instead of getting rid of the animation. So the work around I had to do was parent it to Workspace, then the ViewportFrame to stop the frame from showing anims.


#154

That’s the point. ViewportFrame is meant to be a static render of whatever the Camera subject sees.


#155

Ik, I forgot to ask if this was a feature or something not.


#156

Awesome!


#157

So little issue i ran into and don’t know whiy it happened, but there is a glitch or bug that creating a camera and setting vf.CurrentCamera it will remain nil while even though the camera exists, and even try looping till it parents and still remains nil.


#158

Are you creating your Camera client-side or server-side? Camera instances do not replicate, which is quite a bummer for use with ViewportFrames :stuck_out_tongue:

If you’re making it server-side, you can instead send the necessary information (i.e. a CFrameValue inside of the ViewportFrame to indicate the CFrame of the Camera, if the CFrame isn’t the same every time) to the client instead, and let them create the Camera.


#159

THe issue isnt the CFrame, its the fact that the viewframe.CurrentCamera is nil even though it shouldnt be

Ill give you an example

local Instance.new(“Camera”)
Camera.Parent = vf
vf.CurrentCamera = Camera
print(Camera, vf.CurrentCamera)

Output: Camera, nil


#160

Hmm. I can’t seem to recreate your issue, using the code you provided.

Here’s the place file I tested this with - the contents are in StarterGui.
DragonSkyye_ViewportFrameIssue.rbxl (14.4 KB)


#161

The issue did not appear when i entered play solo or start up a local server, it only appears in an actual roblox game server btw.


#162

I haven’t seen any statement of ViewportFrame being live yet, so I won’t expect it to function as expected in a live server.

Referring to https://developer.roblox.com/resources/release-note/Release-Note-for-363 it’s still pending to go live.