Max Payne - Revision history

Ridd3r: /* Weapon Jam/Misfire */

2012-01-14T10:19:33Z

‎Weapon Jam/Misfire

Ridd3r: /* Weapon Selection - No Equip */

2012-01-14T10:19:23Z

‎Weapon Selection - No Equip

Ridd3r: /* Weapon Selection - Double Select */

2012-01-14T10:18:12Z

‎Weapon Selection - Double Select

Ridd3r: /* Weapon Selection - No Equip */

2012-01-14T10:17:49Z

‎Weapon Selection - No Equip

Ridd3r: /* Weapon Selection - Double Select */

2012-01-14T10:17:22Z

‎Weapon Selection - Double Select

Ridd3r at 09:24, 22 October 2011

2011-10-22T09:24:02Z

Ridd3r: /* Complex Cutscenes */

2011-08-18T23:29:07Z

‎Complex Cutscenes

Ridd3r: /* Complex Cutscenes */

2011-08-18T22:52:11Z

‎Complex Cutscenes

Ridd3r: /* Quick Saves */

2011-08-18T18:55:32Z

‎Quick Saves

Ridd3r: /* Editing */

2011-08-18T18:53:50Z

‎Editing

@@ Line 322: / Line 322: @@
 == Weapon Jam/Misfire ==
-'''Discovered by:''' ridd3r
+'''Discovered by:''' Many people
 '''Description:''' When firing (mainly seems to happen with the pump shotgun and deagle) the gun can click and not shoot. Also the bullets can not fire at all, despite the explosion (mainly pump shotgun and sawn-off).

@@ Line 315: / Line 315: @@
 == Weapon Selection - No Equip ==
-'''Discovered by:''' Many People
+'''Discovered by:''' Many people
 '''Description:''' After selecting a weapon, sometimes nothing can happen when you try and equip.

@@ Line 308: / Line 308: @@
 == Weapon Selection - Double Select ==
