Yessss!!
5 Likes
Is there a reason for when you select a big instance outside workspace it causes studio to hang? I store maps on serverstorage under a folder and whenever I select the folder my studio just hangs, same for unselecting. 
5 Likes
legend
3 Likes
ohhh, okay, that’s cool!! thanks for explaining
1 Like
Still don’t see it in studio or in game. Wonder if its actually fixed.
1 Like
Could you for once fix the important things and not some side issues?
2 Likes
The “important things” might take longer to do than the “side issues”. We don’t know what they are working on, maybe the “important things” are still in progress and still actively being looked at.
3 Likes
When Editable Mesh will be on the client?
1 Like
ROBLOX has a lot of bugs, and some are even been reported for years but they instead came up with some small unimportant fixes that no one asked. Check Bug reports and feature requests and how many of these have ever been fixed.
1 Like
-
If you only work on big name features and long term bugs you’ll end up with a featureful but bug riddled product where the core flows work well but people don’t want to touch anything off the beaten path with a 10 foot pole.
-
If you only work on fixing all the small easy bugfixes as they come in, you’ll have a generally solid product but with some big blind spots / deficiencies.
The best approach is to do a mix of both. Our current threshold is that we aim to fix at least 80% of the new bug reports that come in from the community.
14 Likes
Most of the bugs reported in bug reports are not fixed.
People complain about pathfinding service and humanoid a lot. The path parameters dont work and this is something that have been like that since its release
2 Likes
It can look like that, but that’s because most bug reports get fixed fairly quickly and fall off the front page of the bug reports section once they’re marked as resolved.
Some bugs are harder and can’t be fixed right away because they need to wait for architectural changes, or are long term bugs that may be hard to fix period because people have started relying on the broken behavior as the new expected behavior. Those are the ones that stick around and come up repeatedly on the front page of bug reports.
12 Likes
Letting people get used to broken behaviour is not a good card for engineers. People are hoping to get the big heavy bugs fixed because that is what prevent us from making games. I had times when i almost quit roblox developing just because of some bugs. and the way engineers just find some bugs too hard to fix is a big issue. How cant a multibillion dollar company Get major noticable bugs fixed?
1 Like
Here’s an example:
-
Say that we’re rewriting the internals of the Humanoid and plan to have the changes released within 6 months. Now someone reports a bug with the humanoid.
-
We know that this bug will be resolved with the new version of the code. We could fix the bug in the old version of the code too but we could also just wait 6 months and have it fixed for free.
-
Fixing the bug in the old code would effectively be taking away time from other potential bugfixes that wouldn’t otherwise be resolved. The cost of waiting of course being that the bug will remain broken for longer. It’s a tradeoff.
That’s currently the case for the Explorer pane for example. We’re in the process of rewriting it as a Lua plugin, so some of the less severe bugs with it that otherwise might get fixed are being left unfixed for the time being since they’ll be resolved anyways by the rewrite. Though if severe problems show up with it we still have to fix those right away regardless.
17 Likes
When Engineers have a plan to do a massive change, then someone reports a bug, then the best thing to do is to notify the reporter about that big update plan and that their bug is going to be fixed in that big change.
The issue is when engineers dont give any information about upcoming humanoid/any service changes. there are no info about anything so people keep giving the same bugs thinking engineers dont know it/ignore it.
Simple way to say something like “We are doing a massive change and rewriting the internals of the humanoid. The rewritting will be released within 6 months, your bug might be solved there.”
Otherwise people will give the same report.
Also some major bugs exist for years and are not being talked about in updates.
7 Likes
Unfortunately it’s not always that simple. For example, there may be speculative work on a rewrite of something but where we’re not 100% sure that the rewrite will pan out, or work may not have started yet and priorities might shift, or maybe it will end up taking much more than 6 months for some reason.
Especially for hot-button topics it’s problematic to promise timelines / action unless we’re very confident that we can stick to the promise. If you see a long term high profile bug report with no response it’s likely the case that the situation around the bug is complicated in such a way where there’s no clear response to give.
5 Likes
I mean how could engineers not priorotize main bugs since it affects more developers. Not everything is quick fix i understand, but still something being hard is not a reason to give up on solving it. I mean engineers should have full control and knowledge on the ROBLOX internal code and be able to 100% know what they are doing and how to solve it.
Do roblox engineers priorotize easy fixes over hard fixes?
There are enough hard bugs existing in the engine and Studio that we could never solve every single thing that could be considered a bug even if we spent literally all the time working on bugs and no time on new features. So prioritization is a necessity.
It’s not so much about prioritizing one over the other, rather they get fixed in different ways. “Hard” fixes are usually hard because as described above, they require re-architecture. They do get solved, but normally not as one-off bug fixes, rather as part of larger code restructuring efforts which fix many known problems with that part of the codebase at once.
11 Likes