I've got a 13" Samsung ATIV 9 laptop that I use Sonar X3 to play live with. I've got the current build of Windows 10 on it, and Sonar runs solid on it.

The screen resolution capability on the device is 3200x1800 ... but at that resolution, things can get really microscopic ... so I generally keep the resolution at 1080 on the device ... when running Sonar. That way all the text is readable, and the project buttons are at a reasonable scale for manipulation via either mouse or touch screen.

... but when I open any project with True Pianos in it, Sonar reverts to a resolution similar to 3200x1800. The whole program flips to teeny tiny text and miniscule head of a pin sized controls ... almost impossible to manipulate and see.

Is there any way to prevent the plug from doing this ... or lock Sonar's resolution? I should also let folks know that when the program opens, I get a "Cannot find Master.ins File" error that I click through.

Any help in this matter is warmly appreciated.

Kev- 

As a pioneer in using an Operating system that is not yet supported you have the pleasure of working out all the bugs.

There nothing in Sonar to change, lock or set screen resolution as it and any plugins get their resolution from Wimdows.

Shades of Brazil -
And LIVE, yet! Who said the Frontier Spirit is dead?
(Sorry - I am no help at all - just had to offer my kudos).

One of the funniest (silliest) movies of all time.

I know ... bleeding edge is fun, but often problematic. :D

I was wondering if there was anything in the .ini file that could be tweaked to lock Sonar in at a particular resolution ... or perhaps change the "options" of the plug and alter a setting to keep it steady.

It is ONLY True Piano that triggers the change of the resolution. If the project doesn't have that particular plug in, then it remains at the desired resolution.

It's not the first program to go rogue. My Quicken 2015 will open, but in no way will perform half its functions. Based on your info, I'll also go check on the Insider Forum for Windows 10 to see if there's a way to correct.

As an aside, regarding the error message ...

What does the master.ins do?

Master.ins contains the instrument definitions available to SONAR. To restore the file, hold the SHIFT key when opening SONAR. This adds missing config files like master.ins to your user directory. Note, this is different from safe mode which is triggered by holding the SHIFT key when opening a project.

Great info, Scook. Thank you.

Might not having the instrument definitions loaded contribute to the odd behavior of that plug in?

no

I had a similar issue with Studio One in the past and I figured out a fix. 
 
The issue (I believe) is that normally Sonar is scaling so it's visible even though your display is super high resolution.  But sometimes the plugins don't scale and then I guess the DAW disables scaling and drops into the full resolution which makes everything tiny.
 
There is a fix, but there's a tradeoff for it.  The tradeoff is that you'll most likely have to drop the resolution on your display.
 
Try disabling display scaling for higher-DPI settings.  The way to do that is to right-click the icon for Sonar on your desktop.  Go to the "compatibility" tab and check "Disable display scaling for high DPI settings"  I believe that will make Sonar run without scaling which will make everything look tiny.  However it should eliminate the problem when you open your plugin.  Then you just need to drop your screen resolution until you can see things OK.
 
However I notice that you already drop your resolution down so maybe it's just a problem with the settings stored for True-Pianos or something and this fix might not work in that case.