UDocumentation UE5.7 10.02.2026 (Source)
API documentation for Unreal Engine 5.7
FMapErrors Struct Reference

#include <MapErrors.h>

Static Public Attributes

static CORE_API FLazyName MatchingLightGUID
 
static CORE_API FLazyName MatchingActorGUID
 
static CORE_API FLazyName ActorLargeShadowCaster
 
static CORE_API FLazyName NoDamageType
 
static CORE_API FLazyName NonCoPlanarPolys
 
static CORE_API FLazyName SameLocation
 
static CORE_API FLazyName InvalidDrawscale
 
static CORE_API FLazyName ActorIsObselete
 
static CORE_API FLazyName StaticPhysNone
 
static CORE_API FLazyName VolumeActorCollisionComponentNULL
 
static CORE_API FLazyName VolumeActorZeroRadius
 
static CORE_API FLazyName VertexColorsNotMatchOriginalMesh
 
static CORE_API FLazyName CollisionEnabledNoCollisionGeom
 
static CORE_API FLazyName ShadowCasterUsingBoundsScale
 
static CORE_API FLazyName MultipleSkyLights
 
static CORE_API FLazyName MultipleSkyAtmospheres
 
static CORE_API FLazyName MultipleSkyAtmosphereTypes
 
static CORE_API FLazyName InvalidHairStrandsMaterial
 
static CORE_API FLazyName InvalidTrace
 
static CORE_API FLazyName BrushZeroPolygons
 
static CORE_API FLazyName BrushNullPolygons
 
static CORE_API FLazyName CleanBSPMaterials
 
static CORE_API FLazyName BrushComponentNull
 
static CORE_API FLazyName PlanarBrush
 
static CORE_API FLazyName CameraAspectRatioIsZero
 
static CORE_API FLazyName AbstractClass
 
static CORE_API FLazyName DeprecatedClass
 
static CORE_API FLazyName FoliageMissingStaticMesh
 
static CORE_API FLazyName FoliageMissingClusterComponent
 
static CORE_API FLazyName FixedUpDeletedLayerWeightmap
 
static CORE_API FLazyName FixedUpNonMatchingTargetLayer
 
static CORE_API FLazyName FixedUpIncorrectLayerWeightmap
 
static CORE_API FLazyName FixedUpInvalidLandscapeMaterialInstances
 
static CORE_API FLazyName FixedUpSharedLayerWeightmap
 
static CORE_API FLazyName LandscapeComponentPostLoad_Warning
 
static CORE_API FLazyName LandscapeLazyObjectPtrDeprecation_Warning
 
static CORE_API FLazyName LandscapeProxyFixupSharedData_Warning
 
static CORE_API FLazyName DuplicateLevelInfo
 
static CORE_API FLazyName NoKillZ
 
static CORE_API FLazyName LightComponentNull
 
static CORE_API FLazyName RebuildLighting
 
static CORE_API FLazyName StaticComponentHasInvalidLightmapSettings
 
static CORE_API FLazyName PrimitiveComponentHasInvalidTranslucentShadowSetting
 
static CORE_API FLazyName UseFauxOrthoViewPosDeprecation_Warning
 
static CORE_API FLazyName StaticLightWithLumen_Warning
 
static CORE_API FLazyName RebuildPaths
 
static CORE_API FLazyName ParticleSystemComponentNull
 
static CORE_API FLazyName PSysCompErrorEmptyActorRef
 
static CORE_API FLazyName PSysCompErrorEmptyMaterialRef
 
static CORE_API FLazyName SkelMeshActorNoPhysAsset
 
static CORE_API FLazyName SkeletalMeshComponent
 
static CORE_API FLazyName SkeletalMeshNull
 
static CORE_API FLazyName AudioComponentNull
 
static CORE_API FLazyName SoundCueNull
 
static CORE_API FLazyName StaticMeshNull
 
static CORE_API FLazyName StaticMeshComponent
 
static CORE_API FLazyName SimpleCollisionButNonUniformScale
 
