Skip to content

Releases: invoke-ai/InvokeAI

v4.2.5

27 Jun 01:38
Compare
Choose a tag to compare
v4.2.5 Pre-release
Pre-release

🚨 macOS users may get black images when using LoRAs or IP Adapters. Users with CUDA GPUs may get unexpected OOMs. We are investigating. 🚨

v4.2.5 includes a handful of fixes and improvements, plus one exciting beta node - tiled upscaling via MultiDiffusion.

If you missed v4.2.0, please review its release notes to get up to speed on Control Layers.

Tiled Upscaling via MultiDiffusion

MultiDiffusion is a fairly straightforward technique for tiled denoising. The gist is similar to other tiled upscaling methods - split the input image up in to tiles, process each independently, and stitch them back together. The main innovation for MultiDiffusion is to do this in latent space, blending the tensors together continually. This results in excellent consistency across the output image, with no seams.

This feature is exposed as a Tiled MultiDiffusion Denoise Latents node, currently classified as a beta version. It works much the same as the OG Denoise Latents node. Here's a workflow to get you started: sd15_multi_diffusion_esrgan_x2_upscale.json

image

We are still thinking about to expose this in the linear UI. Most likely, we expose this with very minimal settings. If you want to tweak it, use the workflow.

How to use it

This technique is fundamentally the same as normal img2img. Appropriate use of conditioning and control will greatly improve the output. The one hard requirement is to use the Tile ControlNet model.

Besides that, here are some tips from our initial testing:

  • Use a detail-adding or style LoRAs.
  • Use a base model best suited for the desired output style.
  • Prompts make a difference.
  • The initial upscaling method makes a difference.
  • Scheduler makes a difference. Some produce softer outputs.

VRAM Usage

This technique can upscale images to very large sizes without substantially increasing VRAM usage beyond what you'd see for a "normal" sized generation. The VRAM bottlenecks then become the first VAE encode (Image to Latents) and final VAE decode (Latents to Image) steps.

You may run into OOM errors during these steps. The solution is to enable tiling using the toggle on the Image to Latents and Latents to Image nodes. This allows the VAE operations to be done piecewise, similar to the tiled denoising process, without using gobs of VRAM.

There's one caveat - VAE tiling often introduces inconsistency across tiles. Textures and colors may differ from tile to tile. This is a function of the diffusers handling of VAE tiling, not the tiled denoising process introduced in v4.2.5. We are investigating ways to improve this.

Takeaway: If your GPU can handle non-tiled VAE encode and decode for a given output size, use that for best results.

📈 Patch Nodes for v4.2.5

Enhancements

  • When downloading image metadata, graphs or workflows, the JSON file includes the image name and type of data. Thanks @jstnlowe!
  • Add clear_queue_on_startup config setting to clear problematic queues. This is useful for a rare edge case where your queue is full of items that somehow crash the app. Set this to true, and the queue will clear before it has time to attempt to execute the problematic item. Thanks @steffy-lo!
  • Performance and memory efficiency improvements for LoRA patching and model offloading.
  • Addition of a simplified model installation methods to the Invocation API: download_and_cache_model, load_local_model and load_remote_model. These methods allow models to be used without needing them to be added to the model manager. For example, we are now using these methods to load ESRGAN models.
  • Support for probing and loading SDXL VAE checkpoint.

Fixes

  • Fix handling handling of 0-step denoising process.
  • If a control image's processed version is missing when the app loads, it is now re-processed.

Performance improvements

  • Improved LoRA patching.
  • Improved RAM <-> VRAM model transfer performance.

Internal changes

  • The DenoiseLatentsInvocation has had its internal methods split up to support tiled upscaling via MultiDiffusion. This included some amount of file shuffling and renaming. The invokeai package's exported classes should still be the same. Please let us know if this has broken an import for you.

💾 Installation and Updating

To install or update to v4.2.5, download the installer and follow the installation instructions.

To update, select the same installation location. Your user data (images, models, etc) will be retained.

Missing models after updating from v3 to v4

See this FAQ.

Error during installation ModuleNotFoundError: No module named 'controlnet_aux'

See this FAQ

What's Changed

New Contributors

Full Changelog: v4.2.4...v4.2.5

v4.2.4

04 Jun 23:43
Compare
Choose a tag to compare

