# Illegal Property Override Warnings - Request Thread

**URL:** <https://forums.unrealengine.com/t/illegal-property-override-warnings-request-thread/2720634>\
**Category:** Announcements\
**Tags:** unreal-editor-for-fortnite, fortnite-creative, fortnite\
**Created:** [May 14, 2026, 12:35pm UTC](https://forums.unrealengine.com/t/illegal-property-override-warnings-request-thread/2720634 "2026-05-14T12:35:13Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Flak](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/flak/32/769441_2.png) [@Flak](https://forums.unrealengine.com/u/Flak)\
**Post date:** [May 14, 2026, 12:35pm UTC](https://forums.unrealengine.com/t/illegal-property-override-warnings-request-thread/2720634/1 "2026-05-14T12:35:13Z")

</div>

Illegal property override warnings are a side effect of a hidden property validation fix from v40.00.

Report any that affect properties you need in this thread, and we’ll consider exposing them in UEFN.

They’ll be treated as errors in a future release.

---

<div class="post-metadata">

**Author:** ![HackeRPiratE](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@HackeRPiratE](https://forums.unrealengine.com/u/HackeRPiratE)\
**Post date:** [May 14, 2026, 3:45pm UTC](https://forums.unrealengine.com/t/illegal-property-override-warnings-request-thread/2720634/2 "2026-05-14T15:45:46Z")

</div>

I am seeing **Illegal Property Value** errors when referencing cosmetic icons.

Weapon icons in the `/Game/` path currently pass validation: `/Script/Engine.Texture2D'/Game/UI/Foundation/Textures/Icons/Weapons/Items/T-Icon-Weapons-AssaultRifleMark2Base-L.T-Icon-Weapons-AssaultRifleMark2Base-L'`

However, character icons in the `/BRCosmetics/` path are being flagged as illegal references: `/Script/Engine.Texture2D'/BRCosmetics/UI/Foundation/Textures/Icons/Heroes/Athena/Soldier/T-Soldier-HID-A-448-Athena-Commando-M-PennantSeasOne-C-L.T-Soldier-HID-A-448-Athena-Commando-M-PennantSeasOne-C-L'`

Please consider exposing or whitelisting these `/BRCosmetics/` paths for use in custom Verse UI and Canvas slots so they do not become hard errors in future releases.

---

<div class="post-metadata">

**Author:** ![froggerdinger](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/froggerdinger/32/1087952_2.png) [@froggerdinger](https://forums.unrealengine.com/u/froggerdinger)\
**Post date:** [May 14, 2026, 4:59pm UTC](https://forums.unrealengine.com/t/illegal-property-override-warnings-request-thread/2720634/3 "2026-05-14T16:59:46Z")

</div>

Pixel Programmable distance on foliage is currently considered an illegal property override if set above 0.0, despite being exposed in editor. This greatly limits the amount of optimization one can do for custom foliage. This is especially important when creating higher fidelity experiences or more open world maps like rpg’s or larger BR’s. This simple fix could save a lot of frame rate optimization.

Additionally I understand this feature isn’t supported for lower end platforms however a simple scalability switch could be included to counteract that.

---

<div class="post-metadata">

**Author:** ![WambliWaste](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/wambliwaste/32/679588_2.png) [@WambliWaste](https://forums.unrealengine.com/u/WambliWaste)\
**Post date:** [May 14, 2026, 9:35pm UTC](https://forums.unrealengine.com/t/illegal-property-override-warnings-request-thread/2720634/4 "2026-05-14T21:35:16Z")

</div>

All my ItemPlacer (+200) on my map

example:

Item Placer144 (/BR\_EVOLUTION/FNBS.FNBS:PersistentLevel.BP\_ItemContainer\_C\_UAID\_D843AE9F8DE00CA302\_1901809040) Riferimento non consentito: /BRCosmetics/Weapons/WeaponSkins/Wraps/Materials/MI\_WeaponWrap\_RushedMummy . (AssetValidator\_AssetReferenceRestrictions)

 ![Registro dei messaggi 14_05_2026 23_07_44](https://d3kjluh73b9h9o.cloudfront.net/original/4X/9/7/f/97fd3d94fc52da4226b596aa99bd080626c71c02.png)

---

<div class="post-metadata">

**Author:** ![SilkyxMilky](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/silkyxmilky/32/1133454_2.png) [@SilkyxMilky](https://forums.unrealengine.com/u/SilkyxMilky)\
**Post date:** [May 15, 2026, 6:15pm UTC](https://forums.unrealengine.com/t/illegal-property-override-warnings-request-thread/2720634/5 "2026-05-15T18:15:07Z")

</div>

upvote

---

<div class="post-metadata">

**Author:** ![Velocity\_Zero](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/velocity_zero/32/1036910_2.png) [@Velocity\_Zero](https://forums.unrealengine.com/u/Velocity_Zero)\
**Post date:** [May 19, 2026, 7:05am UTC](https://forums.unrealengine.com/t/illegal-property-override-warnings-request-thread/2720634/6 "2026-05-19T07:05:42Z")

</div>

@Flak I’m not sure it’s already tracked or not.

- When someone creates a read-only `MSS` asset (meta sound source) from the provided presets (looped or one shot), they now yield an illegal property warning about the mono / stereo channels.
- There’s nothing any creator can do here, because those assets are fully read-only and configured by the engine/Epic.
- If this becomes a hard validation error, **it will break every map that uses scene graph `sound_component`** as such an MSS asset is reflected as SG verse component class ❗

* * *

Additionally here’s my report I was point out several times that I need the aspect ratio settings to be whitelisted until SG UI lands the proper solution in the future.

> [@\[Major\] Request for whitelisting certain illegal UMG.SizeBox properties](https://forums.unrealengine.com/t/major-request-for-whitelisting-certain-illegal-umg-sizebox-properties/2719131):
>
> Summary I’ve been using a few missing umg size box values to constraint my user interface to an expected aspect ratio. Such constraints are otherwise not possible. I’ve been notified by Epic that the proper solution should be addressed with SG UI in the future and therefore the following [issue](https://forums.unrealengine.com/t/major-min-max-aspect-ratio-child-layout-settings-are-still-hidden-on-the-umg-size-box/2651683/) will not be resolved in the near future. However until then those settings that are now flagged and warned as being illegal should be whitelisted and remain as such until a proper solution enters beta phas…

---

<div class="post-metadata">

**Author:** ![VerySpicyGames](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@VerySpicyGames](https://forums.unrealengine.com/u/VerySpicyGames)\
**Post date:** [May 20, 2026, 3:28am UTC](https://forums.unrealengine.com/t/illegal-property-override-warnings-request-thread/2720634/7 "2026-05-20T03:28:34Z")

</div>

@Flak

Here are ours:

- Would be neat if we could do WalkableSlopeOverride on static mesh. Its kinda hard to make own stairs without it

![UnrealEditorFortnite-Win64-Shipping_d6iNK6hUuX](https://d3kjluh73b9h9o.cloudfront.net/original/4X/3/f/2/3f225dec2653704ff7964fc8e1016d05042551c3.png)

- +1 on Stereo mode on MSS

![UnrealEditorFortnite-Win64-Shipping_Jt2SPFxJeL](https://d3kjluh73b9h9o.cloudfront.net/original/4X/c/5/6/c56b0d073331e39ad91d18e6561850113ba3221e.png)

- Physics Materials would also be nice to have back, in our specific case we used them on a Physics Asset on a skeletal mesh

---

<div class="post-metadata">

**Author:** ![SquidGamer7](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@SquidGamer7](https://forums.unrealengine.com/u/SquidGamer7)\
**Post date:** [July 5, 2026, 8:33pm UTC](https://forums.unrealengine.com/t/illegal-property-override-warnings-request-thread/2720634/8 "2026-07-05T20:33:02Z")

</div>

Hey Flak! Can you please explain why hidden property validation was even added? I have a whole post explaining why I think it was a very bad addition here: [Remove/Revert the Illegal Property Override errors [CRITICAL] - General / Issues and Bug Reporting - Epic Developer Community Forums](https://forums.unrealengine.com/t/remove-revert-the-illegal-property-override-errors-critical/2733633/3)

You wouldn’t even normally be able to overwrite these values without manually changing from a text editor, and if you do that it most likely means you know what you are doing and need those values. There should be no reason for this to exist.

---

<div class="post-metadata">

**Author:** ![BruteNemesisAR](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/brutenemesisar/32/1171256_2.png) [@BruteNemesisAR](https://forums.unrealengine.com/u/BruteNemesisAR)\
**Post date:** [August 10, 2026, 5:39pm UTC](https://forums.unrealengine.com/t/illegal-property-override-warnings-request-thread/2720634/9 "2026-08-10T17:39:06Z")

</div>

Pretty Much all sound attenuation settings are running into warnings / errors now. Here is a list of what should be MOST of them:

bAttenuateWithLPF  
bEnableListenerFocus  
bEnableFocusInterpolation  
bEnableOcclusion  
bUseComplexCollisionForOcclusion  
bEnablePriorityAttenuation  
bApplyNormalizationToStereoSounds  
bEnableLogFrequencyScaling  
bEnableSourceDataOverride  
SpatializationAlgorithm  
BinauralRadius  
CustomLowpassAirAbsorptionCurve  
CustomHighpassAirAbsorptionCurve  
AbsorptionMethod  
OcclusionTraceChannel  
ReverbSendMethod  
PriorityAttenuationMethod  
NonSpatializedRadiusEnd  
NonSpatializedRadiusMode  
LPFRadiusMin  
LPFRadiusMax  
LPFFrequencyAtMin  
LPFFrequencyAtMax  
HPFFrequencyAtMin  
HPFFrequencyAtMax  
FocusAzimuth  
NonFocusAzimuth  
FocusDistanceScale  
NonFocusDistanceScale  
NonFocusPriorityScale  
FocusVolumeAttenuation  
NonFocusVolumeAttenuation  
FocusReleaseInterpSpeed  
OcclusionLowPassFilterFrequency  
OcclusionVolumeAttenuation  
OcclusionInterpolationTime  
ReverbWetLevelMin  
ReverbWetLevelMax  
ReverbDistanceMin  
ReverbDistanceMax  
PriorityAttenuationMin  
PriorityAttenuationDistanceMin  
PriorityAttenuationDistanceMax  
CustomReverbSendCurve  
CustomPriorityAttenuationCurve

Someone also suggested walkable slope overrides on static meshes which I believe we also should be allowed to use. Useful for creating things like ladders.

---

<div class="post-metadata">

**Author:** ![NoxyLuca](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/noxyluca/32/1197919_2.png) [@NoxyLuca](https://forums.unrealengine.com/u/NoxyLuca)\
**Post date:** [August 10, 2026, 5:42pm UTC](https://forums.unrealengine.com/t/illegal-property-override-warnings-request-thread/2720634/10 "2026-08-10T17:42:03Z")

</div>

Bring it back epic

---

<div class="post-metadata">

**Author:** ![Andrewslab](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Andrewslab](https://forums.unrealengine.com/u/Andrewslab)\
**Post date:** [August 12, 2026, 10:57pm UTC](https://forums.unrealengine.com/t/illegal-property-override-warnings-request-thread/2720634/11 "2026-08-12T22:57:45Z")

</div>

Dealing with this issue still, my open world is less immersive without this capability. Please fix this Epic

---

<div class="post-metadata">

**Author:** ![DionPowder](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/dionpowder/32/1221509_2.png) [@DionPowder](https://forums.unrealengine.com/u/DionPowder)\
**Post date:** [September 7, 2026, 5:43pm UTC](https://forums.unrealengine.com/t/illegal-property-override-warnings-request-thread/2720634/12 "2026-09-07T17:43:54Z")

</div>

![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/7/9/4/7943b87d8e403c7b4e88020a829c9aea7c5cb5da.png)

All of these properties for the sound attunation assets, we need more options in general for this asset type, we are SO limited on what we can do compared to epic it is actually stupid…
