We got 3 675 releases recently, did something had to be fixed?
What does this exactly mean? Sounds promising
Doubt it’ll make much of a big difference anyways.
I think it has to do with Server Authority on the roadmap
this is so peak
and i hope this means what i think it means… i can’t reliably brake-check people in car games because the physics act unfunny, so i hope this can improve that!
When Studio will be finally saving NVIDIA panel configuration? Because after every udpate I need to set FPS cap. Today were 3 updates. And every time had to add studio to the GPU panel… Honestly…
I don’t know about any of you guys but I am excited for this:
The new camera speed shifting has been bugging me and I belive the only way to disable it is with the view selector enabled . Glad to see more customizable studio setting features.
This is big. I had to store attachments I would clone under a part, now I can store them in a folder!
A man can hope Casey, a man can hope…
I’m apparently running the production channel, but studio says that 674 is the latest version? Anyone know how to fix it?
I reached these requirements long ago
Studio was rolled back to the previous version to resolve several issues.
We’ll be doing a patch release.
What were the issues in the new version?
Also, what even is “AuroraScript” for?
There was AuroraScript.DumpMispredictions
and predictions is also a term in networking. So, then it most likely is.
Now, I want to enable it.
Its probably going to be a in-game setting like GuiService.BackgroundTransparency
.
Also don’t use tables like that, as people can use a controller on their phone, a controller on pc, or even a keyboard with a phone. You’re better off properly scaling your UIs using size constraints and the like.
Useless type features 90% of Roblox devs won’t use vs Existing features that has been nerfed to the ground ruining hundreds of people’s work. Good job Luau team!
While working with Parallel Luau recently, I noticed that I can only have up to 3 parallel workers in-game, but 8 in Studio. In the past I could have 8 in-game. I am unsure if this was intentional, but it drastically reduces the benefits of Parallel Luau, as you can see by the FPS difference in the following video: In-Studio: Actor Test.rbxl (56.3 KB) In-game:
How hard is it to set this back to 8?
I hope this gets changed, i wanna use my cpu cores and stuff as much as possible.
i was hoping it would be something like a readable enum (idek if thats even possible if it were a property) that represents their input device because i’m using that table knowing it’s a necessary evil for its use cases
trust me i dont like using this table as much as whatever made you tell me to not use the table
it exists because i wanted a way to change the on-screen inputs for my games when i play on controller, so by “narrowing” the different userinputtypes to keyboard/controller/touchscreen, something like this is possible:
also i cant find where i said that i scale my interfaces wrt to this table, since i use a mix of scale and offset for my interfaces