User talk:Taltharius - Revision history

Taltharius at 14:10, 25 February 2024

2024-02-25T14:10:49Z

← Older revision		Revision as of 14:10, 25 February 2024
Line 30:		Line 30:

	When loading any given xtbl file, Volition's Table File Editor expects that an xtbl named "foley.xtbl" will be present in the same folder as the rest of the extracted xtbl files; it throws an error if no foley.xtbl is found.		When loading any given xtbl file, Volition's Table File Editor expects that an xtbl named "foley.xtbl" will be present in the same folder as the rest of the extracted xtbl files; it throws an error if no foley.xtbl is found.


	Oddly enough, Red Faction: Guerrilla does not have an xtbl with this exact name (presumably, the older Saints Row games did, which also use xtbl files).		Oddly enough, Red Faction: Guerrilla does not have an xtbl with this exact name (presumably, the older Saints Row games did, which also use xtbl files).


	The traditional workaround for modding RFG xtbl files with the editor, was to simply create a blank foley.xtbl file with nothing in it. However, I recently stumbled across a better workaround, which I will describe below.		The traditional workaround for modding RFG xtbl files with the editor, was to simply create a blank foley.xtbl file with nothing in it. However, I recently stumbled across a better workaround, which I will describe below.


	In the Steam Edition, you can find "dlc01_foley.xtbl" in the "dlcp01_misc.vpp_pc" archive. In the Remaster, it can be found in "misc.vpp_pc" archive. Extract it, then place it with the rest of your extracted xtbl files.		In the Steam Edition, you can find "dlc01_foley.xtbl" in the "dlcp01_misc.vpp_pc" archive. In the Remaster, it can be found in "misc.vpp_pc" archive. Extract it, then place it with the rest of your extracted xtbl files.


	Afterwards, rename it to "foley.xtbl", and the Table File Editor should accept it. This also allows a bunch of audio references in the editor to work properly as well.		Afterwards, rename it to "foley.xtbl", and the Table File Editor should accept it. This also allows a bunch of audio references in the editor to work properly as well.

Taltharius at 14:10, 25 February 2024

2024-02-25T14:10:27Z

← Older revision		Revision as of 14:10, 25 February 2024
Line 1:		Line 1:
			== 120FPS bug ==

	In Red Faction: Guerrilla (both the Steam Edition and the Re-Mars-tered version), when the framerate exceeds 120FPS for too long, a rendering glitch that causes most of the terrain to vanish can occur in the Badlands. Harpoons fired from Marauder turrets will also frequently get stuck in the turret at framerates exceeding 120FPS.		In Red Faction: Guerrilla (both the Steam Edition and the Re-Mars-tered version), when the framerate exceeds 120FPS for too long, a rendering glitch that causes most of the terrain to vanish can occur in the Badlands. Harpoons fired from Marauder turrets will also frequently get stuck in the turret at framerates exceeding 120FPS.

Line 23:		Line 25:

	* Using the Nvidia Control Panel to set "Max Frame Rate" to 120.		* Using the Nvidia Control Panel to set "Max Frame Rate" to 120.


			== Better workaround for foley.xtbl issue with table file editor ==

			When loading any given xtbl file, Volition's Table File Editor expects that an xtbl named "foley.xtbl" will be present in the same folder as the rest of the extracted xtbl files; it throws an error if no foley.xtbl is found.

			Oddly enough, Red Faction: Guerrilla does not have an xtbl with this exact name (presumably, the older Saints Row games did, which also use xtbl files).

			The traditional workaround for modding RFG xtbl files with the editor, was to simply create a blank foley.xtbl file with nothing in it. However, I recently stumbled across a better workaround, which I will describe below.

			In the Steam Edition, you can find "dlc01_foley.xtbl" in the "dlcp01_misc.vpp_pc" archive. In the Remaster, it can be found in "misc.vpp_pc" archive. Extract it, then place it with the rest of your extracted xtbl files.

			Afterwards, rename it to "foley.xtbl", and the Table File Editor should accept it. This also allows a bunch of audio references in the editor to work properly as well.

Taltharius at 14:09, 25 February 2024

2024-02-25T14:09:09Z

← Older revision		Revision as of 14:09, 25 February 2024
Line 23:		Line 23:

	* Using the Nvidia Control Panel to set "Max Frame Rate" to 120.		* Using the Nvidia Control Panel to set "Max Frame Rate" to 120.

	When loading any given xtbl file, Volition's Table File Editor expects that an xtbl named "foley.xtbl" will be present in the same folder as the rest of the extracted xtbl files; it throws an error if no foley.xtbl is found.

	~~Oddly enough, Red Faction: Guerrilla does not have an xtbl with this exact name (presumably, the older Saints Row games did, which also use xtbl files).~~

	The traditional workaround for modding RFG xtbl files with the editor, was to simply create a blank foley.xtbl file with nothing in it. However, I recently stumbled across a better workaround, which I will describe below.

	In the Steam Edition, you can find "dlc01_foley.xtbl" in the "dlcp01_misc.vpp_pc" archive. In the Remaster, it can be found in "misc.vpp_pc" archive. Extract it, then place it with the rest of your extracted xtbl files.

	~~Afterwards, rename it to "foley.xtbl", and the Table File Editor should accept it. This also allows a bunch of audio references in the editor to work properly as well.~~

Taltharius at 14:08, 25 February 2024

2024-02-25T14:08:54Z

