In that many here are using the Unified Installer, would it be possible if an update is made to an existing mod contained in it that it be noted in that update that it replaces the UI version or some such?
Recently, seeing newer versions past the UI when I downloaded it I tried updating various aircraft and the like (the UI not stating version of contained mod), the result being due to some conflict an entire re-install which if you've ever had to hunt for hidden registry files and the like is an experience to be missed.
In any case, simply updating the UI would not be the best plan....That meaning you'd have to download the entire thing again (though obviously future versions will).....Yet something that might tell us besides post dates if there has been an improvement/later version would be helpful.
K2
Billfish
The UI is still at version 1.0 which means no additions have been made to it.
Most of the mods released since the UI was implemented have self installers and state on the download page that they are UI compatible.
I have added updates to installed maps, cockpits, effects, etc without incident and am wondering just what messed up your install to the point of a complete reinstall?
I have found that the uninstall program in Control Panel/Add Remove programs section is very effective at removing 1946 from the Ubisoft directory, which must be accomplished before the INSTALL button on the DVD will work. You also need to empty out the 1946 folder of any mod stuff that the uninstaller leaves behind.
The only advice I can give is, when you get the game installed and add the 4.08 patch, let the self installer on the UI do its thing, run the game from the exe in the game folder before messing with version switchers and such and, once you have determined that the game will launch, copy it somewhere before you start adding other mods.
Then, install only those mods with self installers and state that they are UI compatible on their download page.
Once people, even many that think they know what they are doing, start messing around, adding stuff manually and editing this and that file in the game, they often meet disaster.
Another thing that the AAA staff have stated over and over and over is that if you add stuff from other sites, problems can arise.
Well what caused the screw up I've no idea.....Past aircraft like spit1, 410, etc. I could no longer see the name of it in the plane selection screen during coops, and if I picked one could not arm it, it then locking me out of all others......However, once in the sim could still see them.
In any case not my point........My point being it would be nice if there was a more clear version system to know what mod updates/newer versions of a sub mod of the UI we had.....
IOW:
Spit 1 of UI might be ver. 2.1........Yet I have no idea.
Spit 1 stand alone patch is now 2.9 I believe
So perhaps it might be as simple as adding version numbers to the included mods listed on the UI lead post, or any of a hundred other ways to let us know a mod be it new or a newer version is "post" UI build.
K2
"Spit 1 of UI might be ver. 2.1........Yet I have no idea.
Spit 1 stand alone patch is now 2.9 I believe "
OK, If a new slot plane, for example, the Spit MKI, gets an update and you reinstall the SpitMkI from its download page, it updates the UI version of said plane.
Let me use another example, the great Slovenia Map by |ZUTI|, avaialble here: viewtopic.php?t=10515
This map has been through several updates and has sucessfully installed into my UI modded copy each time with no problems.
So, if one installs, using the self installer, an updated version of any mod into their UI modded install all should be well.
You said: "So perhaps it might be as simple as adding version numbers to the included mods listed on the UI lead post, or any of a hundred other ways to let us know a mod be it new or a newer version is "post" UI build."
This would be a cumbersome process for the AAA team and is actually unnessary due to the fact that any upgrade to anything listed on the UI lead post will update the UI and that most non beta mods or upgrades to released mods state that they are UI compatible.
I do not know if this discussion is of any help to you or will lead to any resolution of your problem but am willing to carry on if it helps anyone.
BF
come over to the BR site
i maintain an up to date list of post AAAui planes and things that have been tested and work
i know you know how to find us
cy there
jay
Billfish, As far as Team Pacific maps go, ( the Slot and the up coming New Guinea - New Britian map) we have a poilcy of putting the map version # in the lower left of the map. i'm starting to see other map makers begining to do this as well. zoom out your map and it should be there. Current Slot is 1.3
....well i have to agree here with BF , it would be so much easier for average users if mod versions had been listed.
viewtopic.php?t=7662&highlight=unified+installer
I've forwarded your request/suggestion to AAA team so hopefully next version will have them included ....
regards
Z
some data that is useful in sorting out these problems is knowing what % you game crashes (if it does). Also something simple that can be done to check if had a bad install is to just comment out the folder you think maybe bad.
example: your game is working. you down load the B-17F. now if your game doesn't work. you can go into your mods folder and find the folder called "B-17F" and just add a "-" in front of it changing it to "-B-17F". Now your game will not look at that mod when it is loading up. If your game now works again, that must have been the offending mod.
