Lor Dric said:
Looking for a dedicated person to be my second, need someone good at organizing, play testing and moderating
Looking for dedicated play testers
Looking for a coder that is better than me (which isn't saying much I suck at coding)
Sorry about that, I haven't gotten anything done here. Have you given thought as to what this mod would be like without WSE?
I should do something useful here, to repay your kindness.
Maybe I'll see how many features get gimped without WSE, as a technical review.
Also I'd like to review the source with WRECK.
And I can update Rigale
Those 3 projects should keep me busy beyond February, so its right that you get at least 1 more coder to make the progress you deserve. Darned impressive resources/items/troops/companions list. You make me look idle so far as productivity...
- GS
-----
further Edit Monday morning:
bah left source at home / mega removed
but using the morning to test if WSE 4.04 && Warband 1.166 can be made to work, else 1.153 d/ling now to "work" PC* (except its really from my home).
http://forums.taleworlds.com/index.php/topic,324890.0.html
It IS interesting its just WSE makes it more difficult to install. I'd like to see later if WSE can be comfortably removed from the source, or if that nerfs too many features. My (brief) understanding is many multiplayer features needed WSE and some things like burning arrows, but generally WSE was not needed for most of it. I'll be most curious to see... as no WSE makes it eligible for Steam if can update to 1.166 Warband support.
Got WSE 3.2.0 & Warband 1.153 running this per Pizzaraider's guide, easy to do thanks.
Trying in separate folder 1166 & WSE 4
Installed Warband 1166 but editing WSE to auto-launch Warband kept trying to spawn warband for 1.153 and getting an error.
Ahh a little investigation shows I need to edit the path stored by Warband in Windows registry with Regedit and search for Warband.
A little later I ended up uninstalling 1.153 via Control Panel: programs and applications: Mount & Blade Warband (uninstall)
then reinstalling 1.166 so that the path to mb_warband.exe is clear of all but 1.166 path info
Now WSE 4.0.4 finds Warband correctly and loads; AVG then claims a "threat" unspecified, which is the editing of program code as data, and in this case entirely normal not a "virus". Virus programs also edit code and one of Win 8 defaults is to block this by
default selecting "turn on DEP Data Execution Prevention for all programs and services except those I select"
you'd have to set this to "Turn on DEP for essential Windows programs and services only" OR make an exception for WSE
My 1.158 launcher at my C: drive SSD still exists/runs because I link to it directly from a desktop icon.
It's always good to shave 20-30 seconds off Perisno loads, as it has many textures. I'd do the same for Empires except
I'm not at all a fan of the downgrade_called_1.166 so will use it "sparingly". Don't change what isn't broken, please, Taleworlds...
Instead I ran Warband 1.166 directly (there is a folder WSE v4.0.4 placed alongside "modules" folder with the wse_settings.ini having a path added like this:
;Path where WSE created files are stored (empty for default)
storage_path = F:\Mount&Blade Warband_1166\WSE v4.0.4\
Anyway when I launch Warband.exe directly (v 1.166) I actually am able to run Empires III What issues I see look like things outside WSE, and are more technical issues at the compiler level, fairly easily cleaned up if I have more time.
(3 weeks? 4?)
Lor Dric is super active so I suppose there will be new beta load and resources in a few hours.
I just wanted to say maybe its working with 1.166.