Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Building pak files should not trigger warnings #190

Open
mikeroberts3000 opened this issue Apr 19, 2023 · 0 comments
Open

Building pak files should not trigger warnings #190

mikeroberts3000 opened this issue Apr 19, 2023 · 0 comments

Comments

@mikeroberts3000
Copy link
Collaborator

mikeroberts3000 commented Apr 19, 2023

For example, there are some warnings when building PAK files for kujiale_0000:

F:\code\github\spear\cpp\unreal_projects\SpearSim\Content\Shared\Koolab\Robot\ThirdPersonBP\ThirdPersonCharacter.uasset: [Compiler] InputAction Event references unknown Action 'ResetVR' for  InputAction ResetVR

And for warehouse_0000:

LogBlueprint: Warning: FMemberReference::ResolveMember (GetInstanceAssetPlayerTimeFromEnd) bSelfContext == true, but no scope supplied!
LogBlueprint: Warning: FMemberReference::ResolveMember (GetInstanceAssetPlayerTimeFromEnd) bSelfContext == true, but no scope supplied!
LogBlueprint: Warning: FMemberReference::ResolveMember (GetInstanceAssetPlayerTimeFromEnd) bSelfContext == true, but no scope supplied!
LogBlueprint: Warning: FMemberReference::ResolveMember (GetInstanceAssetPlayerTimeFromEnd) bSelfContext == true, but no scope supplied!
LogBlueprint: Warning: FMemberReference::ResolveMember (TryGetPawnOwner) bSelfContext == true, but no scope supplied!
LogBlueprint: Warning: FMemberReference::ResolveMember (TryGetPawnOwner) bSelfContext == true, but no scope supplied!
LogBlueprint: Warning: FMemberReference::ResolveMember (HitBySomething) bSelfContext == true, but no scope supplied!
LogBlueprint: Warning: FMemberReference::ResolveMember (HitBySomething) bSelfContext == true, but no scope supplied!
LogBlueprint: Warning: FMemberReference::ResolveMember (HitBySomething) bSelfContext == true, but no scope supplied!
LogBlueprint: Warning: FMemberReference::ResolveMember (HitBySomething) bSelfContext == true, but no scope supplied!
LogBlueprint: Warning: FMemberReference::ResolveMember (GetAnimationFromCollisionAngle) bSelfContext == true, but no scope supplied!
LogBlueprint: Warning: FMemberReference::ResolveMember (GetAnimationFromCollisionAngle) bSelfContext == true, but no scope supplied!
LogBlueprint: Warning: FMemberReference::ResolveMember (HitByCar) bSelfContext == true, but no scope supplied!
LogBlueprint: Warning: FMemberReference::ResolveMember (HitByCar) bSelfContext == true, but no scope supplied!
LogBlueprint: Warning: FMemberReference::ResolveMember (HitByCar) bSelfContext == true, but no scope supplied!
LogBlueprint: Warning: FMemberReference::ResolveMember (HitByCar) bSelfContext == true, but no scope supplied!
LogBlueprint: Warning: FMemberReference::ResolveMember (HitByCar) bSelfContext == true, but no scope supplied!
LogBlueprint: Warning: FMemberReference::ResolveMember (HitByCar) bSelfContext == true, but no scope supplied!
LogBlueprint: Warning: FMemberReference::ResolveMember (ReceiveActorBeginOverlap) bSelfContext == true, but no scope supplied!
LogBlueprint: Warning: FMemberReference::ResolveMember (ReceiveActorBeginOverlap) bSelfContext == true, but no scope supplied!
LogBlueprint: Warning: FMemberReference::ResolveMember (ReceiveTick) bSelfContext == true, but no scope supplied!
LogBlueprint: Warning: FMemberReference::ResolveMember (ReceiveTick) bSelfContext == true, but no scope supplied!
LogBlueprint: Warning: FMemberReference::ResolveMember (UserConstructionScript) bSelfContext == true, but no scope supplied!
LogBlueprint: Warning: FMemberReference::ResolveMember (UserConstructionScript) bSelfContext == true, but no scope supplied!
@mikeroberts3000 mikeroberts3000 changed the title Building pak files should be warning-free for warehouse_0000 Building pak files should be warning-free Apr 19, 2023
@mikeroberts3000 mikeroberts3000 changed the title Building pak files should be warning-free Building pak files should not trigger warnings Apr 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant