Spider-Man: The Movie

From PCGamingWiki, the wiki about fixing PC games
This page is a stub: it lacks content and/or basic article components. You can help to expand this page by adding an image or additional information.
Spider-Man: The Movie
Spider-Man: The Movie cover
Developers
Treyarch
Windows LTI Gray Matter
Publishers
Activision
Release dates
Windows April 14, 2002
Spider-Man: The Movie guide on StrategyWiki
Spider-Man: The Movie on MobyGames
Spider-Man: The Movie on Wikipedia
Spider-Man
Subseries of Marvel
Spider-Man (1986) 1986
The Amazing Spider-Man and Captain America in Dr. Doom's Revenge! 1989
The Amazing Spider-Man 1990
Spider-Man & Venom: Separation Anxiety 1995
Spider-Man: The Sinister Six 1996
Spider-Man 2001
Spider-Man: The Movie 2002
Spider-Man 2: The Game 2004
Ultimate Spider-Man 2005
Spider-Man 3 2007
Spider-Man: Friend or Foe 2007
Spider-Man: Web of Shadows 2008
Spider-Man: Shattered Dimensions 2010
The Amazing Spider-Man (2012) 2012
The Amazing Spider-Man 2 2014
Spider-Man: Homecoming - Virtual Reality Experience 2017
Spider-Man: Far From Home Virtual Reality 2019

Availability[edit]

Source DRM Notes Keys OS
Retail
Disc check (requires the CD/DVD in the drive to play)
Windows

Demos[edit]

Essential improvements[edit]

Skip intro videos[edit]

Delete/rename video files[citation needed]
  1. Go to <path-to-game>\movies
  2. Delete or rename ACTIVISN.bik, GrayMatr.bik, Origin1.bik and Treyarch.bik.

Patches[edit]

Patch 1.3 is the last patch and resolves a number of issues.

Game data[edit]

Configuration file(s) location[edit]

System Location
Windows <path-to-game>\game.ini[Note 1]

Save game data location[edit]

System Location
Windows <path-to-game>\SavedGames0[Note 1]

Video settings[edit]

Graphics feature State WSGF Notes
Widescreen resolution
See the WSGF entry.
Multi-monitor
Ultra-widescreen
See the WSGF entry.
4K Ultra HD
See the WSGF entry.
Field of view (FOV)
Windowed
See the glossary page for potential workarounds.
Borderless fullscreen windowed
See the glossary page for potential workarounds.
Anisotropic filtering (AF)
See the glossary page for potential workarounds.
Anti-aliasing (AA)
MSAA can be forced through the graphics card control panel.
Vertical sync (Vsync)
See the glossary page for potential workarounds.
60 FPS
FMVs are locked at 30 FPS.
120+ FPS

Input settings[edit]

Keyboard and mouse State Notes
Remapping
Mouse acceleration
Strong mouse acceleration in-game. Can't be disabled.
Mouse sensitivity
Low, Medium, High settings.
Mouse input in menus
No mouse acceleration in menus.
Mouse Y-axis inversion
Controller
Controller support
Uses DirectInput and won't recognize all XInput inputs. If your controller has a DirectInput mode, use that. If not, see Game doesn't recognize all inputs from XInput controller.
Full controller support
Controller remapping
Controller sensitivity
Controller Y-axis inversion
Additional information
Button prompts Input settings icon - Generic Controller.svg
Controller hotplugging
Haptic feedback
Simultaneous controller+KB/M

Audio settings[edit]

Audio feature State Notes
Separate volume controls
Surround sound
Subtitles
Closed captions
Mute on focus lost

Localizations

Language UI Audio Sub Notes
English

VR support[edit]

3D modes Native Notes
vorpX
G3D
User created game profile, requires D3D8to9, see vorpx forum profile introduction.

Issues Fixed[edit]

Game doesn't recognize all inputs from XInput controller[edit]

Use AntiMicro to map unrecognized inputs to keyboard and mouse
  1. Replace the [KEYBOARD], [JOYSTICK], and [MOUSE] sections of <path-to-game>\game.ini with the below:
    
    [KEYBOARD]
    JUMP=49
    PUNCH=96
    KICK=98
    WEB=100
    CROUCH=3
    START=46
    WEB_SWING=97
    WEB_ZIP=99
    WEB_MODIFIER=37
    CAMERA_LOCK=94
    TARGET_CAMERA=101
    UP=23
    DOWN=19
    LEFT=1
    RIGHT=4
    R_UP=86
    R_DOWN=85
    R_LEFT=84
    R_RIGHT=83
    [JOYSTICK]
    JUMP=1
    PUNCH=3
    KICK=2
    WEB_ATTACK=4
    CROUCH=9
    START=8
    WEB_SWING=-1
    WEB_ZIP=6
    WEB_MODIFIER=7
    CAMERA_LOCK=5
    TARGET_CAMERA=10
    [MOUSE]
    JUMP=-1
    PUNCH=-1
    KICK=-1
    WEB_ATTACK=-1
    CROUCH=-1
    START=-1
    WEB_SWING=-1
    WEB_ZIP=-1
    WEB_MODIFIER=-1
    CAMERA_LOCK=-1
    TARGET_CAMERA=-1
    
  2. Set up AntiMicro with this profile.
  3. If you like, you can also set AntiMicro to use this profile when the game is run, as well as set AntiMicro to run on PC startup, both from AntiMicro's settings, if you want to automate the process for playing the game.

