This has nothing to do with performance, just a layover setting I used when livestreaming the game.
Spider man 2000 all cutscenes windows#
Any notifications, specifically stream crashes or other windows errors will crash the game.
Spider man 2000 all cutscenes manual#
Despite the program, both PC versions have the exact same glitches and tricks, only difference is movement.Īs the game manual insists, any form of task switching, most notably alt+tabbing, is not supported by the game. As for the in-game settings go, only the brightness and screen resolution can be changed. Despite the difference in speed, with DxWnd, I've still managed to outpace the game and trigger failures, crashes, and unexpected deaths in the game. The game does not intend you to go as fast as older PC's couldn't handle, which is why playing the game too fast has consequences. Jumping is actually faster than swinging in the original PC version, contrary to the console versions where swinging and swing cutting is faster. As in the previous run submitted, the difference with DxWnd and non-DxWnd is apparent in the movement of Spider-Man. Scorpion!" has a notorious PC glitch of Spider-Man swinging underneath the floor during the in-game cutscene before the fight, resulting in an instant death upon control. Because of the outlandish game speed, I've had complete game crashes in every single level without DxWnd's assistance. The PC version of this game is prone to random game crashes and is quite likely to crash in the final chapter. This option helps deter crashing and game speed.
I talked to the runner about the dxwnd usage and got the following info about what exactly DxWnd is used for: Neutral (until I see an explanation for the lack of cut scene skips) And if the runner sees this, it'd be interesting to hear some comments about the youtube run as well and how it compares to this submission. However, I'd need to know more about the cut scenes before being able to say more. The submitted run looks good (outside the death) and seems acceptable imo (despite the possibility of a faster run out there). I just compared the two videos for the first level and the gameplay in the other video appeared to be slightly tighter. Why was that not possible in this run? If that's a different version, you should try to get hold of that one instead. That video managed to skip all the cut scenes somehow. I found a video on easy (this submission is on kids mode (=very easy?)) that I believe is faster. Other than that it seemed like it was well played. One ugly death (15 sec lost) and what looked like a couple of minor mistakes. All I can say is that the audio and video look fine from a viewer perspective. I'm assuming the game cannot be played or something on modern PCs without it?Ī/V: The discussion above on the capturing method is beyond my knowledge, so I can't comment on if it's been correctly done or not. I would love to hear more details about why this is necessary. I think it should be, but I am no moderator. I cannot comment on the game itself, but the above should be evaluated by the moderators to see if it's acceptable. As far as I know the FPS cannot be changed after the game is started, so cheating by limiting the FPS too much should be quite detectable. The program does enable games that aren't meant to be windowed, to be played in a windowed mode and it does so by injecting 3rd party wrapper for system calls.ĭxWnd also does coordinate correction and provides an FPS limiter.
The question is if such actions are passable by the rules. The execution was otherwise quite flawless.ĭxWnd modifies more system calls than Direct X, but it does not alter the games code. So, aside from that, I'd accept this run, despite the death. Does this count as a game mod? I don't think it should be, as it isn't directly modifying the game itself, only DirectX.
so DxWnd appears to be a program that overrides the version of DirectX that the game sends API calls to, as well as overriding certain DirectX behaviour.
0 kommentar(er)
