WowAce

What version of Grid2  are you using (Version is displayed in General/About Tab) ?

v3.0.35

What game client version, classic or retail, windows or mac and language are you using ?

12.0.1.66044, retail, windows 10, english

What steps will reproduce the problem?

/reload

  
Did you try having Grid2 as the only enabled addon and everything else disabled?

Yes, it did not happen with only Grid2 enabled. It does happen with only Grid2 and AzortharionUI enabled which does not interact with raid frames.

Was it working in a previous version? If yes, which was the last good one?
I don't believe so.

Do you have an error log of what happened? If you don't see any errors, make sure that error reporting is enabled (`/console scriptErrors 1`) or install [BugSack](https://mods.curse.com/addons/wow/BugSack).
No errors, I have BugSack and BugGrabber.

Please provide any additional information below.

-  Y position breaks, X position is fine.

- Opening and closing Grid2 settings fixes the position
- Y position value is correct when just opening Grid2 settings
- it's sometimes in the correct position after /reload other times not, random 

its related to pixel-perfect scale feature - i checked AzortharionUI and have this feature

i did install lightweighted addon pixelperfectuiscale for test 1440p and its the same. Grid2 position moves and when i open settings - and move some x,y padding margin its fixed until next reload

Grid2 has no pixel perfect features, i cannot fix this issue, its a game decission the placement of the grid2 graphics elements.

Or maybe AzortharionUI is changing the UI scale of the game too late in the boot process, when some addons graphics elements are already configured and placed in the screen.

Grid2 already waits at the last minute to place the UI elements on the screen just to let another addons or code to configure  the UI settings like UI Scale.

Grid2 uses the standad AceAddon library, and sets the ui elements in the OnEnable()  callback , any code changing the UI Scale or another UI elements should do that before the OnEnable() callkback, for example in the OnInitialize () callback.