4.11.1 Arrow component causing rendering issues
A few rendering / post-process issues have occurred in the latest build of out game and I think rendering the arrow component (of a blueprint) in game has been the cause.
With the arrow component set to visible in game the scene's Ambient Occlusion disappears, the Screen Space Reflections become more powerful and the the Bloom intensifies. With the arrow component set to hidden in game the issues do not occur.
The arrow component was being used on a blueprint actor with a projectile movement that is functioning as a grenade. The arrow was being used to test/debug the rotation and direction of the actor. This actor is spawned on a button press and the rendering issues only exist during it's lifetime.
This issue is far from game breaking, but did cause us plenty of confusion whilst trying to test the grenade blueprints.
Attached below should be:
asked Apr 13 '16 at 11:11 AM in Bug Reports
Thank you for the detailed repro steps and explanation. I was able to see this in 4.11 and setup a test project looking specifically at the three Post Process issues you called out. These look to have been resolved on our internal build of 4.12. Look for these fixes in a future release.
answered Apr 14 '16 at 04:12 PM
Tim Hobson ♦♦ STAFF
Follow this question
Once you sign in you will be able to subscribe for any updates here