Official Quick Search Preview

Still have artifacts in Unity2021.1.3

 

Thanks for the reply.

How can I discard the extra results? Will be nice to add an option in QSearch settings to restore legacy search results behavior.
Extra results are more annoying than helping when we get +50-100 unnecessary results.

Yes. It's stuck. Cancel is helped but from time to time it appears again.

It would be so nice. Now QSearch so slow and annoying. I hope it becomes stable ^_^

 

Yes.

So far, I have not found a pattern, but if I find it - I'll write it right away.

You did not understand me. The solution is really more convenient than the old one, but not yet polished. In my opinion, it is a bad idea to redefine the search system for unity without choosing the old or new (for example, like in the input system) for the first time.

Perhaps I am having problems because I have a lot of files in my project, and for small games, the QSearch works very well.

 

Thanks. I will try to use these options.

Nice. I'll be waiting for it. GL

 

I upgraded to the latest quick search package 3.0.0 preview 8 and now I am missing the Favorites View (the view where it shows all the saved queries for quick access) which previously worked and allowed me to really quick try out several different queries. To be specific, the view that is explained here: https://forum.unity.com/threads/quick-search-preview.635863/page-12#post-6905027
Is there some setting to activate/deactivate that view?

I am on Unity 2020.3.4f1

 

Thanks @jonathans42 for the super fast reply with the solution!

 

Searching for a prefab, that does not exist, yields the correct results (no results at all), but also produces a red error message "Unkown filter "ref"." on the bottom. The message let me believe that the syntax of the query is wrong, which it isn't.

Using the same query but with an existing prefab:

 

1. Is it possible to search for matches containing a string completely and in order?
So that e.g. "_nature" will match only assets that contain the full phrase, like "test_nature" but not "test_allnature"?
In the documentation I could only find the possibility to use "!" and "=" for exact matches, but that's not what I want given that I do not know the full name in advance.

In this screenshot, you can see that everything with "_nonnature" in the name is matched too

EDIT: I also just realized two additional things:
2. The highlighting in the screenshot is only working on some of the matches. This seems off.
3. my query contains "t:Material", but the results contain a prefab. Shouldn't the prefab be excluded from the results?

 

Awesome, looking forward to the new version!

Oh wow, with Regexes I quickly solved my task, thanks so much!

I see. Thank you for the explanation. It does indeed embed that material. Hmm.. this functionality is really great to have if you need to search inside prefabs. But in my case, I just want all the Materials (excluding prefabs that reference Materials). Is there an easy way command to exclude prefabs (basically the indexed dependencies?) from the search? EDIT: I just added the material extension to my search query as a quick solution.

Will send it to you via PM ASAP.

 

For the file extension, I need to search for multiple possible endings. So my query would look like this:

If I now additionally preselect only audio clips, it suddenly does not yield any results anymore:

I made sure that the t:AudioClip isn't the issue given that this query still contains the asset I am looking for (the one ending with "_nature.wav"):


Am I missing something here?

EDIT: I managed to get it working by swapping the query conditions around:

 

I use a QuickSearch query to find the references to my audio file:

When I do the same via code I get this SearchItem as result:

Here we can see that the GameObject I am looking for is present in the data property. Now is there a way to find out which component of this GameObject actually references my AudioClip?
(As can be seen in the first screenshot, the PlayAudio script references the "ambience_nature.wav". So I want to find out via code that the PlayAudio actually is the component that references my AudioClip.)

 

I wrote you a pm with all the details as I had another question related to that anyways.

Thanks! I already thought about the possibilities of how to approach this but the only way I know so far to deal with that is to iterate over all components using GetComponent<MonoBehaviour>() and then using reflection to iterate over the component properties to get to know which are of what type which is very slow and then looking at the value of the property and verifying it is the one that is actually referencing my AudioClip.
But using indexed data would be way faster for sure.

 

Is it possible to search for method names in unity events?

Here is an example, i would like to find all objects that reference this method. I need this because i would like to rename the method and find all objects that referenced it and fix the reference on the unity event.

 

Thank you. This tool is phenomenal in the amount of inconveniences it solves.

 

hey Baste cc: @jonathans42,

