This is very odd that even though I was told that this is fixed internally no bug report, issue, anything has been filed or listed. And now to hear that the latest build still has this issue and is presumably not fixed? No ETA on next release? Come on Epic! If these forums are for interacting on these issues, please INTERACT and let people know what is going on with YOUR product. An update. A message. Anything. Very disappointing.