-'''Discovered by:''' Many
+'''Discovered by:''' Many people
 '''Description:''' When selecting a weapon, instead of going to the first weapon on the list, the 2nd weapon down is selected (even though it's only pressed once).

@@ Line 315: / Line 315: @@
 == Weapon Selection - No Equip ==
-'''Discovered by:''' ridd3r
+'''Discovered by:''' Many People
 '''Description:''' After selecting a weapon, sometimes nothing can happen when you try and equip.

@@ Line 308: / Line 308: @@
 == Weapon Selection - Double Select ==
-'''Discovered by:''' ridd3r
+'''Discovered by:''' Many
 '''Description:''' When selecting a weapon, instead of going to the first weapon on the list, the 2nd weapon down is selected (even though it's only pressed once).

@@ Line 27: / Line 27: @@
 ===Quick Saves===
-Everytime the a quick save is performed, the game lags for a few frames (seems to vary from 1-5, but usually 2). It's unclear what determines the amount of lag, but PC performance plays a part, therefore the lag should be edited out. Note that Max Payne will never lose frames, if it encounters a problem with available memory or processing speed then the game will freeze for a few frames (though audio can continue as normal).
+Every time a quick save is performed, the game lags for a few frames (seems to vary from 1-5, but usually 2). It's unclear what determines the amount of lag, but PC performance plays a part, therefore the lag should be edited out. Note that Max Payne will never lose frames, if it encounters a problem with available memory or processing speed then the game will freeze for a few frames (though audio can continue as normal).
 A typical quick save will be as follows:
-quick save on frame 100, frames 101-102 will be frozen on frame 100, movement continues at frame 103. The game saved will appear in the bottom right hand corner on frames 105. Where the game saved appears is exactly the frames that you will be respawned at when you quick load. The segmented DoA run done by ridd3r included both the game saved frame and the starting frame, so essentially a repeat frame. The reason for this is you have to get to a save to continue from it, so it should be A-B B-C C-D, not A-B-C-D. This was not done in the 25:34 NYM run, but there the in-game timer is used and this is not an issue.
+Quick save on frame 100, frames 101-102 will be frozen on frame 100, movement continues at frame 103. The game saved will appear in the bottom right hand corner on frame 105. Where the game saved appears is exactly the frames that you will be respawned at when you quick load. The 42:41 segmented DoA run included both the game saved frame and the starting frame, so essentially a repeat frame. The reason for this is you have to get to a save to continue from it, so it should be A-B B-C C-D, not A-B-C-D. This was not done in the 25:34 NYM run, but there the in-game timer is used and this is not an issue.
 It is likely that frames 103-104 occur under the cover of the loading screen, with visible gameplay starting at frame 105. Therefore, to edit the video continuously, the following should be done for the above example (as it would look in the SDA editing program Anri-chan):
@@ Line 38: / Line 38: @@
 Range#1/Frame#2: 100
-Range#2/Frame#3: 101
+Range#2/Frame#3: 103
-Range#2/Frame#4: 102
+Range#2/Frame#4: 105
-−
-Range#3/Frame#5: 103
-−
-Range#3/Frame#6: 105
 ===Complex Cutscenes===
-There are 3 cutscenes in the game where it is not clear exactly where the game is being saved if a save glitch is performed. Through a combination of logic and analysing the audio track in Sony Vegas, the positions of the saves were analysed. A quick save makes a sound and so you can pin point the frame it was done and work out the correct editing from there. However, save glitching itself varies and sometimes the save sound is inaudible. Therefore, using concrete results, a universal standard has to be applied to all three cases (all three are save glitches of a comic strip, thus the same as far as the game engine is concerned). The general rule is 10 black frames until the save occurs and then x black frames before fade-in after reloading the save. The time for the save is The following shows what was done for the 44:31 segmented DoA run by ridd3r:
+There are 3 cutscenes in the game where it is not clear exactly where the game is being saved if a save glitch is performed. Through a combination of logic and analysing the audio track in Sony Vegas, the positions of the saves were analysed. A quick save makes a sound and so you can pin point the frame it was done and work out the correct editing from there. However, save glitching itself varies and sometimes the save sound is inaudible. Therefore, using concrete results, a universal standard has to be applied to all three cases (all three are save glitches of a comic strip, thus the same as far as the game engine is concerned). The general rule is 10 black frames until the save occurs and then x black frames before fade-in after reloading the save. The following shows what was done for the 42:41 segmented DoA run:
 Part II, Chapter 1 - Segment 1 (up to the first comic strip):
-A total of 14 totally black frames. Note that upon reloading the save, there can be varying amounts of black frames, though 4 is normal. It's important to include all frames after loading the save, therefore have 14 - the number of black frames after loading, as the number of black frames after fade-out.
+A total of 14 totally black frames. Note that upon reloading the save, there can be varying amounts of black frames, though 4 is normal. It's important to include all frames after loading the save, therefore have 14 minus the number of black frames after loading as the number of black frames after fade-out.
 Part II, Chapter 1 - Segment 2 (up to the boss fight comic strip):
-A total of 12 totally black frames. Note that upon reloading the save, there can be varying amounts of black frames, though 2 is normal. It's important to include all frames after loading the save, therefore have 12 - the number of black frames after loading, as the number of black frames after fade-out.
+A total of 12 totally black frames. Note that upon reloading the save, there can be varying amounts of black frames, though 2 is normal. It's important to include all frames after loading the save, therefore have 12 minus the number of black frames after loading, as the number of black frames after fade-out.
 Part II, Chapter 5 - Segment 2 (up to Punchinello's room):

@@ Line 48: / Line 48: @@
 ===Complex Cutscenes===
-There are 3 cutscenes in the game where it is not clear exactly where the game is being saved if a save glitch is performed. Through a combination of logic and analysing the audio track in Sony Vegas, the positions of the saves were established. A quick save makes a sound and so you can pin point the frame it was done and work out the correct editing from there. The following shows what was done for the 44:31 segmented DoA run by ridd3r:
+There are 3 cutscenes in the game where it is not clear exactly where the game is being saved if a save glitch is performed. Through a combination of logic and analysing the audio track in Sony Vegas, the positions of the saves were analysed. A quick save makes a sound and so you can pin point the frame it was done and work out the correct editing from there. However, save glitching itself varies and sometimes the save sound is inaudible. Therefore, using concrete results, a universal standard has to be applied to all three cases (all three are save glitches of a comic strip, thus the same as far as the game engine is concerned). The general rule is 10 black frames until the save occurs and then 2 black frames before fade-in after reloading the save. The time for the save is The following shows what was done for the 44:31 segmented DoA run by ridd3r:
 Part II, Chapter 1 - Segment 1 (up to the first comic strip):
-Edit out all the save lag which is visible, then there should be a total of 14 completely back frames before fade in. There are 5 completely black frames when you reload after successfully save glitching, thus you should include the first 9 black frames from the 1st segment and the 5 black frames from the start of the 2nd segment.
+A total of 12 totally black frames. Note that upon reloading the save, there can be varying amounts of black frames, as the save glitch position can vary. It's important to include all frames after loading the save, therefore have 12 - the number of black frames after loading, as the number of black frames after fade-out.
 Part II, Chapter 1 - Segment 2 (up to the boss fight comic strip):
-Again editing out all visible lag before the screen goes black and then there should be 12 totally black frames before fade in. There are 2 black frames when you reload after a successful save glitch, therefore include 10 black frames from segment 2 and then the first 2 black frames from segment 3.
+A total of 12 totally black frames. Note that upon reloading the save, there can be varying amounts of black frames, as the save glitch position can vary. It's important to include all frames after loading the save, therefore have 12 - the number of black frames after loading, as the number of black frames after fade-out.
 Part II, Chapter 5 - Segment 2 (up to Punchinello's room):
-After fadeout there should be 9 black frames before fade in and 3 frames of the slightly faded cutscene. There aren't any black frames when you reload after save glitching.
+A total of 10 totally black frames. There are no black frames after loading, therefore just have 10 black frames after fade-out.
 For the following it's clear where the save is taking place, though save lag affects the fadeout and so the following should apply:

@@ Line 23: / Line 23: @@
 == Editing ==
-TBC
+When it comes to editing runs which focus on best real time, i.e all but New York Minute runs, then the following is important to note:
 == New York Minute Mode ==