static CORE_API FLazyName MoreMaterialsThanReferenced
 
static CORE_API FLazyName MoreNaniteMaterialsThanReferenced
 
static CORE_API FLazyName ElementsWithZeroTriangles
 
static CORE_API FLazyName LevelStreamingVolume
 
static CORE_API FLazyName NoLevelsAssociated
 
static CORE_API FLazyName FilenameIsTooLongForCooking
 
static CORE_API FLazyName UsingExternalObject
 
static CORE_API FLazyName RepairedPaintedVertexColors
 
static CORE_API FLazyName LODActorMissingStaticMesh
 
static CORE_API FLazyName LODActorMissingActor
 
static CORE_API FLazyName LODActorNoActorFound
 
static CORE_API FLazyName InvalidVirtualTextureUsage
 

Detailed Description

This file contains known map errors that can be referenced by name. Documentation for these errors is assumed to lie in UDN at: Engine\Documentation\Source\Shared\Editor\MapErrors

Member Data Documentation

◆ AbstractClass

FLazyName FMapErrors::AbstractClass
static

Class { }::{ } is obsolete and must be removed (Class is abstract): NEEDS DESCRIPTION

◆ ActorIsObselete

FLazyName FMapErrors::ActorIsObselete
static

{Actor} is obsolete and must be removed!: This warning is caused when there is an instance of a actor in a level that has been marked deprecated. This is usually because a actor was marked deprecated after the level was created, but the map was never updated. This can be fixed by simply deleting the actor.

◆ ActorLargeShadowCaster

FLazyName FMapErrors::ActorLargeShadowCaster
static

{Actor} : Large actor casts a shadow and will cause an extreme performance hit unless bUseBooleanEnvironmentShadowing is set to true: A large actor has been set to cast shadows - this will cause extreme performance issues and should have bUseBooleanEnvironmentShadowing set to true.

◆ AudioComponentNull

FLazyName FMapErrors::AudioComponentNull
static

Sound {Actor} : Ambient sound actor has NULL AudioComponent property - please delete!: This warning is caused when there is a Ambient sound actor with a "None" AudioComponent. It is usually found in older maps where duplication was used to create a actor and can be fixed by deleting the actor causing the warning and creating a new one.

◆ BrushComponentNull

FLazyName FMapErrors::BrushComponentNull
static

{Actor} : Brush has NULL BrushComponent property - please delete!: This warning is caused when there is a Brush with a "None" ConstraintInstance component. It is usually found in older maps where duplication was used to create a Brush and can be fixed by deleting the Brush causing the warning and creating a new one.

◆ BrushNullPolygons

FLazyName FMapErrors::BrushNullPolygons
static

{Brush Actor} : Brush has NULL polygons property - please delete!: This warning indicates that you have a brush in the level with a "None" polygons reference. The brush should be deleted as it isn't doing anything useful.

◆ BrushZeroPolygons

FLazyName FMapErrors::BrushZeroPolygons
static

BSP Brush {Brush Actor} : Brush has zero polygons - please delete!: This warning indicates that you have a brush in the level that doesn't have any polygons associated with it. The brush should be deleted as it isn't doing anything useful.

◆ CameraAspectRatioIsZero

FLazyName FMapErrors::CameraAspectRatioIsZero
static

Camera Camera has AspectRatio=0 - please set this to something non-zero

◆ CleanBSPMaterials

FLazyName FMapErrors::CleanBSPMaterials
static

Run 'Clean BSP Materials' to clear {count} references: This warning indicates that there are material references on brush faces that aren't contributing to the BSP, and that applying the Tools->'Clean BSP Materials' operation can clean up these references.

◆ CollisionEnabledNoCollisionGeom

FLazyName FMapErrors::CollisionEnabledNoCollisionGeom
static

{ActorName} has collision enabled but StaticMesh ({StaticMeshName}) has no simple or complex collision.

◆ DeprecatedClass

FLazyName FMapErrors::DeprecatedClass
static

