i just created shipping package, one of my system doesnt work, i tested it in PIE, even the development package.
so i made in blueprint to attach actor to component of other actor.
the attach actor is spawned then attach it to component of other actor, so it can follows anywhere the other actor goes.
but the system somehow doesnt attach the actor to the other in SHIPPING package.
PIE and Development package work perfectly.
this is frustrating.
Hi bilyjoe1000.
When moving between different build configuration levels with regards to packaged builds, the code / blueprints are optimised differently and as such may behave in a slightly different way. The same may also apply when moving from play in editor to a packaged build as editor-only functionality is optimised away.
With regards to your secondary actor not attaching to the primary actor, it is possible that these optimisations have changed the order that the actors spawn/initialise in the level to be different in a shipping build than in a development build / PIE. In order to determine what the issue is here I would suggest adding in some logging (due to the fact it’s shipping then normal logs wouldn’t work, so I’d suggest printing to screen instead) after each actor spawns so you can confirm whether or not the first actor is already spawned into the level when the secondary actor tries to attach to it.
It’s good practice to implement checks when trying to run integral logic; for example you could use an IsValid node to confirm that the primary actor exists before trying to attach anything to it (you could also print an error message to screen here). If you find that the primary actor is not valid yet you could also implement a Delay node so the attach logic does not run until after the actor has spawned in.