SP Dark Ages [Submod] Dark Age 867AD

Users who are viewing this thread

I'm having the exact same problem as the above poster. I'm 40 hours into a blood eagle playthrough on their most recent patch, and can start VC games just fine. Problem seems to be related to DA specifically.

I'm able to start a new game on VC-Vanilla just fine (latest warband and VC), as well as on the most recent Blood Eagle/Warband combo.

Can you try re-packing and uploading the archive again maybe?
 
Hello, I have discovered that the problem has to do with a mismatch between menus.txt (from Vanilla VC) and the Dark Age mod. Specifically something in menu_start_game_0 seems to be off, and in a few other places it is likely to cause the same issues. Can we get the mod author to upload his menus.txt or include it in the archive?
 
Zeqe said:
Hello, I have discovered that the problem has to do with a mismatch between menus.txt (from Vanilla VC) and the Dark Age mod. Specifically something in menu_start_game_0 seems to be off, and in a few other places it is likely to cause the same issues. Can we get the mod author to upload his menus.txt or include it in the archive?
Dark Age does not change menus.txt

I downloaded from the Nexus and it works fine with VC 2.032

Nexus archives created by 7-zip archiver.. you need 7-Zip to unpack it
 
I tried a lot of different things, but I finally found out why Tarassos and I are likely having this problem. I was wrong about menus.txt, but when I edited the

"set_version" in module config file from 1168 to 1172 it now works completely fine

It's at the very top of the file, and I can't open it now because I am at work, but changing that one line to reflect that my Warband version was 1.172 fixed the problem and everything seems to be working fine now.
 
Zeqe said:
I tried a lot of different things, but I finally found out why Tarassos and I are likely having this problem. I was wrong about menus.txt, but when I edited the

"set_version" in module config file from 1168 to 1172 it now works completely fine

It's at the very top of the file, and I can't open it now because I am at work, but changing that one line to reflect that my Warband version was 1.172 fixed the problem and everything seems to be working fine now.
Thanks a lot man it worked finally so simple :wink:
 
strange..
I have the same line and everything works
Code:
module_name = DarkAge_2_0
compatible_with_warband = 1
operation_set_version = 1168
 
ha3481 said:
I have the same line and everything works

VC has a engine check on some parts of the code, like in the "NEW GAME" button. If you are using a mismatched version (say VC 2.032 with engine 1.153), it won't let you continue.

 
kalarhan, thanks for the clarification

the question was about compatibility Dark Age 2.2 with the version 2.032
Zeqe said:
Is this not compatible with VC 2.032 and the latest warband?
уes, compatible
version 2.2 was created for VC 2.028. then I tested this version on VC 2.032 beta/release and it works fine, so there is this line
Code:
operation_set_version = 1168

so I don't understand why appeared this problem and how it was solved this way
Zeqe said:
I edited the "set_version" in module config file from 1168 to 1172 it now works completely fine


 
ha3481 said:
so I don't understand why appeared this problem and how it was solved this way

I explained this a few times, including some earlier posts in this thread, but if we need to go deeper and get our hands dirty with code, then lets do it  :grin:

user warning: tech talk below

from module_game_menus.py
Code:
game_menus = [
  ("start_game_0",menu_text_color(0xFF000000)|mnf_disable_all_keys,
    "Welcome to Viking Conquest.",
    "none",
    [
      (try_begin),
        (assign, reg0, 0),
        (get_operation_set_version, reg0),
        (ge, reg0, warband_version),
        (assign, "$campaign_type", camp_storyline),
        (assign, "$difficulty_type", camp_d1),
        
        #(start_presentation, "prsnt_choice_campaign"),
        (assign, reg60, 1),
        (start_presentation, "prsnt_vc_options"),
        #(call_script, "script_change_player_relation_with_faction" ,"fac_kingdom_4", 0),
      (else_try),
        (change_screen_quit),
      (try_end),
    ],
    [
    ]
  ),

this is the code called when you click the button "start a new game".

Code:
(get_operation_set_version, reg0),
this operation asks the engine which version the current module is made for. How does the game knows this? From module.ini you can add this line
Code:
operation_set_version = 1153

note that Native doesn't use this. This option was added later and is meant to protect DLC and mods from using the wrong engine version. Why? Well if you try using a mod meant for 1.168 with the engine from 1.153 (a example), you would get several errors/bugs/missing operation/etc. In short, it doesn't work.

So you can't create a mod with 1.170 and use it with 1.153? Not what I just said. If you only use code that existed on 1.153, then it would still be compatible (ish).

Now lets look at module_constants.py
Code:
warband_version = 1170  #matching what is in module.ini
vc_version = 2032
the comment above should be clear. Lets go back to the menu code. It says:

Code:
 (ge, reg0, warband_version),
or in other words: the [number from module.ini] must be equal or great than [the number from constants]. If not go back to the main menu.

Now lets look at recent VC version:
2.032: warband_version = 1170, operation_set_version = 1170 => 1170 >= 1170 => TRUE -> continue

Now what happens if a player uses the wrong combination, say code from 2.032 and module.ini from 2.028?
mix bag: warband_version = 1170, operation_set_version = 1168 => 1168 >= 1170 => FALSE -> back to main menu


TLDR: you need to remember to update your module.ini to match the current VC version module.ini
 
kalarhan said:
you need to remember to update your module.ini to match the current VC version module.ini
thanks for the advice  :cool:

kalarhan said:
Now what happens if a player uses the wrong combination, say code from 2.032 and module.ini from 2.028?
mix bag: warband_version = 1170, operation_set_version = 1168 => 1168 >= 1170 => FALSE -> back to main menu
Warband 1.172 / Viking Conquest 2.032
for example, I open module.ini and change line
Code:
operation_set_version = 1170
to
Code:
operation_set_version = 1168
and Viking Conquest 2.032 works fine..
 
ha3481 said:
works fine..

it doesn't. I don't know what you are doing exactly, but test this:

1) open module.ini and comment that line out (add a #). That means the variable is now set to zero (0)
2) save the file (otherwise it doesn't change anything)
3) start the game (you need to launch it again, module.ini is not reloaded from the game)
4) click the start new game button
5) it will take you back to main menu

then do the same test, this time on step 1 set a lower number like 1153

then do the same test, this time on step 1 set a number like 1169

then do the same test, this time on step 1 set a number like 9999
 
:grin:

replace your first entry on presentations.txt to display your versions numbers


Code:
prsnt_game_start 1 0 1
-60.000000  46 902 1 999999 2124 1 1000 2133 2 1224979098644774912 2032 2123 3 72057594037927937 1224979098644774912 1000 2119 3 72057594037927938 1224979098644774912 1000 4 0 31 2 72057594037927938 0 2320 2 1 1585267068834415762 5 0 2147483678 2 72057594037927938 10 2320 2 1 1585267068834415763 5 0 2147483678 2 72057594037927938 100 4 0 2119 3 1224979098644774913 72057594037927938 10 31 2 1224979098644774913 0 2108 2 72057594037927938 10 3 0 2320 2 1 1585267068834415764 5 0 4 0 2119 3 1224979098644774913 72057594037927938 100 31 2 1224979098644774913 0 2108 2 72057594037927938 100 5 0 2119 3 1224979098644774913 72057594037927938 10 31 2 1224979098644774913 0 2108 2 72057594037927938 10 3 0 2320 2 1 1585267068834415765 3 0 2320 2 2 216172782113787568 2320 2 1 1585267068834415766 55 1 72057594037927946 2133 2 72057594037927947 1170 2320 2 1 1585267068834415767 1106 1 1 910 3 144115188075856621 1585267068834414695 6160 921 2 144115188075856621 0 1107 1 0 1106 1 1 1107 1 1 609 1 1 729 2 1 800 730 2 1 50 926 2 144115188075856621 1

it will display instead of 2.032 the following: "2.023 . Eng: 0. Code: 1170", where "eng" comes from module.ini, and "code" from constants.py (or your game_menus.txt)
 
kalarhan said:
it will display instead of 2.032 the following: "2.023 . Eng: 0. Code: 1170", where "eng" comes from module.ini, and "code" from constants.py (or your game_menus.txt)
Code:
module_name = Viking_Conquest2032
compatible_with_warband = 1
operation_set_version = 1170
Code:
presentationsfile version 1
 102
prsnt_game_start 1 0 1
-60.000000  46 902 1 999999 2124 1 1000 2133 2 1224979098644774912 2032 2123 3 72057594037927937 1224979098644774912 1000 2119 3 72057594037927938 1224979098644774912 1000 4 0 31 2 72057594037927938 0 2320 2 1 1585267068834415762 5 0 2147483678 2 72057594037927938 10 2320 2 1 1585267068834415763 5 0 2147483678 2 72057594037927938 100 4 0 2119 3 1224979098644774913 72057594037927938 10 31 2 1224979098644774913 0 2108 2 72057594037927938 10 3 0 2320 2 1 1585267068834415764 5 0 4 0 2119 3 1224979098644774913 72057594037927938 100 31 2 1224979098644774913 0 2108 2 72057594037927938 100 5 0 2119 3 1224979098644774913 72057594037927938 10 31 2 1224979098644774913 0 2108 2 72057594037927938 10 3 0 2320 2 1 1585267068834415765 3 0 2320 2 2 216172782113787568 2320 2 1 1585267068834415766 55 1 72057594037927946 2133 2 72057594037927947 1170 2320 2 1 1585267068834415767 1106 1 1 910 3 144115188075856621 1585267068834414695 6160 921 2 144115188075856621 0 1107 1 0 1106 1 1 1107 1 1 609 1 1 729 2 1 800 730 2 1 50 926 2 144115188075856621 1 


prsnt_game_credits 1 121 2
...

at the beginning of the previous video I did the verification of Warband in Steam by "Verify integrity of game files.."
 
I think I understand your confusion, ha3481.

When you update VC and Warband through steam the numbers will automatically be right due to how that process works:

Warband gets updated to 1.172h, then viking conquest gets updated to 2.032

The set_version in the module.ini will be right (i.e., it will be 1170 or 1172 to match Warband)

The issue we had with your latest mod archive is that there was a mismatch in the module.ini in the archive. (It was 1168, but needed to be HIGHER than 1170 to match 2.032's needs)

From my understanding, this is because 2.032 is coded to check and make sure that the set_version is higher than 1170, the warband version it was designed for.

Simple fix for the archive is just to reupload a module.ini with 1170 or higher in the set_version.

EDIT: Thanks for all your hard work, ha3481. I really enjoy the visual mods and didn't like having to play blood eagle to get them, due to personal taste preferences BE always felt too easy for me.
 
thank  :smile:
Zeqe said:
blood eagle
originally Blood Eagle - is a Viking Conquest 2.02x that includes several submodes.. Sword and Shield submod as gameplay overhaul and Dark Age submod (v1.3) as graphic overhaul combined in one module which develops and improves by Kale3 and HooTmAn.. now the Blood Eagle is developing in parallel and independently from the Dark Age..
the main condition for me is the compatibility of savegames, so I try not to change the gameplay and code
 
I can't download this from Nexus  :sad:

I'm logged in there, but when I click either of the download links, I get a popup saying "An error occured" with no other explanation.


EDIT - I've just checked another mod on Nexus and I get the same error.  Probably something at their end.
 
Question: So many trees in villages and towns. Any fix?
Answer: I have no time and good PC now to edit scenes.. Now I'm using my old Asus EEE PC 1201n (latest updates since version 2.0 made on this PC).. netbook is very problematic to edit the scenes.  :mrgreen:
Maybe later..
 
Back
Top Bottom