New Monitor Broke SDK

Here’s a weird one. Today I got a fancy new Samsung Odyssey G7 4K, curved monitor. It works perfectly in all respects except for the SDK. Typing and gaming, including MSFS itself and its virtual cockpits, all work as expected (and much more immersive than my old, flat 1080p monitor).

HOWEVER, I can’t use the SDK at all. This is because the clickable areas for all the buttons, menus, etc., do not correspond to where those buttons, menu, etc., are displayed. The clickable areas are actually displaced about 3" left and 3" above where the buttons are drawn, which means I can’t use anything near the top or left edges of the screen, and have great difficulty using anything near the right edge. So basically, the new monitor has made the SDK unusable for me.

Anybody seen this or have advice? Like I said, it’s ONLY the SDK that has this problem.

The only thing I can come up with with a short brow ruffle is try the SDK while running a lower refresh rate maybe?

This happened to me when I had the sim in windowed mode.

1 Like

Thats because when using the SDK you must set the sim to the full native resolution of your monitor. If your monitor is 4K you must set the sim to 4K. I thought that Samsung G7 was 1440p native resolution? I might be wrong though.

1 Like

OK, I’ll check the game settings for the resolution. You are correct, it’s 1440p native. But every other program I’ve run, from just Windows itself on up to various games and apps, has automatically rolled with new monitor. MSFS gave every indication of having done so just flying around normally before messing with the SDK.

Anyway, went into MSFS, changed the rest to match the monitor (it was still 1900x1080) and now the SDK works again. Thanks muchos.

1 Like

Glad you got it sorted.