Bello! Here are the release notes for 729.
I’ve been trying to touch grass a bit more and it’s been improving the stress levels! I hope you all can do the same, if you can. Have a wonderful week!
Bello! Here are the release notes for 729.
I’ve been trying to touch grass a bit more and it’s been improving the stress levels! I hope you all can do the same, if you can. Have a wonderful week!
Cool but when will they be released tho
After the last announcement regarding 2D clothing, I really needed to hear this, thank you!
I was going to suggest we all go outside and touch grass but then roblox will find a way to ruin that too, so don’t bother
GRASS??? HISS
I DESPISE IT! NEVER. EVER say THAT word in front of me EVER AGAIN.
Good fix tho!!
![]()
I will touch more grass, i promise!
yet another releaseless release note
so awesome
reducing your stress levels yet stressing out devs by making the 2d clothing publishing fee 600 robux
ts is never coming ![]()
There’s active progress happening on SurfaceAppearance.ResampleMode.
It has not been forgotten, it’s just taking a while to make it to production.
“Pending Notes For 729” would, uh…Yeah.
I’m curious about why it’s taking so long to ship. It seems like something that would be relatively simple to implement.
I like this change actually. I think it semi-opens up the opportunity for people who have those setups where they use a mouse-and-controller, with a controller for locomotion/etc and a mouse to aim. I believe a device like that is called the Hex Evo.
UI Style transitions out of beta when. ![]()
![]()
Has there ever been a statement as to why release notes are published with items sometimes months before they are actually live? Why not wait?
The release notes pull directly from engineering workflow, engineers merging code in can mark their changes as “Public Facing” and provide release notes. So the change shows up in the release notes when it first gets merged into the codebase, not when it releases. This is simple and clean, because something is either merged or it isn’t, there’s no inbetween.
There could be a separate process associated with when something is releasing but that would be additional process engineers would have to spend their time engaging with that would take away from their time actually shipping the thing. In particular because whether something is released is a very messy status: It can be released on some platforms and not others, or be released and then get rolled back.
As is the Release Notes creation is done at a very simple convenient time during the engineering process which means engineers are happy to engage with it. The tracking could be moved to something more accurate but a the cost of convenience so that would probably also result in people bothering to add significantly fewer release notes.
Chat?
Why did they not just map it to DPadUp?
And will pressing DPadUp trigger ButtonUp, probably not… since it’s a KeyCode, so gg.
How is a fix for this already “out” ? What?
![]()
same thing?
All games that have voice chat enabled are saved. ![]()
![]()
![]()
PBR textures get baked into a single compressed asset to reduce memory consumption. This has to be reliably uploaded and transcoded to load across all devices and graphics vendors that Roblox consumes (e.g. DX11, OpenGL, Metal, Vulkan, etc). Presumably they have to do something extra to make the Pixelated sample mode work correctly.
Anytime something goes wrong in this chain, it has to go down for everything else. It takes up to 2 weeks for code changes to propagate from being committed, to actually being in a release build of Roblox. Once it’s stable and working on all devices, it will be switched on for good.
Player / developer intent.
Someone pressing the micro-gamepad buttons probably doesn’t intend to do the same thing as someone pressing the D-pad buttons. Despite both being a set of directional buttons they serve different roles (one is the primary control on the device, the other is a secondary control).