What RnD said. I chose to not show wallpapers in the DS UI and the  DS Config wont show my previously applied background to revert back to it. I had to open WB Config to reapply the wallpaper.  Win7 Ultimate 64 bit.

 I set it to run a dream on monitor 1 only. It changed my wallpaper on monitor 2 to Desktop Earth  dream.

(OK, that worked Zubaz. I was looking in the config for a way to unload, like in former versions.)

EDIT: Sorry, I mistook your first reply to be a facetious one...hehe.   Yes, I want to load a wallpaper = Unload DeskScapes.

It seems like there should be a way to disable DeskScapes from within the DeskScapes UI. Who would think to apply a wallpaper from outside the DS UI to disable DeskScapes?

Applying a wall from within DS doesn't unload DS.

Here too. Even with wallpapers showing, the previously applied wall isn't an option. So what you end up with is having to go outside of DeskScapes to unload DeskScapes.

I had to apply a wall with DisplayFusion in order to unload DeskScapes.

I guess the question is why do you want to disable it (unload has never been an option)?

Duh, why wouldn't we?  I like changing my wallapapers with DisplayFusion. I don't want DeskScapes to handle wallpapers.

Neil, in earlier versions you would have the option to load your default background (unload DeskScapes)

 Quoting Neil, reply 8.         "I guess the question is why do you want to disable it (unload has never been an option)? "           

Same here, it loaded Aquarium, the first in my list, on the other monitors. 

BTW, I changed it again and I got a dream on monitor one, same selected dream on monitor two. Monitors 3 and 4 got an unchosen static wall. And I don't have wallpapers showing in DeskScapes.

The CPU usage used by a dream has not changed with DS8.  The preview may use more because it runs things at a slightly higher resolution internally than before, but an applied dream should be the same as before.  When it comes to video dreams the cpu usage is very much controlled by two things, your video codecs and your video drivers.  Videos use cpu to decode, thats a fact of life.

Now if thats a static wallpaper using all that cpu then thats something that needs addressing.  If nothing else I would be interested to know what process is using the cpu.

To use that much cpu would be interesting especially as it would apparently be on multiple cores which doesn't fit with the standard cpu usage pattern.  I assume it isn't a case of DeskScapes UI obtaining your list of images and building previews is it?  Thats a cpu intensive task and if you have shown it your entire my pictures folder for example it can take some time.

The easy way to tell is see what process is using what.  DeskScapes dreams when applied should use cpu in the explorer process.  DeskScapesConfig is the UI process and DSHost is used for certain dream combinations when applied.

I've been testing it with different dreams and it's not using enough cpu cycles to even register.

This is what we would expect to see.  It will vary depending on dream type.  I would expect static walls = none, dynamic = varied depending on the dream, but typically low, hybrid = low and video = more depending on encoder type, bit rate and any hardware acceleration.

Neil, do beta releases get given to use so we can "beta test" and report back?

That's all I'm doing here.

If you removed the option to revert to my previous background, why not just say that. Say it's not a bug and it was intended to leave no way to disable/unload DeskScapes?

Your answers here come off as if they aren't bugs and you intentionally chose not to give an unload option.

One should not need to load a wallpaper with a third party application in order to disable/unload DeskScapes.

And it disabled DeskScapes.

Trust me it worked the same.  The UI was a little different but the same rule applied.  A dream had to be applied to the primary monitor (by dream I mean anything that can be applied from within the UI).

Going forward the best solution may be for DeskScapes to simply look at the last applied wallpaper and set it to any monitors that do not have an applied dream.

OK, same rig and codecs, same dream. DeskScapes3, vastly different results.

Note that CPU use is assigned to one core. Somewhat high, but I have 3 more cores to play with.

Again, only one core in use with the result of much less total CPU being used. I am not sure how someone with a single core system could even run DS8.

Two items of note. On the fresh DS3 install, it showed my wallpaper on monitor one and Desktop Earth on the second in the UI until I clicked on monitor 2 in the UI. Then it showed the correct walls applied on both. Applying a dream to monitor one left the wallpaper unchanged on 2. I am not using Display Fusion, btw,and use WB to apply walls for the most part.

Also noted, the preview in DS3 paused when moving/resizing the config window or using the snipping tool. In DS8 it does not. Not a biggy there.

I am merely pointing out what I am experiencing, not knocking the software, as I was under the impression that this what beta testing is for. I have used DeskScapes since it's release and have had this rig for years so I am familiar with its performance. I made note of what I observe to be major, in my opinion, changes in the operation and function of the new version. As we all know, not all systems will react the same with all software. 

Monitor1 Acer X223W on NVIDIA GeForce GTS 450

Current Resolution 1680x1050 pixels

Work Resolution 1680x978 pixels  

State enabled, primary, output devices support

Monitor Width 1680  

Monitor Height 1050  

Monitor Bpp 32 bits per pixel

Monitor Frequency 59 Hz  

Monitor2  PL716s on NVIDIA GeForce GTS 450

Resolution 1280x1024 pixels  

Work Resolution 1130x984 pixels  

State enabled  

Monitor Width 1280

Monitor Height 1024  

Monitor Bpp 32 bits per pixel  

Monitor Frequency 75 Hz  

NVIDIA GeForce GTS 450  Memory 1024 MB  Memory type 2  Driver version 9.18.13.1090 (310.90)

No additional codecs or media players installed. Win7/64 Ultimate and what came with it.