Vampire: The Masquerade - Bloodlines Speedrun Wiki

User Tools

Site Tools

Trace:
setting_up_the_game

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
setting_up_the_game [2017/06/24 21:32]
lurk [Install the game] 		setting_up_the_game [2017/08/07 15:37] (current)
lurk [Get the files]
Line 5: Line 5:
  
 ===== Get the files ===== ===== Get the files =====
-After installing you'll need to replace some files to make the game playable. You can download them [[https://lurk.moe/vtmb/vtmb-speedrun.zip|here]]. This also includes the Unofficial Patch's vampire.exe and lurk's configuration files.+After installing you'll need to replace some files to make the game playable.  
 + 
 +**You can download them [[https://lurk.moe/vtmb/vtmb-speedrun.zip|here]].**  
 + 
 +This includes  
 +<code>vampire.exe // from the Unofficial Patch   
 +cfg/autoexec.cfg // 
 +cfg/config.cfg //lurk's configuration files 
 +engine.dll // hexedited to fix less than 15mb issue 
 +shaderapidx9.dll // hexedited to fix low detail 
 +vampire.dll // from the Unofficial Patch</code>
  
 ===== Install the game ===== ===== Install the game =====
Line 17: Line 27:
 The Source engine used in Bloodlines is a very early version which operates entirely within the confines of a 32bit program, so running in 64bit can be an issue. When vampire.exe checks to see how much memory your system has upon initially loading, it expects a 32bit INT number as a result. However, since a 64bit number returns, the extra bits are seen as a negative flag which tells the program that you have a negative amount of RAM, or less than 15mb. This can also occur on 32bit systems if it has more than 2gb of RAM, since Bloodlines will loop back to negative numbers beyond 2gb.  The Source engine used in Bloodlines is a very early version which operates entirely within the confines of a 32bit program, so running in 64bit can be an issue. When vampire.exe checks to see how much memory your system has upon initially loading, it expects a 32bit INT number as a result. However, since a 64bit number returns, the extra bits are seen as a negative flag which tells the program that you have a negative amount of RAM, or less than 15mb. This can also occur on 32bit systems if it has more than 2gb of RAM, since Bloodlines will loop back to negative numbers beyond 2gb. 
  
-To fix this, an edited engine.dll is used which fixes the base problem. +To fix this, an edited engine.dll is used which fixes the base problem. Do not use the unofficialengine.dll unless for some reason the hexedited engine.dll does not work. 
  
 Another issue the engine has is how it loads models/textures/maps/objects/etc. This is done in a brute force fashion: all of your memory is filled with dummy textures, then once finished the game takes the total result from that and figures out how much memory it needs to use. If you have more than 2gb of RAM, a negative number is returned. Since the Source engine was designed to work with different hardware setups automatically to meet the needs of whatever it's running on, the game decides to blur most of the textures to an extremely low detail since it believes you have negative RAM, and therefore a shit system. Another issue the engine has is how it loads models/textures/maps/objects/etc. This is done in a brute force fashion: all of your memory is filled with dummy textures, then once finished the game takes the total result from that and figures out how much memory it needs to use. If you have more than 2gb of RAM, a negative number is returned. Since the Source engine was designed to work with different hardware setups automatically to meet the needs of whatever it's running on, the game decides to blur most of the textures to an extremely low detail since it believes you have negative RAM, and therefore a shit system.
Line 25: Line 35:
 Finally, Microsoft turned off the secdrv service because of security exploits. Unfortunately, Bloodlines (and many other games) depend on the service to load. To fix this, instead of using the usual vampire.exe, we use the vampire.exe from the Unofficial Patch, which has fixed the program to run without the need of the service. Finally, Microsoft turned off the secdrv service because of security exploits. Unfortunately, Bloodlines (and many other games) depend on the service to load. To fix this, instead of using the usual vampire.exe, we use the vampire.exe from the Unofficial Patch, which has fixed the program to run without the need of the service.
  
 +So, replace:
 +<code>
 +..\Activision\Vampire - Bloodlines\vampire.exe
 +..\Activision\Vampire - Bloodlines\Bin\engine.dll
 +..\Activision\Vampire - Bloodlines\Bin\shaderapidx9.dll
 +..\Activision\Vampire - Bloodlines\Vampire\cfg
 +</code>
 ===== Run the game and watch the intro ===== ===== Run the game and watch the intro =====
-Run the game and make sure it works. You have to watch the introduction cutscene at least once before you can get the skip intro button. +Run the game and make sure it works. You have to watch the introduction cutscene at least once before you can get the skip intro button. You can usually use the console command //vskip_intro "1"// to skip the intro.
  
 ===== Setup game configuration files ===== ===== Setup game configuration files =====
setting_up_the_game.1498339920.txt.gz · Last modified: 2017/06/24 21:32 by lurk

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki