Hi Rose,i found that,with the latest update on steam,editing .exe to Unlock PlayStation 4 DLC is not working now,because those number has changed.Is it possible to fix it ?
https://www.pcgamingwiki.com/wiki/Control#Unlock_PlayStation_4_DLC
User talk:Rose
June 14 - Samurai Shodown (2020) becomes available on Steam after being exclusive to Epic Games Store since June 11, 2020.
Not particularly notable but good enough for us, so I made the edit. Thanks.
Hi, I saw that you reverted / partly reverted all my edits on the Area 51 games. The issue is that 99% of users that search for Area 51 will want the 2005 game, but currently we send them to the 1995 game. Shouldn't the most popular game be the standard?
Hello. The disambig template is not meant to link to all games with similar titles like you did. We could improve the description of each of the current two but it's the series box that covers all games of the Area 51 series and allows the reader to easily navigate between them.
The naming of the articles is something to discuss within the talk pages of the relevant articles for more users to notice. Personally, I'm not familiar with the games to argue one way or another but it's otherwise consistent to give priority to the first released game.
At the moment, searching "Area 51" will direct you first to the 1995 game, with a redirect link only to the 2019 game. Only after clicking on the link to the article for the 2019 game does one get a link to the 2005 game.
Look at the article for the 2005 game, and compare it to the 1995 game and the 2019 game. The 2005 game is well-documented, has a number of fixes, and links to a mod that provides better support for modern high resolutions. The other games have basically no information whatsoever. Does this not clearly show which game should be prioritised in search results?
It is something worth a global discussion to be raised on the forums or the article talk page. You have a point and it does raise the question of whether we go by the chronological order, prominence outside of the wiki or go by completion which is always subject to change as the community contributes more information.
Does everything need to be so bogged down by bureaucracy? Even in a wiki for PC game troubleshooting? Why is it that anything which a clear answer needs to be discussed by some politburo ad infinitum so that the beneficial change can never be made? Or until those willing to make the change become disinterested?
I wasn't merely referencing article completion, I was using it as a metric as to which game of the three is the most popular. I think one look at the three articles to see which game actually has people playing it would be more illuminating than discussing a default site-wide policy.
It would be understandable to have the first game in a franchise be prioritised when there are newer games with the same name; technically, Area 51 2005 is part of the same series as the 1995 light-gun game. But why does the article for the 1995 game offer a link only to the completely unrelated 2019 game?
Precedents matter. Considering PCGW does not currently have dedicated disambig pages, the way to realize your idea would be to rename Area 51 to Area 51 (1995) and have the original page redirect to Area 51 (2005). From there, one could argue that any currently popular game can simply take over any other games of identical titles. We would then need a metric to effectively and objectively resolve disputes of this nature.
The alternative solution would be to make no change to the article titles but link from the disambig template (even though all the games are already linked through the series box below the infobox). This would increase the prominence of the wanted article at the cost of repetition and at the risk of the disambig template listing all games, effectively defeating the purpose of the series box (part of the original cause of this discussion).
Honestly, the series box is small and kind of hidden on the right side, you have to scroll down to even get to it. Most people won't even see it.
Hi, thank you for pointing out the issues with my edit on Unity. Before making the new edit though, I thought I should discuss a few matters.
1. ACU has dither-in/dither-out effect when it comes to LOD. A continuously condensing dithering filter will be put on primarily large objects (entire buildings/simplified models, trees/2D sprites, etc.) and then on small details (objects such as lamps and leaves (at the highest LOD setting) or small dirt textures on walls, etc.) as the player approaches them until the old models are swapped out with the new ones. The time window for this is very small (less than a second) unless the player hits 125 FPS. at 125-130 FPS range the time window for small objects will increase exponentially and at 130 FPS+ most assets won't be loaded completely. I have a few screenshots demonstrating this but don't know how to post them on the site, but this very easy to prove. Your note which says: "The weight of the effect is to be judged by each player for themselves" implies that this is subjective but I don't see how. If what the player sees is having their character suspended in mid-air if they enter a building or have the rest of the city look like a very poorly made arts and crafts project, that's an undeniable hit to the presentation. Having said that, I'm still unsure as to how to enter the 120+ FPS status. The player can technically hit 120 FPS but above that is such a broken mess that it's simply unplayable; this is for 120 PLUS after all. [On a side note this may be fixable with a few hex edits, but it's very difficult for me to determine the exact hex value, maybe more experienced users can look into this?]
2. After AC I, every game in the series have been using mouse smoothing and before AC Syndicate all of them have the exact issue: mouse sensitivity is tied to FPS. This could render games that would have been completely fine at high FPS, absolutely unplayable with a mouse (This issue doesn't effect arrow keys or right analog stick, despite sharing the same values) and unity's no different. I could increase the sensitivity exclusively on unity with Cheat Engine and I can provide a guide but I couldn't do it on other entries, but the same principle still applies; it's still a static value loaded on to the memory. Because of this, I thought I should mention Cheat Engine on these entries so others could look into it themselves. I have the intension of adding the guide to Unity, but seeing the Cheat Engine part removed made me question what would happen if add this in on other pages.
Sorry for making this post so long and thanks for reading.
Hi,
You may be absolutely right but the anecdotal nature of your experience is the definition of subjectivity. The wiki still allows self-references but the claims are rather big and thus likely to be questioned even beyond that. You can reference other sources that confirm your findings as per the guidelines.
As for the calling for help, that can be done through the discussions pages or forum threads, but wiki articles are not the place for uncertainty or information that expects the reader to "figure out the rest".
This post was hidden by Radmaxx (history)
"or mention things that hold no value"
In what world do you live in, where telling the user, that you can not disable vignette without also disabling other effects is a "thing that holds no value"?! Maybe next time YOU do the research about what a setting exactly changes so I don't have to come in again and correct it.
There is no added value in repetition within two adjacent sentences. "0 = All off" delivers the same message as "Please note: Setting the tonemapper to 0 will disable all types of tonemapping shaders."
Similarly, the "Look below to see which value has what effect." sentence is unnecessary when the values and descriptions are right below it and impossible to not notice.
Lastly, saying "there is no way to disable those effects individually" holds no value because it provides no solution, which goes against the purpose of fixboxes. The core of your contributions was retained after my edit.
The wiki is a community effort, so you, me, or anyone coming to correct is a part of what it is all about.
There is no citation for the DRM-free executable change as I just tested out myself this afternoon after noticing there was no dll file in the game directory, and it opened fine without needing Steam running! Not sure if there is something else I need to add to cover this?
OK, will take a look at that tomorrow then. Thanks!
Done! I have used some of your wording, hope that's ok.
Thanks. That's alright. The reason I asked for a reference is that the game definitely used to have Steamstub DRM across multiple updates, getting in the way of direct file modification. It's good to know that it is no longer the case.
If Xbox Play Anywhere is going to be removed from key points because its also listed under Availability, it needs to also be changed on Gears of War 4 for the sake of consistency. Id argue its more of a key point and that the reference was useful information for the user and its removal was a detriment but *shrug*
Edit- I see Xbox Play Anywhere does link to a PCGW glossary entry describing the service so my point about the reference is null but the prior still stands.
Also checked all other Play Anywhere title articles just to ensure consistency .
The wiki is community-created, so the presence of something on a page does not make it valid or in line with the current guidelines. Is the key point in question also applicable to the Steam version of the game, making it universal? Either way, the wiki is focused on PC gaming, and it is not expected that most of its users would find this information of extreme importance that should be delivered from the first paragraph. Moreover, key points in general are to be largely replaced by the relatively new introduction template.
Key points are easily digestible and don't waste the users time on walls of text. This has been my least favorite change recently. Regardless, not trying to be argumentative. An observation and suggestion, nothing more.
I understand your concern and I think there is value to it, but nothing on the wiki is mandatory unless it's part of the Assignments system. One can contribute as little as a sentence or none at all. That aside, even under the previous revision of the guidelines, I would stick to my argument on the lack of applicability of the information to most or all users to warrant the prominence that it got.
I made a couple edits in Horizon ZD and they were removed. First and most importantly is the games massive memory leak. On 3 systems (2 intel, one Ryzen 3900) that all had 32 gigs of DDR4 the game went from 10% system memory use to 20, 30 and so on over 2 hours until it hit 68% of system memory usage. All memory was free'd upon exiting the game. There is also evidence that it's causing a memory leak on the GPU end. The game uses 98% of the vram on a 2080ti after 2 hours and 8 99% on a 5700xt.
Next is HDR... the image displayed is NOT HDR. It doesn't reach the proper levels to meet the criteria for HDR but even forgetting that fact the game is running with 8 bit color when HDR is enabled and it should be 10bit. I can directly compare HDR with the ps4 version and the colors of completely wrong when HDR is enabled in the PC version. It's like a different game.
Hi. It was not me that undid the edits but I had supported the decision on the wiki Discord.
The statements looked like a forum post - the style was very informal ("mess up", "apparently", etc) and they addressed the reader directly, which is against the guidelines. Moreover, there was a lot of uncertainty from the use of expressions like "more testing is needed", "seems" and "appears". Coupled with the complete lack of references and explanations for what a memory leak is or how one can benefit from the knowledge, it definitely had no place on the wiki in that form.
Shadowstealer7 improved on it by describing the issue as high memory usage, which is easier to understand and harder to contest, especially when backed with references.
As for HDR, there is nothing in the guidelines that suggests it should be compared to that of consoles before setting it either way. It is simply defined as "Support for expanded color space", which was further supported by my screenshots within the reference comment following your questioning of it.
> Next is HDR... the image displayed is NOT HDR. It doesn't reach the proper levels to meet the criteria for HDR
What criteria are those? I took a couple of screenshots previously today and used HDR + WCG Image Viewer to visualize a heatmap and, uh... I don't see whatever you're seeing.
- Original image (some details are lost in the HDR-to-SDR conversion -- as seen when compared to the heatmap)
- Heatmap (blue-green-orange is basically lower than 300 nits)
- SDR as grayscale
Beyond that, yeah, it sucks that the game doesn't make use of 10-bit at least. Preferably all HDR games should render in 16-bit and then just tonemap it down, but woe betide us. :|
First high memory use is different from a memory leak. I don't know how you would like me to create a reference for it since you need tools to test for said leak. I tested on multiple machines multiple times and every single time a memory leak was verified.
As for HDR I'm not comparing it to the console version whatsoever. It doesn't meet the HDR spec in terms of nits. Again tools are needed for testing. I'm using professional calibration tool, a device that sits in front of the display. The display used first was a 65 inch LG CX OLED and the second was a pc monitor, also an LG OLED (IPS). As a side note LG makes OLED panels for essentially all manufacturers except samsung. The only difference is software that runs the panel and LG is considered the best.
Regardless, it's obvious that there is no way I can "win" here so I will stop trying. That doesn't change the fact that I'm right and even the patch today did not fix either issue.
I understand people might not understand what a memory leak means, and this is not the place to explain but acknowledging it's existence would likely drive the user to search memory leak and they would find a layman's explanation on the first page of Google, bing and duckduckgo.
I noticed all the amazing work you've been putting into the Death Stranding page, and I specifically wanted to ask about the screenshots you uploaded for the key assignments. It looks like you've done a scrolling screenshot of some kind which I'm very impressed with, and I'm curious to know what program you used to do it as I'd like to be able to use the same technique myself when uploading screenshots to the wiki. I've looked a bit into it in the past but I've never had much luck with being able to constantly pull it off as there seems to be different methods and I don't see how it would work for a in-game scrolling window.
Hi! Thanks. It's just multiple screenshots taken and manually stitched together. After pasting the next image, I temporarily reduce the opacity of the new layer, zoom in and manually align the pixels with the arrow keys.
Ah jeez so you do it the hard way. It did cross my mind that you might of just been manually editing the images yourself, though I should of realised it was the most likely answer. Big props to you then for going to all that extra time and effort!