Tei
Sergeant at Arms
![](ranks/new/sergeant_at_arms.png)
If you have a 32bit operating system refer to points "1. Fixing" and "2. Adjusting VM". If you have a 64bit operating system refer only to point "2. Adjusting VM". If you have a crash while launching the game (or a skybox error) refer to "Early crashes". You can also refer to Known things that will cause you to CTD or lag heavily for further reading. |
And remember to always
![mofodg7.gif](http://img34.imageshack.us/img34/4760/mofodg7.gif)
(violators will be ignored)
Have in mind that this thread is mainly about AD 1257 module so if you're playing something else and it's still not working then: a) you did something wrong, b) the problem lays somewhere else.
Crucial edit:
If it works for you then don't brag about it creating new posts - just vote. It's easier for me to respond to problems, questions and such when I don't have to dig through irrelevant posts. It's not like I'm not glad about fixing your problems, it's just not needed to inform me about it.
If it doesn't work or you are having a problem with applying it - post your questions and I will do my best to help you guys out. The problem may lay somewhere else and the fix may not be the solution to your problem.
Also keep in mind that it isn't a regular bug thread and I won't be too helpful in issues going over the basic subject of the fix. I'll say more - it will piss me off.
If it doesn't work or you are having a problem with applying it - post your questions and I will do my best to help you guys out. The problem may lay somewhere else and the fix may not be the solution to your problem.
Also keep in mind that it isn't a regular bug thread and I won't be too helpful in issues going over the basic subject of the fix. I'll say more - it will piss me off.
Early crashes:
If you're having a crash at the very beginning of your voyage (right after killing the bandit, after arriving to a town, while loading the mod etc.) then:
- if you're crashing while the game is loading or just after clicking any of the buttons in the menu then you:
a) have to tick the "Load textures on demand" in Configuration settings (however, it works for few people without having it checked. for me it used to crash before loading everything up).
b) have to re-download the mod (maybe the installer got corrupted during or after the download)
- if you have modded the files somehow - revert to original. Sometimes editing the files can screw few things up.
- ATI video card owners may have problems with their visuals in the game (with or without this fix). Try reverting to 10.5 or 10.6 version of graphic drivers.
- for some people it's about skyboxes errors. Refer to this thread for a fix.
- if you're crashing while the game is loading or just after clicking any of the buttons in the menu then you:
a) have to tick the "Load textures on demand" in Configuration settings (however, it works for few people without having it checked. for me it used to crash before loading everything up).
b) have to re-download the mod (maybe the installer got corrupted during or after the download)
- if you have modded the files somehow - revert to original. Sometimes editing the files can screw few things up.
- ATI video card owners may have problems with their visuals in the game (with or without this fix). Try reverting to 10.5 or 10.6 version of graphic drivers.
- for some people it's about skyboxes errors. Refer to this thread for a fix.
Things to do before:
Before using this solution make sure that your hardware drivers are up to date (if ATI - read above), same with DirectX. It would be good to have OS updated as well, however it is not mandatory (as long as Microsoft won't make another patch messing everything up). Also, if you're using any kind of program/plug-in modifying your boot file (like Bootskin for example), this solution may not work - deactivate it and try then.
Description:
Probably many of you get crashes while saving a game, sometimes during or after a bigger battle, switching screens (like while going to tavern, etc) or just about 10-20 minutes of playing. It is a fairly common problem with this mod, but there are people who never crash, so the only probable reason was OS or hardware specific. I've been cross-checking issues like that (mainly about saves) with other games and found out a nice solution at JoWood forums. Seems to work - I've asked one of this board's member, Earende, about applying this solution and it worked out nice. Few friends of mine say that it works for them too. I've played for 2 hours yesterday (on Vista) and quit by myself without any crashes so it does seem like a legit solution.
Feel free to comment if you're having problems - I'll try to answer the best way I can. I check this thread every day, so...
Feel free to comment if you're having problems - I'll try to answer the best way I can. I check this thread every day, so...
! ! ! Using this solution involves editing system settings so watch out what you're doing ! ! !
Explanation:
If you're running a 32bit operating system and get the crashes while saving or otherwise dumping a lot of memory usage then it is most likely because of the fact that 32bit operating systems only provide an address space of 2GB to every user process running. It means that whenever memory usage for 1257 (filled with lots of textures) goes sky rocket it most likely exceeds 2GB and then you get the crash. The way to avoid crashing is configuring your OS to give more address space to process.
The fix is pretty easy, as it is described, and can be represented in two points:
[list type=decimal]
[*]"Fixing", which is basically making the operating system to put more memory into a single process.
[*]"Adjusting VM" (Virtual Memory), which is needed to be set correctly.
[/list]Skipping any of those two points may most likely change nothing so be sure to apply both of those solutions (64bit OS users do only the adjusting, without the fix). If this workaround will make more harm than good (unlikely to happen) then refer to "Reverting the process" section.
The fix is pretty easy, as it is described, and can be represented in two points:
[list type=decimal]
[*]"Fixing", which is basically making the operating system to put more memory into a single process.
[*]"Adjusting VM" (Virtual Memory), which is needed to be set correctly.
[/list]Skipping any of those two points may most likely change nothing so be sure to apply both of those solutions (64bit OS users do only the adjusting, without the fix). If this workaround will make more harm than good (unlikely to happen) then refer to "Reverting the process" section.
1. Fixing
(32bit OS only)
Windows XP
- Menu Start -> Run, type sysdm.cpl and press ENTER
- a window should open, go to tab Advanced -> Startup and Recovery Settings -> Edit
- at this point you're editing your boot.ini file. Don't mess things up.
Look for the line with your operating system mentioned and add "/3GB /USERVA=2990" without quotes. Should look like this:
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect /3GB /USERVA=2990 - save changes and reboot
- if you are running as an Administrator go to Menu Start -> Run, type cmd and press ENTER
- if not go to Menu Start -> Programs -> Accessories, press RMB on Command Prompt and select Run as Administrator
- in Command Prompt type "bcdedit /set IncreaseUserVA 2990" without quotes and press ENTER
- reboot
2. Adjusting VM
(32bit & 64bit OS)
(Thanks Tina for reminding me about VM)
This solution probably won't work if your RAM and Virtual Memory summary is lower than it should be. You can't do much about RAM (well, if you have cash then you can do much about it) but you can change the values of VM.
Known problems with changing the VM settings:
- (XP) boot.ini file doesn't exist - there are three possibilities here: first one is that you don't have the administrative privileges to edit the file; second one is that the file, for reasons unknown, actually doesn't exist; third one is that the file is hidden. Solution to the first problem is logging in as an administrator user. Second one is described → here ←. Solution to the third problem is setting the folders to show hidden and system files (I really don't know what will it change but was suggested by some people, so - try it out), but I don't remember where do you change that in XP and Vista so refer to system help (press F1 on your desktop).
- can't set the VM values over 4096 MBs (4GBs) - most likely the drive you are trying to use for the swap file space is formated with FAT32 file system. This allocation forbids to use files bigger than 4GBs. You'll have to use a hard drive or partition formated with NTFS file system.
- also, have in mind that we are talking about disk space, so make sure that you have enough disk space to be used as VM
Windows XP, Windows Vista, Windows 7 (or at least I think that the route is the same in each of these systems)
- Menu Start -> Settings -> Control Panel -> System -> Advanced
- Performance -> Settings
- Advanced tab -> Change
The tricky part is setting the values right. Microsoft suggests (http://support.microsoft.com/kb/308417 , Step 2) to set the minimal value as 1.5x of your RAM and maximal value as 3x your RAM (so if you have, for example, 2GBs of ram then minimal is 3.5GBs and max is 6GBs... so that's 3500MBs and 6000MBs). There's plenty of topics on the web with performances results and such revolving around this subject so... Google. - Save, reboot
3. Reverting the process
It may happen that using this fix will make some pieces of software to work differently than before, deviate in some way or produce and error. Luckily, this solution is completely revertible. If you want to get back to your previous settings, then:
Windows XP
- Menu Start -> Run, type sysdm.cpl and press ENTER
- a window should open, go to tab Advanced -> Startup and Recovery Settings -> Edit
- at this point you're editing your boot.ini file. Don't mess things up.
Look for the line with your operating system mentioned and erase "/3GB /USERVA=2990". Should look something like this:
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect - save changes and reboot
- if you are running as an Administrator go to Menu Start -> Run, type cmd and press ENTER
- if not go to Menu Start -> Programs -> Accessories, press RMB on Command Prompt and select Run as Administrator
- in Command Prompt type "bcdedit /deletevalue IncreaseUserVA" without quotes and press ENTER
- reboot
4. Issues
Because some of you are obviously too fkn lazy to use the incredible tool like a search engine:
http://blogs.technet.com/b/askperf/archive/2007/03/23/memory-management-demystifying-3gb.aspx
So... if you're not running any programs, games and such that 'force' you to use the 3gb switch, just turn it off.
If it still isn't working as it should then the problem lays somewhere else, check here -> Known things that will cause you to CTD or lag heavily for an answer. Nothing helps? Check the bugs thread. Nothing? Hmm... run-time errors. Still not working? Oh, I dunno... format c: -> reinstall, the problem lays somewhere else or you are doing something wrong.