Wallpaper Engine

Wallpaper Engine

View Stats:
Vodka Apr 9, 2018 @ 11:17pm
Custom wallpaper option won't work
For some reason I few days to now the custom wallpaper don't want to load, instead of it, it just shows a white screen. I read alot of discussions saying about being problem of the wallpaper script itself and only the creator of it could resolve but it turns out it's on EVERY wallpaper, I tried to uninstall and reinstall it but no success, it still the same. Every time I select an image from the deafult windows image folder (the same I've been using all those years without any problem with wallpaper engine) which is the same folder windows links with onedrive (as I said before, it worked without any problem in the past, is not onedrive's fault) so if I need to format my computer i can still use the same image with wallpaper engine simply dont work anymore, interesting tho if I put the image on ANY other folder it works, but its not the ideal for me for the reason it always worked pretty well with the deafult images folder of windows and if I need to format the images will be always there. Also, sometimes when I start my computer I got an error saying
Failed to create child process: bin/ui32.exe (Windows error code: 2, Dir relative to: C:\Program Files (x86)\Steam\steamapps\common\wallpaper_engine)
which is weird cause when I go on the folder the ui32 still there...
It starts again after I click Ok on the notification, but still, with white wallpaper in any case
Sorry for my bad grammar, I'm not american
Originally posted by Biohazard:
Do you think you could try the most recent beta version in regard to this: https://steamcommunity.com/app/431960/discussions/2/350544272219415004/

I think OneDrive's files are now an amalgamation of symlinks and files, which sounds weird and honestly I don't really get it, but I think I was able to find a way to single them out so they can be handled normally now.
< >
Showing 1-15 of 21 comments
Biohazard  [developer] Apr 10, 2018 @ 4:22am 
Regarding the latter error, the files of the program were moved. Windows does not update the auto start setup then.

You need to close the program and open it from Steam, so that it is started from the currently installed location. Then disable and enable the auto start. Perhaps this will also help with OneDrive, but I don't know.

OneDrive is a special folder. It might not be ready quickly enough if you use 'high priority' mode so perhaps you could try it without that.
Vodka Apr 11, 2018 @ 7:23am 
Thanks for the response! Yeah... I always open it from steam, maybe if I go to the regedit on start up configs I could fix this bug? I already messed with this thing before in the past for another program, so it's not a big deal to me to mess with it if this could resolve something in first place. What do you think? Should I give a try?

I can't understand why OneDrive is a special folder, It always worked pretty well with your program back then, but now sunddenly it stopped, also, all the images are saved on my computer, so they are there even with or without OneDrive being executed
Is not like a cloud only folder or something, it has his own directory (which is C:\Users\myusername\OneDrive\Images). Maybe if I somehow uninstall onedrive and then install back again it could resolve this bug? What do you think?
Biohazard  [developer] Apr 11, 2018 @ 7:44am 
Originally posted by Vodka:
maybe if I go to the regedit on start up configs I could fix this bug?

I think all you need to do is start it from Steam and then turn auto start off and on, this should register it in the proper location again and the error about bin/ui32.exe should not happen anymore.

Originally posted by Vodka:
I can't understand why OneDrive is a special folder

The user folders are not directly accessible after login, same goes for the desktop 'folder'. So with high priority enabled, the program will try to access a path that doesn't exist yet.

However with OneDrive I think there are even additional restrictions, at least some people reported they had issues accessing it in the past. Perhaps try the two things above first and it might make the OneDrive folder accessible again without any further action.
Vodka Apr 11, 2018 @ 11:05am 
Originally posted by Biohazard:
Perhaps try the two things above first and it might make the OneDrive folder accessible again without any further action.

Yeah... I tried and It did not worked, but when I uninstalled the Onedrive it worked again, all the images on the same OneDrive directory (which was not deleted after the uninstall) was working normally, but when I installed it back the white screen appeared again. There is most centanly new additional restrictions to OneDrive probably because a new update... I really hope you can resolve that on a future update, even tho is not your fault, maybe you can find a way to fix that in the future? I don't know, but it's certanly OneDrive has changed something. Til' there I will keep with the workaround of manually putting any image I want as custom wallpaper in another folder every single time.
An additional note: Isn't only in the images folder of OneDrive, is EVERY folder located in OneDrive AFTER he is installed that makes Wallpaper Engine goes blank on custom wallpaper. Dunno if this could help you with something but I wish you the best to resolve it, I really like your program and how simply it is to use, but with this "bug" it's getting a little bit... "tricky". Thanks for the responses!
Biohazard  [developer] Apr 11, 2018 @ 12:11pm 
I don't think I can change anything from inside Wallpaper Engine. To the program, it is like any other folder.

When you don't have the OneDrive program installed and running, the access works to the same files? It only doesn't work when OneDrive's program is running?
Vodka Apr 11, 2018 @ 2:46pm 
When it's uninstalled it let me access the files like any other folder, but before uninstall I tried closing the OneDrive process to see exactly if not running it would let me access the folder through wallpaper engine, it doesn't aswell, It's like OneDrive gives the folder some privileges when it is installed.
I also tried to install the OneDrive in another folder and then the default folder as cited before (C:\Users\myusername\OneDrive\Images) is working like a charm, meanwhile, the new OneDrive folder (C:\Users\myusername\Cloud\OneDrive\Images), isn't.
Dunno if they added a new registry that changes the folder somehow, but It's just like that:
-Uninstalled = Works
-Installed, Not Running = White screen
-Installed, Running = White screen
Biohazard  [developer] Apr 11, 2018 @ 3:19pm 
What if you create a symbolic link to the image folder inside your onedrive folder and then let Wallpaper Engine access it through the symbolic link? https://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/

Otherwise OneDrive might have some kind of options somewhere to be more permissive, but I wouldn't know where to look exactly. It sounds like not the OneDrive background application is causing it but something much more fundamental, like you said.

Maybe this file will contain some information, could you share it via www.pastebin.com ? C:\Program Files (x86)\Steam\steamapps\common\wallpaper_engine\bin\debug.log
Vodka Apr 11, 2018 @ 4:16pm 
So.. I created a Symbolic link as directory junction, it worked pretty well, but yet, the wallpaper engine returns a white screen...

About logs..
I did a fresh start on Wallpaper Engine, and proceed to:
-Start it from steam
-Change from one wallpaper installed to another
-Change it back again
-Select the custom wallpaper located on OneDrive
Keep in mind this is a clear log too
Here is the log:
[0411/195331.371:ERROR:broker_win.cc(134)] Error sending sync broker message
[0411/195331.371:ERROR:command_buffer_proxy_impl.cc(101)] ContextResult::kFatalFailure: AllocateAndMapSharedMemory failed
[0411/195403.507:ERROR:broker_win.cc(134)] Error sending sync broker message
It seems that the errors broker_win and command_buffer, just appears randomly from one wallpaper installed to another (I use notepad++ to see when the log was being updated) sometimes it shows, sometimes on the SAME wallpaper it doesn't. Still no logs when I select the custom wallpaper.
I'm also using "verbose" on log level

Now the other one (whith more information on it) I will put on pastebin:
https://pastebin.com/Gtr1Tfqd
This one I tried alot of different options on wallpaper engine trying to fix the white screen, and as it might show to you on the logs
Edit: also this log is older than the first one
Last edited by Vodka; Apr 11, 2018 @ 4:18pm
Vodka Apr 11, 2018 @ 4:22pm 
And I just got an achievment called "Pest" and I bet it was for 128 warnings from changing so much and so fast from a wallpaper to another lol
Last edited by Vodka; Apr 11, 2018 @ 4:22pm
Biohazard  [developer] Apr 12, 2018 @ 6:14am 
Most of these errors are just from Chromium and some from the wallpaper, none seem to be related to file access though.

Perhaps you could also share this file: C:\Program Files (x86)\Steam\steamapps\common\wallpaper_engine\bin\log.txt
Vodka Apr 12, 2018 @ 9:11am 
Okay... So there is two:
This one is from wallpaper_engine folder
https://pastebin.com/TMf08pad
This one is from wallpaper_engine/bin folder
https://pastebin.com/2aDQk0Ep

Now this, as before, is from a fresh start:
This one is from wallpaper_engine folder
https://pastebin.com/hiAqWEYL
This one is from wallpaper_engine/bin folder
https://pastebin.com/6xXU3gFq
IMPORTANT NOTE: I DID NOT USED THE SYMLINK I CREATED BEFORE ON ANY OF THOSE LOGS

Same steps as before:
-Start it from steam
-Change from one wallpaper installed to another
-Change it back again
-Select the custom wallpaper located on OneDrive
Also, the log did not updated after chosing a custom wallpaper, it only updated when I changed from one installed wallpaper to another

It seems like after the OneDrive being installed it changes the whatever folder he is located to a symlink, and gives privileges which wallpaper engine can't access, is that it?

If you want me to try with the symlink I created before and then post the logs to compare the differences betwen OneDrive and the symlink created, just ask for it.

Last note: On that logs, the only thing I edited it was the user name to "myusername" to stay like said before.
Last edited by Vodka; Apr 12, 2018 @ 9:12am
Biohazard  [developer] Apr 12, 2018 @ 9:17am 
Yes, this error must be related:

2018-04-11T23:07:09Z: Deny request: 'C:/Users/myusername/Cloud/OneDrive/Images/4096x2160-70609-nebula-space-art-4k-ultra-hd-wallpaper__space-and-galaxy.jpg' is a symlink or not a file (file:///C%3A/Users/myusername/Cloud/OneDrive/Images/4096x2160-70609-nebula-space-art-4k-ultra-hd-wallpaper__space-and-galaxy.jpg).

This simply means that Wallpaper Engine is asking if Windows if this file exists. Windows says no. Windows is probably lying to Wallpaper Engine because of something OneDrive is doing to 'protect' the files.

Also there are two different paths, which is weird:

C:/Users/myusername/OneDrive/Images/link/4096x2160-70609-nebula-space-art-4k-ultra-hd-wallpaper__space-and-galaxy.jpg C:/Users/myusername/Cloud/OneDrive/Images/4096x2160-70609-nebula-space-art-4k-ultra-hd-wallpaper__space-and-galaxy.jpg

One is with 'Cloud' and one is without. Perhaps that is how OneDrive is breaking this, so not a permission issue.
Vodka Apr 12, 2018 @ 9:28am 
Did you got the log from the last one from the fresh start or the older log (the first two)? Maybe you found two paths because as I said before:

Originally posted by Vodka:
I also tried to install the OneDrive in another folder and then the default folder as cited before (C:\Users\myusername\OneDrive\Images) is working like a charm, meanwhile, the new OneDrive folder (C:\Users\myusername\Cloud\OneDrive\Images), isn't.

The "file:///C%3A" part on the logs is common right? Or should it not happen too?

So there is no way to fix this bug?
Biohazard  [developer] Apr 12, 2018 @ 9:41am 
Ah, yes, then the paths were both fine I think. The weird characters are correct too, it is just URL encoding.

I set up OneDrive and Windows is apparently saying that these files are just not 'files'. I'm using the library 'Boost C++' for this. Maybe these are some new special files I can detect by fixing it inside Boost or there is just no way to detect them as some other kind of 'file'.
Vodka Apr 12, 2018 @ 9:55am 
Okay.. So clearly it's all the fault of some update on OneDrive right? As I never had problems before with it and suddenly this happens... I hope on future you or OneDrive itself can fix it and we can get rid of this, and I hope all the info here provided helps you out, I will keep using as I mentioned before with workaround. Thanks for the responses though! Nice to see the developer cares about it's costumers and also his program. I really appreciate it!
< >
Showing 1-15 of 21 comments
Per page: 1530 50

Date Posted: Apr 9, 2018 @ 11:17pm
Posts: 21