Voxel Plugin
1.2 Legacy
2.0p52.0p42.0p22.0p12.0p-3402.0p-3202.0p-3172.0p-3041.2 Legacy
1.2 Legacy
2.0p52.0p42.0p22.0p12.0p-3402.0p-3202.0p-3172.0p-3041.2 Legacy
  • Getting Started
    • Quick Start
      • Examples
    • World Generation
      • C++ World Generators
      • Voxel Graph Quick Start
      • Floating Islands
  • Core Systems
    • VoxelWorlds
      • Import Content
      • Voxel Data Items
      • Collisions and Navmesh
      • World Size and Level Of Details
      • Save and Load
      • Multiplayer
      • Easy Systems RPG
    • Voxel Graphs
      • Voxel Graph General Concepts
      • Voxel Graphs Tips and Tricks
      • Voxel Graph Nodes Reference
      • Voxel Graph Outputs
      • Voxel Graph Parameters
      • Custom Graph Nodes
    • Voxel Spawners
    • Materials
      • Multi Index Materials
  • Technical Notes
    • Performance and Profiling
    • Console Commands
    • Blueprint API
    • Release Notes
      • Release Notes 1.1
      • Release Notes 1.2
    • UE5.1 - Material Crash
Powered by GitBook
On this page
  • Symptoms
  • Root cause
  • What this means
  • Can you fix it
  • Any workarounds

Was this helpful?

  1. Technical Notes

UE5.1 - Material Crash

Symptoms

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0xffffffffffffffff

UnrealEditor_Voxel!<lambda_3c46313d3ddd529728500977f568835c>::operator()() [D:\build\U5M-Marketplace\Sync\LocalBuilds\PluginTemp\HostProject\Plugins\VoxelPro\Source\Voxel\Private\VoxelRender\MaterialCollections\VoxelInstancedMaterialCollection.cpp:238]
UnrealEditor_Voxel!UVoxelInstancedMaterialCollection::GetVoxelMaterial_NotCached() [D:\build\U5M-Marketplace\Sync\LocalBuilds\PluginTemp\HostProject\Plugins\VoxelPro\Source\Voxel\Private\VoxelRender\MaterialCollections\VoxelInstancedMaterialCollection.cpp:301]

...

Root cause

In 5.1.1, Epic made header changes. This made 5.1.0 binary incompatible with 5.1.1. You can find more details here: https://twitter.com/phyronnaz/status/1635303337229971460?s=20

What this means

The marketplace builds plugins against 5.1.0. If you use such a build against 5.1.1, you will get crashes.

In other words: if you use Voxel Plugin from the marketplace in 5.1.1, you will get crashes.

Can you fix it

We can't do anything on our end. We've reached out to the marketplace and they're looking into potential fixes.

Any workarounds

Only workarounds right now are:

  • Stay on 5.1.0

  • Build the plugin from source (eg by copying the plugin source to YourProject/Plugins)

If you have more question make sure to join our discord: https://discord.voxelplugin.com

PreviousRelease Notes 1.2

Last updated 11 months ago

Was this helpful?