Changelog

EasyMesh Batch Exporter v1.6.1 🚀

📝 TLDR

v1.6.1 is a big game-pipeline release, headlined by three authoring features, a tidier settings layout, and a round of important FBX fixes:

• 🏷️ Naming Convention panel: prefix, suffix, and engine convention now live in their own collapsible panel with a single on/off toggle — enable it to apply your naming, switch it off to keep clean, untouched filenames
• 🧱 Custom collision meshes: parent a collision mesh to your render mesh and it is exported into the same file, renamed for your target engine (the most requested pipeline feature — discussion #13)
• 📍 Attachment points & slots: include empty children as named sockets so engines can bind weapons, props, and effects — with optional auto-generated slot empties
• 🛠️ FBX fixes: Forward/Up axis controls now actually work (#14), FBX imports into Unreal at the correct scale (no more 1/100, #9), and LOD hierarchies import as a single mesh with LODs instead of separate meshes (#12)
• ⚡ Faster exports: dense-mesh FBX export is dramatically faster, plus a new Fast triangulation option
• 📐 GLTF & STL scaling: the export scale setting is now respected (previously ignored)
• 🎛️ Consistent conventions: collision naming gains an explicit Convention field driven by the active preset, matching the file Naming Convention
• 🔄 Zero breaking changes to stored settings: new features are off/opt-in or default to sensible behaviour (see the upgrade notes about re-exporting FBX assets)

🎉 New Feature: Naming Convention Panel

Prefix, suffix, and engine naming — together in one place, with a single switch. File naming now has its own Naming Convention panel (just above Quick LODs), collapsible and with an enable/disable checkbox in its header — exactly like the Quick LODs and Collision Meshes panels.

🛠️ How It Works: Naming

• Toggle on (the default): the exporter applies your Prefix, Suffix, and the selected engine Convention (Godot / Unity / Unreal) to every exported filename.
• Toggle off: filenames are left as the object's own name (only cleaned of illegal characters) — no prefix, suffix, or convention applied.
• The active convention follows the preset selector at the top of the panel, so picking Godot, Unity, or Unreal sets the right naming for you.

🎯 Conventions

Heads-up: the old None / Default convention option has been replaced by the panel's on/off toggle. Switching the panel off is the new "no convention". As a result, prefix and suffix are part of the same feature — to use them, keep the Naming Convention panel enabled.

🎉 New Feature: Custom Collision Meshes

Export your hand-authored collision geometry alongside your assets. Creating custom collisions is a near-essential step in any game asset pipeline. Until now the exporter dropped them. v1.6.1 detects collision mesh children, renames them to your engine's convention, and packs them into the same FBX/glTF as the render mesh so the engine binds them automatically on import.

🛠️ How It Works: Collisions

1. Author your collision mesh in Blender and parent it to the render mesh (the same model the attachment-points feature uses).
2. Name the collision object with a shape prefix so the exporter can detect it and read its shape:
   • UCX_ → convex hull
   • UBX_ → box
   • USP_ → sphere
   • UCP_ → capsule
3. Enable Collision Meshes in the EasyMesh panel and pick a Convention.
4. Export your render mesh as usual — the collision is included automatically.

🎯 Collision Conventions

The convention is chosen explicitly and is set for you by the active preset: Godot → Godot, Unreal → Unreal, Unity → None (Unity has no engine-specific collision naming).

Note: Godot has no primitive collision shapes, so box/sphere/capsule sources are all exported as convex collisions.

🔍 Detection Options

• Prefixed Only (default): only children named UCX_/UBX_/USP_/UCP_ count as collisions, and the prefix sets the shape.
• All Children: every mesh child is treated as a convex collision.

✅ Works Everywhere

• Single export (one file per object)
• glTF batch / combine (Godot workflow — collisions combined into the one file)
• LOD hierarchy (Unreal LOD groups — collisions parented under the LOD group)

Selecting a collision object together with its parent no longer produces a stray standalone collision file — collisions are only ever written through their render mesh.

🎉 New Feature: Attachment Points & Slots

Mark sockets on your assets so engines can attach things to them. Game assets rarely live alone — a character needs weapon sockets, a vehicle needs mount points, a prop needs an effect anchor. v1.6.1 lets you author those locations as empty children of your render mesh and exports them into the same file, so the engine sees ready-made attachment points on import.

🛠️ How It Works: Attachment Points

1. Add an empty as a child of your render mesh and position it where you want the socket.
2. Enable *Include Attachment Points* in the EasyMesh panel (on by default).
3. Export as usual — the empties travel with the mesh in the same FBX/glTF.

🎯 Settings

Tip: Use Prefixed Only with attach_ to keep helper empties in your scene without exporting them — only the sockets you name end up in the file.

⚡ Performance & New Options

• 🚀 Much faster FBX export: axis and scale conversion is now pre-baked into the geometry with a fast, C-level transform, and the FBX exporter runs with neutral settings instead of re-baking every vertex itself. On dense meshes this is dramatically quicker, with identical output. (The LOD-hierarchy path keeps the exporter's own baking to preserve the LOD-group relationship.)
• ⏩ New "Fast" triangulation method: in addition to Beauty / Fixed / Shortest Diagonal, the new Fast option lets the format exporter triangulate during export rather than in a separate pass — much faster on high-poly and organic meshes.
  • Trade-off: it may slightly alter shading on non-planar quads (normals are recomputed rather than preserved), so Keep Normals is disabled when Fast is selected.
• 📐 GLTF & STL scaling: the export Scale setting is now applied to GLTF/USD and STL exports (via the object transform). Previously the scale value was silently ignored for these formats.

✨ Bug Fixes & Improvements

• 🐛 FBX Forward/Up axis now works (#14): the Forward/Up axis controls were a silent no-op — the conversion was only written to the FBX header, which importers ignore. The chosen axes are now baked into the geometry, so models import with the correct orientation.
• 🐛 Correct FBX scale in Unreal (#9): FBX files imported into Unreal at 1/100th scale because the scale lived only in the FBX header (which Unreal ignores). Scale is now baked into the geometry, so files import at the intended size.
• 🐛 LOD hierarchies import as a single mesh in Unreal (#12): the parent empty is now tagged as an FBX LodGroup, so Unreal imports one Static Mesh with LOD0…LODn instead of a pile of separate meshes. (The LOD group node is also renamed to a clean {ObjectName}.)
• 🐛 Attachment points in single-object mode: empties were silently dropped when exporting a single object (they only survived in batch/hierarchy modes). They are now included correctly in every mode.
• 🎛️ Standardised collision naming: the collision Engine Profile field is renamed Convention to match the file Naming Convention, and the old Auto value (which silently guessed the engine from your file naming) is gone in favour of an explicit, preset-driven choice.
• 🧪 New test coverage: validation for collision detection and per-convention naming, attachment-point handling, the naming-convention toggle, and FBX smoothing/scale regressions across all export paths.

📋 Compatibility & Upgrade Notes

• ✅ Blender 4.2.0+: fully supported (developed against 4.5/5.2)
• 🔄 Opt-in features: collision export and slot-empty generation are disabled by default; attachment points are on by default but are a no-op unless your mesh has empty children
• 🏷️ Naming feature defaults to on: prefix/suffix/convention behave as before for existing settings. The neutral "None / Default" convention is now the panel's off state — your stored prefix, suffix, and convention values are preserved either way.
• 📦 Formats: collisions and attachment points apply to FBX and glTF (the formats that carry a node hierarchy); other formats ignore those settings
• ♻️ Existing presets: already-saved built-in preset files won't carry the new collision Convention until you use Reset to Default on them (or reinstall); until then it simply defaults to None. Any preset that stored the removed AUTO collision value loads cleanly and falls back to None — no errors.
• ⚠️ FBX transforms change vs older versions: the axis (#14) and scale (#9) fixes mean FBX geometry is now baked with the correct orientation and size. If you have existing assets that compensated for the old (buggy) behaviour, re-export them so downstream scenes pick up the corrected transforms.
• 📐 GLTF/STL now honour Scale: if you previously relied on the export scale being ignored for these formats, your exports will now be scaled — set Scale to 1.0 to keep the old behaviour.

Thanks to PecakePie for the suggestion! Share your collision and naming workflows on GitHub Discussions, or report any issues here. 🙏

Changelog

EasyMesh Batch Exporter v1.5.0 🚀

📝 TLDR

v1.5.0 adds two major workflow features:

• Presets system: Save/load export configurations with built-in presets for Godot, Unity, and Unreal
• Custom presets: Create and share team export standards via JSON files
• glTF batch export: Combine multiple objects into a single file based on collection membership
• Zero breaking changes: All existing workflows remain unchanged

🎉 Major New Features

🎯 Presets System

Save and load your export configurations instantly

Speed up your workflow with ready-to-use presets for different game engines and projects. No more manually configuring dozens of settings each time you switch projects!

Built-In Game Engine Presets

Three preconfigured presets included:

• 🤖 Godot Preset:

  • glTF/GLB format with batch export enabled
  • Snake_case naming convention
  • Optimised material export for Godot's PBR workflow
  • Automatic triangulation and mesh smoothing

• 🎲 Unity Preset:

  • FBX format with embedded textures
  • Capitalised_Words_With_Underscores naming
  • Triangulation enabled for consistent rendering
  • Render modifiers applied automatically

• 🎯 Unreal Preset:

  • FBX format with LOD hierarchy support
  • PascalCase naming with prefix preservation
  • Optimised smoothing for Unreal's rendering pipeline
  • Forward axis configured for UE5 standards

Custom Preset Creation

• 💾 Save Your Settings: Create unlimited custom presets for specific projects or asset types
• ⚡ One-Click Loading: Switch between entire configurations instantly
• 📋 Project Templates: Perfect for teams maintaining consistent export standards
• 🔄 Version Control Friendly: Preset files are simple JSON for easy sharing via Git

🤖 glTF Batch Export (Godot Workflow)

Combine multiple objects into a single optimised file

Perfect for Godot developers who want clean, organised imports without dozens of individual files cluttering their project.

How It Works

• 📦 Smart Batching: Select multiple objects, export once, get a single glTF/GLB file
• 🏷️ Collection-Based Naming: Automatically names the file after the shared collection (e.g., "Trees" collection → trees.glb)
• 🎯 Individual Processing: Each object still gets full processing pipeline (modifiers, LODs, triangulation)
• 🔄 LOD Compatible: Generate LODs for each object and export everything together
• 💾 Memory Efficient: Reuses existing memory optimisation for large batches

Perfect For

• 🌳 Environment Assets: Export all trees, rocks, or props as single files
• 🏗️ Modular Buildings: Combine building parts into unified assets
• 🎮 Character Rigs: Export character with accessories as one file
• ⚡ Scene Assembly: Batch export complete scene sections for Godot

Why These Features Matter

⏱️ Massive Time Savings

• Switch from Godot to Unity workflow in one click instead of adjusting 20+ settings
• Export entire collections in seconds instead of tedious one-by-one exports
• Share team export standards via JSON presets instead of documentation

🎯 Zero-Configuration Workflows

• Godot preset + Batch mode = Production-ready assets in under 30 seconds
• Jump between game engines without memorising format requirements
• Consistent results across your entire team

🏗️ Professional Pipeline

• Version control your export configurations alongside your project
• Document export standards as shareable preset files
• Reduce human error with standardised configurations

🔧 Usage Examples

Quick Start with Presets

1. Select your objects in the 3D viewport
2. Open EasyMesh panel → Presets section
3. Click "Godot" preset (or Unity/Unreal)
4. Click "Export" - Done! ✅

Godot Batch Workflow

1. Organise objects into collections (e.g., "Trees", "Rocks")
2. Load "Godot" preset (enables batch mode automatically)
3. Select all objects in collection
4. Export → Single trees.glb file with all objects and LODs
5. Import into Godot and your scene tree is already organised!

Custom Preset for Your Studio

1. Configure all your preferred export settings once
2. Scroll to Presets section → Enter preset name (e.g., "Studio_Standard")
3. Click "Save Preset"
4. Share presets/Studio_Standard.json with your team via Git
5. Everyone loads the same preset - instant consistency! 🎯

Multi-Engine Projects

• Working on Unreal? Load "Unreal" preset
• Exporting reference for Unity? Load "Unity" preset
• Prototyping in Godot? Load "Godot" preset
• Same assets, different exports, zero reconfiguration

✨ Bug Fixes & Improvements

Fixes

• 🐛 Unreal Naming Convention: Fixed edge cases in PascalCase conversion handling Blender's default naming patterns
• 🧹 Code Quality: High, medium, and low priority fixes improving stability and performance
• 📝 Documentation: Updated README and added comprehensive ARCHITECTURE.md

Improvements

• 🎨 Better Defaults: Embed textures enabled by default for smoother FBX workflows
• 🔄 Alphabetical Organisation: Naming conventions now sorted alphabetically in UI
• 🧽 Metaball Smoothing: Enhanced auto-smooth application for metaball exports

📋 Compatibility & Upgrade Notes

• ✅ Blender 4.2.0+: All features fully supported
• 🔄 Zero Breaking Changes: Existing workflows continue unchanged
• 💾 Automatic Preset Creation: Built-in presets created automatically on first launch
• 📁 Preset Location: Find your presets in [addon]/presets/ directory

This release is all about workflow efficiency! Share your custom presets or workflow improvements on GitHub Discussions. Found a bug? Report it here. 🙏

Changelog

🎉 Major New Features

🎮 Game Engine Integration

Complete workflow optimisation for Unity, Unreal Engine, and Godot

Smart Naming Conventions

Choose from game engine specific naming standards that automatically format your exported files:

• 🎯 Unreal Engine: PascalCase naming (e.g., MyAwesomeMesh.fbx)
  • Preserves known prefixes like SM_, SK_, BP_
  • Handles version numbers correctly (e.g., Cube.2 → Cube2)
  • Fixed handling of Blender's default naming patterns
• 🎲 Unity: Capitalised_Words_With_Underscores (e.g., My_Awesome_Mesh.fbx)
• 🤖 Godot: snake_case naming (e.g., my_awesome_mesh.fbx)
• 📂 Default: Basic filename sanitisation only

LOD Hierarchy Export (FBX format only)

Export your objects with LOD levels as structured hierarchies perfect for Unity and Unreal Engine workflows:

• 🎯 Individual Processing: Each selected object gets its own LOD hierarchy (not merged)
• 📦 Structured Output: Creates {ObjectName}_LODGroup.fbx with parent empty containing all LOD levels
• 🔢 Proper Naming: LOD objects named as {basename}_LOD00, {basename}_LOD01, etc.
• 🎮 Game Engine Ready: Compatible with Unity and Unreal Engine LOD systems out-of-the-box
• ⚡ Same Pipeline: Each LOD follows the same processing pipeline as regular exports (modifiers, triangulation, etc.)

⚡ Geometry Nodes Optimisation

Enhanced support for complex procedural workflows

• 🔍 Smart Detection: Automatically detects objects using geometry nodes modifiers
• 💾 Preserve Data Layers: Maintains custom attributes and data from geometry nodes during export
• 🏗️ Instance Handling: Improved handling of collection instances often generated by geometry nodes
• 📊 Detailed Logging: Clear console messages when geometry nodes are being processed
• 🔧 Evaluation Pipeline: Uses Blender's evaluation system to properly bake geometry node results

🎨 Enhanced Metaball Support

• ✨ Auto-Smooth: Metaball exports now automatically apply smooth shading with 30° threshold
• 🧹 Cleaner Workflow: Improved cleanup of temporary conversion objects
• 🎯 Better Integration: Enhanced material preservation during metaball-to-mesh conversion

Performance Optimisations

• 🚀 Memory Efficiency: Enhanced memory management for large geometry node setups
• ⚡ Faster Processing: Optimised evaluation pipeline for complex procedural meshes
• 🔄 Progressive LODs: Maintains efficient progressive LOD building (faster and less memory used)

🎯 Why This Release Matters

v1.4.0 makes EasyMesh more specialised as a game development tool:

• 🎮 Zero-Configuration Game Engine Export: Choose your target engine and get perfectly formatted file names
• 🏗️ Professional LOD Workflows: Export LOD groups that import seamlessly into Unity/Unreal
• 🔧 Complex Asset Support: Handle the most sophisticated geometry node setups with confidence
• ⚡ Streamlined Pipeline: From Blender concept to game-ready asset in fewer steps

🔧 Usage Examples

Unreal Engine Workflow

1. Set naming convention to "Unreal Engine"
2. Enable "Export as Hierarchy" in LOD settings
3. Select objects like myCharacter.001, weapon.2
4. Get perfectly formatted: MyCharacter1_LODGroup.fbx, Weapon2_LODGroup.fbx

Geometry Nodes Assets

• Complex procedural meshes with custom attributes export seamlessly
• Console shows clear "geometry nodes - applying to mesh" confirmations
• All data layers and instances properly preserved

Multi-Engine Projects

• Switch between Godot (snake_case) and Unity (Capitalised_Words) naming
• Same LOD setup works across different target engines
• Consistent, professional file organisation

📋 Compatibility & Upgrade Notes

• ✅ Blender 4.2.0+: All features fully supported
• 🔄 Zero Breaking Changes: Existing workflows continue unchanged

This release represents months of refinement based on community feedback and real-world game development needs. Report issues or share your workflow on GitHub! 🙏

Changelog

🎉 What's New

glTF Export Enhancement

• Added Draco Compression toggle for glTF exports
  • Located under the "Compression" section when glTF format is selected
  • Disabled by default (optimal for Godot imports)
  • Enables Draco mesh compression for smaller file sizes when needed
  • Helpful note in tooltip about Godot's runtime compression

Why This Matters

Many users export to game engines like Godot, which have their own runtime compression systems. Having Draco compression enabled by default can actually be counterproductive in these cases. This update gives you control over when to use Draco compression, allowing you to optimise your exports for your specific workflow.

Technical Details

• New property: mesh_export_use_draco_compression (BoolProperty)
• UI label simplified to "Draco Compression" for cleaner interface
• Compression settings apply to both .glb and .gltf export formats

Compatibility

• Blender 4.2.0 and above
• No breaking changes from v1.3.0

I'd love to hear about your experience with the new features! Report issues or suggest improvements on GitHub. 🙏

Changelog

🎉 New Features

Export Curves and Metaballs as Meshes!

EasyMesh Batch Exporter now supports exporting Curve and Metaball objects, automatically converting them to meshes during the export process. This significantly expands the range of Blender objects you can batch export.

Curve Export

• Automatic Conversion: Curve objects (Bezier, NURBS, paths) are seamlessly converted to mesh format during export
• Modifier Support: All modifiers are properly applied during conversion
• LOD Generation: Full support for generating LODs from curve objects
• Material Preservation: Materials assigned to curves are maintained in the exported mesh

Metaball Export

• Smart Conversion: Metaballs are evaluated and converted to high-quality meshes
• Material Transfer: Materials from the original metaball are properly transferred to the exported mesh
• Clean Workflow: Temporary conversion objects are automatically cleaned up after export
• Full Integration: Works with all existing export formats (FBX, OBJ, GLTF, etc.)

Enhanced UI Feedback

The export button now provides context-aware labelling:

• "Export Meshes (3)" when selecting only mesh objects
• "Export Curves (2)" when selecting only curve objects
• "Export Metaballs (4)" when selecting only metaball objects
• "Export Objects (5)" when selecting mixed object types

This gives you instant clarity about what will be exported before clicking the button.

Why This Matters

Previously, users had to manually convert curves and metaballs to meshes before exporting, which was time-consuming and disrupted workflows. Now you can:

• Export architectural curves directly without manual conversion
• Batch export metaball-based organic models with ease
• Mix meshes, curves, and metaballs in a single export operation
• Maintain your non-destructive workflow right up to export

Technical Details

• Curves and metaballs are converted to mesh data using Blender's evaluation system
• Original objects remain untouched in your scene
• Conversion happens in memory for optimal performance
• Full support for all export settings including LODs, modifiers, and texture resizing

Upgrade Notes

• No breaking changes - all existing functionality remains unchanged
• Simply update to v1.3.0 to start exporting curves and metaballs
• Your existing export presets and workflows will continue to work perfectly

I'd love to hear about your experience with the new features! Report issues or suggest improvements on GitHub. 🙏

Changelog

🚀 Performance & Stability Update

Major Performance Improvement: Optimised Scaling for Large Meshes

Problem: Users reported crashes and extremely long export times when using scale values (especially scale: 100) with large meshes (1M+ polygons). The addon was applying scale transformations to all vertex data in memory before export, causing massive memory usage and potential crashes.

Solution:

• FBX, OBJ, STL formats: Scale is now passed directly to the export operators via global_scale parameter, avoiding memory-intensive vertex transformations
• GLTF, USD formats: Scale is disabled for these formats as they don't support global scaling and would require vertex transformation

Changes:

1. Memory Optimisation:

   • No longer applies scale transforms to mesh vertices for FBX, OBJ, STL
   • Significantly reduces memory usage for large meshes
   • Faster export times, especially with high scale values

2. Format-Specific Handling:

   • FBX, OBJ, STL: Full scale support via export operator parameters
   • GLTF, USD: Scale is ignored with warning message to prevent crashes

3. User Warnings:

   • Clear logging when scale is ignored for GLTF/USD formats
   • Users are advised to apply scale manually before export for these formats

Impact

• ✅ Prevents crashes when exporting large meshes with scale
• ✅ Significantly faster export times for scaled meshes
• ✅ Reduced memory usage during export
• ⚠️ GLTF and USD formats no longer support scale parameter (for stability)

Technical Details

• Modified setup_export_object() to return scale factor without applying transforms
• Updated export_object() to pass scale to export operators
• Added format-specific scale handling logic
• Improved memory management for large mesh operations

Bug Fix: Negative Axis Values for OBJ/STL/USD Export

Problem: When using negative axis values (e.g., "-Z" for forward or up axis), OBJ, STL, and USD exports would fail because these formats expect "NEGATIVE_Z" instead of "-Z".

Solution: Added automatic conversion of axis values for OBJ, STL, and USD formats:

• Converts "-X", "-Y", "-Z" to "NEGATIVE_X", "NEGATIVE_Y", "NEGATIVE_Z" respectively
• FBX format continues to use the original "-Z" format as expected
• No changes needed for positive axis values

Impact

• ✅ Fixed export failures when using negative axis orientations with OBJ/STL/USD
• ✅ Maintains compatibility with all export formats
• ✅ Seamless conversion happens automatically

This update prioritises stability and performance for users working with large meshes. If you need scaling for GLTF/USD formats, please apply the scale manually in Blender before export. I'd love to hear about your experience with the new features! Report issues or suggest improvements on GitHub. 🙏

Changelog

EasyMesh Batch Exporter v1.2.1

🐛 Bug Fix Release

Fixed: Package Size Issue

Problem: Previous releases were inadvertently including the entire releases/ directory in the addon package, causing unnecessarily large file sizes. Each new release was packaging all previous releases within it, creating a compounding size issue.

Solution: Updated the build configuration to properly exclude development and release files from the final package.

Technical Details

• Added paths_exclude_pattern to blender_manifest.toml
• Now excludes: releases/, .git/, .github/, pycache/, and other development files
• Result: Package size reduced by ~80%

No functionality changes, this is purely a packaging fix. If you have v1.2.0 installed and working, there's no need to update unless the file size was causing issues.

Thank you to all users for your feedback and suggestions! I'd love to hear about your experience with the new features! Report issues or suggest improvements on GitHub. 🙏

Changelog

EasyMesh Batch Exporter v1.2.0

🎨 Texture Optimisation & UI Improvements

This release brings powerful texture management features and UI refinements to make your export workflow even smoother.

✨ New Features

Texture Optimisation

• Aspect Ratio Preservation: Textures now maintain their original proportions during resizing, preventing distortion
• Smart Format Detection: Automatically preserves appropriate formats (PNG for alpha, JPEG for RGB, HDR for high dynamic range)
• Customisable LOD Texture Sizes: Full control over texture dimensions for each LOD level (8K down to 128px)
• Normal Map Quality Preservation: Option to keep normal maps at one LOD level higher resolution
• Compression Quality Control: Adjustable quality setting for lossy formats (0-100%)
• Intelligent Resizing: Prevents upscaling of textures already smaller than target size

Texture Export Preview Panel

• New collapsible "Texture Export Preview" sub-panel
• Accurate file size estimations based on actual compression ratios
• Shows both uncompressed and compressed sizes
• Format-aware calculations (different for JPEG vs PNG)
• Dynamic unit display (KB/MB) for better readability

🔧 Improvements

UI/UX Enhancements

• Export Indicators Toggle: Moved to Recent Exports panel header for cleaner interface
• Auto-Clear Indicators: Unchecking the toggle immediately clears all viewport indicators
• Better Terminology: "JPEG Quality" renamed to "Compression" for accuracy
• Smarter Panel Organisation: Texture preview positioned to minimise UI disruption

Technical Improvements

• More accurate texture size calculations using realistic compression ratios
• Memory-efficient texture processing during export
• Better handling of various texture formats and colour spaces
• Improved texture file naming with LOD suffixes

📊 Texture Size Estimation Accuracy

• Before: Estimates could be off by 10-100x (e.g., 11MB estimated vs 125KB actual)
• After: Estimates now within 20% of actual file sizes

🐛 Bug Fixes

• Fixed texture resizing for non-square textures
• Corrected alpha channel detection for various image formats
• Resolved issues with texture path references during export

📝 Notes

• Texture optimisation features are fully compatible with Unreal Engine's texture streaming system
• All texture modifications are non-destructive (original files remain unchanged)
• The addon now provides professional-grade control over texture optimisation

Thank you to all users for your feedback and suggestions! I'd love to hear about your experience with the new features! Report issues or suggest improvements on GitHub. 🙏

Changelog

Overview

Significant performance improvements and new user controls that make working with large, complex meshes a breeze.

What's New

Large Mesh Optimisation

Finally, export those massive 2+ million polygon meshes without crashes! This update introduces intelligent memory management that automatically detects and optimises for large meshes:

• Automatic detection at 500K and 1M polygon thresholds
• Progressive memory cleanup every 3 modifiers during processing
• Smart garbage collection to prevent memory exhaustion
• Enhanced logging with formatted polygon counts (e.g., "1,250,000 polygons")

Modifier Control System

Take complete control over which modifiers are applied during export with a three-mode system:

• None - Skip all modifiers for fastest export (perfect for base mesh exports)
• Visible - Apply only viewport-visible modifiers (default, recommended)
• Render - Apply render-enabled modifiers (most complete export)

Export Indicators Toggle

New checkbox to enable/disable viewport colour feedback:

• Cleaner viewport when colour accuracy matters
• Better performance by disabling timer overhead when not needed
• Smart behaviour - Recent Exports panel automatically hides when disabled

💡 Performance Tips

For best results with large meshes:

• Use "None" modifier mode for meshes over 1M polygons
• Close other applications to maximise available memory
• Monitor console output for "Memory optimisation" messages
• Export in smaller batches when working with multiple large objects

🔧 Technical Improvements

• Immediate geometry clearing for faster memory release
• Enhanced error handling throughout the export pipeline
• Pre-export optimisation for large mesh operations
• Improved UI layout with new control sections

📊 Compatibility

• Blender: 4.2.0 and above
• Backwards compatible: Existing projects work without changes
• All export formats: FBX, OBJ, glTF, USD, STL

🙏 Acknowledgements

Special thanks to the people who reported issues with large mesh exports and provided valuable feedback on modifier handling workflows.

💬 Feedback

I'd love to hear about your experience with the new features! Report issues or suggest improvements on GitHub.

Changelog

Overview

v1.0.4 brings several improvements to the export functionality and user interface, with a focus on enhanced GLTF support and interface refinements.

What's New

Enhanced Export Options

• Added GLTF-specific properties for more control over your exports:
  • Choose between binary (.glb) or JSON (.gltf) format types
  • Option to export materials or use placeholders

Export Improvements

• Fixed unit handling: Prevented scaling and unit settings from applying when exporting to GLTF or USD formats
• Streamlined transformation workflow: Created a unified apply_transforms function to handle location, rotation, and scale transformations

Bug Fixes

• Resolved AttributeError that occurred when clicking the selection button in the Recent Exports panel

Interface Enhancements

• Improved zero location option: Added appropriate title to the zero location transform option
• Updated unit display: Now using lowercase letters for units (m and cm) throughout the interface
• Simplified triangulation options: Merged triangulate checkbox and method selection into a single line for a cleaner interface

Developer Notes

Thank you for using EasyMesh! Your feedback and suggestions are always welcome. As always, please report any issues on the GitHub repository.

Changelog

Bug Fixes

• Export Scaling Improvements: Fixed issues with object scale handling during export. The exporter now correctly applies scale transformations before export.
• Improved Object Duplication: Now using duplicate_move_linked with proper mesh data handling to ensure cleaner exports without affecting original objects.
• Mesh Data Management: Objects now have their mesh data made "single user" during the export process, preventing unintended modifications to linked meshes.

New Features

Units Control

• Added support for selecting export units (metres or centimetres)
• This makes integration with game engines easier, especially for those using centimetre-based workflows

Enhanced FBX Export Options

• Added smoothing controls for FBX exports with three options:
  • Face: Standard face smoothing
  • Edge: Edge-based smoothing for better control
  • Off: Export only normals without smoothing data

Symmetry-Aware LOD Generation

• Added symmetry options for LOD generation to maintain model balance
• Choose symmetry axis (X, Y or Z) to preserve model structure during decimation
• Creates lower-poly models that maintain visual quality along the symmetry plane
• Particularly useful for character models, vehicles, and architectural elements

Developer Notes

Thank you for trying EasyMesh Batch Exporter. These improvements should make the export workflow smoother and provide more control over your exports. As always, please report any issues on the GitHub repository.

Changelog

Bug Fixes

• Property Registration Fix: Resolved critical issue with registration of properties that was causing the add-on to completely break after introducing MeshExporterSettings(PropertyGroup) class
• Add-on Stability: Restored full functionality to all features that were impacted by the property registration bug

Impact

This update resolves a critical issue that prevented the add-on from working properly. Users who experienced crashes or broken functionality should now be able to:

• Export meshes without errors
• Access all settings through the UI panel
• Use all features including LOD generation and export indicators

Sorry for the inconvenience! If you encounter any issues with this release, please report them on our GitHub issue tracker.

Changelog

Bug Fixes

• Export Indicators Expiration: Fixed the colour-coding system for exported objects
  • Exported objects now reliably marked as green for 1 minute
  • Then yellow for 4 minutes
  • Finally return to their original colour and are removed from the recent exports list

Performance Improvements

• Enhanced performance by:
  • Replacing bpy.ops with context.scene.objects
  • Reducing mode switching operations

Maintenance

• Cleaned up the Blender manifest file

Changelog

First release