Far Cry 3 Assets of Incomplete Builds: Difference between revisions

From Hidden Palace
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
(One intermediate revision by the same user not shown)
Line 12: Line 12:


=2011 Assets=
=2011 Assets=
==~Mar 23, 2011 prototype==
==~Mar 23, 2011 prototype==


Line 18: Line 19:
It contains a world called pvp_kas06_pitaya which, as the name implies, was used for multiplayer mode. No files are corrupted and it is 100% safe to extract them. Luckily, even though these assets are the oldest recoverable, they didn't have any corrupted files, unlike their successors.
It contains a world called pvp_kas06_pitaya which, as the name implies, was used for multiplayer mode. No files are corrupted and it is 100% safe to extract them. Luckily, even though these assets are the oldest recoverable, they didn't have any corrupted files, unlike their successors.


==Apr 11, 2011 prototype==
==~Apr 11, 2011 prototype==


[https://hiddenpalace.org/File:FC3_(~Apr_11,_2011)_(Only_1_World).zip Download here]
{{Download|file=FC3_(~Apr_11,_2011)_(Only_1_World).zip|title=Assets}}


* Originally found on a Terarelease 1.0 hdd [https://drive.google.com/file/d/106gzyqyvIzjSsQNrBTjNwVQKo7M44PZ2/view?usp=sharing Ubisoft Massive HDD #1 - Far Cry 3, Assassin's Creed 4.rar].
It contains a world called pvp_kas06_pitaya. From its name, this is the world used in multiplayer mode. Unfortunately, pvp_kas06_pitaya is corrupted and it doesn't seem to be possible to recover this file via hex. However, it should be noted that this file still stores files, albeit incomplete. pvp_kas06_pitaya. nfo is partially corrupted and although it is possible to add the missing lines, the recovery is unfortunately partial (and it was not possible to do so). However, this file turns out to be useless because given that the beginning of pvp_kas06_pitaya is missing, the only option would be to recover the files via hex manually and work your way through the list.
* It is unknown whether it is an internal multiplayer build or not.
* The build date is not accurate as it was based on the file creation date on the HDD.
* This build only contain one world (by itself) which translates into an extremely incomplete build. This World is pvp_jas16_durian. pvp_jas16_durian.dat has a medium chance of being corrupted and other files are not corrupted. pvp_jas16_durian_english.dat is not corrupt. The remaining files have a low chance of being corrupted.


==Sep 12, 2011 Multiplayer prototype==
==Sep 12, 2011 Multiplayer prototype==


[https://hiddenpalace.org/File:Far_Cry_3_FLINT-MSV-MAIN-PACKAGE-580.0_(Sep_12,_2011_00.44.35).zip Download here]
{{Download|file=Far_Cry_3_FLINT-MSV-MAIN-PACKAGE-580.0_(Sep_12,_2011_00.44.35).zip|title=Assets}}


* Originally found on a Terarelease 1.0 hdd [https://drive.google.com/file/d/106gzyqyvIzjSsQNrBTjNwVQKo7M44PZ2/view?usp=sharing Ubisoft Massive HDD #1 - Far Cry 3, Assassin's Creed 4.rar].
This build has executables which lets you know that the build name is FLINT-MSV-MAIN-PACKAGE-580.0 which means it's an internal multiplayer prototype. Unfortunately, only fcx.xdb, fcx.xex and fcx.exe (decompiled version of xex) seem to be what's left of this build.
* The build extracted from HDD is quite incomplete, containing only the files fcx.exe, fcx.xdb and fcx.xex, which goes without saying that the build in its current state cannot be reproduced (there are even older files that the build date, but even then they would be insufficient to work).
 
* Looking at its build name, it is possible to say that it is an internal multiplayer build.
==~Oct 2011 prototype==
* The build name is FLINT-MSV-MAIN-PACKAGE-580.0
 
An nfo file for an October 2011 version exists, although it is extremely incomplete. It belongs to a world called coop_press. Curiously, this world, unlike the February version, was supposed to store E3 files, which is strange because the E3 prototypes use a separate world named fc3_e3. It should be noted, however, that this world was probably used for internal conferences (hence the name press).
 
=2012 Assets=


==Jan 14, 2012 prototype==
==Jan 14, 2012 prototype==


[https://hiddenpalace.org/File:Fc3_(Jan_14,_2012)_(Very_Incomplete,_Only_2_Worlds).zip Download here]
'''Description missing. It seems to be possible to repair the files via hex.'''
 
* Originally found on a Terarelease 1.0 hdd [https://drive.google.com/file/d/106gzyqyvIzjSsQNrBTjNwVQKo7M44PZ2/view?usp=sharing Ubisoft Massive HDD #1 - Far Cry 3, Assassin's Creed 4.rar].
* It is unknown whether it is an internal multiplayer build or not.
* The build date is not accurate as it was based on the file creation date on the HDD.
* This build only contains two worlds (by themselves) which translates into an extremely incomplete build. These two worlds are:
** '''coop_press''': coop_press.nfo and coop_press_english.dat have a high chance of being corrupted according to fatx. coop_press.dat has a medium chance of being corrupt. coop_press.fat, coop_press_english.fat and coop_press_english.nfo have a low chance of the files being corrupted and the rest not being corrupted;
** '''pvp_jas21_ginger''': pvp_jas21_ginger'.dat has a high chance of being corrupted. All files named "english" have a low chance of being corrupted and other files are not corrupted.


==Feb 2, 2012 prototype==
==~Feb 2, 2012 prototype==


[https://hiddenpalace.org/File:FC3_(~Feb_2,_2012)_(Only_World_Files).zip Download here]
'''Description missing. It seems to be possible to repair the files via hex.'''


* As fc3_main (campaign mode) world exists in this build, it is possible to say that it is not an internal multiplayer build.
* Originally found on a Terarelease 1.0 hdd [https://drive.google.com/file/d/106gzyqyvIzjSsQNrBTjNwVQKo7M44PZ2/view?usp=sharing Ubisoft Massive HDD #1 - Far Cry 3, Assassin's Creed 4.rar].
* Only the worlds could be recovered, as it seems that everything else (including executables) no longer exists. This makes the build unplayable.
* Supposedly all worlds are recovered and according to fatx:
** '''coop_pvp_sof04''': All the files that have "english" and "vistas" in the name have a low chance of being corrupted. The remaining files are not corrupted;
** '''coop_skadi''': All the files with name "vistas" have a high chance of being corrupted, coop_skadi.dat has a medium chance of being corrupted and the remaining ones have a low chance of being corrupted;
** '''coop_sleipnir''' The coop_sleipnir_english.dat, coop_sleipnir.nfo and coop_sleipnir_vistas.nfo have a high chance of being corrupted. coop_sleipnir.dat has a medium chance of being corrupted and the other files have a low chance of being corrupted;
** '''coop_vidar''': The coop_vidar_english.fat and the coop_vida_english.nfo have a low chance of being corrupted. coop_vidar.dat has a medium chance of being corrupted and the rest have a high chance of being corrupted;
** '''fc3_main''': fc3_main_english.dat has a high chance of getting corrupted. fc3_main.dat has a low chance of being corrupted and the other files are not corrupted;
** '''frontendworld''': frontendworld.dat and all files with "english in the name" have a low chance of being corrupted. The remaining files are not corrupted;
** '''multicommon''': multicommon_english.dat has a high chance of getting corrupted. multicommon.dat has a medium chance of being corrupt and the remaining files have a low chance of being corrupt;
** '''pvp_jas18_buddhashand''': pvp_jas18_buddhashand.nfo and pvp_jas18_buddhashand_english.dat have a high chance of being corrupt. pvp_jas18_buddhashand.dat has a medium chance of being corrupt. pvp_jas18_buddhashand.fat, pvp_jas18_buddhashand_english.fat, and pvp_jas18_buddhashand_english.nfo have a low chance of becoming corrupted. The remaining files are not corrupted;
** '''pvp_jas19_wat''': All files with "vistas" in the name have a high chance of becoming corrupted. pvp_jas19_wat.dat has a medium chance of being corrupted and the other files have a low chance of being corrupted;
** '''pvp_lee01_pear''': pvp_lee01_pear.dat has a medium chance of getting corrupted and all other files have a low chance of getting corrupted.
* Using xenia and adding the main world files to the build [[Far Cry 3 (Mar 30, 2012 Multiplayer prototype)]], xenia will give a black screen due to the lack of devkit support. using a modified version it is possible to solve this however the build will stay infinitely loading. this may be a problem with this modified version of xenia.
{{Download}}
{{Download}}
{{Prototype Footer|{{Navbox prototype|Far Cry 3}}}}
{{Prototype Footer|{{Navbox prototype|Far Cry 3}}}}

Revision as of 21:39, February 3, 2025

Click to upload a new image...Dummy link
Far Cry 3 Assets of Incomplete Builds
Game Far Cry 3
System Other
Genre FPS

The development of Far Cry 3 began in 2009 and its base retail version was completed in October 2012. So there are +- 3 years of development. Despite the existence of several builds, their abundance is only in September and October 2012, which is somewhat more sparse looking back over time, so only 1 build from August 2012, 2 builds from May 2012 and 1 build from March 2012 exist as complete. These 4 builds were obtained from an HDD named Ubisoft Massive HDD #1 - Far Cry 3, Assassin's Creed 4 which, on analysis, shows that this HDD originally stored prototypes of this game and later stored prototypes of Assassin's Creed IV: Black Flag. The most interesting thing about this is that this HDD started being used in 2009 to store Far Cry 3 prototypes. Unfortunately, given that it was used for 4 years, nothing remains from that time other than an empty folder. However, there are still remnants of files related to builds between March 2011 and February 2012. Despite appearing useless since these are builds that are far from complete, we're talking about assets from a bygone era that can be used to be restored and used in the retail versions of the game. With this, the decision was made to share these assets.

in pogress.

2011 Assets

~Mar 23, 2011 prototype

Download Assets (info)
Error: The download file provided does not exist, please upload it or fix the file name if it's incorrect.

It contains a world called pvp_kas06_pitaya which, as the name implies, was used for multiplayer mode. No files are corrupted and it is 100% safe to extract them. Luckily, even though these assets are the oldest recoverable, they didn't have any corrupted files, unlike their successors.

~Apr 11, 2011 prototype

Download Assets (info)
Error: The download file provided does not exist, please upload it or fix the file name if it's incorrect.

It contains a world called pvp_kas06_pitaya. From its name, this is the world used in multiplayer mode. Unfortunately, pvp_kas06_pitaya is corrupted and it doesn't seem to be possible to recover this file via hex. However, it should be noted that this file still stores files, albeit incomplete. pvp_kas06_pitaya. nfo is partially corrupted and although it is possible to add the missing lines, the recovery is unfortunately partial (and it was not possible to do so). However, this file turns out to be useless because given that the beginning of pvp_kas06_pitaya is missing, the only option would be to recover the files via hex manually and work your way through the list.

Sep 12, 2011 Multiplayer prototype

Download Assets (info)
Error: The download file provided does not exist, please upload it or fix the file name if it's incorrect.

This build has executables which lets you know that the build name is FLINT-MSV-MAIN-PACKAGE-580.0 which means it's an internal multiplayer prototype. Unfortunately, only fcx.xdb, fcx.xex and fcx.exe (decompiled version of xex) seem to be what's left of this build.

~Oct 2011 prototype

An nfo file for an October 2011 version exists, although it is extremely incomplete. It belongs to a world called coop_press. Curiously, this world, unlike the February version, was supposed to store E3 files, which is strange because the E3 prototypes use a separate world named fc3_e3. It should be noted, however, that this world was probably used for internal conferences (hence the name press).

2012 Assets

Jan 14, 2012 prototype

Description missing. It seems to be possible to repair the files via hex.

~Feb 2, 2012 prototype

Description missing. It seems to be possible to repair the files via hex.