v4.2.4 brings one frequently requested feature and a host of fixes and improvements, mostly focused on performance and internal code quality.

If you missed v4.2.0, please review its release notes to get up to speed on Control Layers.

Image Comparison

The image viewer now supports comparing two images using a Slider, Side-by-Side or Hover UI.

To enter the comparison UI, select a compare image using one of these methods:

  • Right click an image and click Select for Compare.
  • Hold alt (option on mac) while clicking a gallery image to select it as the compare image.
  • Hold alt (option on mac) and use the arrow keys to select the comparison image.

Press C to swap the images and M to cycle through the comparison modes. Press Escape or Z to exit the comparison UI and return to the single image viewer.

When comparing images of different aspect ratios or sizes, the compare image will be stretched to fit the viewer image. Disable the toggle button at the top-left to instead contain the compare image within the viewer image.

Screen.Recording.2024-06-05.at.9.26.00.am.mov

📈 Patch Nodes for v4.2.4

Enhancements

Fixes

  • Fixed problem when using a latents from the blend latents node for denoising with certain schedulers which made images drastically different, even with an alpha of 0.
  • Fixed unnecessarily strict constraints for ControlNet and IP Adapter weights in the Control Layers UI. This prevented layers with weights outside the range of 0-1 from recalling.
  • Fixed error when editing non-main models (e.g. LoRAs).
  • Fixed the SDXL prompt concat flag from not being set when recalling prompts.
  • Fixed model metadata recall not working when a model has a different key. This can happen if the model was uninstalled and reinstalled. When recalling, we fall back on the model's name, base and type, if the key doesn't match an existing model.

Performance improvements

Big thanks to @lstein for these very impactful improvements!

  • Substantially improved performance when moving models between RAM and VRAM. For example, an SDXL model RAM -> VRAM -> RAM roundtrip tested at ~0.8s, down from ~3s. That's about 75% faster!
  • Fixed bug with VRAM lazy offloading which caused inefficient VRAM cache usage.
  • Reduced VRAM requirements when using IP Adapter.

Internal changes

  • Modularize the queue processor.
  • Use pydantic models for events instead of plain dicts.
  • Improved handling of pydantic invocation unions.
  • Updated ML dependencies. @Malrama

💾 Installation and Updating

To install or update to v4.2.4, download the installer and follow the installation instructions.

To update, select the same installation location. Your user data (images, models, etc) will be retained.

Missing models after updating from v3 to v4

See this FAQ.

Error during installation ModuleNotFoundError: No module named 'controlnet_aux'

See this FAQ

What's Changed

New Contributors

Full Changelog: v4.2.3...v4.2.4

v4.2.3

23 May 22:27
Compare
Choose a tag to compare

If you missed v4.2.0, please review its release notes to get up to speed on Control Layers.

📈 Patch Nodes for v4.2.3

  • Spellcheck is re-enabled on prompt boxes

  • DB maintenance script removed from launcher (it currently does not work)

  • Reworked toasts. When a toast of a given type is triggered, if another toast of that type is already being displayed, it is updated instead of creating another toast. The old behaviour was painful in situations where you queue up many generations that all immediately fail, or install a lot of models at once. In these situations, you'd get a wall of toasts. Now you get only 1.

  • Fixed: Control layer checkbox correctly indicates that it enables or disables the layer

  • Fixed: Disabling Regional Guidance layers didn't work

  • Fixed: Excessive warnings in terminal when uploading images

  • Fixed: When loading a workflow, if an image, board or model for an input for that workflow no longer exists, the workflow will execute but error.

    For example, say you save a workflow that has a certain model set for a node, then delete the model. When you load that workflow, the model is missing but the workflow doesn't detect this. You can run the workflow, and it will fail when it attempts to use the nonexistent model.

    With this fix, when a workflow is loaded, we check for the existence of all images, boards and models referenced by the workflow. If something is missing, that input is reset.

  • Docs updates @hsm207

  • Translations updates @gallegonovato @Harvester62 @dvanzoerlandt

💾 Installation and Updating

To install or update to v4.2.3, download the installer and follow the installation instructions.

To update, select the same installation location. Your user data (images, models, etc) will be retained.

Missing models after updating from v3 to v4

See this FAQ.

What's Changed

Full Changelog: v4.2.2post1...v4.2.3

v4.2.2post1

21 May 02:49
aa0c59b
Compare
Choose a tag to compare

