Stability Matrix Model Browser Missing/Wrong Search Results #1336

Activity

1. Narixv

   added

   bugSomething isn't workingSomething isn't working

   on Jul 21, 2025
2. mcDandy commented on Aug 3, 2025

   

   mcDandy

   on Aug 3, 2025

   More actions

   Can confrim

   👍React with 👍1Reacted by Narixv
3. SamFinni commented on Oct 2, 2025

   

   SamFinni

   on Oct 2, 2025

   Last edited by SamFinni

   More actions

   i just tracked this down with Postman, and turns out there's some issues with CivitAI's API causing this. i believe this post is referring to the same bug. from my testing, it seems to be particularly related to their pagination being unreliable (though still deterministic), such that it may return 0-to-* results on any given page response (seemingly no standard size), and even if a page has 0 results, its nextCursor (next page) may have >0 results. worse, if you're sorting by say, downloads descending, the sorting is only applied within a given page; the following page may have a model with a higher download count.

   this means whatever you're searching for may not be shown in the first, or second, or third, etc, page, even if it should be the first result based on the CivitAI results for the same search. more annoying is the fact that there's no 'end' marker in the pagination results, and based on my testing it will eventually begin to return completely unrelated results, meaning a solution along the lines of "continue automated calling until no more pages" won't work either. just a straight up broken API on CivitAI's side for now.

   edit: related issue on CivitAI's repo
4. mohnjiles commented on Oct 3, 2025

   

   mohnjiles

   on Oct 3, 2025

   Member

   More actions

   Yep that's the issue I made a couple weeks ago 😄

   If you'd like to use the suggested "Tag" workaround from that reddit post, you can prefix your searches with # in SM's model browser to search by Tag instead of Query. Will see about making that the default in the next update also.

   👍React with 👍1Reacted by Narixv
5. Narixv commented on Oct 9, 2025

   

   Narixv

   on Oct 9, 2025

   Last edited by Narixv

   Author

   More actions

   Re: Stability Matrix Model Browser Missing/Wrong Search Results
   Issue: 1336
   ATTN: @mohnjiles @SamFinni

   Hello,

   After some testing on the SM's latest stable build (ver. 2.15.1) It seems that in addition to Civit's API issue it might also be Civit's new "auto mod age rating"...

   When browning models on Civit with Browsing Levels (PG, PG-13) enabled I am unable to view R+ models and content, This is expected.

   However, what has changed now is when Browsing Levels (PG, PG-13, R, X, XXX) are enabled, some models and content I was previously able to view, I can no longer do so with those settings enabled.
   See Attachment 1 ↓
   

   In addition it also seems that some creator profiles are also being restricted based on the settings above.
   See Attachment 2 ↓
   

   It seems that these seeings are passed though to SM's account page when we are asked to integrate Civit with SM to utilize the Model Browser.
   See Attachment 3 ↓
   

   I hope this information helps.

   Thank you,
6. mutag3ne commented on Oct 26, 2025

   

   mutag3ne

   on Oct 26, 2025

   More actions

   Another thing potentially worth mentioning is that it will prioritize the first word in a search to such a heavy degree that finding anything with that search's second word can require several scrolling updates. CivitAI's onsite search engine is already bad at that, but it at least has a "Relevancy" sorting option that does tend to help in my experience. Stability Matrix's model browser does not have that, and so it feel impossible to narrow searches.

   I'm guessing that CivitAI's slapdash API doesn't include anything for that relevancy sorting option? And if it does, could it please be utilized in the model browser?
7. github-actions commented on Dec 26, 2025

   

   github-actionsbot

   on Dec 26, 2025 – with GitHub Actions

   More actions

   This issue is stale because it has been open 60 days with no activity. Remove the stale label or comment, else this will be closed in 7 days.
8. github-actions

   added

   staleStale issue or inactive for long period of timeStale issue or inactive for long period of time

   on Dec 26, 2025
9. github-actions commented on Jan 2, 2026

   

   github-actionsbot

   on Jan 2, 2026 – with GitHub Actions

   More actions

   This issue was closed because it has been stale for 7 days with no activity.
10. github-actions

    closed this as not plannedon Jan 2, 2026
11. mohnjiles

    added a commit that references this issue on Aug 29, 2026

    Merge pull request LykosAI#1336 from ionite34/backport/main/pr-1332

    ...

    2c8a68b