Rendering is also done partially on a sepparate thread.
1 Like
What do you exactly mean by this? CPUs are used for logic and GPUs for rendering. Multiple threads will just spread the logic on multiple CPU threads and your 1050ti won’t be affected.
3 Likes
This is one of the bests new features of the year for the Roblox Studio! Amazing.
1 Like
The only practise (afaik) that isn’t faster is getfenv and setfenv.
Question: In the old VM, you guys got rid of tail calling. I think it was removed due to debugging complexity? Is that still the case, or do we get tail calling back in the new VM?
7 Likes
We don’t have existing plans to revive tail calls. There are more call kinds in the new VM so guaranteed tail calling is somewhat more involved compared to vanilla VM, and in regular code the performance advantages are not significant. So I would say it’s unlikely that they will come back.
4 Likes
Tail recursion is still possible by creating a variable before the function. Sure, it’s no optimized like in the default Lua, but most cases can be easily replaced with a while loop.
Without proper tail recursion, you risk stack overflows with recursive functions. But yeah, usually they can be reformatted into a while loop
3 Likes
Right but the thing is, you risk stack overflows with recursive functions anyhow unless all calls are in tail position 
Generally speaking “interesting” recursive algorithms are non-trivial to implement with tail recursion, and “boring” recursive algorithms are trivial to implement with iteration.
6 Likes
I’ve been waiting for this update. Thank you!
I have been hyped about this update since it was announced in Beta! Thank you for making the games better and Better!
So regarding multi-threading, how is such a thing like that going to be implementation wise? Is it going to be done via the roblox lua API functions or is it going to be automated internally in the VM? I feel like lua is very tricky language to do such a thing effectively.
2 Likes
Local script will never be safe.
The reason why is because local scripts run on the user’s computer. Meaning that they will always be able to access them if they run on their computer.
It is the same for place stealing; Exploiters will allways be able to steal places because roblox sends the places to their for their client to render and so that the character isn’t really buggy.
Uh… What? The place can’t exactly be stolen. Anything inside the ServerStorage and ServerScriptService isn’t replicated. Also, the thing that is being sent isn’t the place itself, but rather the properties, which include hierarchy meaning that a place can be somewhat reconstructed.
If the entire place was sent then decompilers wouldn’t be required as the scripts would already contain the source.
4 Likes
there has been multiple instances where my prior and current pc havent been using the GPU for some reason. Oh and roblox lags a lot sometimes when I move my mouse too much, same thing happened more regularly on my prior pc [x2]
1 Like
Because all the logic is done on the CPU. That includes particles, beams and other integrated stuff. Running on multiple threads might make it faster, but only if they include multithreading on the C++ side. Your GPU will still not be affected in any way.
2 Likes
I honestly like this update. I can use more coroutines then ever in one script! makes it very useful for loops.
2 Likes
sadly exploiters have already caught up, most of them created updates before the full release just to be ready 