Works for me in 5.1.1. Unless you can find an issue for it on the bug tracker it’s probably specific to your project and I wouldn’t expect 5.2 to magically fix it.
You will have to calculate the desired value based on the users screen resolution. You’d have to do the same thing with a post process material.