This release brings many fixes and enhancements, including two long-awaited features: undo/redo in workflows and load workflow from any image.

If you missed v4.2.0, please review its release notes to get up to speed on Control Layers.

📈 Patch Nodes for v4.2.2post1

v4.2.2 had a critical bug related to notes nodes & missing templates in workflows. That is fixed in v4.2.2post1.

✨ Undo/redo in Workflows

Undo/redo redo now available in the workflow editor. There's some amount of tuning to be done with how actions are grouped.

For example, when you move a node around, do we allow you to undo each pixel of movement, or do we group the position changes as one action? When you are typing a prompt, do we undo each letter, word, or the whole change at once?

Currently, we group like changes together. It's possible some things are grouped when they shouldn't be, or should be grouped but are not. Your feedback will be very useful in tuning the behaviour so it un-does the right changes.

✨ Load Workflow from Any Image

Starting with v4.2.2, graphs are embedded in all images generated by Invoke. Images generated in the workflow editor also have the enriched workflow embedded separately. The Load Workflow button will load the enriched workflow if it exists, else it will load the graph.

You'll see a new Graph tab in the metadata viewer showing the embedded graph.

Graph vs Workflow

Graphs are used by the backend and contain minimal data. Workflows are an enrich data format that includes a representation of the graph plus extra information, including things like:

  • Title, description, author, etc
  • Node positions
  • Custom node and field labels

This new feature embeds the graph in every image - including images generated on the Generation or Canvas tabs.

Canvas Caveat

This functionality is available only for individual canvas generations - not the full composition. Why is that?

Consider what goes into a full canvas composition. It's the product of any number of graphs, with any amount of drawing and erasing between each graph execution. It's not possible to consolidate this into a single graph.

When you generate on canvas, your images for the given bounding box are added to a staging area, which allows you to cycle through images and commit or discard the image. The staging area also allows you to save a candidate generation. It is these images that can be loaded as a workflow, because they are the product of a single graph execution.

👷 Other Fixes and Enhancements

  • Min/max LoRA weight values extended (-10 to +10) @H0onnn
  • Denoising strength and layer opacity are retained when sending image to initial image @steffy-lo
  • SDXL T2I Adapter only blocks invoking when dimensions aren't multiple of 32 (was erroneously 64)
  • Improved UX when manipulating edges in workflows
  • Connected inputs on nodes collapse, hiding the nonfunctional UI component
  • Use ctrl/cmd-shift-v to paste copied nodes with input edges
  • Docs updates @hsm207
  • Fix: visible seams when outpainting
  • Fix: edge case that could prevent workflows from loading if user hadn't opened the workflows tab yet
  • Fix: minor jank/inefficiency with control adapter auto-process (control layers only)
  • Internal: utility to create graph objects without going crazy
  • Internal: rewritten connection validation logic for workflows with full test coverage
  • Internal: rewritten edge connection interactions
  • Internal: revised field type format

💾 Installation and Updating

To install or update to v4.2.2post1, download the installer and follow the installation instructions.

To update, select the same installation location. Your user data (images, models, etc) will be retained.

Missing models after updating from v3 to v4

See this FAQ.

What's Changed

New Contributors

Full Changelog: v4.2.1...v4.2.2post1

v4.2.2

20 May 22:26
Compare
Choose a tag to compare

This release brings many fixes and enhancements, including two long-awaited features: undo/redo in workflows and load workflow from any image.

If you missed v4.2.0, please review its release notes to get up to speed on Control Layers.

📈 Patch Nodes for v4.2.2

✨ Undo/redo in Workflows

Undo/redo redo now available in the workflow editor. There's some amount of tuning to be done with how actions are grouped.

For example, when you move a node around, do we allow you to undo each pixel of movement, or do we group the position changes as one action? When you are typing a prompt, do we undo each letter, word, or the whole change at once?

Currently, we group like changes together. It's possible some things are grouped when they shouldn't be, or should be grouped but are not. Your feedback will be very useful in tuning the behaviour so it un-does the right changes.

✨ Load Workflow from Any Image

Starting with v4.2.2, graphs are embedded in all images generated by Invoke. Images generated in the workflow editor also have the enriched workflow embedded separately. The Load Workflow button will load the enriched workflow if it exists, else it will load the graph.

You'll see a new Graph tab in the metadata viewer showing the embedded graph.