{ }::{ } is obsolete and must be removed (Class is deprecated): NEEDS DESCRIPTION

◆ DuplicateLevelInfo

FLazyName FMapErrors::DuplicateLevelInfo
static

Level Duplicate level info: Two WorldInfos somehow exist...

◆ ElementsWithZeroTriangles

FLazyName FMapErrors::ElementsWithZeroTriangles
static

{Count} element(s) with zero triangles in static mesh {StaticMesh}: TODO

◆ FilenameIsTooLongForCooking

FLazyName FMapErrors::FilenameIsTooLongForCooking
static

Uncategorized Filename is too long ({FilenameLength} characters) - this may interfere with cooking for consoles. Unreal filenames should be no longer than {Length} characters. Filename value: {Filename}: Please rename the file to be within the length specified.

◆ FixedUpDeletedLayerWeightmap

FLazyName FMapErrors::FixedUpDeletedLayerWeightmap
static

Landscape {LandscapeComponent} : Fixed up deleted layer weightmap:

◆ FixedUpIncorrectLayerWeightmap

FLazyName FMapErrors::FixedUpIncorrectLayerWeightmap
static

{LandscapeComponent} : Fixed up incorrect layer weightmap texture index:

◆ FixedUpInvalidLandscapeMaterialInstances

FLazyName FMapErrors::FixedUpInvalidLandscapeMaterialInstances
static

{LandscapeComponent} : Fixed up invalid material instances for a landscape component when its weightmap allocations don't match the material's layer configuration :

◆ FixedUpNonMatchingTargetLayer

FLazyName FMapErrors::FixedUpNonMatchingTargetLayer
static

{LandscapeComponent} : Fixed up target layer info object not matching with the parent landscape's:

◆ FixedUpSharedLayerWeightmap

FLazyName FMapErrors::FixedUpSharedLayerWeightmap
static

Fixed up shared weightmap texture for layer {Layer} in component {Component} (shares with {Name}):

◆ FoliageMissingClusterComponent

FLazyName FMapErrors::FoliageMissingClusterComponent
static

Foliage in this map is missing {MissingCount} cluster component(s) for static mesh {MeshName}. Opening the Foliage tool will fix this problem.: TODO

◆ FoliageMissingStaticMesh

FLazyName FMapErrors::FoliageMissingStaticMesh
static

Foliage Foliage instances for a missing static mesh have been removed.: TODO

◆ InvalidDrawscale

FLazyName FMapErrors::InvalidDrawscale
static

{Actor} has invalid DrawScale/ DrawScale3D: This warning is caused when either DrawScale, DrawScale3D X, DrawScale3D Y, or DrawScale 3D Z is equal to zero. Meaning that the actor will not be shown because it is being scaled to zero on one of its axis. To solve this problem, change any DrawScale's that are zero to be non-zero by selecting the actor and changing its drawscale at the bottom of the main UnrealEd window.

◆ InvalidHairStrandsMaterial

FLazyName FMapErrors::InvalidHairStrandsMaterial
static

Actor gas invalid hair strands material

◆ InvalidTrace

FLazyName FMapErrors::InvalidTrace
static

{ActorName} has WorldTrace blocked. It will be considered to be world geometry

◆ InvalidVirtualTextureUsage

FLazyName FMapErrors::InvalidVirtualTextureUsage
static

Virtual Textures {ObjectName} is using a virtual texture ('{TextureName}') on an unsupported property ('{PropertyName}').

◆ LandscapeComponentPostLoad_Warning

FLazyName FMapErrors::LandscapeComponentPostLoad_Warning
static

Landscape ({ProxyName}) has overlapping render components at location ({X, Y}):

◆ LandscapeLazyObjectPtrDeprecation_Warning

FLazyName FMapErrors::LandscapeLazyObjectPtrDeprecation_Warning
static

Landscape proxy {ProxyName} of {LevelName} points to a LandscapeActor that is not currently loaded. This will lose the property upon save.

◆ LandscapeProxyFixupSharedData_Warning

