Wallpaper Engine

Wallpaper Engine

The Pulse
Lord DN 17 Mar, 2017 @ 3:50am
waveRenderer.init
The wallpaper is not working for me. The right side looks something like this[prntscr.com] and the left upper corner looks like this[prntscr.com]. The rest of the wallpaper is black. Is there anything I can do to fix this? Is this a bug in the code? Also please note fps counter is disabled in the settings, and it still shows one.
Last edited by Lord DN; 17 Mar, 2017 @ 3:52am
< >
Showing 1-6 of 6 comments
Squee  [developer] 17 Mar, 2017 @ 9:52am 
Is there any chance the "audio recording" checkbox is turned off. The message "wavaeRender.init" is all good, but it should be hidden once the wallpaper receives audio. So that bit would suggest it isn't receiving audio ( or there is another problem occuring that caused the wallpapers to not start correctly ).

But that still doesnt really explain the fps stats still showing. That suggests the wallpaper isnt starting correctly. Was it like this since you downloaded the wallpaper? Or have you been able to use it and change the settings, after which it stopped working?
Lord DN 18 Mar, 2017 @ 4:41am 
The audio recording is turned on. I downloaded it since it looked nice, but I haven't been able to use it yet. It has never worked for me.
Squee  [developer] 19 Mar, 2017 @ 6:50am 
I am clueless what it could be. It just looks like its not starting up as its showing elements that should be hidden once it started. I would have to dive back into the code as I havent worked on it in a long time to see which situations could cause it not to boot.

After starting the wallpaper could you look into the folder ....\steam\steamapps\common\wallpaper_engine\bin\ and then open the files debug.log and log.txt with notepad or something and check their last lines to see if you can see any message that might be related?
Lord DN 20 Mar, 2017 @ 7:39am 
When I tried starting it about a minute ago it just..worked..so I guess there's nothing to fix anymore, still want my debug.log contents?
Squee  [developer] 20 Mar, 2017 @ 11:26am 
Did you reboot since the problem? Then maybe the reboot fixed something .. And no need for the debug.log if its fixed, but if it happens again I would be curious. Most likely there is nothing in there that can help me, but might as well check to be sure if it occurs again.
Lord DN 20 Mar, 2017 @ 11:36am 
Yeah it's been 1 reboot since then
< >
Showing 1-6 of 6 comments
Per page: 1530 50