Sniper Elite - February 4, 2020

Edit history:

SDAVerification: 2020-02-04 02:50:08 pm

SDAVerification: 2020-02-04 02:49:39 pm

2020-01-22 11:52:38 am

Game Page: Doesn't exist yet

Sniper Elite () (pc) [Any %] [Segmented]

Decision: Canceled

Reason: The runner will work on an improvement, submission canceled

https://queue.speeddemosarchive.com/verificationfiles/2247/

This run will be available for a month. After that these link(s) will no longer work.

Thread title:

SDAVerification

2020-01-22 11:52:38 am

Run Information

Sniper Elite () (pc) [Any %] [Segmented]

Verification Files

http://v.speeddemosarchive.com/sniperelite-20200118/

Please refer to the Verification Guidelines before posting.

Please post your opinions about the run and be certain to conclude your post with a verdict (Accept/Reject). If you wish to remain anonymous, you can also send a pm with your reply to 'sdaverification' (please state clearly in that case which run you have verified). This is not a contest where the majority wins - Each verification will be judged on its content.

spartaque12

2020-01-31 04:12:44 pm

well run looks pretty good to me, unfortunately there were some minor mistakes during run, but i would accept it.

LotBlind

Edit history:

LotBlind: 2020-02-02 08:50:20 am

2020-02-02 08:50:04 am

I'm currently ill and I thought I'd watch this whole run but I already know what the verdict will have to be.

I see this is a big improvement from the last run that got rejected (though that one seems to have had the loading screens in the timing for some reason). It still uses the same number of segments (one per mission), but I was told that you could save in the middle of missions as well, so I was trying my best to convey to the previous runner that you could and should use more than one segment per mission. We want segmented runs to be as different as possible from single-segment runs. They should answer the question "what would the speedrun look like if everything went as well as it possibly could?"

In a true segmented speedrun, you could get more double kills and such. Maybe manipulate enemy movements to be more favorable. Throw the grenade at 14:07 a little earlier. Prefire shots faster than you can react to the target appearing. There should probably be more like 80-100 segments, not 27.

If there is no carryover between two missions (if all your equipment and weapons are reset at the start of the next mission), you can reuse the same segment in missions where it can't be made faster. Otherwise, if you redo a segment in the middle of the run, you have to make sure your ammunition and health (and anything else that can help save time) is at least as good as in the segment that follows. Ask me if you don't understand this.

If you don't understand why our quality standards are this high: if we had accepted spartaque's first run, we'd have to have accepted the second run too (if he or someone else had made one) and now this third one. Our audience will watch runs for games they don't know, but they won't watch lots of runs for the same game and category unless they were reaally into it. That's why we want the first submission already to look really optimized. If they'll only watch one run, you don't want it to be the slow and sloppy one.

