There’s an issue with box selecting in the new beta explorer.
I can’t box select outside of instances, but I could in the old explorer. Not sure if they intentionally removed it, and also don’t know if it affects anything, so just saying here.
There’s a bug currently with box selecting from the area after the last Instance. If you select from the empty space beside the Instances it will work.
1 Like
I don’t mind this change in principle — but there was no early warning. This broke quite a few of my plugins, which scan for and manipulate all PVInstances in workspace.
1 Like
For reference we did do some early testing of it in-experience without it breaking anything there.
I’m curious what specific pattern broke.
I figured this would be a relatively safe change from the plugin perspective because a lot of codepaths involving PVInstance subclasses have to be coded defensively anyways to avoid breaking from stuff like new BasePart types.
Did stuff break break, or just the camera getting moved too when it shouldn’t have been?
1 Like
Stuff broke in the sense that we call PivotTo on all PVInstances, causing the Camera to be moved.
There was also a case (my personal favorite) where one of our models (an elevator), which happened to have a ThumbnailCamera, would now treat it as a valid floor.
(PS: We’ve already fixed this through excluding the camera from PVInstance checks)
Ideally you wouldn’t have to exclude the Camera.
Do you just mean you did that as the quick fix to get things working again or do you have some cases that would end up needing the inelegant exclude even if refactored to align with the change?
I believe this will make a few things also behave quite interestingly! Since the Model class for example also inherits the PVInstance class, any children within it when the pivot is changed automatically move with it.
Maybe this would allow for you to just parent a model (e.g a viewmodel) into the camera and it now automatically moves with the camera? No longer requiring you to manually pivot it to the camera every frame?
@tnavarts I’m curious if this is true? Is this behaviour from the PVInstance class or another one? Also, are there any plans on possibly allowing rendering layers so we could finally make viewmodels that don’t clip though the world and are properly affected by world lighting? ViewportFrames work, but these can’t accurately display the lighting of the world. Not to mention their antialiasing on the edges are quite jagged.
3 Likes
Why was “Highlight hierarchy under selection” removed? I prefer it off…
Found this out the hard way, but using the command bar to add a HapticEffect into workspace and saving the game and leaving will brick your game and prevent you from re-entering
1 Like
A fix could be downloading the place as an rbxlx file, searching for and removing any HapticEffect instances, saving, turning the file into rbxl, and publishing it.
1 Like
I believe it’s related to this:
1 Like
Was this change enabled today by any chance? I’m getting MUCH better FPS in studio playtest and in my game and was wondering why
I asked around any my players are getting much better FPS as well (without me having published an update)
11 Likes
One of the tools we use frequently takes your current selection, or the whole workspace, and fixes floating-point issues in positions, orientations, sizes, and pivots.
To prevent the CurrentCamera (or any others, for that matter) from being inadvertently moved, we need to have that exclusion added.
Having said this, it’s such a small use case, with a small one-line addition, that I am not particularly concerned about adding it. I just wanted a heads up before having it changed.
PS: Shameless plug! Please add back the class inheritance bar to the documentation.
3 Likes
if you didn’t already realize yet by the way this is a CRAZY change because you will be able to potentially make camera offsets with controlled rotation, completely putting Humanoid’s CameraOffset property out of use
this is a crazy thing for roblox jesus christ i love this
This is already possible, but I’ll accept any change that makes this easier!
I noticed that too, however right now they reverted it, atleast thats what i think, it seems to be back like it was before, can you check? If your fps is worse now
Yeah, I think whatever it was was reverted some time last night, the increased FPS I had is gone 
hopefully that was just some A/B test thing and it’ll get pushed soon