FLazyName FMapErrors::LandscapeProxyFixupSharedData_Warning
static

Landscape proxy {Proxy} had one or more shared properties not in sync with its parent landscape actor {Parent}. This has been fixed but the proxy needs to be saved in order to ensure cooking behaves as expected..

◆ LevelStreamingVolume

FLazyName FMapErrors::LevelStreamingVolume
static

Volume LevelStreamingVolume is not in the persistent level - please delete: This warning is caused when there is a level streaming volume that does not exist in the persistent level. This can be problematic because the volume will not be considered when checking to see if a streaming level should be loaded or unloaded. You can fix this problem by deleting the level streaming volume and recreating it.

◆ LightComponentNull

FLazyName FMapErrors::LightComponentNull
static

Lighting {Actor} : Light actor has NULL LightComponent property - please delete!: This warning is caused when there is a Light actor with a "None" LightComponent. It is usually found in older maps where duplication was used to create the actor and can be fixed by deleting the actor causing the warning and creating a new one.

◆ LODActorMissingActor

FLazyName FMapErrors::LODActorMissingActor
static

{LODActor} : Actor is missing. The actor might have been removed. We recommend you to build LOD again.

◆ LODActorMissingStaticMesh

FLazyName FMapErrors::LODActorMissingStaticMesh
static

Hierarchical LOD {LODActor} : Static mesh is missing for the built LODActor. Did you remove the asset?

◆ LODActorNoActorFound

FLazyName FMapErrors::LODActorNoActorFound
static

{LODActor} : NoActor is assigned. We recommend to delete this actor.

◆ MatchingActorGUID

FLazyName FMapErrors::MatchingActorGUID
static

Actor {Actor} has same GUID as {Actor} (Duplicate and replace the orig with the new one): Duplicate and replace the original with the new one.

◆ MatchingLightGUID

FLazyName FMapErrors::MatchingLightGUID
static

Lighting {LightActor} has same light GUID as {LightActor} (Duplicate and replace the orig with the new one): Duplicate and replace the original with the new one.

◆ MoreMaterialsThanReferenced

FLazyName FMapErrors::MoreMaterialsThanReferenced
static

More overridden materials {Count} on static mesh component than are referenced {Count} in source mesh {StaticMesh}: TODO

◆ MoreNaniteMaterialsThanReferenced

FLazyName FMapErrors::MoreNaniteMaterialsThanReferenced
static

More Nanite overridden materials {Count} on static mesh component than are referenced {Count} in source mesh {StaticMesh}: TODO

◆ MultipleSkyAtmospheres

FLazyName FMapErrors::MultipleSkyAtmospheres
static

◆ MultipleSkyAtmosphereTypes

FLazyName FMapErrors::MultipleSkyAtmosphereTypes
static

◆ MultipleSkyLights

FLazyName FMapErrors::MultipleSkyLights
static

◆ NoDamageType

FLazyName FMapErrors::NoDamageType
static

{Volume} causes damage, but has no damagetype defined.: This warning is caused when there is a volume that is set to cause damage but doesn't have a damage type defined. A damage type is important because it tells the game code how to handle a actor's reaction to taking damage. This can be solved by going to the actor's Property Window->Physics Volume and setting the 'DamageType' property.

◆ NoKillZ

FLazyName FMapErrors::NoKillZ
static

Map should have KillZ set.: This warning is caused when the map's KillZ in the WorldInfo properties is set to the default value. All maps should specify a KillZ appropriate for the level so that players cannot simply fall forever until they reach the playable world bounds.

◆ NoLevelsAssociated

FLazyName FMapErrors::NoLevelsAssociated
static

No levels are associated with streaming volume.: This warning is caused when there are no levels associated with a LevelStreamingVolume, making it non-functional. This problem can be fixed by associating one or more streaming levels with the offending LevelStreamingVolume.

◆ NonCoPlanarPolys

FLazyName FMapErrors::NonCoPlanarPolys
static

