Release Notes - Version v0.6.5
Release notes for version v0.6.5
Release Notes - Version 0.6.5
Release Date: 2025-06-20
Critical Bug Fix: Layer-Specific Image Generation Control
Overview
Version 0.6.5 addresses a critical issue where layer-specific autoGenerateImages settings were being ignored during story node generation. This fix ensures that users have proper control over which image layers are generated, providing better cost control and respecting user preferences.
Issues Resolved
Image Layer Settings Inheritance Fix
Problem: New story nodes were not properly inheriting and respecting layer-specific autoGenerateImages settings from parent nodes. This caused:
- Images being generated even when
autoGenerateImageswas set tofalsefor specific layers - Increased AI generation costs due to unwanted image creation
- System falling back to legacy layer configuration instead of using proper inherited settings
- “layerInstruction NOT FOUND” warnings appearing in system logs
Solution: Implemented comprehensive inheritance collection and data flow improvements:
- Upfront Inheritance Collection: System now collects all inherited layer settings UUIDs before starting image generation
- Temporary NodeImages Structure: Creates proper data structure with inherited settings for new nodes
- Data Flow Correction: Ensures both layer instruction loading and autoGenerate checking have access to correct settings
- Per-Layer Control: Respects individual layer
autoGenerateImagessettings for fine-grained control
Technical Changes
Backend Improvements
File Modified: backend/src/story/services/multi-layer-image.service.ts
Key Changes:
- Added inheritance collection loop to gather layer settings UUIDs upfront
- Created temporary
nodeImagesstructure with inherited settings - Fixed data passing to
createLayerSpecificPromptmethod - Enhanced logging for inheritance debugging
Impact on User Experience
Before v0.6.5:
- Layer-specific
autoGenerateImages: falsesettings were ignored - Images generated for all enabled layers regardless of user preferences
- Higher than expected AI generation costs
- Inconsistent behavior between parent and child nodes
After v0.6.5:
- Layer-specific
autoGenerateImagessettings are properly respected - Images only generated for layers where generation is enabled
- Better cost control through per-layer generation preferences
- Consistent inheritance behavior across story node chains
Cost Optimization Benefits
This fix provides significant cost optimization opportunities:
- Selective Layer Generation: Users can now disable image generation for specific layers (background, middle, foreground)
- Budget Control: Prevent unwanted image generation to stay within budget limits
- Strategic Usage: Generate images only for key story moments or specific visual layers
- Inheritance Efficiency: Settings configured once at parent level automatically apply to all child nodes
Compatibility
- Backward Compatible: Existing stories and settings continue to work without changes
- No Data Migration Required: All existing layer settings remain functional
- Legacy Support: System maintains support for existing layer configurations
Testing
- All 326 backend tests passing
- Layer-specific settings inheritance verified
- AutoGenerateImages functionality confirmed working
- Cost optimization features validated
Upgrade Notes
For Users:
- No action required - the fix is automatically applied
- Existing layer settings will now work as expected
- Review your layer-specific
autoGenerateImagessettings to optimize costs
For Developers:
- Enhanced logging provides better debugging information for inheritance issues
- Temporary
nodeImagesstructure approach can be used as pattern for similar inheritance scenarios
Known Issues
None identified in this release.
Next Steps
Future enhancements being considered:
- Refactoring inheritance logic into dedicated service method
- Adding unit tests specifically for layer settings inheritance scenarios
- Monitoring for edge cases in complex inheritance chains
Version: 0.6.5
Build: Production Ready
Deployment: Automatic via Railway
Database Changes: None
Breaking Changes: None