2015-6 Brytenwalda Reworked pulling together the best features of BW submods +

[gdwitt]

That's not a problem I heard before.
Which mod version are you playing? REworked? 23?
I would need to see your rgl_log.txt to figure out what's happening.
I could also attempt a save game.

Common issues:
USing Tweakmb. Only a few tweaks can cause problems
mixing unmixable mods.
Using WSE itemkinds without launching from WSE.

What weapon were you using?
Did you give any particular order to the troops?

I need to know the pattern to isolate it.

You can also send the savegame via dropbox.

 

[MXDXD]

That's not a problem I heard before.
Which mod version are you playing? REworked? 23?
I would need to see your rgl_log.txt to figure out what's happening.
I could also attempt a save game.

Common issues:
USing Tweakmb. Only a few tweaks can cause problems
mixing unmixable mods.
Using WSE itemkinds without launching from WSE.

What weapon were you using?
Did you give any particular order to the troops?

I need to know the pattern to isolate it.

You can also send the savegame via dropbox.

23, NOT patched.
Content of the log file :

Starting new log file.
Version:  1.168

Not used any other mod.
Didn't use WSE items (as far as I know)
Didn't use TweakMB.

 

[MXDXD]

So.... yeah... I guess I can send a savegame

...Particular instructions for this? Never used Dropbox much, other than for swapping files with my GF.

 

[gdwitt]

One way I test my bugs is my loading the latest mod on my old laptop.
It is much more crash-prone.
My new rig doesn't even show or pause with minor errors.

You can send the savegame to gdwitt at g ma li com.
This is my address dedicated to the mod
It would help if I could see if opcodes are appearing at the crash point.
Send you rgl log as well.

I will try to get to it by Tuesday latest as I have a big interview tomorrow.

You may need to zip file it for it to send over email.

 

[Cenric Cynebalding]

This is the most recent version of Brytenwalda correct?

 

[gdwitt]

Main Brytenwalda is version 1.41. It's code is mostly from 2011-12 with a few minor changes in 2013.
Repolished is a text and graphic enhancement of 1.41 from Dec 2014.
Reworked is active and current.
They are all equally stable and prone to different minor bugs.
I can provide direct source code support to Reworked, but only advice for the others.

To MXD: Try using the lastest patch.
There were 2 minor bugs in the standalone v23 that most computers would not have noticed.
Also, do you give any battle orders at the start of the battle.

 

[LordGolias]

Yes, every night the scripts run.
I could generate a version where the scripts run every 2 days instead of every night.
But that will make politics move half as fast.
What most of us see during those 20 seconds is a slight shaking.
Let me know if you want the special patch.
Cheers,
GDWitt

I also get this. Maybe this shaking is an error on a script?

 

[LordGolias]

Ok.

The glitch problem is on the 2nd trigger (module_triggers.py). It disappears once the line

(call_script, "script_add_notification_menu", "mnu_notification_casus_belli_expired", ":faction_1", ":faction_2"),

is removed.
This call is probably too heavy do be performed over N^2 factions (the loop on the script is over every faction x every faction).

 

[gdwitt]

I will give it a try with that change this weekend.
It's good to have a programmer look at these.
You might notice that I went through many of the triggers and simple triggers and reduced the frequencies of the triggers that didn't seem to depend on otheres.

 

[LordGolias]

You might notice that I went through many of the triggers and simple triggers and reduced the frequencies of the triggers that didn't seem to depend on otheres.

Yes, I noticed, you did great. I believe that decreasing trigger actions can really improve the gameplay on the map.

Another thing that we probably could have is a simple flag on the code that when turned to 1, it jumps all the character creation right into the map view. This facilitates testing.

 

[gdwitt]

You may have noticed that I do have that shortcut in the game start screen.
I originally had it jump to the map, but then when I showed my character screen it would either get stuck in that screen or crash.
I would like to see it set up in another mod where it goes directly to the map.
I'm sure there's a way; I haven't studied it too much and will give it a go this weekend based on an old source code collection I have.

 

[Dulgakhor]

I have Version 23 Standalone + Version 23 Patch C (without flail pack) and it crashes like there is no tomorrow.
I can't go a in-game day or so without getting "Warband stopped to responding" box.
Anyone else experienced that?

P.S. I have two more Brytenwalda mods (ASOIAF and Imperial Rome) and whose work fine, and I reinstalled, tangled with settings and done all standart anti-crash measures, so problem not there.

 

[JC LEON]

which version I need to downlaod from nexus??
v23 and patch C? and after copy patch C content into reworked folder??

 

[LordGolias]

You may have noticed that I do have that shortcut in the game start screen.
I originally had it jump to the map, but then when I showed my character screen it would either get stuck in that screen or crash.
I would like to see it set up in another mod where it goes directly to the map.
I'm sure there's a way; I haven't studied it too much and will give it a go this weekend based on an old source code collection I have.

This was fixed in the github repository[1]. The game creation on "mod" now correctly sends the player to the map.
The issue, I believe, was that there were two global variables, "$wound_type" and "$heal_day", that were initialised in a character creation menu whose the "fast" creation mode was not entering.

In the github repository, these 2 variables were moved to the "game_start" script that contains all initialisations. [2]

[1] https://github.com/LordGolias/Brytenwalda/commit/e98b5431dd1163dd79876ba53ad118afcb35330d
[2] https://github.com/LordGolias/Brytenwalda/commit/e98b5431dd1163dd79876ba53ad118afcb35330d#diff-95c07ed3a392c325f26564e97a770b30R1481

 

[gdwitt]

Dulga,
What you have are actually 2 versions cleverly bundled into one zip file.
Read the instructions in the flail pack read me.
If you use the default setup with Steam, it should not cause any crashes.
If you use the WSE setup, there are a number of problems you may have.
The WSE gives you flails and blunt orders that really work well.

What exactly have you setup?
Are you using the new exe?
If you don't understand the directions for the WSE version, post your comments here https://forums.taleworlds.com/index.php?topic=343546.msg8212751#msg8212751and I will try to clarify things.

When exactly does that error occur? Does it occur at the start of battles or randomly during the game or in the middle of battles?
Does it come with any opcode errors in your rgl_log?
I have a new WSE operation in the script that shouldn't cause any problems if you aren't using WSE.
But if it is, it will show up in your rgl_log.
Please send me a copy if you see any Opcode errors there.

 

[gdwitt]

which version I need to downlaod from nexus??
v23 and patch C? and after copy patch C content into reworked folder??

Download the Standalone then the latest patch.
Patches are all cumulative like this unless I say they're optional.
I deleted patch a and b because they're in C.
Paste C over the Standalone and override the old versions.
Be sure to decide if you want to use the WSE version and just don't pick out parts of the flail pack.
I would stay away from the 100 companions unless you like that feature.

 

[Dulgakhor]

If you use the default setup with Steam, it should not cause any crashes.
If you use the WSE setup, there are a number of problems you may have.
The WSE gives you flails and blunt orders that really work well.

It's Version 23 Standalone + Version 23 Patch C in default Steam, without flail pack. Such fantasy weapons ruins Brytenwalda experience for me, so I did't bother with it at first.
Now I add it, just to see what will happen and I won few days of game.

What exactly have you setup?
Are you using the new exe?

Alright, here is step-by-step of what I did:

Spoiler

1. Extracted Version 23 Standalone in steamapps\common\MountBlade Warband/modules.
2. Added all .txt files from patch C in to steamapps\common\MountBlade Warband/modules/BWReworkedv23  (and one .brf file in to modules/BWReworkedv23/Resource)

3. Added new warband.exe, WSEloader.exe and WSELib.dll into steamapps\common\MountBlade Warband (along with 3 WSE text files)
4. Added item_kinds1flailtrigsUSEwithWSE in to MountBlade Warband/modules/BWReworkedv23 and renamed as item_kinds1
5. Added two new files in to MountBlade Warband/modules/BWReworkedv23/Sounds

6. Launched WSE loader.

When exactly does that error occur? Does it occur at the start of battles or randomly during the game or in the middle of battles?
Does it come with any opcode errors in your rgl_log?
I have a new WSE operation in the script that shouldn't cause any problems if you aren't using WSE.
But if it is, it will show up in your rgl_log.
Please send me a copy if you see any Opcode errors there.

No, no Opcodes or anything. Game just freezes for few seconds and then I get this

Spoiler

Game mostly crashes when I tied to interact with my company. I'm now in Day 4, and if I try to talk to companion or a soldier game will crash 100%. The same happens then I try to enter Hadrian wall. Cities are no problem- I can enter and talk to NPC's here as usual. Day 1 to 3 was without problems.

There was few crashes that happened in world map just because, but only twice.

P.S. After starting new game I imported my character and teleported around to collect companions (because I wanted to start were my old game broke off). Don't think it may had impact, but still.

I'm going to download v23 again and reinstall.

 

[gdwitt]

It looks like you are doing everything right.
I would try to redownload the standalone as the exe might have been compromised.
Make sure you use the new exe file. When I use the Steam exe, the game still runs fine, but there are no crashes.

Go to camp/take an action/ turn on cheat menu
Then as soon as you see a crash, rename your rgl-log and send it to me.

Then while you wait, test to see if it runs with the steam mb_warband.exe.
Just launch without WSELoader and go talk to characters.
Save this rgl_log

I wish the game was less buggy, but we get about 1 random crash complaint every week and I really need some insight.

You could also send me your savegame at gdwitt at gamil so i can test it on my two machines.

 

[Dulgakhor]

OK, files sended.
I think problem is somehow related to this:

Spoiler

}
WARNING: UNABLE TO MAP SOUND CODE:  snd_release_crossbow_medium
WARNING: UNABLE TO MAP SOUND CODE:  snd_release_crossbow_far
WARNING: UNABLE TO MAP SOUND CODE:  snd_bullet_hit_body
WARNING: UNABLE TO MAP SOUND CODE:  snd_player_hit_by_bullet
WARNING: UNABLE TO MAP GAME PRESENTATION CODE:  prsnt_game_escape
WARNING: UNABLE TO MAP GAME SCRIPT CODE:  game_missile_launch
WARNING: UNABLE TO MAP GAME SCRIPT CODE:  game_missile_dives_into_water
WARNING: UNABLE TO MAP GAME SCRIPT CODE:  game_troop_upgrades_button_clicked
WARNING: UNABLE TO MAP GAME SCRIPT CODE:  game_character_screen_requested

P.S. redownloaded and reinstaled. No changes.

 

[Tvrtko II Kotromanic]

I keep losing relations every day with (just) one of my vassals (ex-companion). It goes down around -3 to -4 at the end of every day. Am I doing something wrong?

Edit: Is option to send gifts still active, coz I can't find it in chancellor's menu?