Graph vs Workflow

Graphs are used by the backend and contain minimal data. Workflows are an enrich data format that includes a representation of the graph plus extra information, including things like:

  • Title, description, author, etc
  • Node positions
  • Custom node and field labels

This new feature embeds the graph in every image - including images generated on the Generation or Canvas tabs.

Canvas Caveat

This functionality is available only for individual canvas generations - not the full composition. Why is that?

Consider what goes into a full canvas composition. It's the product of any number of graphs, with any amount of drawing and erasing between each graph execution. It's not possible to consolidate this into a single graph.

When you generate on canvas, your images for the given bounding box are added to a staging area, which allows you to cycle through images and commit or discard the image. The staging area also allows you to save a candidate generation. It is these images that can be loaded as a workflow, because they are the product of a single graph execution.

👷 Other Fixes and Enhancements

  • Min/max LoRA weight values extended (-10 to +10) @H0onnn
  • Denoising strength and layer opacity are retained when sending image to initial image @steffy-lo
  • SDXL T2I Adapter only blocks invoking when dimensions aren't multiple of 32 (was erroneously 64)
  • Improved UX when manipulating edges in workflows
  • Connected inputs on nodes collapse, hiding the nonfunctional UI component
  • Use ctrl/cmd-shift-v to paste copied nodes with input edges
  • Docs updates @hsm207
  • Fix: visible seams when outpainting
  • Fix: edge case that could prevent workflows from loading if user hadn't opened the workflows tab yet
  • Fix: minor jank/inefficiency with control adapter auto-process (control layers only)
  • Internal: utility to create graph objects without going crazy
  • Internal: rewritten connection validation logic for workflows with full test coverage
  • Internal: rewritten edge connection interactions
  • Internal: revised field type format

💾 Installation and Updating

To install or update to v4.2.2, download the installer and follow the installation instructions.

To update, select the same installation location. Your user data (images, models, etc) will be retained.

Missing models after updating from v3 to v4

See this FAQ.

What's Changed

New Contributors

Full Changelog: v4.2.1...v4.2.2

v4.2.1

13 May 22:34
e222484
Compare
Choose a tag to compare

This patch release brings a handful of fixes, plus docs and translation updates.

If you missed v4.2.0, please review its release notes to get up to speed on Control Layers.

📈 Patch Nodes for v4.2.1

  • Fixed seamless not being perfectly seamless sometimes
  • Fixed Control Adapter processor cancellation jank
  • Fixed Depth Anything processor drop-down jank
  • Fixed Control Adapter layers preventing interactions with layers below them (e.g. cannot move a Regional Guidance layer)
  • Fixed two issues with model cover images
    • When editing a model, the cover image disappeared, but reappeared on refresh
    • When converting a model to diffusers, the cover image was lost forever
  • Fixed NSFW checker for new installs
  • Prevent errors when using T2I adapter
    • May not invoke when image dimensions are not a multiple of 64
    • Control Adapter model select differentiates between ControlNet and T2I Adapter models
    • Reworked Invoke button tooltip describing why you may not Invoke when there is a configuration issue
  • Fixed translations for canvas layer select
  • Fixed Invoke button not showing loading state while queuing
  • Docs update @gogurtenjoyer
  • Translation updates @Harvester62 @Vasyanator @Pfannkuchensack @flower-elf @gallegonovato

💾 Installation and Updating

To install or update to v4.2.1, download the installer and follow the installation instructions.

To update, select the same installation location. Your user data (images, models, etc) will be retained.

Missing models after updating from v3 to v4

See this FAQ.

What's Changed

Full Changelog: v4.2.0...v4.2.1

v4.2.0

09 May 13:17
Compare
Choose a tag to compare

Since the very beginning, Invoke has been innovating where it matters for creatives. Today, we're excited to do it again with Control Layers.

Invoke 4.2 brings a number of enhancements and fixes, with the addition of a major new feature - Control Layers.

🧪 Control Layers

Integrating some of the latest in open-source research, creatives can use Control Adapters, Image Prompts, and regional guidance to articulate and control the generation process from a single panel. With regional guidance, you can compose specific regions to apply a positive prompt, negative prompt, or any number of IP Adapters to be applied to the masked region. Control Adapters (ControlNet & T2I Adapters) and an Initial Image are visualized on the new Control Layers canvas.

