So I tried out the new Next-Gen Explorer, and uh… it doesn’t show half my stuff. Which is kind of wild considering its one job is literally to show my stuff.
I make a new game, add some parts, take a look at the newgen explorer, expecting to see my game stuff normally, and instead I’m greeted with a minimalist masterpiece: just a few objects chilling at the top while entire descendants and models are missing like they got evicted. Nothing in search, nothing collapsed, just straight-up gone.
Let me remind you: It has been in testing phase for like 8 months now, made by employees sometimes paid hundreds of thousands of dollars with “4+ years of expertise”, and it fails more than FaceDev’s projects.
Video for reference:
I don’t know if it’s trying to be modern or mysterious, maybe both at the same time, but right now it feels like using a treasure map that refuses to show the treasure. Please fix it before I lose the last two brain cells I have left after playing valorant ranked with golden teammates.
Thanks.
4 Likes
Can we refrain from putting unnecessary derogatory junk in bug reports? Thanks. The weird joke dumping is obfuscating the issue too. Let’s treat our comm line with Roblox a little more respectfully. Any large rewrite of complex core tooling will have growing pains for a little while as users with wildly different system setups get their hands on it. It’s not possible to anticipate all possible cases before release.
17 Likes
How persistent this behavior is for you? If you open and close the place, does anything change?
Can you provide the logs file from this session? There’s a high chance this is already fixed but that you haven’t gotten our recent update.
Hi, I’ve tagged this as needing more info unless you can provide the logs. There isn’t much to do with this bug report as it is.
in my experience closing and opening directories can unhide hidden items. This isn’t a global problem but also occurs when viewing specific models and many children are not visible. This is particularly a problem when selecting children in the viewport and the explorer automatically opens a closed directory (something it fails to do sometimes at that).
another example of the new explorer not exploring is it no longer features speechmarks or instance types for the search bar, no longer able to filter for caps sensitive results or exact matches.
Can you elaborate on this? The new explorer uses the exact same search filter as the old one. The ability to do something like type “Part” to get everything with parts was removed at the same time the new filter came out.
I sometimes have this issue too and to fix it I select the affect part and change its ancestry. I have no idea why it happens though, it seems to be random.
that should be brought back, but also what I mean is that you cannot surround the search term with speech marks to EXPLICITLY get matching results, not results similar to your search term, but EXACT name matches.
You can do exact name searches with Name=ExactMatchHere (spaces can be done with quotes).
Again, this is not a regression–this has been the behavior for several years.
If you can file a repro, please file a ticket for it. We are hunting down these cases but right now do not have any.
it is a regression when we used to be able to do this though! While I do not disagree that name=phrase may have existed for many years, I am well familiar with the functionality of surrounding the phrase with speech marks, 3 more characters is a bit much compared to speech marks which indicate something is to be taken literally, i.e. when denoting a string in code
I wasn’t previously aware of that alternate method to do this, and I would like if there were some in-program tips to inform us of how to use features like this that we otherwise won’t know about, i.e. a small info “i” near the search bar