@hsdhcdev@SlipperyGem I've run plenty of tests. The model is really strong, but the safety block needs to go
The issue almost certainly isn't in the text encoder it's embedded in the DiT itself. Some manipulations already reduce its aggressiveness, and even a small finetune could be enough to break it
@SlipperyGem@hsdhcdev Actually, there are several approaches worth trying:
1. Fine-tune the model or train an NSFW LoRA/LoKr to shift its priorities.
2. Train a LoRA on censorship artifacts and apply it with a negative weight.
3. Identify where the censorship is encoded and selectively remove it.
@SlipperyGem True.
I've tested Ideogram quite a bit, and I genuinely don't understand why they crippled the model like this. The funniest part is that it'll block completely harmless prompts, yet a long, detailed prompt can sometimes generate nudity just fine. The whole thing feels absurd.
@bdsqlsz The model looks promising, but the safety system is absurdly aggressive. The safety filter can be triggered by something as simple as "an apple."
It's hard to understand why anyone would cripple such a promising model. The community will break through those restrictions anyway.
@ComfyUI@ideogram_ai Is this even real?
TripoSplats, now Ideogram 4, Krea 2 around the corner...
Maybe I slipped in the shower and this is all just a dream???
@davidpwalter Time matters
In my opinion, the core idea here isn’t just viable. It’s probably the only genuinely reasonable and forward-looking direction for engine development at the moment.
@davidpwalter This is phenomenal work! We really need native support for Nanite-like technology in Godot. In my opinion, this is one of the most important things the engine should be focusing on today.
@hybridherbst@sea3dformat@threejs@godotengine
How realistic is it to add something like this to Godot? It would be an absolute killer feature. AI-driven pipelines are becoming more and more relevant. We really need something like nanite for Godot.
@toyxyz3 The new nodes are simply much slower than the old ones. They’re harder to read and overall much less convenient to use. I literally took my workflow that works perfectly fine with the regular nodes, and with the 2.0 nodes it becomes completely unusable.