Release Notes for 661

Updates Release Notes
#22

This was always a hack and Roblox even said in the original glass post to not rely on it. Alas, here we are, the best solution is just a new glass material that introduces the fix, ie, GlassV2. (also this could be an optimisation where you dont need certain glass blocks to render non-opaque stuff.)

This is the same thing that happened with Plastic/SmoothPlastic

1 Like
#23

You cant clone editable instances, thats what this method is for. It clones the data from one editable to another.

#24

I canā€™t seem to find anything on this, what happened with SmoothPlastic?

1 Like
#25

image
image989Ɨ94 6.6 KB

thank u so much

#26

Release Note
Release Note720Ɨ108 13.3 KB

What is the error code exactly? Also why isnā€™t it in the fixed category?

1 Like
#28

as you adding that the pc can have touch enabled

image
image935Ɨ76 11.2 KB

can you as well give us the possibility to detect the platform of the user? like is it a console/ phone/ tablet/ vr/ pc

that will allow us i think to adjust ui for the platform and even mechanics

1 Like
#29

I think that the more likely action will be that future Windows versions might not support it. Perhaps in a situation where Windows adopts the Linux as its kernel.

From my experience, deprecated methods are not prone to break, but do get superceded by easier or more secure methods.

#30

Can I ask why there is a duplicate release note from Release Notes 656, regarding lighting calculations being removed from rendering?

If this is going to become a common practice, please add more statuses to the release notes so we can better understand the state of features, such as if they are delayed or cancelled, so expectations can be better managed.

2 Likes
#31

This will not happen. You should always be basing your UI off of things like screen size and last input types.

5 Likes
#32

Letā€™s say we want to show controller input buttons, like for a tutorial.

We canā€™t even detect what type of controller theyā€™re using. We canā€™t show playstation vs Xbox buttons.

I see you and @MetaVars in almost every patch note denying our access to this without giving a proper reason. Well Iā€™m fed up with it. Give us a reason, and a very good one, not the ā€œUi scalingā€ one you give.

3 Likes
#33

GetImageForKeycode exists, supporting that in a forwards-compatible way: https://create.roblox.com/docs/reference/engine/classes/UserInputService#GetImageForKeyCode

12 Likes
#34

I gave a number of reasons, e.g.:

  • Mixed input devices like Steam Deck or Ally donā€™t work
  • Using a tablet as a monitor with keyboard and mouse doesnā€™t work
  • Chromebook and Windows Surface donā€™t work
  • VR doesnā€™t work
  • ā€¦

Please donā€™t make assumptions based on TouchEnabled, MouseEnabled etc. APIs.
We will replace them with a better API in the future and provide you with input and output capabilities.

13 Likes
#35

you very much can; at least between xbox and PS. hereā€™s code we use to have custom images per-console:

local function IsXbox()
	return UserInputService:GetStringForKeyCode(Enum.KeyCode.ButtonA) == "ButtonA"
end

function ConsoleKeyImageHandler.GetImage(KeyCode: EnumItem): string?
	local Platform = IsXbox() and "Xbox" or "PlayStation"

	return BUTTON_IMAGES[Platform][KeyCode]
end
2 Likes
#36

That could be arguable.
Youā€™re right a lot of people a making ui based on screen size which will not change.

A couple of things that could be useful to have imo that the roblox could handle something like the last input type and give the ability to see the change of the platform (could be useful for mechanics e.g. when to include aim assist).

And as well roblox ui i think already does something like that (changing the jump button size depending on a device)

2 Likes
#37

Here are the updated instances.

Plugin
PluginCapabilities
PluginManager
PluginMouse
PluginToolbar
PluginToolbarButton
StandalonePluginScripts
2 Likes
#38

Apologies if this has already been mentioned elsewhere, but TouchGui is sometimes there and sometimes isnā€™t for certain players in-game. I believe the TouchGui being there is dependent upon the TouchEnabled. Clarification would be nice if thatā€™s not the case. I put pcalls in my game for enabling/disabling the TouchGui or the JumpButton specifically.

To clarify, I think Iā€™m talking about a different topic here. I hear you saying to not assume the platform based on inputType. Kinda similar, but the quote made me think to ask.

1 Like
#39

Why do some changes stay pending for so long compared to others? Thereā€™s still some changes all the way back in #649 (or earlier) that still are pending

2 Likes
#40

UI wise? This makes sense. Though in the future, Roblox should let developers create experiences only aimed at certain groups of users, like users with higher-end hardware with better software, so they can make games without worrying about low-end users, expanding the Engineā€™s potential.

1 Like
#41

You would want to do this based on specs (or some other thing that relates to what you actually want to do for higher end users), not based off device. The newest iPhone is going to be more powerful than the worst Windows.

2 Likes
#42

That is true, though I think this would still require an API of some sort that doesnā€™t give the developer direct access to that info, but still allows the developer to use the full/a great portion of that deviceā€™s capabilities.

1 Like