安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题






I have mostly put all my hobby projects in a "maintenance only" mode. I will still support it and try to fix bugs where possible. I wanted to do more, but for private reasons I just had to stop, and felt it was time to just support it, fix bugs. But I need to pick my battles so to speak and what I spend my energy on. I really wish there was more time in a day.
That is the gist of it. There are other reasons I never added video/audio in the past that you could find if you check somewhere in the history of these comments, but basically at the time it was't possible. And right now I just added a feature stop. I wish I had better news.
The problem is that some of these characters is that if someone along the pipeline of code the encoding is interpreted incorrectly or not up to the newest standards, it can cause errors. The filename receive from WE to open, is ( and I'm making a bit of an assumption here ) not the same as the actual filename ( there are characters that seems to have been processed and changed ).
For now, I think I have the mark this down as can't fix. The correct fix is out of my scope, and any attempts to just apply a bandaid just shows that I can't fix it from my wallpaper. Renaming the file would be the solution.
Thanks for letting me know. I just hope I can fix this one. Bugs must be squashed.
This wallpaper is certainly not the most ideal and far from the most optimized and ill admit to that. But what you are describing does not sound normal to me. The WE devs should know how to reach me, and otherwise tell them they can if they need to. But right now this sounds out of my control and knowledge.
I have no panning, zooming, or transitions enabled. Each monitor is split 3 ways so id imagine that is where the root of the issue lies. The images, just instantly change after 10 seconds, there is no transition. Everywhere in settings hardware acceleration is enabled.
As for my hardware, 32gb DDR5 6000mhz ram, i9 12900ks 16 core, MSI RTX 4090 Suprim LiquidX.
Keep in mind webwallpaper32.exe instances are running on 8 efficiency cores, they are not on par with the performance cores so probably why they utilise more % of cpu.
I would suggest trying to disable panning and/or transitions to see if that helps. If that helps it would really make me think its the hardware acceleration from the GPU that isn't working.
One thing to note that if 1 screen spots multiple processes, it it still only running the wallpaper once. Chromium always starts up with multiple processes for each window. All but one are background processes.
Typically it runs on my efficiency cores and runs fine, but I notice when the instances of Webwallpaper32.exe become unresponsive it will just open a new instance and not close the one thats not responding. So eventually it leads to those 8 cpu cores being locked at 100% when typically they bounce between 25-40% typically.
Ill try boosting its priority to above normal, see if that reduces the process instances from stopping responding. Everything runs fine until one of the instances becomes unresponsive..
Hopefully that irons things out a bit because the whole subdividing each monitor to allow more than one image per monitor is what sets wallpaper engine apart from the other programs like it.
1. weballpaper##.exe is basically just chromium. I do remember it being 3 processes per desktop, but seems to be 5 per desktop ( just to give an indication ). But this is not something I can do anything about as that is a process from wallpaper engine itself to run webwallpaper like mine. So this is something I can't help you with and I will have to direct you to the WE's bug forum for that.
2. Freezing: I would like to touch on this one, because this wallpaper is merely a webpage, it will not have the best performance out there. This wallpaper is prone to some micro stuttering for sure. Transitions and panning options will make these visible. This is often because chromium can only decode ( not load ) an image on the main thread, and as such it blocks the render thread. I have never found a solution for this ( though in recent years stopped checking )
Webwallpaper32.exe sucks, it constantly is freezing and launching new instances until it overloads the cores I have it set to run on. I subdivide each monitor 3 times, I have 3 monitors, there should only be 9 instances running at once, maybe 12 at most, Not 45 instances of webwallpaper32.exe, Each instance is using around 60 threads.
Is there anyway to force SlideshowV4 to use webwallpaper64.exe instead?
What I am trying to do is set up multiple profiles for each monitor. So, as an example, Profile 1 would be Folder A (Monitor 1), Folder B (Monitor 2), and Folder C (Monitor 3).. That I can do...
What I would like is to have Profile A (As above) and then have a Profile 2, that would be say Folder C (Mon 1), Folder D (Mon 2), etc.. I'd like to have multiple Profiles for different folders, setting etc..
What seems to be happening is everytime I set up a new profile it just copies the previous one, so essentially, Profile 1 & Profile 2 are the same..
Any help?
Thanks!
To me it sounds like WE isn't allowing use of the folder for whatever reason. I think that because preset & config handling is done by WE and not by me. I just get the filenames after the folder was selected was accepted.
I would suggest trying the following things: 1. try removing emojies to rule out they are or arent the reason. 2. try to show a slideshow from your document/desktop/pictures folder to ensure that works. 3. try moving the folder to a new location. Anything that might be able to narrow down why WE does or doesn't accept the foldername.
Sometimes, after changing back to Personal Slideshow, I will see initializing, but not see any number of images mentioned, and it will hang for hours. And sometimes, after changing back, it will stay stuck on whatever the Windows desktop background was previously set to.
From what you're saying, it sounds like this might be an upstream bug with how WE loads the filenames...
No worries about looking into this soon. Enjoy your holidays!
When it is stuck initializing, I don't usually see any amount of images mentioned. Usually I will see whatever image the wallpaper was previously set to in Windows personalization settings (usually it's an image set by Wallpaper Slideshow, as it seems that WE interacts with Windows personalization / Windows desktop background settings). Sometimes I see "Use the settings panel to select a directory of images to display", though it seems like an image of that text was previously set as the Windows desktop background, if that makes sense.
It does seem that switching to another WE wallpaper and back resolves the problem maybe 70% of the time. When the problem is resolved, I'll see initializing x/x images within a few minutes of changing back to Personal Slideshow, and then the slideshow will start like normal.
But everything I am hearing right now does make me think it might be that WE is having problems loading filenames from samba at certain moments. I did find that long pausing in WE could cause it to seem the wallpaper restarted. And if the problems occur when the wallpaper start, when WE might not be able to read from samba, that could be the connection.
I do have a question though. When it is stuck initialising, do you see any amount of images mentioned? or only the text "initialising"? And I do understand correct that if you restart the wallpaper is starts fine, as well as changing settings?
And not having controls at the very start is currently correct.
Also, this may be a separate issue, but I noticed that often when resuming from suspend, I am able to see controls / playlists, but no image displays, and I see no items in the playlist. I keep my images on a samba share mapped to a drive letter in Windows. I wonder if perhaps there is a race condition where Personal Slideshow attempts to check/load the image folder before Windows has fully mounted the network drive, after resume from suspend.
If you want feel free to create a discussion and if I got any updates I can update you specifically there. Or not .. I will always post a comment here when I get around to updating the wallpaper. But that might take a while.
- beautiful blue
- landscape
- anime
- games
now my biggest collections are beautiful blue and landscape so they are sometimes the only thing I see for hours without ever seeing anything else, so I want to be able to select multiple folders (multiple categories) and say I want to see today this folder 20% and this folder 20% and this folder 60%
hacky way I found which *could* work is having multiple categories enabled , ignoring duplicates when importing, and just making it more likely a folder will show up by brute force . The problem however I ran into is that the code tries to find the next image by name so it will jump to the very first instance of an image if it runs into a duplicate
I understand if it's too niche and thanks anyway
1. To be able to have images categorized into different folders
2. Then be able to see how much chance a certain folder has to show up?
While I do have to rewrite some of that code to fix a small bug in the future, from what I am hearing now it would indeed be too niche. But I am asking just to be sure, as I got some hacky ideas too that might work.
- a way to determine how likely the will show up like a percentage
- or a way to make it add duplicate files but not break the slide show ?
I have many wallpapers categorized and I often want to change up what is often showing up but I can't do that atm :/
Improved: Fixed a memory problem regarding many filenames. Wallpaper engines feeds the wallpaper all filenames which means I keep them all in memory. While there was code in place to avoid the bug that was occuring, the code didn't kick in until all filenames were loaded and the "memory leak" already occured.
Added: If you set the image size to "fit" then you can repeat the image to fill up the background of the display area.
Added: Can options set the panning direction to always be the same instead of it alternating.
Added: Option to sort the playlist by filename descending.
Not Added: Filtering out subfolder. I will probably end up doing this as this request got me to find a small bug. If you select a new image folder, and it is a child or parent of current folder, playlist will be empty or incorrect until you you restart the wallpaper for now.