Deskscape wrong background

I've installed Deskscapes, and selected a backdrop. I picked another backdrop because it wasn't a widescreen one. Now, when I activate a DriectX application and quit, the dreamscene displays a screenshot of the old scene A, then after a second, switches to scene B. I'm assuming this is to give the illusion it runs in the background, or prevent the scene from disappearing. Does anyone know how to fix this? I've rebooted several times, but its not working.
5,233 views 3 replies
Reply #1 Top

What happens if you apply a standard wallpaper, then a dynamic dream (for example the bouncing box) and then the one you were trying to use? Does that help at all?

Which is the one you're trying to apply and which is the one that's hanging around for a second?

What is the videocard you're using and the video driver date/version?

-Mike
[Stardock Support]

Reply #2 Top
No, applying a regular file as a wallpaper, then selecting a dream scene doesn't help. It will look fine, until a full screen app like World of Warcraft is running. When quit, the wallpaper will be there for a second while dream scene reloads and starts the animation back up. As for the video card it is a NVIDIA GeForce 7900 GTX, 512MB ram.

The drivers are ForceWare 163.69 drivers, I'm not sure of their release date.

It actually dosn't matter what dream I pick, the old choice, if it be Wallpaper, Dream, or Dreamscene file seems to stick around in some from of a screenshot.

It also seems to occour if I hit alt+tab and select the desktop from the program list. The background in the preview looks like the dream, but when you select the desktop, it flashes back to the background, and the dreamscene returns. I'm using the following dreams gotton from wincustomize

PoubelRaysV10

I just tried "notastargate" and that one seems to be different and work, without bringing up the previous wallpaper selection. Could it be because there is a static screenshot in the dream or something?

Reply #3 Top
I think I fixed it now. Vista's background was set to not stretch to screen, and i think that somehow triggered it. Now that it is set to stretch, it seems to be working