The very first custom character I created has returned, reimagined, refined, and elevated in a new model for Illustrious.
What? You thought the model’s name referred to a ship? No, no. Nothing of the sort.
Some people have Asuna as their waifu. Others, on the other hand, gravitate toward something closer to GGO Kirito... especially after what Sword Art Online Code Register did. So then… why not both in a single body? Technically speaking, that would be the ultimate SAO waifu, and deep down you know it to be true, regardless of personal preference.
I am far from the first person to explore this idea. Similar concepts have surfaced online for years, though they tend to be short-lived. I honestly do not understand the hesitation. Are people afraid that Kirito’s vengeful spirit will come after them? If so, I will take that risk on your behalf. Should he appear, I am confident I could one-shot him.
This new Illustrious version was built through considerable effort and dedication. I began by creating a base model using various official Kirito and Asuna resources like artworks and anime screenshots. From there, I generated a large number of images using prompts that deliberately blended both characters. After carefully curating the highest-quality results—nearly a thousand images—I trained a second, definitive model for Kirisuna. As a result, unlike the 1.5 version, there is no longer any need to reference Kirito and Asuna separately in your prompts, only Kirisuna exists in this model now.
The model was also trained on what I consider the appropriate physique for this character since they are half-boy, a “canon” body that reflects the fusion itself. Consequently, if you prefer a more traditionally feminine body with pronounced curves, you will need to specify that explicitly in your prompts. When left unspecified, the model will default to the physique it was trained on—namely, a feminine upper body (such as Asuna’s large breasts), combined with a more masculine lower body (straighter hips and a firmer, less rounded butt), all within an overall athletic build.
Since this is a custom character, some of you may want additional context to enrich the concept. I have provided my own interpretation, though it should not be considered definitive. You are entirely free to imagine your own circumstances and narrative for how this fusion came to be.
Consider this model a Christmas gift to yourself—something to enjoy now and carry forward into the new year.
1.5
This model was trained with several official images of Kirito and Asuna and therefore it understands some physical characteristics from regular Kirito, GGO Kirito and Asuna.
Kirito's main prompts are: black eyes, black hair, short hair, hair between eyes
GGO Kirito's are: purple eyes, black hair, long hair, hair between eyes
Asuna's: brown eyes, brown hair, long hair, braid, french braid, crown braid
The idea of the model is to mix these characteristics as you prefer. I usually consider past ideas that Kirisuna would have long black hair with crown/french braid and brown eyes, but you can do it your way. The model will generate the character as female, which is its intention. But if you prefer the result to be something more "exotic" there are ways out there if you look for it.
It's possible to generate Kirito's and Asuna's default clothes, as seen in the examples. But Asuna's is easier than Kirito's due to the more detailed descriptions. Of course, it's also possible to make just Kirito or just Asuna in this model. But why would you want to do that? There are other models of the characters, separated, and with much better quality than this one.
I'm still struggling to make my models to work with Weight 1, but that won't be the case here again, so you will need to scale it down a bit to make it decent.
The King's journey is endless, seeking the best Queens.
Description
FAQ
Comments (14)
lol
"Is this the fusion of Kirito and Asuna!? Impressive."
I'm sure you're interested in a good battle Son Goku.
After the conversation you find out that this cute girl is a guy.
Perhaps it's much more paradoxical.
This is actually hot ngl
It wouldn't be worth it if wasn't.
Actually switched the heads of my sao asuna figma with gungale online kirito, to have two cute girls as figures now XD
This Lora reminds me so much of this.
Features of Kirito, expressions of Asuna. It's like their child, but not. I have to wonder which one they got their lower half from, but either way I'm good with it. 😋👍
If you want to create perfection, fusion is the answer. Breeding just generates a offspring with fragments of the two, it's diluted. mad scientist glasses
@TheKingMultiversal Oh for sure. Like cloning but with two genetic sources. You might be onto something! 😄
Merging Characters like that sounds like a great idea! I'd really like to know how exactly you made this Lora (tagging, dataset, ...)
Kirisuna and Satori were made differently. Kirisuna involved using a good amount of images of both Kirito and Asuna with the two sharing the same "name", for the training to consider that they are the same character with different looks.
The tags are simply descriptions of Kirito and Asuna individually, so it's still possible to make the two separate in this LoRA. The reason that LoRA manages to mix the two characteristics is precisely because it thinks they are the "same person" (the same name/trigger word) so when you make a Kirito with brown eyes, it uses Asuna's eyes.
When you describe "short hair" and "black hair" it thinks in Kirito's hair, but when you complement it with "braids"/"crown braids"/"french braids" it uses Asuna's hair as a complement and combines the two characteristics.
I realized this would be possible when you don't separate different clothes well, it can generate combinations of clothes, so theoretically the same should be true for physical characteristics. Basically, is lying in training and saying these two different people are the same.
Satori on the other hand was the traditional method, there are interpretations of the character on the internet, so I just used what already existed for training.
@TheKingMultiversal Alright! Sounds pretty straight forward, thank you very much!