Notes

This should be a rough mapping of a standard XInput controller to the PS2 controls based on the locations of the inputs on the Xbox 360 controller and the PS2 controller (A->X, LT->L2, etc). The PS2 control scheme can be found here.
Because of differences in the PC version of the game, there are still a few significant differences in controls from console versions.
  • On PC the gamepad recenter camera control is always tied to the web action control (LT in this control scheme) like the "classic" control scheme on consoles.
  • On PC, the yo-yo spidey move is LT+RB which maps to the "enhanced" control scheme from the console versions.
  • The dodging moves do not work.

Cutscenes are distorted[edit]

  1. Set up dgVoodoo2.
    1. Download dgVoodoo 2.
    2. Copy the DLL files from the MS/x86 folder to <path-to-game>, where SpiderMan.exe is located.
    3. Open dgVoodooCpl.exe. You may want to make a separate profile for the game (hit the Add button at the top of the window, and select the <path-to-game> folder, which you copied the DLL files into).
    4. Under the General tab, set the Appearance to Fullscreen and Scaling mode to Stretched, keep Aspect Ratio.
    5. Under the DirectX tab, set the Resolution to the resolution you intend to run the game with, and uncheck the "dgVoodoo Watermark" option. You can also set the Filtering option here if you want to force anisotropic filtering.
    6. Click the OK button.
  2. Set up DxWnd.
    1. Download DxWnd.
    2. Run dxwnd.exe and go to Edit->Add, then in the Main tab, type in a Name, and for Path browse to and select <path-to-game>\SpiderMan.exe.
    3. In the same Main tab, make sure under Generic, Fullscreen only is checked, and under Position, Desktop center is selected.
    4. In the Video tab, set Window style to default, Window size & position to Anchored, and Screen resolution to Native.
    5. Click the OK button.
  3. Now as long as DxWnd is running when you launch the game, the cutscenes should be visible and stretched to your screen, though they will still be stretched out if you have the game set to run in any aspect ratio besides 4:3.
  4. If you are using a 16:9 aspect ratio, you can download modified cutscene files that are stretched properly for 16:9 aspect ratios to watch the cutscenes in-game without any distortion.
    1. Go to <path-to-game> and make a backup of the movies folder.
    2. Download these modified .BIK files and place them in the movies folder (replacing the old files, which you should have backed up).

Notes

If you like, you can automate launching DxWnd on your PC's startup by placing a shortcut to dxwnd.exe in your Start Menu's Startup folder, and changing the shortcut's properties. In the Properties window of the shortcut, in the Shortcut tab, change Target by adding /T to the end of the text in the field. The resulting field should look something like "<path-to-DxWnd>\dxwnd.exe" /T. The /T parameter launches DxWnd in the system tray.

Issues Unresolved[edit]

Crash/black screen with resolutions higher than 640x480 in Windows 10[edit]

If the game is set to a resolution higher than 640x480 in Windows 10, the game will attempt to change resolutions and might freeze on a black screen after the intro movies, when starting or loading a game, or even whenever you navigate through the menus to watch movies/cutscenes. The only solution so far is to play in 640x480. Unknown if there is a fix to play at higher resolutions.
Play in 640x480[citation needed]
Try using dgVoodoo2 and DxWnd[citation needed]

A possible workaround is to run the game using dgVoodoo2 and DxWnd. Follow the method for setup in Cutscenes are distorted.

Other information[edit]

API[edit]

Technical specs Supported Notes
Direct3D 8.1
Executable 32-bit 64-bit Notes
Windows

System requirements[edit]

Windows
Minimum Recommended
Operating system (OS) 98
Processor (CPU) Intel Pentium III 450 MHz
AMD Athlon
System memory (RAM) 64 MB
Hard disk drive (HDD) 750 MB
Video card (GPU) 32 MB of VRAM
DirectX 8.1 compatible

Notes

  1. 1.0 1.1 When running this game without Administrator elevation, activity in %PROGRAMFILES%, %PROGRAMFILES(X86)%, and %WINDIR% might be redirected to %LOCALAPPDATA%\VirtualStore\ (more details).

References