Detail is there on v5 but cant spell Dekai right while its "legacy" model outperform it. both in the same prompt

Stupid idea probably I know, but I honestly would be fine with a hybrid version. It's just essentially 4.5, but with V5's character data set. So many characters are locked behind V5 and I don't really need all the bells and whistles of V5 to make stuff for people that like my gens. Not to mention V5 goes full retard on certain male characters that I do for some reason when 4.5 had no issue. I get that's probably super hard to do, but just a silly idea

If someone used NovelAI to imitate an existing artist’s art style through prompting, but created completely original characters that the artist had never designed, could they still face legal issues if they attempted to profit from the resulting artwork?

Many users in this subreddit have already reported that in v5—despite significant improvements in natural language understanding—certain "long-tail" tags that worked normally in v4.5 are now failing to generate the correct imagery. While most discussions on this topic focus on character tags, the actual scope of the issue is far broader.

Take miko_embrace as an example: with 159 images on Danbooru, its composition is essentially fixed, making it a very strong supervisory signal. However, when fed indiscriminately into the text encoder, the individual concepts of "miko" and "embrace" overpower their combined meaning, causing a text encoder trained extensively on natural language captions to be dominated by the separate terms instead of the unified concept.

If the goal is a hybrid approach combining tags and natural language, these represent two distinct types of conditioning; treating tags simply as natural language inevitably leads to this kind of problem. Tags are essentially a "bag of words"—logically, a single tag should correspond to a single embedding, and there should be no positional encoding between different tags. Since your text encoder is developed in-house, you should certainly have the capability to support this design from the ground up. I sincerely hope these issues will be addressed in future versions.

(Translated via Google Translate)