So yeah, because of a far too low segment count, which leads into lots of missed headshots, double kills, even triple kills (if the game allows it) slightly unoptimized movement (it's quite tricky in this game), not enough RNG manipulation and probably some unoptimal (too safe) strategies, this has to be a

reject

I'm currently ill and I thought I'd watch this whole run but I already know what the verdict will have to be.

I see this is a big improvement from the last run that got rejected (though that one seems to have had the loading screens in the timing for some reason). It still uses the same number of segments (one per mission), but I was told that you could save in the middle of missions as well, so I was trying my best to convey to the previous runner that you could and should use more than one segment per mission. We want segmented runs to be as different as possible from single-segment runs. They should answer the question "what would the speedrun look like if everything went as well as it possibly could?"

In a true segmented speedrun, you could get more double kills and such. Maybe manipulate enemy movements to be more favorable. Throw the grenade at 14:07 a little earlier. Prefire shots faster than you can react to the target appearing. There should probably be more like 80-100 segments, not 27.

If there is no carryover between two missions (if all your equipment and weapons are reset at the start of the next mission), you can reuse the same segment in missions where it can't be made faster. Otherwise, if you redo a segment in the middle of the run, you have to make sure your ammunition and health (and anything else that can help save time) is at least as good as in the segment that follows. Ask me if you don't understand this.

If you don't understand why our quality standards are this high: if we had accepted spartaque's first run, we'd have to have accepted the second run too (if he or someone else had made one) and now this third one. Our audience will watch runs for games they don't know, but they won't watch lots of runs for the same game and category unless they were reaally into it. That's why we want the first submission already to look really optimized. If they'll only watch one run, you don't want it to be the slow and sloppy one.

So yeah, because of a far too low segment count, which leads into lots of missed headshots, double kills, even triple kills (if the game allows it) slightly unoptimized movement (it's quite tricky in this game), not enough RNG manipulation and probably some unoptimal (too safe) strategies, this has to be a

reject

Skajdrovski

2020-02-02 09:07:41 am

Quote from LotBlind:

I'm currently ill and I thought I'd watch this whole run but I already know what the verdict will have to be.

I see this is a big improvement from the last run that got rejected (though that one seems to have had the loading screens in the timing for some reason). It still uses the same number of segments (one per mission), but I was told that you could save in the middle of missions as well, so I was trying my best to convey to the previous runner that you could and should use more than one segment per mission. We want segmented runs to be as different as possible from single-segment runs. They should answer the question "what would the speedrun look like if everything went as well as it possibly could?"

The game was capped at 30 fps, and that was leading me to very bad aim. at 14:07 if I would throw it earlier, I wouldn't kill all of them. Segmenting in a middle of the run doesn't really affect the amount of ammo because it always is sufficent for lvl and also making more segments for me is probably harder to make because I'm doing everything from point A to point B

In a true segmented speedrun, you could get more double kills and such. Maybe manipulate enemy movements to be more favorable. Throw the grenade at 14:07 a little earlier. Prefire shots faster than you can react to the target appearing. There should probably be more like 80-100 segments, not 27.

If there is no carryover between two missions (if all your equipment and weapons are reset at the start of the next mission), you can reuse the same segment in missions where it can't be made faster. Otherwise, if you redo a segment in the middle of the run, you have to make sure your ammunition and health (and anything else that can help save time) is at least as good as in the segment that follows. Ask me if you don't understand this.

If you don't understand why our quality standards are this high: if we had accepted spartaque's first run, we'd have to have accepted the second run too (if he or someone else had made one) and now this third one. Our audience will watch runs for games they don't know, but they won't watch lots of runs for the same game and category unless they were reaally into it. That's why we want the first submission already to look really optimized. If they'll only watch one run, you don't want it to be the slow and sloppy one.

So yeah, because of a far too low segment count, which leads into lots of missed headshots, double kills, even triple kills (if the game allows it) slightly unoptimized movement (it's quite tricky in this game), not enough RNG manipulation and probably some unoptimal (too safe) strategies, this has to be a

reject

My aim was bad because the game was played in capped 30 fps. Segmenting in the middle of run doesn't really matter if I'm missing a couple of bullets or a ppsh because I often don't need a machine gun. 14:07 - I couldn't throw that nade faster because It wouldn't kill all of them. Segmenting in more than 27 segments isn't really easy for this game, because I'm doing everything from point A to point B and also loading a save is making a black fade in which struggles me to cut it perfectly in vegas pro

[quote="LotBlind"]I'm currently ill and I thought I'd watch this whole run but I already know what the verdict will have to be.

I see this is a big improvement from the last run that got rejected (though that one seems to have had the loading screens in the timing for some reason). It still uses the same number of segments (one per mission), but I was told that you could save in the middle of missions as well, so I was trying my best to convey to the previous runner that you could and should use more than one segment per mission. We want segmented runs to be as different as possible from single-segment runs. They should answer the question "what would the speedrun look like if everything went as well as it possibly could?"

The game was capped at 30 fps, and that was leading me to very bad aim. at 14:07 if I would throw it earlier, I wouldn't kill all of them. Segmenting in a middle of the run doesn't really affect the amount of ammo because it always is sufficent for lvl and also making more segments for me is probably harder to make because I'm doing everything from point A to point B

In a true segmented speedrun, you could get more double kills and such. Maybe manipulate enemy movements to be more favorable. Throw the grenade at 14:07 a little earlier. Prefire shots faster than you can react to the target appearing. There should probably be more like 80-100 segments, not 27.

If there is no carryover between two missions (if all your equipment and weapons are reset at the start of the next mission), you can reuse the same segment in missions where it can't be made faster. Otherwise, if you redo a segment in the middle of the run, you have to make sure your ammunition and health (and anything else that can help save time) is at least as good as in the segment that follows. Ask me if you don't understand this.

If you don't understand why our quality standards are this high: if we had accepted spartaque's first run, we'd have to have accepted the second run too (if he or someone else had made one) and now this third one. Our audience will watch runs for games they don't know, but they won't watch lots of runs for the same game and category unless they were reaally into it. That's why we want the first submission already to look really optimized. If they'll only watch one run, you don't want it to be the slow and sloppy one.

So yeah, because of a far too low segment count, which leads into lots of missed headshots, double kills, even triple kills (if the game allows it) slightly unoptimized movement (it's quite tricky in this game), not enough RNG manipulation and probably some unoptimal (too safe) strategies, this has to be a

reject[/quote]

My aim was bad because the game was played in capped 30 fps. Segmenting in the middle of run doesn't really matter if I'm missing a couple of bullets or a ppsh because I often don't need a machine gun. 14:07 - I couldn't throw that nade faster because It wouldn't kill all of them. Segmenting in more than 27 segments isn't really easy for this game, because I'm doing everything from point A to point B and also loading a save is making a black fade in which struggles me to cut it perfectly in vegas pro

LotBlind

Edit history:

LotBlind: 2020-02-03 09:28:16 am

2020-02-03 09:21:00 am

EDIT: I edited this post after I realized that you included some of your own comments inside the quotation.

The game itself is always capped at 30 FPS or is that because you can't record it at any higher framerate?

"Segmenting in the middle of run doesn't really matter if I'm missing a couple of bullets or a ppsh because I often don't need a machine gun"

So long as you're not accidentally getting any advantage from e.g. a gun's clip being half-empty at the end of one segment but suddenly full in the next one. If you were to redo the whole run, that would eliminate any worries about continuity but in any case please be careful with it if you do want to reuse a segment or two. I can see that you really aren't ever in danger of running out of machine gun bullets so that's probably fine, as you say.

"Segmenting in more than 27 segments isn't really easy for this game, because I'm doing everything from point A to point B"

I don't understand what you mean by this. You can also say it in Russian, which I happen to understand.

"also loading a save is making a black fade in which struggles me to cut it perfectly in vegas pro"

Does it cause you to lose time to save and load? Do you e.g. stop running? Also did you test whether you could make something happen faster if you save at the right time? Maybe it makes an animation finish faster or does something to the enemy AI for example.

The video doesn't have to be perfectly cut when you submit it, so long as it has every frame of gameplay. Does the gameplay resume at the beginning of the fade-in (when reloading) like at the start of missions? Is it just difficult to know which frame is the first frame of the fade-in? You don't particularly have to be worried about things like that. Our timer is used to timing runs very carefully and he can do all that work, so long as all the timed part of the run is present.

14:07 - okay. It was just an example though.

EDIT: I edited this post after I realized that you included some of your own comments inside the quotation.

The game itself is always capped at 30 FPS or is that because you can't record it at any higher framerate?

"Segmenting in the middle of run doesn't really matter if I'm missing a couple of bullets or a ppsh because I often don't need a machine gun"

So long as you're not accidentally getting any advantage from e.g. a gun's clip being half-empty at the end of one segment but suddenly full in the next one. If you were to redo the whole run, that would eliminate any worries about continuity but in any case please be careful with it if you do want to reuse a segment or two. I can see that you really aren't ever in danger of running out of machine gun bullets so that's probably fine, as you say.

"Segmenting in more than 27 segments isn't really easy for this game, because I'm doing everything from point A to point B"

I don't understand what you mean by this. You can also say it in Russian, which I happen to understand.

"also loading a save is making a black fade in which struggles me to cut it perfectly in vegas pro"

Does it cause you to lose time to save and load? Do you e.g. stop running? Also did you test whether you could make something happen faster if you save at the right time? Maybe it makes an animation finish faster or does something to the enemy AI for example.

The video doesn't have to be perfectly cut when you submit it, so long as it has every frame of gameplay. Does the gameplay resume at the beginning of the fade-in (when reloading) like at the start of missions? Is it just difficult to know which frame is the first frame of the fade-in? You don't particularly have to be worried about things like that. Our timer is used to timing runs very carefully and he can do all that work, so long as all the timed part of the run is present.

14:07 - okay. It was just an example though.

Skajdrovski

Edit history:

Skajdrovski: 2020-02-03 11:52:48 am

Skajdrovski: 2020-02-03 11:51:46 am

Skajdrovski: 2020-02-03 11:50:25 am

Skajdrovski: 2020-02-03 11:40:12 am

Skajdrovski: 2020-02-03 11:36:46 am

Skajdrovski: 2020-02-03 11:34:08 am

2020-02-03 11:33:12 am

Quote from LotBlind:

EDIT: I edited this post after I realized that you included some of your own comments inside the quotation.

The game itself is always capped at 30 FPS or is that because you can't record it at any higher framerate?

"Segmenting in the middle of run doesn't really matter if I'm missing a couple of bullets or a ppsh because I often don't need a machine gun"

So long as you're not accidentally getting any advantage from e.g. a gun's clip being half-empty at the end of one segment but suddenly full in the next one. If you were to redo the whole run, that would eliminate any worries about continuity but in any case please be careful with it if you do want to reuse a segment or two. I can see that you really aren't ever in danger of running out of machine gun bullets so that's probably fine, as you say.

"Segmenting in more than 27 segments isn't really easy for this game, because I'm doing everything from point A to point B"

I don't understand what you mean by this. You can also say it in Russian, which I happen to understand.

"also loading a save is making a black fade in which struggles me to cut it perfectly in vegas pro"

Does it cause you to lose time to save and load? Do you e.g. stop running? Also did you test whether you could make something happen faster if you save at the right time? Maybe it makes an animation finish faster or does something to the enemy AI for example.

The video doesn't have to be perfectly cut when you submit it, so long as it has every frame of gameplay. Does the gameplay resume at the beginning of the fade-in (when reloading) like at the start of missions? Is it just difficult to know which frame is the first frame of the fade-in? You don't particularly have to be worried about things like that. Our timer is used to timing runs very carefully and he can do all that work, so long as all the timed part of the run is present.

14:07 - okay. It was just an example though.

This game has some problems with physics when it's running in more than 30 fps like old GTA series. I don't speak russian either as my english skills Smiley

I'm Polish. When you load a save, the game starts imidiately with a long fade-in so I can't see what's happening during that 1-2 sec fade. No I'm not losing any time because saving and loading is keybinded. So... You're saying that I can just put another segment without cutting a fade-in ? How then can I manage to get my overall time ?

[quote="LotBlind"]EDIT: I edited this post after I realized that you included some of your own comments inside the quotation.