Thx for your patience and a huge hurray for all ppl contributing (in few words: the Gabby's Bunch )
Please be sure you downloaded the New 1776 Version 1.5 before posting here!!!
Please, DO NOT add things already said!!
THX
IMPORTANT!! Please read:
Just please, when starting:
But most things work like charme. Just please, when starting:
-Update to Warband version 1.143
-Start a New Game. Delete old 1776 savegames
-DO NOT use any kind of translations. Use only original ENGLISH Warband version.
-Say NO to 16 companions all in 1st tavern
-NEVER EVER make RANDOM face generation . NEVER, please! It will crash the game...
-DO NOT choose ALBANY as first Town to meet Merchant, it still crashes (only sometimes)
-SAVE AS SOON AS POSSIBLE, after Merhant gives you 1st mission, close the game to DESKTOP and load your last save. That helps to avoid some random CTD (Crashes To Desktop) and loads all musics and sounds of 1776 in a correct way (expecially if you played another WB mod, before )
-put to minimum all graphics, Battle size, Cheats off, etc. If all works good, improve some performances issues, step by step, and see what causes crashes.
IF STILL have bad PC or game issues, ........well....sit down confortable, and read (AND DO!!!) all steps here: (it is a pain in the butt, but it solved ALL my old Brytenwalda problems )
FIRST STEP LINK: http://forums.taleworlds.com/index.php/topic,209372.msg4981784.html#msg4981784
SECOND STEP LINK: http://forums.taleworlds.com/index.php/topic,163475.msg3954028.html#msg3954028
Gabby
But most things work like charme. Just please, when starting:
-Update to Warband version 1.143
-Start a New Game. Delete old 1776 savegames
-DO NOT use any kind of translations. Use only original ENGLISH Warband version.
-Say NO to 16 companions all in 1st tavern
-NEVER EVER make RANDOM face generation . NEVER, please! It will crash the game...
-DO NOT choose ALBANY as first Town to meet Merchant, it still crashes (only sometimes)
-SAVE AS SOON AS POSSIBLE, after Merhant gives you 1st mission, close the game to DESKTOP and load your last save. That helps to avoid some random CTD (Crashes To Desktop) and loads all musics and sounds of 1776 in a correct way (expecially if you played another WB mod, before )
-put to minimum all graphics, Battle size, Cheats off, etc. If all works good, improve some performances issues, step by step, and see what causes crashes.
IF STILL have bad PC or game issues, ........well....sit down confortable, and read (AND DO!!!) all steps here: (it is a pain in the butt, but it solved ALL my old Brytenwalda problems )
FIRST STEP LINK: http://forums.taleworlds.com/index.php/topic,209372.msg4981784.html#msg4981784
SECOND STEP LINK: http://forums.taleworlds.com/index.php/topic,163475.msg3954028.html#msg3954028
Gabby
GOOD NEWS: we basically fixed most of worst bugs!!!
PLS keep in mind, though, that you need a powerful pc for this mod. I personally have to play low/medium video performance with my cheap pc.
Please BEFORE reporting your "bugs" here, be sure it is a REAL bug and not just something you did not like or understand.
In case of serious PC problems
In order to prevent the same questions from being asked over and over again, when you get a CTD or Heavy Lag:
-If it's a CTD try to explain in detail what you were doing when the crash happened. Include things such as your ingame settings and such. For the heavy lag please include your ingame settings as well as your Pc specs.
Causes
1. For Windows Vista/7 Anything above a 2 ghz processor, 2 gigs of ram, and 512mb. Windows xp is pretty much the same with a bit more leave way in terms of ram requirements. (Laptops require even more, unless its a laptop built specifically for gaming with high end specs a laptop performs horribly for gaming)
2. Having "Textures on Demand" not checked in the configure settings. (For every PC)
3. Having "Force Single Threading" not checked in the advanced settings. (Primarily for dual or quad core PC's)
4. Putting Ragdolls and Corpses to unlimited. (10 Ragdolls/40 Corpses or less is usually what you want)
5. Having your battlesizer over 200. (I suggest only going above 150 for PC's that exceed the specs I stated above)
6. Having your performance % under 100%. (The better the game looks, the slower it will run)
7. Having background programs running. (This eats up a ton of memory even if they aren't being used. Also M&B gets real anal when you alt + tab out of the game and typically crashes)
8. Having Anti-Aliasing on anything other than off/none. (For a game with graphics like M&B's this doesn't really do anything anyways, but your PC thinks it does and will still use massive amounts of video memory to try and make it work)
9. Having Edit mode selected in the advanced settings. (Only use this for debugging and never for actually playing the game)
10. You installed the mod incorrectly and screwed something up. (It happens sometimes, deal with it)
Potential Fixes
1. Battlesizer to 100 or less. (Will help performance and CTD's)
2. Video settings to "Low". (Will help performance)
3. Using Direct X7. (Looks crappy but helps low end PC's alot)
4. Use the "Start Windowed" option in settings with 800x600 resolution. (Will help performance)
5. Set max frame rate to 70. Even less, 60 or even 50!!!!! (The human eye can only see 60 fps tops anyways, and that's with perfect vision. Having it set to a high number just because your PC can do it isn't always a good idea)
I solved all my problems with this issue, and REMOVING BLOOD!!!!
6. Completely uninstall M&B and delete all files/registry files and do a fresh install. (Sometimes files become corrupted for whatever reason)
7. Turn off your networking and anti virus when you play the game, if you're using a hardcord for your networking unplug it from your PC just incase. (This will free up memory, which the game uses a ton of)
This is what I've experimented with during my time playing M&B. I personally use a 3ghz dual core, 4 gigs of ram, 2257mb video memory, and windows 7 64-bit. I never CTD, I don't lag in the battle maps with max settings and 250 battlesizer, and I have slight stutter on the World Map.
No matter how good your PC is, you will get stutter/lag on the World Map. This is due to the game's engine processing so many scripts constantly, and there is nothing you or Othr can do to fix that minus removing alot of ****.
If you are getting errors that show up with the red text, go into the notes and screen shot it then place it on the bugs board. More than likely it's an error in your installation because I have yet to see another one since this last patch.
If you get a CTD and it gives a pop-up with what caused it to crash take a screen shot of that and place it on the bugs board.
If you haven't bothered to read this far and just spam the board I'll ask Othr to just delete your post and your questions will just be ignored. As new problems/fixes are found I'll add them to the list and let you all know it's been updated.
If the game now works well, increase few things at a time, to discover WHERE your problem was.
If some problems are still there, try to solve your problem at this link http://forums.taleworlds.com/index.php/topic,131274.0.html.
-If it's a CTD try to explain in detail what you were doing when the crash happened. Include things such as your ingame settings and such. For the heavy lag please include your ingame settings as well as your Pc specs.
Causes
1. For Windows Vista/7 Anything above a 2 ghz processor, 2 gigs of ram, and 512mb. Windows xp is pretty much the same with a bit more leave way in terms of ram requirements. (Laptops require even more, unless its a laptop built specifically for gaming with high end specs a laptop performs horribly for gaming)
2. Having "Textures on Demand" not checked in the configure settings. (For every PC)
3. Having "Force Single Threading" not checked in the advanced settings. (Primarily for dual or quad core PC's)
4. Putting Ragdolls and Corpses to unlimited. (10 Ragdolls/40 Corpses or less is usually what you want)
5. Having your battlesizer over 200. (I suggest only going above 150 for PC's that exceed the specs I stated above)
6. Having your performance % under 100%. (The better the game looks, the slower it will run)
7. Having background programs running. (This eats up a ton of memory even if they aren't being used. Also M&B gets real anal when you alt + tab out of the game and typically crashes)
8. Having Anti-Aliasing on anything other than off/none. (For a game with graphics like M&B's this doesn't really do anything anyways, but your PC thinks it does and will still use massive amounts of video memory to try and make it work)
9. Having Edit mode selected in the advanced settings. (Only use this for debugging and never for actually playing the game)
10. You installed the mod incorrectly and screwed something up. (It happens sometimes, deal with it)
Potential Fixes
1. Battlesizer to 100 or less. (Will help performance and CTD's)
2. Video settings to "Low". (Will help performance)
3. Using Direct X7. (Looks crappy but helps low end PC's alot)
4. Use the "Start Windowed" option in settings with 800x600 resolution. (Will help performance)
5. Set max frame rate to 70. Even less, 60 or even 50!!!!! (The human eye can only see 60 fps tops anyways, and that's with perfect vision. Having it set to a high number just because your PC can do it isn't always a good idea)
I solved all my problems with this issue, and REMOVING BLOOD!!!!
6. Completely uninstall M&B and delete all files/registry files and do a fresh install. (Sometimes files become corrupted for whatever reason)
7. Turn off your networking and anti virus when you play the game, if you're using a hardcord for your networking unplug it from your PC just incase. (This will free up memory, which the game uses a ton of)
This is what I've experimented with during my time playing M&B. I personally use a 3ghz dual core, 4 gigs of ram, 2257mb video memory, and windows 7 64-bit. I never CTD, I don't lag in the battle maps with max settings and 250 battlesizer, and I have slight stutter on the World Map.
No matter how good your PC is, you will get stutter/lag on the World Map. This is due to the game's engine processing so many scripts constantly, and there is nothing you or Othr can do to fix that minus removing alot of ****.
If you are getting errors that show up with the red text, go into the notes and screen shot it then place it on the bugs board. More than likely it's an error in your installation because I have yet to see another one since this last patch.
If you get a CTD and it gives a pop-up with what caused it to crash take a screen shot of that and place it on the bugs board.
If you haven't bothered to read this far and just spam the board I'll ask Othr to just delete your post and your questions will just be ignored. As new problems/fixes are found I'll add them to the list and let you all know it's been updated.
If the game now works well, increase few things at a time, to discover WHERE your problem was.
If some problems are still there, try to solve your problem at this link http://forums.taleworlds.com/index.php/topic,131274.0.html.
.1st
WHEN STARTING M&B WB AND CHOOSING 1755 MOD, GO TO "CONFIGURE" AND THEN TO "HIDE BLOOD" / "ENABLE CHEATS" (they both should NOT be marked if you have PC performances problem). GO THEN TO "ADVANCED" AND CHECK IF "Enable Edit Mode" is on.
(It should be OFF for best performance)
.2nd
TURN DOWN ALL YOUR VIDEO SETTINGS, ALL OF THEM TO MINIMUM, BUT EXPECIALLY
"MAX FRAME RATE" TO 60
"TREES DETAILS" AND ANY "SHADER/SHADOWS" TO MINIMUM
- Do not set to zero "Monitor Gamma" of course....or your monitor will become BLACK!
.3rd
TURN TO MINIMUM "BATTLE SIZE" AND ALL POSSIBLE GAME OPTIONS, EVEN INDICATORS.
If the game now works well, increase few things at a time, to discover WHERE your problem was.
If some problems are still there, try to solve your problem at this link
FIRST STEP LINK: http://forums.taleworlds.com/index.php/topic,209372.msg4981784.html#msg4981784
SECOND STEP LINK: http://forums.taleworlds.com/index.php/topic,163475.msg3954028.html#msg3954028
THX
Gabrilduro and his team
IMPORTANT:
1776 OLD FRONTIER IS MADE TO RUN ONLY WITH ORIGINAL WAR BAND UPDATED TO V. 1. 143 or at least v. 1.134