VR Expansion Plugin

Development Platform & Builds XR Development
3028

Hi there,

Now I’ve been struggling with an error for the last 3 days and I’m getting a bit desperate… Maybe someone here has a clue what to try next.

Working on a project with the VRExpansionPlugin, I have some functions to find the PlayerStart with a correct (combination of) tags.

Everything works great in the editor, but when packaging the project I get these errors:



UATHelper: Packaging (Windows (64-bit)):   LogBlueprint: Warning: FMemberReference::ResolveMember (ActorHasTag) bSelfContext == true, but no scope supplied!
UATHelper: Packaging (Windows (64-bit)):   LogBlueprint: Warning: FMemberReference::ResolveMember (K2_FindPlayerStart) bSelfContext == true, but no scope supplied!
UATHelper: Packaging (Windows (64-bit)):   LogBlueprint: Warning: FMemberReference::ResolveMember (GetTransform) bSelfContext == true, but no scope supplied!
PackagingResults: Warning: FMemberReference::ResolveMember (ActorHasTag) bSelfContext == true, but no scope supplied!
PackagingResults: Warning: FMemberReference::ResolveMember (K2_FindPlayerStart) bSelfContext == true, but no scope supplied!
PackagingResults: Warning: FMemberReference::ResolveMember (GetTransform) bSelfContext == true, but no scope supplied!

When I play the packaged project, I’m now spawning at the correct PlayerStart.

Searching for a solution, tried the following:

  • Moved the function from PlayerController to GameMode (someone said could have an impact).
  • Moved the search out of the function, into the main event (someone said could have an impact).
  • Replaced PlayerController and GameMode with fresh copies from the VRExpansionExampleProject and re-created all custom functionality from scratch.
  • Moved the entire content of the project to a fresh copy (with a fresh compile of the latest download of the plugin).
  • Work without K2_FindPlayerStart (which looks for PlayerStartTag instead of the more general Actor Tag.
  • Write a replacement of ‘ActorHasTag’ and stop using ‘ActorHasTag’.

Nothing has made a difference - and while the number of times the above errors are generated vary depending on what functionality I use, they are always there (even if I’m no longer using ‘ActorHasTag’, for example).

Now, I do think (but I’m not sure) the problem is originating in the VRExpansionPlugin (and some version-to-version migrations I’ve made in the past), mainly because when I try to move or save a copy of the PlayerController / GameMode or PawnCharacter, I get the following message:
20190119-16_05_17VR_Player_Controller.png

is why I tried to replace the PlayerController and GameMode with fresh copies - which did in fact cause the above error to disappear (but not the warning when packaging or the missing functionality in the packaged project). Only the Pawn I did not re-write (because that would take a lot of time and it seems unlikely that the pawn can cause … also: with the pawn the above ‘Save’ error disappeared after moving to a fresh copy of the project).

So now I can’t think of anything else to try… and it’s driving me mad!

Hope that someone has ideas :slight_smile: