Problem

When creating a new project in OvEditor, users would encounter an assertion error:

[ASSERT] Attempting to SetProperty on a non-existing property

This caused the editor to display a white screen and prevented normal project creation.

Root Cause

The issue occurred during material deserialization inOvCore::Resources::Material::OnDeserialize(). The deserialization process:

1. Loads the shader and callsSetShader() to populate material properties from shader uniforms
2. Attempts to restore saved property values from the material file usingSetProperty()

TheSetProperty() method has an assertion that fails if the property doesn't exist. This can happen when:

• The shader definition has changed and removed certain uniforms
• The shader hasn't fully loaded its variants yet during initialization
• Material files contain legacy properties from older shader versions

Solution

Replaced allSetProperty() calls withTrySetProperty() in the deserialization visitor. TheTrySetProperty() method:

• Checks if the property exists before attempting to set it
• Returnstrue if successful,false if the property doesn't exist
• Doesnot trigger assertions for missing properties

This provides graceful handling of property mismatches between serialized materials and their current shaders, which is expected behavior during version updates or shader changes.

Changes

• Modified:Sources/Overload/OvCore/src/OvCore/Resources/Material.cpp
  • Lines 183, 187, 191, 195, 199, 203, 207: ChangedSetProperty() toTrySetProperty()

This is a minimal, defensive fix that maintains backwards compatibility while preventing assertions during normal editor operations.

Fixes #<issue_number>

✨ Let Copilot coding agentset things up for you — coding agent works faster and does higher quality work when set up for your repo.