You can read more about how to use Control Layers here - Control Layers

📈 Patch Nodes for v4.2.0

Enhancements

  • Control Layers
  • Add TCD scheduler @l0stl0rd
  • Image Viewer updates -- You can easily switch to the Image Viewer on the Generations tab by tapping the Z hotkey, or double clicking on any image in the gallery.

Major Changes

Also known as the "who moved my 🧀?" section, this list details where certain features have moved.

  • Image to Image: The Image to Image pipeline can be executed using Control Layers by adding an Initial Image layer.
  • Control Adapters and IP Adapters: These have been moved to the Control Layers tab -- with the added benefit of being able to visualize your control adapter's processed images easily!

Fixes

  • Fixed inpainting models on canvas @dunkeroni
  • Fixed IP Adapter starter models
  • Fixed bug where temp files (tensors, conditioning) aren't cleaned up properly
  • Fixed trigger phrase form submit @joshistoast
  • Fixed SDXL checkpoint inpainting models not installing
  • Fixed installing models on external SSDs on macOS
  • Fixed Control Adapter processors' image size constraints being overly restrictive

💾 Installation and Updating

To install or update to v4.2.0, download the installer and follow the installation instructions.

To update, select the same installation location. Your user data will not be touched.

Missing models after updating from v3 to v4

See this FAQ.

What's Changed

New Contributors

Full Changelog: v4.1.0...v4.2.0

v4.2.0b2

06 May 23:42
Compare
Choose a tag to compare
v4.2.0b2 Pre-release
Pre-release

This is a beta release. There may be some hiccups, but overally, it is purring along nicely.

Changes since v4.2.0b1

  • Control Layer masks are cached, reducing time spent outside denoising.
  • Fixed viewer getting stuck when spamming the toggle hotkey
  • Fixed viewer show/hide logic
  • Viewer button more obviously a button
  • Do not run HRO when using an initial image
  • Fixed next/prev buttons getting stuck
  • Fixed upscaling while on canvas tab saves to gallery
  • Snap to canvas bounds with rect tool
  • Perf enhancements in control layers canvas
  • Settings/Control Layers tabs look like tabs
  • Close viewer when adding RG layer
  • Fix auto-switch to viewer on new image
  • Control Layers tab now shows total layer count, not just "valid" layer count
  • Internal: bump all UI deps

🧪 Control Layers

Control Layers give you control over specific areas of the image. Draw a mask and set a positive prompt, negative prompt, or any number of IP Adapters to be applied to the masked region. Control Adapters (ControlNet & T2I Adapters) and the Initial Image are visualized on the canvas.

Full documentation to be included with the full release.

Your feedback is greatly appreciated as we continue to iterate on Control Layers.

❗ Updating from v4.2.0a4

You may get a white screen on first launch, if you were testing the alpha release. This won't be a problem for users updating from the last stable release (v4.1.0). If you encounter this, follow these steps to reset the browser storage:

  • Start the app and get to the blank screen
  • Open your browser's dev tools
  • Open the JS console
  • Paste and run this command to delete the browser storage: indexedDB.deleteDatabase('invoke')
  • Refresh the page

📈 Patch Nodes for v4.2.0

Enhancements

  • Control Layers
  • Add TCD scheduler @l0stl0rd
  • Image viewer updates

Fixes

  • Fixed inpainting models on canvas
  • IP Adapter starter models fixed
  • Fixed bug where temp files (tensors, conditioning) aren't cleaned up properly
  • FIxed trigger phrase form submit @joshistoast
  • Fixed SDXL Checkpoint Inpainting models
  • Fixed installing models on external SSDs on macOS
  • Fixed Control Adapter processors' image size constraints

💾 Installation and Updating

To install or update to v4.2.0b2, download the installer and follow the installation instructions.

To update, select the same installation location. Your user data will not be touched.

Missing models after updating from v3 to v4

See this FAQ.

What's Changed

Full Changelog: v4.2.0b1...v4.2.0b2

v4.2.0b1

03 May 03:47
Compare
Choose a tag to compare
v4.2.0b1 Pre-release
Pre-release

This is a beta release. There may be some hiccups, but overally, it is purring along nicely.

Changes since v4.2.0a4

  • Initial image support in Control Layers, no more dedicated tab
  • Tabs renamed to Generation, Canvas, Workflows, Models and Queue
  • Refactored internal handling of control layers, which fixes all reported UI errors
  • T2I Adapter support in Control Layers
  • FF v125 bug fixed
  • Add TCD scheduler @l0stl0rd
  • Image viewer updates
  • Fixed Control Adapter processors' image size constraints
  • Metadata recall for Control Layers
  • Many small and not-particularly-memorable bugfixes

🧪 Control Layers

Control Layers give you control over specific areas of the image. Draw a mask and set a positive prompt, negative prompt, or any number of IP Adapters to be applied to the masked region. Control Adapters (ControlNet & T2I Adapters) and the Initial Image are visualized on the canvas.

Full documentation to be included with the full release.

Your feedback is greatly appreciated as we continue to iterate on Control Layers.

🐛 Known Issues

  • The viewer stays open after using Send to Image to Image, Send to Unified Canvas, and doing anything that adds a layer.
  • If you spam the viewer button (or hold down the hotkey z), it can get stuck. If you run into this, you'll need to reset the UI to fix it. This will be fixed in the next release.

❗ Updating from v4.2.0a4

You may get a white screen on first launch, if you were testing the alpha release. This won't be a problem for users updating from the last stable release (v4.1.0). If you encounter this, follow these steps to reset the browser storage:

  • Start the app and get to the blank screen
  • Open your browser's dev tools
  • Open the JS console
  • Paste and run this command to delete the browser storage: indexedDB.deleteDatabase('invoke')
  • Refresh the page

📈 Patch Nodes for v4.2.0

Enhancements

  • Control Layers
  • Add TCD scheduler @l0stl0rd
  • Image viewer updates

Fixes

  • Fixed inpainting models on canvas
  • IP Adapter starter models fixed
  • Fixed bug where temp files (tensors, conditioning) aren't cleaned up properly
  • FIxed trigger phrase form submit @joshistoast
  • Fixed SDXL Checkpoint Inpainting models
  • Fixed installing models on external SSDs on macOS
  • Fixed Control Adapter processors' image size constraints

💾 Installation and Updating

To install or update to v4.2.0b1, download the installer and follow the installation instructions.

To update, select the same installation location. Your user data will not be touched.

Missing models after updating from v3 to v4

See this FAQ.

What's Changed

New Contributors

Full Changelog: v4.2.0a4...v4.2.0b1

v4.2.0a4

30 Apr 20:46
Compare
Choose a tag to compare
v4.2.0a4 Pre-release
Pre-release

This is an alpha release. We suggest backing up your database in case there are any issues and you need to roll back.

Changes since v4.2.0a3

  • "Regional Control" -> "Control Layers"
  • Control Adapters supported in Control Layers
  • Updates to Control Layers UI
  • Fixed SDXL Checkpoint Inpainting models
  • Fixed installing models on external SSDs on macOS

🧪 Control Layers

Control Layers give you control over specific areas of the image. Draw a mask and set a positive prompt, negative prompt, or any number of IP Adapters to be applied to the masked region. Control Adapters (ControlNet & T2I Adapters) are visualized on the canvas.

Full documentation to be included with the full release.

Your feedback is greatly appreciated as we continue to iterate on Control Layers.

🐛 Known Issues

These issues will be fixed for the full release.

  • If you undo after deleting a Regional Guidance layer's IP Adapter, Global IP Adapter layer, or Global Control Adapter Layer, the UI may error. You'll just need to click Reset if this happens.
  • There is a bug on Firefox v125 that causes very poor performance in the Control Layers canvas. This is not an issue for Firefox v126 Developer Edition. Other versions of Firefox have not been tested.
  • T2I Adapters are not supported in Control Layers.

📈 Patch Nodes for v4.2.0

Enhancements

  • Control Layers

Fixes

  • Fixed inpainting models on canvas
  • IP Adapter starter models fixed
  • Fixed bug where temp files (tensors, conditioning) aren't cleaned up properly
  • FIxed trigger phrase form submit @joshistoast
  • Fixed SDXL Checkpoint Inpainting models
  • Fixed installing models on external SSDs on macOS

💾 Installation and Updating

To install or update to v4.2.0a4, download the installer and follow the installation instructions.

To update, select the same installation location. Your user data will not be touched.

Missing models after updating from v3 to v4

See this FAQ.

What's Changed

Full Changelog: v4.2.0a3...v4.2.0a4