User talk:PCFPCGW

How did you determine it uses that?

https://www.pcgamingwiki.com/w/index.php?title=Commandos:_Origins&diff=1524271&oldid=1522348

It shows up in the SteamDB files for the demo, I guess it must not have ended up shipping with the final game.

https://steamdb.info/app/3137720/

That's not reliable anyway as stated by SteamDB:

"This process is entirely automatic and does have mismatches"

Only the PhysX indicator of the nvidia control panel is definitive.

Hi,

I noticed you had set the Steam Input API parameter to true on The Inverse, an unreleased game. Please do not do this unless you have the game actually in hand and can verify its support.

The Steam Input API refers to games natively relying on/using the Steam Input API. It does not refer to games that Steam Input (note the lack of "API") works with.

The vast majority of games does not make use of the Steam Input API. And many games that might use Steam Input to support e.g. PlayStation controllers on the Steam client still does not use the API to enable that functionality.

Refer to the Steam Input sections for more information, with a specific focus on the Supported games breakdown. The editing guide can also be of use.

If the intention were to indicate that Steam Input can hook input within the game (required for regular Steam Input to work), you were most likely after the "steam hook input" parameter instead. However also note that this parameter also shouldn't be filled out without actually verifying that a Steam Input emulated/translated controller works within the game beforehand.

Understood, will not happen again

Thanks! Also, I just realized that Steam's own tracking is often completely wrong due to lackluster actions on the part of Valve, and developers end up filling out the information on their store page wrong as a result.

See this recent edit for more details: https://www.pcgamingwiki.com/w/index.php?title=Store%3ASteam&type=revision&diff=1575983&oldid=1575089

Hello, this is a message regarding the removal of OGG Vorbis and XAudio2 from the middleware section of articles.

By popular definition, middleware refers to additional software libraries that sit between an application and the OS, usually for functionality that the OS cannot handle on its own. Examples include FMOD, Miles Sound System, and Wwise for audio playback, Bink Video for video playback, Havok and PhysX for physics, Criware, etc. All of these are software-driven solutions for multimedia features that are not found within the OS itself.

OGG Vorbis and XAudio2, despite how these technologies may appear, are not considered middleware. OGG Vorbis is an audio file format, like MP3 and WAV, that is then processed through audio middleware like FMOD and MSS for playback. On the other hand, XAudio2 is a low-level audio API provided by Windows, not unlike XInput for input or Direct3D for graphics. XAudio2 being an API component of Windows itself differentiates it from middleware solutions.

Hopefully this clears up the reasoning for these two items being removed from the middleware sections of articles. Audio documentation throughout the wiki is generally messy and there have been other inaccuracies, such as DirectSound3D and Aureal A3D being listed under the EAX field of the Audio template on several pages when DS3D is actually the API that EAX provides extensions to, while A3D is a completely separate audio API of its own. I may ask the PCGW staff about adding an XAudio2 field to the API template in the future.

Thank you for your clarification. I appreciate the time. I will adjust my editing accordingly!

Hi, please familiarize yourself with the System requirements section of the editing guide. These edits do not follow the guidelines:

• https://www.pcgamingwiki.com/w/index.php?title=Nightmare_of_Decay&diff=next&oldid=1257002
• https://www.pcgamingwiki.com/w/index.php?title=Nightmare_of_Decay&type=revision&diff=1256995&oldid=1256883

In particular, note these specific guidelines:

• Format to use when writing CPUs:
  • General CPUs (i.e. no specified brand): <frequency> <CPU type>
  • Specific CPU (i.e. specific Intel or AMD processor): <CPU name> <frequency>
• All CPUs and GPUs will be named out in full.
  • Ex. Intel Pentium II, ATI Radeon 9800 (CPU and GPU brand should alway be included for specific processors)

Let me know if you have any questions.

Thank you! I was not aware. I will make sure to familiarize myself with this and reflect that in my behavior

Hi! I am writing to you about Cocos2d and the definition of "engine". If Cocos2d is used simply as a wrapper, is it really right to list it as "engine" on a game page? Listing it under "Engine" makes it look like the whole game was made using it. But maybe it's just me.

There is precedent for adding wrappers into the "Engine" field. Consider ScummVM, which really isn't even an engine. Yet it appears not only in the "Engine" field, but the release date field as well in the Sam & Max Hit the Road article. Unity is also listed as an engine for Doom Classic and Final Fantasy IX.

If you want to make it clear to readers that Cocos2d isn't the original engine, you could mention it in the intro and/or add "Wrapper" to the engine template:

{{Infobox game/row/engine|Cocos2d|Wrapper}}

Thank you for the response, you two. I am fine either way, as long as clear guidelines are set for me to follow. The main point of confusion for me was Halo: The Master Chief Collection, which is listed as using Unreal Engine 4. However, none of the games actually USE Unreal, it's just used as a wrapper for the main menu. So, would we have to clarify there? I thought it would be obvious if it was meant to be a wrapper but maybe I'm not thinking correctly. Regardless, a clear guideline would be very helpful. Thank you and I apologize for any inconvenience

Halo: The Master Chief Collection is something of a unique situation since we also handle that bundle of game uniquely on PCGW as we tried to see if a "collection based" "game" would be feasible on the site, so it's doubly unique I guess :D

Anyway, the main page actually has a * besides the Saber3D Engine that clarifies the point. I guess it could be possible to add a similar star to the other subpages as well, or alternatively we could just omit Unreal Engine 4 on the subpages while retaining it on the main Halo: The Master Chief Collection page, since as you mention it's only used for the main menu.

Either solution would work, I think.

Please do not

1) Upload covers separately when you can replace them with "Upload a new version of this file" (The images are cached and it will take time for thumb to generate)

https://i.imgur.com/o6uzmf1.png

2) Replace already higher quality covers with the lower res Steam ones. Only exception is if the previous cover is littered with logos or has abnormal aspect ratio.

3) Use random names for the images. We always use "Game name cover.jpg" or .png

I have cherrypicked what covers were better but majority of them were deleted, because they were either worse quality or totally different design.

Sorry about that. I'm still new to this and I'm trying to give back to a website that has helped me a lot. I'm still figuring things out so I apologize for any inconveniences

I will make sure to be more careful with how I handle things in the future

Thank you! Have fun editing :)

Hi many thanks for contributing to the wiki and adding reception scores. I just wanted to check you are aware you may be adding IGDB user scores rather than critic scores - please take a look at our updated Editing guide.

In an attempt to bring focus to the issue, I've issued a temporary 1 hour ban to your account. I'm currently in the process of correcting all of the pages to the critics score from IGDB instead of the currently listed member ratings score of IGDB.

I see. Thank you so much for correcting me and I'm sorry for any confusion this caused

Thank you, I've removed the block again.

I went through the last few pages that I hadn't gone through yet, so I believe all of the previous pages have been corrected now. Feel free to continue to add the correct IGDB score on new pages :)