Solutions to common problems when working with custom styles.

Style Creation Issues

"You must select a checkpoint model before saving"

Problem: Trying to save a style without a checkpoint.

Solution:

1. Click the search/add button in the Checkpoint section
2. Browse and select a checkpoint model
3. Try saving again

Why it happens: Every style requires a checkpoint as the foundation.

Cannot Find Compatible LoRAs or Embeddings

Problem: Search results are empty or limited when adding LoRAs/embeddings.

Solution:

1. Check which checkpoint architecture you've selected
2. LoRAs and embeddings must match the checkpoint's architecture
3. Try searching with different filters
4. Consider switching to a different checkpoint if you need specific LoRAs

Why it happens: Models must share the same architecture to work together.

Style Changes Not Saving

Problem: Modifications to a style aren't being saved.

Solution:

1. Make sure you clicked "Save Changes" or "Save Style"
2. Check for validation errors displayed in red
3. Verify you have a checkpoint selected
4. Try closing and reopening the modal

Why it happens: Validation errors or forgotten save action.

Style Application Issues

Style Doesn't Look as Expected

Problem: Generated images don't match the intended style.

Solution:

1. Review which LoRAs are active and their weights
2. Try removing LoRAs one at a time to identify conflicts
3. Test with just the checkpoint to verify base output
4. Consider trying a different checkpoint architecture
5. Adjust LoRA weights to balance effects

Why it happens: Conflicting LoRAs, incorrect weights, or incompatible models.

Changes Not Appearing After Regeneration

Problem: Regenerated images still show old style.

Solution:

1. Verify you saved the style after making changes
2. Check that the style is actually applied at the correct level
3. Confirm you regenerated the correct entity
4. Wait for generation to complete fully
5. Clear browser cache if issue persists

Why it happens: Unsaved changes or incorrect style application.

Entity Using Wrong Style

Problem: Character or location uses unexpected style.

Solution:

1. Check the style hierarchy - entity-specific overrides story defaults
2. Verify which style is assigned at each level in Styles modal
3. Remove entity-specific override if you want story default
4. Regenerate after making changes

Why it happens: Entity-specific style overriding story default.

Generation Quality Issues

Images Cost Too Many Credits

Problem: Credit cost is higher than expected or affordable.

Solution:

1. Switch to a cheaper checkpoint (flux1s instead of flux1d)
2. Use hidreamfast for lowest cost option
3. Remove unnecessary LoRAs (they may add cost)
4. Use story defaults instead of entity-specific when possible
5. Apply premium styles only to key characters

Why it happens: High-quality checkpoints and complex model stacks cost more.

Images Look Low Quality

Problem: Generated images don't meet quality expectations.

Solution:

1. Upgrade to a higher quality checkpoint (flux1d)
2. Adjust LoRA weights for better balance
3. Remove conflicting or low-quality LoRAs
4. Test different checkpoints to find best match
5. Ensure embeddings are relevant to content

Why it happens: Using fast/cheap checkpoints or incompatible models.

Inconsistent Character Appearance

Problem: Same character looks different across regenerations.

Solution:

1. Use the same style consistently for that character
2. Avoid changing styles mid-story unless intentional
3. Set entity-specific style to lock in appearance
4. Don't switch checkpoints after establishing look
5. Regenerate with same seed if available

Why it happens: Style changes or random variation in generation.

Technical Issues

LoRAs Disappearing After Checkpoint Change

Problem: LoRAs were removed when changing checkpoint.

Solution:

1. This is expected behavior - LoRAs must match checkpoint architecture
2. Select new LoRAs compatible with the new checkpoint
3. Save the style with new compatible models

Why it happens: Architecture mismatch - system prevents incompatible combinations.

Modal Won't Open or Close

Problem: Styles modal or editor not responding.

Solution:

1. Try clicking the close button again
2. Check if there are unsaved changes prompting confirmation
3. Refresh the page if modal is stuck
4. Clear browser cache and reload

Why it happens: Unsaved changes warning or browser issue.

Style Deleted Accidentally

Problem: Deleted a style by mistake.

Solution:

1. Styles cannot be recovered once deleted
2. Recreate the style manually
3. In future, create backup copies before experimenting
4. Note model names before deleting for easier recreation

Prevention: Create duplicate styles before making major changes.

Common Misunderstandings

"Why can't I use this LoRA?"

Answer: LoRAs must match your checkpoint's architecture. If it's not appearing in search, it's incompatible with your current checkpoint.

"Why did my style reset?"

Answer: If you changed the checkpoint to a different architecture, incompatible LoRAs and embeddings are automatically removed.

"Why does my character look different?"

Answer: Check if an entity-specific style is applied. Entity-specific always overrides story defaults.

"Why is it so expensive?"

Answer: flux1d and other high-quality checkpoints cost more credits. Use flux1s or hidreamfast for cheaper generation.

Getting Help

If your issue isn't covered here:

1. Check the Tips guide for optimization strategies
2. Review Style Structure to understand technical details
3. Revisit Creating Custom Styles for creation steps
4. Contact support with specific details about your issue

When reporting issues, include:

• Which checkpoint you're using
• Any LoRAs or embeddings in your style
• Steps to reproduce the problem
• Screenshots if applicable