{Actor} : Brush has non-coplanar polygons: This warning is caused when there is a brush in the level that has non-coplanar polygons. This is usually caused by using brush editing tools in geometry mode in extreme ways and can cause missing polygons in the level. This warning can be resolved by deleting the brush and recreating it.

◆ ParticleSystemComponentNull

FLazyName FMapErrors::ParticleSystemComponentNull
static

Particle System {Actor} : Emitter actor has NULL ParticleSystemComponent property - please delete!: This warning is caused when there is a Emitter actor with a "None" ParticleSystemComponent. It is usually found in older maps where duplication was used to create the actor and can be fixed by deleting the actor causing the warning and creating a new one.

◆ PlanarBrush

FLazyName FMapErrors::PlanarBrush
static

{Brush} : Brush is planar: Planar brush used - please note that this may not work well with collision.

◆ PrimitiveComponentHasInvalidTranslucentShadowSetting

FLazyName FMapErrors::PrimitiveComponentHasInvalidTranslucentShadowSetting
static

Component is a using CastVolumetricTranslucentShadow but this feature is disabled for the project! Turn on r.Shadow.TranslucentPerObject.ProjectEnabled in a project ini if required.

◆ PSysCompErrorEmptyActorRef

FLazyName FMapErrors::PSysCompErrorEmptyActorRef
static

PSysComp has an empty parameter actor reference at index {Index} ({Actor}): Param.Actor should not be NULL.

◆ PSysCompErrorEmptyMaterialRef

FLazyName FMapErrors::PSysCompErrorEmptyMaterialRef
static

PSysComp has an empty parameter material reference at index {Index} ({Actor}): Param.Material should not be NULL.

◆ RebuildLighting

FLazyName FMapErrors::RebuildLighting
static

Maps need lighting rebuilt: This warning is caused when lighting has been invalidated by moving or modifying a light actor. This can cause problems because the rendered lighting in the level is not accurately representing the current state of lights in the level. This error can be solved by going to the Build menu and rebuilding lighting for a map.

◆ RebuildPaths

FLazyName FMapErrors::RebuildPaths
static

Navigation Paths need to be rebuilt: TODO

◆ RepairedPaintedVertexColors

FLazyName FMapErrors::RepairedPaintedVertexColors
static

Actors {Actor} : Repaired painted vertex colors: Painted vertex colors were repaired on this actor.

◆ SameLocation

FLazyName FMapErrors::SameLocation
static

{Actor} in same location as {Another Actor}: This warning is caused when there is a actor that is in the same exact location as another actor. This warning is usually the result of a accidental duplication or paste operation. It can be fixed by deleting one of the actors, or disregarded if the placement was intentional.

◆ ShadowCasterUsingBoundsScale

FLazyName FMapErrors::ShadowCasterUsingBoundsScale
static

Actor casts dynamic shadows and has a BoundsScale greater than 1! This will have a large performance hit: Serious performance warning... either reduce BoundsScale to be <= 1 or remove dynamic shadows...

◆ SimpleCollisionButNonUniformScale

FLazyName FMapErrors::SimpleCollisionButNonUniformScale
static

{StaticMesh} has simple collision but is being scaled non-uniformly - collision creation will fail: Simple collision cannot be used with non-uniform scale. Please either fix the scale or the collision type.

◆ SkeletalMeshComponent

FLazyName FMapErrors::SkeletalMeshComponent
static

{Actor} : Skeletal mesh actor has NULL SkeletalMeshComponent property: The specified SkeletalMeshActor has a NULL SkeletalMeshComponent.

◆ SkeletalMeshNull

FLazyName FMapErrors::SkeletalMeshNull
static

{Actor} : Skeletal mesh actor has NULL SkeletalMesh property: The specified SkeletalMeshActor has a NULL SkeletalMesh.

◆ SkelMeshActorNoPhysAsset

FLazyName FMapErrors::SkelMeshActorNoPhysAsset
static

