Fawzia dokhtar-i-Sanjar
Master Knight
Post any bugs here, but please don't put your suggestions, questions or comments here - this thread is strictly for bugs!
Unless you put the following in your bug report, you won't get any help.
a) Who you were fighting
b) Number of your troops and of the enemy troops in the siege or battle
c) Location of the battle
d) Specs of your machine and video card, how much memory, etc.
e) Specific details of a non-battle crash, such as taking to a particular type of troop or npc
Posting specs of your machine and video card are crucially important.
This will help find the problem. Saying "my game crashed" without specific details will not help locate the problem. If you can, keep a save game to send our techies. If you have an older or not very powerful machine, save before battles. Other issues may arise from ATI video cards, which have always had issues with M&B, but we have tested POP 3 with both ATI and Nvidia. Treebeard hopes he has dealt with ATI issues in the port - he has ATI and all works without crashing on his machine.
As usual, any bugs caused by tweaks or file modifications made by you will NOT be supported. We'd advise you leave the files alone, at least until you've played the game at least once, the way we designed it. Massive amounts of code have been rewritten and many new ones put into PoP, Warband. Any previous tweaks you used will probably not work, including any of Magelord's or PoP 3 for V 1.011 versions. Only those mods that we list as included in PoP, Warband were tested by us, so include other mods at your own risk.
Please remember that PoP, Warband like PoP 3 for V 1.011 is a very demanding game in terms of memory, textures, sounds, etc. You can use Battle Sizer with it, but you may not be able to crank up the numbers of troops per battle as high as you normally do in Native vanilla Warband or another mod. Griefer, who has very high-powered equipment, has played with no crash problems with Battle Sizer set to 400. That is as high as the Dev Team tested. Unless you have top-tier equipment, we suggest you start with Battle Sizer at 150 or below, and gradually inch up your numbers to see how high a number your own machine can handle.
We strongly recommend that you keep multiple saves.
TRY THESE FIXES BEFORE YOU POST!
We are aware that there is a problem for some Steam version users - switch to the CD or download Warband versions.
If you are playing the game in a language other than English and getting Native names for towns, etc. and the Native map, switch your language to English.
Did you try any (or all) of these things:
Did you install the Warband upgrade V 1.134 and then install the PoP 3 patch for V 1.134?
Reduce corpses and ragdolls to a very low number or even 0
Switch from DX9 to DX 7
When you start Warband go to Configure - Video - Check the box which says "Load Textures on Demand"
When you start Warband go to Configure - Advanced - UNcheck the box which says "Force Single Threading"
Reduce Battle Sizer to under 150 per battle if you are using it then gradually inch up the numbers until you hit crash level
When the game loads go to "Options" - Reduce shadow quality to "low" & reduce texture quality to "low" & shader quality to "Medium" & Grass Density to 50% & Realistic shadows on plants to either quick or none & Tree detail to medium
Eliminate unnecessary programs running in the background
Check that your video and audio drivers are up to date
Memory can indeed be an issue - the game's use of your ATI memory, as Treebeard explained in the ATI guide.
This has also helped a LOT of people with similar problems:
http://forums.taleworlds.com/index.php/topic,131274.0.html
http://forums.taleworlds.com/index.php/topic,127609.0.html
If you have not tried any and/or all of the above suggestions, I'd suggest trying some of these solutions. Many people posting in this thread have had similar issues which were corrected by one or a combination of the above. Don't dismiss a solution just because you think it has no relation to your problem - it may well have, but you will never find out unless you try a few.
Treebeard's Guide for ATI card problems:
UPDATE: If nothing else helps, try downloading and installing older driver versions of Catalyst. Version 10.3 is recommended for the ATI 5000 series, but you may have to go back even more (for example to 9.9 drivers) for older version of the ATI card (like the 4000 series).
If you still have problems AFTER trying some of these solutions, and after reading Treebeard's sticky about ATI problems, if you have an ATI card, please post your machine's specs, video card specs, etc. Just saying "my game crashed" is quite pointless as nobody knows why without further information.
Unless you put the following in your bug report, you won't get any help.
a) Who you were fighting
b) Number of your troops and of the enemy troops in the siege or battle
c) Location of the battle
d) Specs of your machine and video card, how much memory, etc.
e) Specific details of a non-battle crash, such as taking to a particular type of troop or npc
Posting specs of your machine and video card are crucially important.
This will help find the problem. Saying "my game crashed" without specific details will not help locate the problem. If you can, keep a save game to send our techies. If you have an older or not very powerful machine, save before battles. Other issues may arise from ATI video cards, which have always had issues with M&B, but we have tested POP 3 with both ATI and Nvidia. Treebeard hopes he has dealt with ATI issues in the port - he has ATI and all works without crashing on his machine.
As usual, any bugs caused by tweaks or file modifications made by you will NOT be supported. We'd advise you leave the files alone, at least until you've played the game at least once, the way we designed it. Massive amounts of code have been rewritten and many new ones put into PoP, Warband. Any previous tweaks you used will probably not work, including any of Magelord's or PoP 3 for V 1.011 versions. Only those mods that we list as included in PoP, Warband were tested by us, so include other mods at your own risk.
Please remember that PoP, Warband like PoP 3 for V 1.011 is a very demanding game in terms of memory, textures, sounds, etc. You can use Battle Sizer with it, but you may not be able to crank up the numbers of troops per battle as high as you normally do in Native vanilla Warband or another mod. Griefer, who has very high-powered equipment, has played with no crash problems with Battle Sizer set to 400. That is as high as the Dev Team tested. Unless you have top-tier equipment, we suggest you start with Battle Sizer at 150 or below, and gradually inch up your numbers to see how high a number your own machine can handle.
We strongly recommend that you keep multiple saves.
TRY THESE FIXES BEFORE YOU POST!
We are aware that there is a problem for some Steam version users - switch to the CD or download Warband versions.
If you are playing the game in a language other than English and getting Native names for towns, etc. and the Native map, switch your language to English.
Did you try any (or all) of these things:
Did you install the Warband upgrade V 1.134 and then install the PoP 3 patch for V 1.134?
Reduce corpses and ragdolls to a very low number or even 0
Switch from DX9 to DX 7
When you start Warband go to Configure - Video - Check the box which says "Load Textures on Demand"
When you start Warband go to Configure - Advanced - UNcheck the box which says "Force Single Threading"
Reduce Battle Sizer to under 150 per battle if you are using it then gradually inch up the numbers until you hit crash level
When the game loads go to "Options" - Reduce shadow quality to "low" & reduce texture quality to "low" & shader quality to "Medium" & Grass Density to 50% & Realistic shadows on plants to either quick or none & Tree detail to medium
Eliminate unnecessary programs running in the background
Check that your video and audio drivers are up to date
Memory can indeed be an issue - the game's use of your ATI memory, as Treebeard explained in the ATI guide.
This has also helped a LOT of people with similar problems:
http://forums.taleworlds.com/index.php/topic,131274.0.html
http://forums.taleworlds.com/index.php/topic,127609.0.html
If you have not tried any and/or all of the above suggestions, I'd suggest trying some of these solutions. Many people posting in this thread have had similar issues which were corrected by one or a combination of the above. Don't dismiss a solution just because you think it has no relation to your problem - it may well have, but you will never find out unless you try a few.
Treebeard's Guide for ATI card problems:
There are two issues currently that players with ATI cards can encounter:
Distorted, Invisible or otherwise malfunctioning textures and texture glitches.
To prevent any such glitches, you should go to the folder where PoP is installed, for example:
C:\Program Files (x86)\Mount&Blade Warband\Modules\Prophesy of Pendor 3.2
In this folder you’ll see a file named “game_variables.txt” Open this file in Notepad or Wordpad.
It will look like this”
# Initial Buffer_sizes
# Modders may adjust these large enough so that the game will not need to restore
# buffers during the game. However keeping them excessively large will reduce performance in most systems.
#Buffer_sizes (if smaller than 65535, this also represents the maximum vertex count for a corresponding mesh)
new_buffer_size_dx7_regular_ffp_static = 262144
new_buffer_size_dx7_regular_ffp_dynamic = 262144
new_buffer_size_regular_ffp_static = 32768
new_buffer_size_regular_ffp_dynamic = 32768
new_buffer_size_regular_static = 131072
new_buffer_size_regular_dynamic = 65536
new_buffer_size_skinning_static = 131072
new_buffer_size_skinning_dynamic = 65536
new_buffer_size_normal_map_static = 131072
new_buffer_size_normal_map_dynamic = 65536
new_buffer_size_normal_map_skinning_static = 131072
new_buffer_size_normal_map_skinning_dynamic = 65536
Comment out all New_buffer_size lines by putting a # in front of each line. Afterwards it will look like this:
# Initial Buffer_sizes
# Modders may adjust these large enough so that the game will not need to restore
# buffers during the game. However keeping them excessively large will reduce performance in most systems.
#Buffer_sizes (if smaller than 65535, this also represents the maximum vertex count for a corresponding mesh)
#new_buffer_size_dx7_regular_ffp_static = 262144
#new_buffer_size_dx7_regular_ffp_dynamic = 262144
#new_buffer_size_regular_ffp_static = 32768
#new_buffer_size_regular_ffp_dynamic = 32768
#new_buffer_size_regular_static = 131072
#new_buffer_size_regular_dynamic = 65536
#new_buffer_size_skinning_static = 131072
#new_buffer_size_skinning_dynamic = 65536
#new_buffer_size_normal_map_static = 131072
#new_buffer_size_normal_map_dynamic = 65536
#new_buffer_size_normal_map_skinning_static = 131072
#new_buffer_size_normal_map_skinning_dynamic = 65536
Save and close the text file. Now you should have less problems with graphics glitches.
If the game hangs at startup, at “Loading Settings Data”.
If this happens you need to go to Configure in the Pre-launch menu and lower the Texture Detail settings:
Start by lowering it to 99% and then try running PoP. If that doesn’t help, then lower the Texture Details to 89%.
Distorted, Invisible or otherwise malfunctioning textures and texture glitches.
To prevent any such glitches, you should go to the folder where PoP is installed, for example:
C:\Program Files (x86)\Mount&Blade Warband\Modules\Prophesy of Pendor 3.2
In this folder you’ll see a file named “game_variables.txt” Open this file in Notepad or Wordpad.
It will look like this”
# Initial Buffer_sizes
# Modders may adjust these large enough so that the game will not need to restore
# buffers during the game. However keeping them excessively large will reduce performance in most systems.
#Buffer_sizes (if smaller than 65535, this also represents the maximum vertex count for a corresponding mesh)
new_buffer_size_dx7_regular_ffp_static = 262144
new_buffer_size_dx7_regular_ffp_dynamic = 262144
new_buffer_size_regular_ffp_static = 32768
new_buffer_size_regular_ffp_dynamic = 32768
new_buffer_size_regular_static = 131072
new_buffer_size_regular_dynamic = 65536
new_buffer_size_skinning_static = 131072
new_buffer_size_skinning_dynamic = 65536
new_buffer_size_normal_map_static = 131072
new_buffer_size_normal_map_dynamic = 65536
new_buffer_size_normal_map_skinning_static = 131072
new_buffer_size_normal_map_skinning_dynamic = 65536
Comment out all New_buffer_size lines by putting a # in front of each line. Afterwards it will look like this:
# Initial Buffer_sizes
# Modders may adjust these large enough so that the game will not need to restore
# buffers during the game. However keeping them excessively large will reduce performance in most systems.
#Buffer_sizes (if smaller than 65535, this also represents the maximum vertex count for a corresponding mesh)
#new_buffer_size_dx7_regular_ffp_static = 262144
#new_buffer_size_dx7_regular_ffp_dynamic = 262144
#new_buffer_size_regular_ffp_static = 32768
#new_buffer_size_regular_ffp_dynamic = 32768
#new_buffer_size_regular_static = 131072
#new_buffer_size_regular_dynamic = 65536
#new_buffer_size_skinning_static = 131072
#new_buffer_size_skinning_dynamic = 65536
#new_buffer_size_normal_map_static = 131072
#new_buffer_size_normal_map_dynamic = 65536
#new_buffer_size_normal_map_skinning_static = 131072
#new_buffer_size_normal_map_skinning_dynamic = 65536
Save and close the text file. Now you should have less problems with graphics glitches.
If the game hangs at startup, at “Loading Settings Data”.
If this happens you need to go to Configure in the Pre-launch menu and lower the Texture Detail settings:
Start by lowering it to 99% and then try running PoP. If that doesn’t help, then lower the Texture Details to 89%.
UPDATE: If nothing else helps, try downloading and installing older driver versions of Catalyst. Version 10.3 is recommended for the ATI 5000 series, but you may have to go back even more (for example to 9.9 drivers) for older version of the ATI card (like the 4000 series).
If you still have problems AFTER trying some of these solutions, and after reading Treebeard's sticky about ATI problems, if you have an ATI card, please post your machine's specs, video card specs, etc. Just saying "my game crashed" is quite pointless as nobody knows why without further information.