Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
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.
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?
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.
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.
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!
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?
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
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
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
Perhaps you could also share this file: C:\Program Files (x86)\Steam\steamapps\common\wallpaper_engine\bin\log.txt
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.
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:
One is with 'Cloud' and one is without. Perhaps that is how OneDrive is breaking this, so not a permission issue.
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?
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'.