This likely has to do with start position being tied to view port size, so it may be bugged on small displays or high resolution displays. Will fix for the future!
