安装 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(越南语)
Українська(乌克兰语)
报告翻译问题



https://webcache.googleusercontent.com/search?q=cache:zQIL_wJevFAJ:https://psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/%3Fid%3D2027909325
Interestingly though, you can't re-upload the exact same image with the same name. Steam will see it's a duplicate (even though it shows up empty and as 0.00kb when editing the guide). Changing the image slightly does however work.
Anyway, thanks getting back on the topic!
When will this bug be fixed?!
If you have the image on your computer, you can just change the image slightly (I changed a single pixel in MS Paint), save it, and upload it. Without having to change the guide at all, the picture should show up again.
So doing some hunting (after Steam support tried to tell me it was a client issue - despite the fact that affected 3 people I checked with, and any browser or client), I see that today, the fixes I just put in 2 days ago are all gone again.
But I also noticed that the "last Update" timestamp was showing as a week before the date I did my update (it shows as the 19th, when it should be showing the 27th).
So server synchronization seems to be rolling back my fixes at some random time frame, to a random time in the past (a week or so).
Now that I've noticed this aspect, I have created a new support ticket (since they automatically closed the last one - a half hour before I saw the new problems- argh!!!) detailing that my changes got rolled back somehow...
I'd suggest anyone else experiencing this to start adding notes (I use the private dev comments) to insert the time stamp that I make each fix attempt. Creating a log trail...
Maybe it will help steam get off its arse and do something to resolve the issue.
I e-mailed support to point out the frustration, but all I got was "we'll pass it along".