Skeletal Mesh {Actor} : SkeletalMeshActor has no PhysicsAsset assigned.: In order for a SkeletalMesh to have an accurate bounding box, it needs to have a PhysicsAsset assigned in its SkeletalMeshComponent. An incorrect or inaccurate bounding box can lead to the mesh vanishing when its origin is not in view, or to poor shadow resolution because the bounding box is too big.

◆ SoundCueNull

FLazyName FMapErrors::SoundCueNull
static

Ambient sound actor's AudioComponent has a NULL SoundCue property!: This warning is caused when there is a AmbientSound actor with a NULL SoundCue property. This is a problem because the actor won't actually be playing any sounds. This can be fixed by first choosing a sound cue in the generic browser and then going to the actor's Property Window->Audio Category->Audio Component and setting the 'SoundCue' property.

◆ StaticComponentHasInvalidLightmapSettings

FLazyName FMapErrors::StaticComponentHasInvalidLightmapSettings
static

Component is a static type but has invalid lightmap settings! Indirect lighting will be black. Common causes are lightmap resolution of 0, LightmapCoordinateIndex out of bounds.

◆ StaticLightWithLumen_Warning

FLazyName FMapErrors::StaticLightWithLumen_Warning
static

{LightComponent} is using static lighting while Lumen is enabled. Static lights will fail to render.

◆ StaticMeshComponent

FLazyName FMapErrors::StaticMeshComponent
static

{Actor} : Static mesh actor has NULL StaticMeshComponent property - please delete!: This warning is caused when there is a static mesh actor with a "None" StaticMeshComponent component. It is usually found in older maps where duplication was used to create the actor and can be fixed by deleting the actor causing the warning and creating a new one.

◆ StaticMeshNull

FLazyName FMapErrors::StaticMeshNull
static

Static Mesh {Static Mesh Actor} : Static mesh actor has NULL StaticMesh property: This warning is caused when there is a static mesh actor in a level with a NULL StaticMesh property. This can be a problem because the actor exists and is using memory, but doesn't have a static mesh to actually draw. This warning is usually the result of creating a StaticMesh actor without first selecting a StaticMesh in the generic browser. This warning can be fixed by first selecting a static mesh in the generic browser and then going to the StaticMesh actor's Property Window->StaticMeshActor Category->StaticMeshComponent->StaticMeshComponent Category to set the 'StaticMesh' Property.

◆ StaticPhysNone

FLazyName FMapErrors::StaticPhysNone
static

{Actor} bStatic true, but has Physics set to something other than PHYS_None!: This warning is caused when an actor has its bStatic flag set to true but its Physics is set to PHYS_None. Since bStatic means that the actor will not be moving, having Physics set to PHYS_None is contradictory. Actors set with the bStatic flag are also not ticked(updated). This error can be solved by going to the actor's properties and changing its Physics to PHYS_None.

◆ UseFauxOrthoViewPosDeprecation_Warning

FLazyName FMapErrors::UseFauxOrthoViewPosDeprecation_Warning
static

bUseFauxOrthoViewPos has been deprecated. Property will be lost on re-save.

◆ UsingExternalObject

FLazyName FMapErrors::UsingExternalObject
static

{ObjectName} : Externally referenced

◆ VertexColorsNotMatchOriginalMesh

FLazyName FMapErrors::VertexColorsNotMatchOriginalMesh
static

{Actor} (LOD {Index}) has hand-painted vertex colors that no longer match the original StaticMesh {StaticMesh}: It looks like the original mesh was changed since this instance's vertex colors were painted down - this may need a refresh.

◆ VolumeActorCollisionComponentNULL

FLazyName FMapErrors::VolumeActorCollisionComponentNULL
static

{Actor} : Volume actor has NULL collision component - please delete: The specified volume actor has a NULL collision component and should probably be deleted.

◆ VolumeActorZeroRadius

FLazyName FMapErrors::VolumeActorZeroRadius
static

{Actor} : Volume actor has a collision component with 0 radius - please delete: The specified volume actor has a zero radius for its collision component and should probably be deleted.


The documentation for this struct was generated from the following files: