| ||||||
Table layout[]
The latest revision, that uses the table, is much more confusing and much harder to read than listing the patches under separate subsections. Please, if you're going to make such a huge change, try to improve on it so it becomes a bit clearer. Right now the version numbering is all over the place and makes no sense, the dates look awful on the second row in each box, and the table just looks bad in general. I'm not going to come in here and revert such a big change, but I do hope someone improves on it.
—Preceding unsigned comment added by 62.106.4.250 (talk • contribs) 18:21, December 11, 2015 (UTC). Please sign your posts with ~~~~!
- The purpose of the table was to make it clear that the PC patch called "1.2.37" is exactly the same as the PS4 patch called "1.02" and the Xbox patch called "1.2". All three of those patches will apply the same changes to the game, and will cause the version number "v 1.2.37.0.0" to appear in the "Settings" menu of the game.
- Looking at the New Vegas patches page, it's not clear that PC patch "1.4.0.525" is the same as PS3 patch "1.06" - you actually have to go to the patch page to see that.
- The idea was that every patch was listed in the first column, and the other columns indicate which platforms those patches were available on, along with what they were called on that platform, and when they were released for that platform.
- If you're only interested in, say, PS4 patches, then reading down the "PS4" column will show all patches for that platform.
- I was also considering removing the beta patches, since they aren't listed on the New Vegas patches page, and you'll notice that the release notes for the final patch "v 1.2.37.0.0" are just a composite of the release notes for patches "v 1.2.33 Beta" and "v 1.2.37 Beta".
Dogmeat is now permanently invisible, thanks 1.6--68.62.55.57 16:57, July 18, 2016 (UTC)
Pages for beta releases[]
I'm not sure if it's worth maintaining separate pages for beta releases. There are likely to be lots of these, many with very few changes, and the changelogs will likely just be rolled up into the next final release for each minor version bump. Should suffice just to include them in the table with a link to the official release notes page.
I'll delinkify the latest one, unless anyone anyone particularly wants to create a new page with just a single change in it. Aya42 (talk) 18:44, January 20, 2016 (UTC)
- Steam did merge 1.3.47 Beta and 1.3.45 Beta release notes into one page. --Alfwyn (talk) 15:43, February 2, 2016 (UTC)
Patch version number[]
I think the patch should be called 1.3, that is what is found in the patch note. The resulting version number is another thing, and should be documented separately. Depends a bit on how we think future patches are handled. Just as addendum to patch 1.3? As patch 1.3.1? As a series of 1.4.x betas, followed by an official 1.4? --Alfwyn (talk) 03:26, February 5, 2016 (UTC)
- I'd just continued the page naming convention that was already in place, although I'm not too fond of it, either. The page used to look like this, so I wanted to do something to make it clear that PC and PS4 versions of patch 1.2 were effectively the same thing. Although including the "<major>.<minor>.<patchlevel>[<whatever>]" format that is used in-game would be useful to include in the table, it needn't be the name used in the per-patch pagenames.
- The goals of the table were...
- To include the full in-game version number somewhere, to make it easy for people to determine which version they have.
- To have a single link to a platform-agnostic page per patch, to avoid multiple pages with duplicated content.
- To include what the patch is called on each platform, and when it was released for each platform, if applicable.
- To include a link to the official release notes for each patch, so people can see what changes are, without having to wait for someone to create the per-patch detail pages.
- I'm not certain how the version number is formatted in the Steam client, so it may be an oddity that the in-built version history on the PS4 is the only platform which calls it 1.0x instead of 1.x. This may be unnecessary detail, although that was also to support the possibility of the per-platform version numbers diverging, as they did in New Vegas.
- The divergence may be related to the fact that the PC, Xbox 360, and PS3 all had different architectures with incompatible CPU instruction sets, but since the PC, Xbox One, and PS4 are all based on x86-64 architectures, it may be less likely to occur for Fallout 4.
- I would speculate that the version control process goes something like...
- After release of 1.3.47 final, build potential release candidate 1.4.48
- Send release candidate to QA, and if not completely broken, release as beta, then bump to 1.4.49 and repeat
- After a certain amount of time has passed, release whatever the last stable beta was as 1.4.x final
- ...but looking at the Skyrim patch history, it may be more complex.
- If we discontinue having pages for betas, it should suffice to name the pages "Fallout 4 patch 1.x", since there's yet to be more than one final release per minor version bump. Aya42 (talk) 12:24, February 5, 2016 (UTC)
- Yeah, but there simply seems to be no source for a patch "v 1.2.37.0.0" and "v 1.3.47.0.0", it is just called 1.2 and v1.3 in the patch notes, only the beta updates had subversion numbers there. We shouldn't invent our own numbering. --Alfwyn (talk) 02:44, February 7, 2016 (UTC)
- That column was intended to show the in-game name, i.e. what you see at the bottom of the settings menu, which is arguably the most authoritative source of all. Definitely reads "v 1.2.37.0.0" on current PS4 version. I don't have the 1.3 patch yet, so I can't confirm what it says for that. Not sure if it's embedded in the binary, or in the ESM, but it must exist somewhere. Aya42 (talk) 14:04, February 7, 2016 (UTC)
- I see, that makes things more complicated, technically that is the version of the executable. I think things should look more like Fallout 3 patches, that is focus on the patch version as published. --Alfwyn (talk) 14:26, February 7, 2016 (UTC)
- That column was intended to show the in-game name, i.e. what you see at the bottom of the settings menu, which is arguably the most authoritative source of all. Definitely reads "v 1.2.37.0.0" on current PS4 version. I don't have the 1.3 patch yet, so I can't confirm what it says for that. Not sure if it's embedded in the binary, or in the ESM, but it must exist somewhere. Aya42 (talk) 14:04, February 7, 2016 (UTC)
- Yeah, but there simply seems to be no source for a patch "v 1.2.37.0.0" and "v 1.3.47.0.0", it is just called 1.2 and v1.3 in the patch notes, only the beta updates had subversion numbers there. We shouldn't invent our own numbering. --Alfwyn (talk) 02:44, February 7, 2016 (UTC)
(←) Perhaps, although the main difference on the Fallout 3 page is that it doesn't list beta patches, which greatly simplifies things. I had considered just eliminating the beta patches, but I thought that might be a controversial change.
I'm happy with something much simpler like...
| Version |  PC release date
|
 PS4 release date
|
 Xbox One release date
|
Notes |
|---|---|---|---|---|
| 1.1 | - | November 9, 2015 | November 9, 2015 | - |
| 1.2 | December 7, 2015 | December 8, 2015 | December 9, 2015 | release notes |
| 1.3 | February 1, 2016 | (TBA) | (TBA) | release notes |
...given that the full executable version numbers are of no consequence unless they're being compared to the beta versions. Aya42 (talk) 16:33, February 7, 2016 (UTC)
- I tried that approach by moving beta patches out of the table, they were only available for the pc anyway. I reversed chronological sorting so the most up to date is at the top and used the "Patch" prefix mainly to have more than a tiny number to click on. --Alfwyn (talk) 18:12, February 7, 2016 (UTC)
- Was thinking the same thing, i.e. moving beta patches into their own section. New version looks good to me, and hopefully less confusing. I'll go ahead and rename the final patch pagenames to the shorter titles. I couldn't find any release notes for patch 1.1, just an announcement that it was available. Was that patch ever released on Steam? Aya42 (talk) 18:46, February 7, 2016 (UTC)
- There was no 1.1 patch after the 1.1.30 beta one. Not sure if there was a pre-release patch like for the other platforms. But there is no good way to go back on the PC anyway if one didn't make manual backups of the files, so it is more a theoretical question I think. --Alfwyn (talk) 19:19, February 7, 2016 (UTC)
- Was thinking the same thing, i.e. moving beta patches into their own section. New version looks good to me, and hopefully less confusing. I'll go ahead and rename the final patch pagenames to the shorter titles. I couldn't find any release notes for patch 1.1, just an announcement that it was available. Was that patch ever released on Steam? Aya42 (talk) 18:46, February 7, 2016 (UTC)
Update missing[]
There was a recent update on fallout 4 done on 3/28, and theres no information on it anywhere that I can locate. The only thing I notice was two new songs on Diamond City Radio. —Preceding unsigned comment added by 67.215.210.73 (talk • contribs). Please sign your posts with ~~~~!
- There haven't been any new official patches since 1.4, but if you've installed the Automatron add-on, that will have added new content, which may include new songs on the radio. It certainly added some new background music which can be heard when in some of the new locations added. Aya42 (talk) 08:46, March 31, 2016 (UTC)
- (Not sure how to use this kind of thing so bear with me) I did find out the songs weren't part of the update, they were added via The Third Rail in Goodneighbor, my bad, but if you say it wasn't a official patch then I'm not sure. I installed Automatron, beat it then uninstalled it using separate saved games. The update that occurred was a few days after being it with it uninstalled at the time. So I have no idea. —Preceding unsigned comment added by 67.215.210.73 (talk • contribs) 18:20, April 1, 2016 (UTC). Please sign your posts with ~~~~!
There was a 600MB PC update on 15/08/16 possibly experimental, no info online anywhere. Feel free to delete this comment, just a passing anon 217.36.229.180 13:18, August 17, 2016 (UTC)
PS4 update 1.05[]
This was released today, but it's apparently not patch 1.5. Aya42 (talk) 22:53, April 5, 2016 (UTC)
Question on Update[]
I know this is a odd point, but is it me or does this page seems out of date or incorrect in some way. I mean I'm sure there were more updates released this year, so is this page only for official updates or is it merely lacking? —Preceding unsigned comment added by 67.215.210.73 (talk • contribs) 22:44, April 27, 2016 (UTC). Please sign your posts with ~~~~!
- Perhaps. Depends which platform you're referring to, because they're all slightly different. The article page is separated into the official patches which were released on all platforms, and the PC beta patches. It doesn't include the patch data included in the official add-ons, which are covered on Fallout 4 add-ons, nor the PS4-only patch called 1.05, which I now suspect was actually the full patch data for Wasteland Workshop, and the add-on data was merely small piece of data which activated it. Unless you're referring to the table on this talk page, which was just a prototype for what the table on the article page should look like. Aya42 (talk) 09:49, April 28, 2016 (UTC)
v. 1.10.98.0.1[]
New patch released today? There's no info about that on Bethesda.net yet. Download size was about 86mb (iirc). The game states a version 1.10.98.0.1 ElchMoose (talk) 19:46, June 27, 2018 (UTC)