For anyone having this issue in v5, (specifically on launch) it can be caused by launching the application on another monitor. In fact PrusaSlicer has the exact same issue. I only found out because I got feed up with Simplify3D due to the issue and went to PrusaSlicer. At least PrusaSlicer provides ...