My Living Desktop works great with Mountain Lion. Occasionally there is an initial installation issue. After first upgrading, if you receive a message saying that My Living Desktop is not compatible with Mountain Lion or if it behaves strangely, simply reboot your Mac and start My Living Desktop again. You might need to do this twice until Mountain Lion fully recognizes My Living Desktop. After that, My Living Desktop runs fine.
There is a problem with some version of OS X’s screen saver selection preference that will incorrectly report this message. This can come up right after an update to My Living Desktop but does not always happen. The fix is simple: Just select any other screen saver then re-select My Living Desktop. That resets the screen saver selection within OS X and the System Preferences and fixes the problem.
There is a problem with OS X that sometimes the USERS screen saver folder does not get created automatically like it should. This can cause My Living Desktop to misbehave during registration. To resolve this issue, simply launch My Living Desktop and when asked if you want to install the My Living Desktop screen saver, you must say YES. You needn't use the screen saver, just install it which will create the missing screen saver folder. Then just register your My Living Desktop as usual.
Removing My Living Desktop is as easy as dragging the application to the trash. As long as it is running, it will detect that you have trashed it and will commence removal of all the portions of itself: the screen saver, the scenes, the preferences, and other miscellaneous files.
There is a problem with some older Quicktime Video Codecs Plugins such as Flip4Mac, Divx, or 3ivx that can cause a message about scenes being corrupted when they are actually fine. These and any other outdated Quicktime Codecs must be properly removed in order for My Living Desktop to work correctly. It is recommended that you run the appropriate un-installers for each of the old Plugins and in the case of Flip4Mac, they have finally updated their codec to work with 10.7 and 10.8.
Several users have also found success by simply reinstalling OS X. You can do the simpler overwrite install of OS X instead of a full clean install and this resolves the issue as well.