Anybody experienced this behavior .? look at the left PC (don't pay attention to the drawing witch is for another thread)
 

 
click on off makes it display good ....
 
also i noticed that the first time i launched platnum (coming from X1) i hade visuals near the PC names modules when you want to isnert FX (like the LA2A picture near the name to insert it) , now i have names only expt for the X1 based one )

Starting with X3, when VST3 was introduced, you're supposed to reset and rescan your vst's.
Have you done that?
Since you're moving from X1 to Platinum, I would expect that you would need to do that.

it's done by default ....when i launched X1 µ...it rescaned all existing one and recreated entry ....

Seen something similar once in Platinum. I replaced a prochannel module with one with a smaller interface. It looked like the new module's graphic was superimposed on a blank grey one like your screenshot shows.

Switched view away from PC and back and everything was back to how it should be. So far I haven't been able to reproduce the error. Over that last 30 years I've seen other software and Windows itself scramble its graphics once in a while so if it's not a common thing in Sonar it might be a Windows/graphics card or driver issue.

Zo
it's done by default ....when i launched X1 µ...it rescaned all existing one and recreated entry ....

Reset and then rescan, not just rescan.

Yup reset + rescan.
 
Also try updating your display drivers.

Thanks.

Moved to Sonar forums for further discussion, if a reproducible bug is found we can move it back to problem report forums...

I made a thread on this for this reason with Platinum. A reset plus a rescan should be made. 

For those having the gui issue

1) locate the "Internal" folder (in ...:\....\....\Shared Components\Shared Utilities\Internal) cut the the dll with issues , past on desktop
2) Laucnh Platnum ....
3) close platnum 
4) bring back the dll in there location 
5) relaunch PLatnum

Done ....

For the softube :

Passive EQ , Active , Focusing , Tsar adn Fet ...i'm still trying to figure it out cause they're not in internal , and doing the workaround on the regular VST did done the trick (witch is a full reset scan but only on plugin we want ) 
 
No need to do a full rescan , rescan of the cuplrit is what solves it .....

But you still need to do a reset and rescan for the VST3 migration or uncheck the vst3 migration options.
Wow, you're stubborn!