Blueprints not showing correctly in a packaged build

I have a blueprint actor for a physics cube which you can move around the level and change its gravity .

Everything functions fine when playing in editor or via the Launch Game command . However when every I try in a packaged build it will not display correctly . It is just one component that does not display correctly , all the collision settings appear to be fine .

You can see an example here .

https://www…com/watch?v=RqRK3NUPK2Q&feature=youtu.be

So far I have tried :

1.Exporting the build in a variety of different packaging settings

2.Duplicating the actor .

3.Adding a new version of the same component that is not showing correctly .

I still get the same issue .

What makes this confusing is that there are no errors when I compile the Blueprint , or in the the saved logs .

I could maybe re create the actor from scratch , but that would be a lot of work so it is best avoided .

Has anyone experienced a similar issue or know what could be causing the problem ?

Can you please show the blueprint at least?

Image is attached .

The “PhysicsMesh” has Simulate Physics set to true . This mesh is invisible .

Then there is the “VisibleMesh” This does not simulate physics and is there to show when the gravity has changed .

The “CollisionLineMesh” and “CollisionMarker” are there to show where the object will land . These are both showing correctly .

As I said before the “visibleMesh” will display correctly in the editor , but not in a packaged build .

I have tried adding a new static mesh component or making the “physicsMesh” Visible , but I still get the same issue .

Hi ,

  • Does this occur in a clean, blank project with no additional content or is it limited to one project?
  • What steps can I take to reproduce this on my end?
  • What OS or device are you packaging to?

It is for Windows 64 . I downloaded a fresh project and it appears to be fixed .

Hopefully it won’t happen again .

The issue has re appeared , but this time for different blueprints that were previously unaffected .

My colleague is able to package a build without any issue . I tried to package a build on my laptop to see if it was my PC causing the issue , I had the same problem . (This is for Windows 64)

When I migrated the content to a blank project there were so many compiler errors that I was unable to package a build .

If I try and recreate the in a blank project using starter content there is no issue .

Not sure what the best way for you to re create because migrating content to a blank project will cause packaging errors .

Has anyone experienced similar issues ?

I’ve updated to 4.12 and the issue appears to be fixed .