did you ever implement the right-click and search stuff you asked about? It seems like a fairly fundamental search: click on an asset and find out where in the project it's used. I saw that the 2.1 preview docs mention a syntax guid: / id: search type which I was hoping would do the trick. At the moment the fastest way for me to find guid dependencies is using a Sublime Text 'find in files' text search under the Assets folder.

@jonathans42 I installed QuickSearch again because I was hoping to be able to easily search for specific assets/guids in the project, what scenes/prefabs they're used in, etc. We previously tried QuickSearch v1 but removed it due to some issues with Unity Editor launch times being painfully slow on some machines (never figured out why sorry, but removing QuickSearch fixed it). I was just testing QuickSearch v2 (v2.0.2) again to check how it performs and for a while it looked ok, but the indexing is really slow and on a MacBook Pro with 32gigs of ram and plenty of free space indexing scenes runs out of memory and fails to index. I also tried v3 preview 9 and it took ~4 hours to index our project, and even though it was running as a background task it was beachballing the editor constantly making it unusable.

Obviously the indexing is working hard, but what are your broad expectations for how long various project sizes might take to index for the first time, ie. is 4+ hours reasonable or is something not right? Is there any way to work around the indexing process running out of memory? Is the index valid and/or will it attempt to reindex things that have failed?

Thanks for any info.

 

Nope. We had a right click option already that runs git grep in the background. I was considering replacing it with the quick search option as it should have some advantages, but it never got important enough that I took the time.

 

Thanks for your followup @jonathans42 Ok, so ~4 hours is long but in the ballpark for a large project. After trying v3 I did return to v2.0.2 again to try to install the samples to test the dependency/find by guid stuff (the v2.1 and v3 preview docs could be out of date, but the samples mentioned are not available in the package manager for those preview package versions). I couldn't get search by dep: or id: working though so I must be missing an installation somewhere.

My current project folder (with a bunch of extra builds and other stuff under it) is ~30gig at the moment. The indexing kicked off before I did anything with the search manager, and to be honest I only found the search manager when I went through this thread and saw it mentioned - I did not see it in the docs. The Assets index ended up at 117meg, has just over 5 million elements with ~12k docs, and had Files, Types, Properties and Dependencies checked.

I also tried a Scenes index and it ended up at 1.5gig, has ~64 million elements, 242 docs, 455k objects and had Files, Types, and Dependencies checked (they were the default options). At the end of this index the console showed 150+ out of memory warnings indexing all sorts of differently sized scenes. So, out of the box perhaps I needed to change some of the default options.

When I tested v3 preview 9 I didn't have any search manager stuff open or configured. It just did whatever it did in the background process for the ~4 hours after installing the package. Unity was unusable while indexing and the activity monitor showed cpu at 100% and Unity not responding for long periods of time. In between these stalls it the background process view was showing it processing about 1 object per second, and about every 10-20 objects it would stall again.

And sorry, I should have mentioned in my earlier post, this was all using Unity 2020.3.9. I have not looked at 2021.x tech stream as this is a shipping project.

 

Hello, I was wanting to try taking advantage of the indexing of assets that QuickSearch does, for use in my own tool. But for the life of me I cannot figure out how to access the API. I looked, but didn't see anything on the docs.
I'm sorry, I'm sure I am just missing something really obvious.

Appreciate any help, thanks.

 

Ah, thank you! I was trying to find a namespace with `QuickSearch` in it. That explains it!
Does an equivalent API for searching exist in prior versions to 2021?

I am making a tool that lets you group assets in to collections/tags, and I wanted to add a 'smart collection' that adds items to itself based on filters. Basically a glorified wrapper around QuickSearch

 

I see thanks, so there is no equivalent API available in 2019.4?

Cool! I hope it becomes official!

 

I was testing to see if it would make sense to switch my own system over to just using QuickSearch, and doing an initial test I noticed that it seems to lag when doing the very first search request after domain reload, but is very fast after that. Is this known? Am I doing something wrong? Is there some way to 'initialize' QuickSearch to prevent the lag?

This is all I am doing.

Code (CSharp):

1.  if (GUILayout.Button("Query Cube"))
2. {
3.             _queryText = "Cube";
4.             _items.Clear();
5.             context?.Dispose();
6.             context = SearchService.CreateContext(SearchService.Providers, _queryText);
7.             SearchService.Request(context, (_, items) =>
8.             {
9.                 _items.AddRange(items);
10.             }, _ =>
11.             {
12.                 context?.Dispose();
13.             });
14. }

Any inside it appreciated

 

I was also wondering if someone could tell me how fast a request or partial request takes for large projects. Or point me to where I could find that info. I have 10k files that I use for testing, and it returns the results very quickly for the(Great job on this, gotta love binary search and multi threading). But I was hoping not to have to make 50k - 100k+ files just to test it my self.

 

Alright got it. That makes sense!

Oh good! I was wondering if you could maybe explain how the incremental items return work? I guess it isn't too important. I just like knowing how the systems work. Like when/how often does it return items?

Nice, I appreciate you sharing this info and helping me!

Got another less technical question. How do you find items based on if their name contains a string? Using `name:` only matches to the front. And I saw in a comment from last year that you don't do a `string.Contains()` for performance reasons. However just entering a string in to the search field will return items as long as they have the string in their name, not just the front.
So, how do?
(Also if there is anything that would be helpful for me to do or let you know about, please let me know)

 

I wonder what the reason is why the search results don't get cached?
Would it not make them faster?
or is comparing the cache with the current search taking up the same time as doing a new search?

 

Thank you vert much for the info!

I see, thanks! Regex seems to be much slower, and possibly hangs the UI? Is it single threaded?
Forgive me, I looked all over the docs but could not find the `select{}` expression/filter and when trying to use it my self it says a handler needs to be set first. Is there somewhere I can read more about this?

As I am working with QS I am finding it actually rather difficult to get the exact results I am looking for. It does a lot of 'smart' search stuff, which is really, really nice when trying to search for something in the editor and works great! But I am finding it to be quite hard when working with the API to get just the items I am wanting.

Part of this is that there are multiple filters that do exactly the same thing, or very close to the exact same thing, so it can be hard to figure out which one to use where. And part of it is the docs I think. Having more examples of how each filter can (and can't) be used would help, and more exact description of what they do and don't return.

An example of this would be trying to only get items that are in a folder at a certain path.
First I thought

dir:

would be the proper filter, but it doesn't accept a path, only a single folder name. Then I realized that

p:<folder path>/

would work (making sure to end with a forward slash). It does the exact same as

find:

and

dir:

also does the exact same, but less as long as you end with a forward slash. (Genuinely not sure the use-case of

dir:

)
There is also

t:folder

which I can't get to work, but seems rather pointless, along with that is

t:file

which does the same as

find:

and

p:

I think?

I assume the reason for the redundancy is that different providers/filters have these since the user can chose which to add/remove. But it makes it a bit harder to learn when trying to get precise results.

 

Is there a way to stop this updating during play mode? Makes game unresponsive for ~5 seconds.

I am using 2019.1.9f1.

 

I don't think I have Quick Search package installed just the one that comes with 2021.1 (they look the same) so I don't know which version that is, I checked the package manager and couldn't find any reference to an installed Search package in Built-in/MyAssets/Unity Registry etc.

I never really use the Search window, I only noticed it as I was getting the issue in play mode.

 

Hello,
I have been trying to make an asset filtering system wrapper around QS, but I am running in to a problem.
It seems that you cannot do use the OR operand with paths? For example

p:assets/plants/ or p:assets/creatures/

. My goal is to find all assets that are in either of those paths. Please let me know if I am doing something wrong, if this is simply not supported.

(The more I test, it seem that the

p:

must be first? If that is the case that is a problem for me as you can see since I need to do two of them)

 

I have issues searching objects in hierarchy that have names with spaces.

For example, i have an object in hierarchy

This is what it finds:

the object in question is not found for some reason.

Also, when i try to find references to an object with the name 'Panel - Options Menu' it finds nothing.

Am i doing something wrong? any help is appreciated.

QS version:


P.S. I have searched this thread for anything related to the word 'space' and found nothing relevant.
P.P.S. The scenes are indexed.