Originally Posted by
Trig
As I said, you've no idea what you're talking about.
The "optimisation" you mention didn't reduce the size or quality of any texture. We instead remapped dozens of models to same textures, to reduce texture load and stress on the computer graphics and memory and make things run smoother. We also fixed a bunch of glitches in them, added new haversacks, canteens, backpacks and other historical details and added a full set of historically accurate rifles, smoothbores, revolvers and swords to the mod. All the textile colours have been updated to match the historic ones as closely as possible. If you prefer some other look, that is your right, but we weren't guided by what you might or might not like, but by historical accuracy and 3.6 uniforms are historically accurate, texture- and model-wise, while older ones are not. But be that as it may, the optimisation of units reduced the incidence of crashes, not increased them.
On the other hand, if you look at older posts in this forum, users kept asking for more and more historic regiments. Never satisfied with the current amount, someone always wanted another "legendary" regiment (and often just the fact that it was his reenactment one was what merited its "legendary" status). So we added some 200 different units into the game, which seems to mess with the game somewhat, as it involves way more loading than vanilla does.
There are also some glitches in the maps that cause crashes, as non-vanilla objects were introduced, which we have enitrely inherited from old versions and haven't edited in the slightest ourselves. The startpos files, which determine the starting campaign values were also inherited from before, not edited by us, and in spite of asking possible startpos modders for years to perhaps clean them up and fix the broken bits, noone did.
So, your smartass hostile bashing of the last team that wasted a couple of years of "unprofessional" work (meaning a couple of hours of work almost every day for 2-3 years, for free) trying to update a faulty product we inherited, because every previous team eventually lost the will to work on it, as E:TW is a nightmare to mod, is also not helping the guy with his problem, while at the same time it is rude and disrespectful to people involved in the making of it.
I don't know why his game is crashing. My game isn't crashing. And I'm using exactly the same files you can all download here. I completely uninstalled Empire, then re-installed it, then ran the ACW auto-installer. The game launches fine, the campaign launches fine, battles don't crash and if they ever do, I just reduce graphics a bit, then they don't anymore on the second attempt. The campaign will crash at some point, but it already crashed at some point when I first started working on this mod, just before 3.5 was released. The guy who worked on 3.5, left it in an unfinished state and disappeared without a trace, probably he died. After him, noone was able to locate the reason for the crashes. Your speculations are just that, speculations.
We told people who kept pressuring us to release the next version that we can either release a somewhat buggy version or not release at all, since there was no sign of any "professionals" showing up to fix this for free (and you sure as hell weren't gonna pay for a professional to work on this), and the majority consensus was that we should release in current state and maybe eventually someone might appear and work on it further.
So, if you don't know what you're talking about, as you weren't around when stuff was being done, don't couple your ignorance with arrogance coming here telling people to "stay away from the mod until professionals take over".