← Older revision		Revision as of 14:08, 25 February 2024
Line 23:		Line 23:

	* Using the Nvidia Control Panel to set "Max Frame Rate" to 120.		* Using the Nvidia Control Panel to set "Max Frame Rate" to 120.

			When loading any given xtbl file, Volition's Table File Editor expects that an xtbl named "foley.xtbl" will be present in the same folder as the rest of the extracted xtbl files; it throws an error if no foley.xtbl is found.

			Oddly enough, Red Faction: Guerrilla does not have an xtbl with this exact name (presumably, the older Saints Row games did, which also use xtbl files).

			The traditional workaround for modding RFG xtbl files with the editor, was to simply create a blank foley.xtbl file with nothing in it. However, I recently stumbled across a better workaround, which I will describe below.

			In the Steam Edition, you can find "dlc01_foley.xtbl" in the "dlcp01_misc.vpp_pc" archive. In the Remaster, it can be found in "misc.vpp_pc" archive. Extract it, then place it with the rest of your extracted xtbl files.

			Afterwards, rename it to "foley.xtbl", and the Table File Editor should accept it. This also allows a bunch of audio references in the editor to work properly as well.

Taltharius at 14:50, 20 February 2024

2024-02-20T14:50:04Z

← Older revision		Revision as of 14:50, 20 February 2024
Line 18:		Line 18:
	* Using Radeon Chill and setting both "Min FPS" and "Max FPS" to 120.		* Using Radeon Chill and setting both "Min FPS" and "Max FPS" to 120.

	* (Not recommended) Using ~~Framerate target control~~ to enforce a 120FPS limit. ~~Older~~ method than Radeon Chill, and often considered worse for input lag.		* (Not recommended) Using Frame Rate Target Control to enforce a 120FPS limit. This is an older method than Radeon Chill, and often considered worse for input lag.

	== Method that only works with an Nvidia GPU ==		== Method that only works with an Nvidia GPU ==

	* Using the Nvidia Control Panel to set "Max Frame Rate" to 120.		* Using the Nvidia Control Panel to set "Max Frame Rate" to 120.

Taltharius at 14:49, 20 February 2024

2024-02-20T14:49:16Z

← Older revision		Revision as of 14:49, 20 February 2024
Line 12:		Line 12:
	* Using the Rivatuner Statistics Server to enforce a 120FPS limit.		* Using the Rivatuner Statistics Server to enforce a 120FPS limit.

	* Setting the game's refresh rate to 120Hz, then enabling VSync. This only works if you have a 120Hz ~~(or higher)~~ monitor.		* Setting the game's refresh rate to 120Hz, then enabling VSync. This only works if you have a 120Hz-capable monitor.

	== Methods that only work with an AMD GPU ==		== Methods that only work with an AMD GPU ==

Taltharius at 14:29, 20 February 2024

2024-02-20T14:29:42Z

← Older revision		Revision as of 14:29, 20 February 2024
Line 2:		Line 2:


	Capping the framerate at 120FPS will prevent both these problems from occurring, and may also prevent other subtle bugs/glitches from occurring.		Capping the framerate at 120FPS will prevent both of these problems from occurring, and may also prevent other subtle bugs/glitches from occurring.

Taltharius at 14:25, 20 February 2024

2024-02-20T14:25:52Z

← Older revision		Revision as of 14:25, 20 February 2024
Line 12:		Line 12:
	* Using the Rivatuner Statistics Server to enforce a 120FPS limit.		* Using the Rivatuner Statistics Server to enforce a 120FPS limit.

	* Setting the game's refresh rate to 120Hz, then enabling VSync. This only works if you have a 120Hz monitor.		* Setting the game's refresh rate to 120Hz, then enabling VSync. This only works if you have a 120Hz (or higher) monitor.

	== Methods that only work with an AMD GPU ==		== Methods that only work with an AMD GPU ==

Taltharius at 05:42, 20 February 2024

2024-02-20T05:42:33Z

← Older revision		Revision as of 05:42, 20 February 2024
Line 1:		Line 1:
	In Red Faction: Guerrilla (both the Steam Edition and the Re-Mars-~~stered~~ version), when the framerate exceeds 120FPS for too long, a rendering glitch that causes most of the terrain to vanish can occur in the Badlands. Harpoons fired from Marauder turrets will also frequently get stuck in the turret at framerates exceeding 120FPS.		In Red Faction: Guerrilla (both the Steam Edition and the Re-Mars-tered version), when the framerate exceeds 120FPS for too long, a rendering glitch that causes most of the terrain to vanish can occur in the Badlands. Harpoons fired from Marauder turrets will also frequently get stuck in the turret at framerates exceeding 120FPS.

Taltharius at 05:29, 20 February 2024

2024-02-20T05:29:28Z

← Older revision		Revision as of 05:29, 20 February 2024
Line 1:		Line 1:
	~~A rendering glitch can occur in~~ the ~~Badlands~~ when the framerate exceeds 120FPS for too long. Harpoons fired from Marauder turrets will also frequently get stuck in the turret at framerates exceeding 120FPS.		In Red Faction: Guerrilla (both the Steam Edition and the Re-Mars-stered version), when the framerate exceeds 120FPS for too long, a rendering glitch that causes most of the terrain to vanish can occur in the Badlands. Harpoons fired from Marauder turrets will also frequently get stuck in the turret at framerates exceeding 120FPS.


	Capping the framerate at 120FPS will prevent both these ~~things~~ from occurring, and may also prevent other subtle bugs/glitches from occurring.		Capping the framerate at 120FPS will prevent both these problems from occurring, and may also prevent other subtle bugs/glitches from occurring.