Beta 2.2 is Available
Beta 2.2.0
Don't let the changelog fool you, this is a
major change from the last release. Nearly 20% of
the code has been ripped out and replaced with the brand new
manager core!
I recommend creating a custom backup session before using
this release
Changelog
r105
- removed debug forms from project and svn
r104
- finished replacing old core with new core
- temporarily removed Sanitize XML tool. It will return next version
- reworked staging and pre-staging to be more efficient and have less code duplication
- completely removed old DAModDetails and DAXMLParser
r103
- main install and uninstall routines converted to new code
- added new dialog for comparing old and new mod when trying to install a mod with the same UID as an existing mod. This should make it clearer if you are upgrading or not.
r102
- increased size of webform to display mod details. This webform now displays ALL mod details. The mod title and URL have been moved into this form
- Improved styling of webform
- Added damodder.css stylesheet that controls styling for the webform
- Tied filtering into new core, and optimized filter routines for a significant improvementin filtering speed
r101
- optimized the DrawItem function for the installed mods list box to speed up draw time
- temporarily disabled localization while integrating new core. Localization will be available again once integration is completed
- started to integrate the new mod manager core
r100
- new files for new core added to svn
r99
- initial version of new DAMManager core written and tested
r98
- removed temporary builder tab
r97
- added DASettings class to manage saving and loading application settings
- Application settings for Language and Default Backup Settings are now saved, and loaded on program start
r96
- minor changes to sanitize xml tool
r95
- updated log version
Known Issues
- Localization has been disabled for this release. It was easier to integrate the new core without it. However, the new core was built with localization in mind, rather than hacked in like before, so re-enabling it will be very easy and will be done for the next version.
- Readme/Changelog functions are not currently available and will return next version
- The sanitize xml tool is being reworked and is not currently available
- Probably something else i'm forgetting...
This is a major re-write and as such there is bound to be some bugs that I missed. I'll be amazed I didn't mess something up. I did do some basic quick tests, installing one mod of each type supported, and uninstalling them, but thats about it. Please give it a good run through and any bugs you find, open a ticket on the Lighthouse and i'll be spending tomorrow fixing everything found.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by Alex "Alex... on 14 Dec, 2009 07:15 AM
Downloaded, i will run my installation tests with this during the day, thank you for the update =)
Btw. is there now a check for NET 3.5 when starting it in place? not sure if you allready included that.
2 Posted by Alex "Alex... on 14 Dec, 2009 11:32 AM
Just tried it out now the first time, still on testing, but i have to say i am impressed with the new css style, looks WAY better than before =)
And another question, this "Save Defaults" Button that is new, whats its purpouse and what gets saved where?
should it be working? i filed a error to the bugtracker because its not working for me.
3 Posted by Mark on 14 Dec, 2009 01:27 PM
First off, thanks for this. It are the bestest (when it is working =P).
Deleted old files (2.1)
Copied new files to the same directory as before.
Tried to install several different mods at random in groups, and singly after reverting addins.xml to a backup.
Every time the xml file has all the line breaks deleted and as a result none of the mods work.
My Setup:
Win 7 X64
Dragon Age 1.02
DAModder in same folder and different folder than addon repository
I have 3rd party and DLC addons installed.
Notepad ++ used to edit xml
here is the xml for your viewing pleasure.
Support Staff 4 Posted by jwvanderbeck on 14 Dec, 2009 02:10 PM
Heh well I knew there would be some bugs to work out but it looks like there is a lot. time to get crackin :p
Support Staff 5 Posted by jwvanderbeck on 14 Dec, 2009 03:46 PM
Rather silly that DA won't read the file without line breaks, but whatever. I opened a ticket for the whitespace. Ticket 107
Support Staff 6 Posted by jwvanderbeck on 14 Dec, 2009 04:37 PM
Due to two bugs in 2.2, I am recommending that you do not use 2.2 for installing any mods for actual use, as the resulting AddIns file will be both un-useable and all mixed up with standard and core mods.
This issue will be (in fact already has been) corrected in 2.2.1 and you will want to restore your Game Settings from the backup you made before using 2.2
Sorry about that, but I did warn you it was a major re-write :)
7 Posted by Alex "Alex... on 14 Dec, 2009 05:18 PM
no problem for me, i have allways a seperate copy of my "\BioWare\Dragon Age" directory just for testing =)
could you really solve everything i reported so fast?
Support Staff 8 Posted by jwvanderbeck on 14 Dec, 2009 05:24 PM
Generally tickets are closed by the SVN commit that fixes them, so yeah if a ticket is closed, its fixed :)
Support Staff 9 Posted by jwvanderbeck on 14 Dec, 2009 06:27 PM
Beta 2.2.1
Changelog
r113
r112
r111
r110
r109
r108
r107
r106
Known Issues
This is just a bug fix release, so the disabled features from 2.2 are still disabled.
Please restore to a Game Settings backup from before B2.2 before using this release or you will still experience some bugs that have been fixed.
This release fixes most of the issues in 2.2 but I still recommend creating a custom backup session of at least Game Settings before using this release
10 Posted by Alex "Alex... on 14 Dec, 2009 06:30 PM
downloaded, will be testing, reporting back as i discover bugs or finish testing
Support Staff 11 Posted by jwvanderbeck on 14 Dec, 2009 06:44 PM
I'm sure you will fill my box right back up with more bugs lol!
I really appreciate all the work you put into testing. It makes it so much easier for me.
12 Posted by Alex "Alex... on 14 Dec, 2009 08:02 PM
Thank you John =)
Allready have a new Bug, or allmost new =(
Support Staff 13 Posted by jwvanderbeck on 14 Dec, 2009 08:59 PM
Ok I hope I got it this time. Tracked down an issue with a darn typo when processing the "bioware" attribute. Gah!
Support Staff 14 Posted by jwvanderbeck on 14 Dec, 2009 09:04 PM
Ok let's try this again.
Beta 2.2.2
r114
15 Posted by Alex "Alex... on 14 Dec, 2009 09:05 PM
Will you release a beta 2.2.2 with a fix for this?
I have a hard time testing with this bug that puts all into one category, but the good thing is that most other things seem to work that i tried.
16 Posted by Alex "Alex... on 14 Dec, 2009 09:06 PM
lol posted the same time ^^
downloaded and i will report back =)
Support Staff 17 Posted by jwvanderbeck on 14 Dec, 2009 09:06 PM
I appreciate your patience. I really want to get this new core locked down so I can move forward safely.
18 Posted by Alex "Alex... on 14 Dec, 2009 09:40 PM
well i can be dedicated if i feel like it ;)
is there a way i can set a issue unresolved in the bugtracker?
I made several notes to issues you have marked as resolved that i think you may have overlooked and that would require an answer from you, or where i would hope to get a answer from you (or really make it unresolved because the bug is still there)
Support Staff 19 Posted by jwvanderbeck on 14 Dec, 2009 09:47 PM
If it doesn't let you change the state, which I guess makes sense, usually just leaving a comment is enough because it still shows up in the history as being changed, and I get an email.
But consistency is important so here is what we can do. If you find a ticket that you really feel should be re-opened -- meaning it is exhibiting the exact same issue, then tag is as "reopen".
If the issue is similar but not quite the same, just make a new ticket.
20 Posted by Alex "Alex... on 14 Dec, 2009 09:52 PM
okay i see, i will do as you explained it, thank you
Support Staff 21 Posted by jwvanderbeck on 14 Dec, 2009 10:36 PM
Ok things look a lot better now. Only a couple open tickets caused by the big change, so i'm going to go take a break and then start in on restoring functionality with the new core. localization, readmes, etc.
Support Staff 22 Posted by jwvanderbeck on 15 Dec, 2009 04:28 AM
Beta 2.2.3
Mostly minor changes, and localization is back.
r115
r116
r118
Support Staff 23 Posted by jwvanderbeck on 15 Dec, 2009 04:55 AM
So how is the 2.2 branch now? I need to be sure the new core is solid and we've shaken the bugs out. Anyone else experiencing any issues with 2.2.3? I know there are still a few tickets open, but anything not reported?
24 Posted by Alex "Alex... on 15 Dec, 2009 09:07 AM
I havent jet tested Beta 2.2.3, will do that later today if i have a break (hopefully)
25 Posted by Alex "Alex... on 15 Dec, 2009 04:03 PM
i am done with testing Beta 2.2.3, all issues i found where reported.
Support Staff 26 Posted by jwvanderbeck on 16 Dec, 2009 10:52 PM
Beta 2.2.4
Highlights
This version introduces a brand new install dialog & install process that allows for less popup dialogs, and a more flexible install that will allow things like conflict checking and sub-package installations. The old process was just getting out of hand.
The install process now creates a "File Manifest", which is a list of all files installed for a mod, saved in FileList.xml along with the mod. This file manifest allows DAModder to ensure that all files are removed when a mod is uninstalled, even if the mod is packaged in a way that places files in unexpected locations.
Changelog
r120
r121
r122
r123
r124
r125
r127
r128
r130
Known Issues
Support Staff 27 Posted by jwvanderbeck on 16 Dec, 2009 11:38 PM
Quick update to 2.2.4 to fix the folder install. I'm not updating the version number so if you already downloaded 2.2.4, please download it again from this attachment.
28 Posted by maddbomber83 on 17 Dec, 2009 06:02 PM
I am using DAModder_Beta_2_2_4.zip from post #28 in this thread. I am trying to install an update to the Advanced Tactics mod (going from 2.3 to 2.4). This mod can be found at (http://social.bioware.com/project/861/).
I have encountered a bug. I updated several mods using zip files and one mod using a dazip file (they were all updates to existing mods). When I logged into the game none of my dazip style mods (including the bioware ones) worked.
I restored the AddIns.xml from a backup and everything was fine again. I then tried installing that dazip file using DAModder and once again, all my DAZip based mods were broken.
Restoring to the backup again, I tried installing that DAZip mod using Bioware's Update program. Everything worked fine.
I'm not sure if this is a bug with DAModder or maybe the author of the mod did not update it correctly; but Bioware's Updater is able to get it installed without breaking the other mods (and it works properly in game) where DAModder cannot.
I've attached the AddIns.xml file from the Bioware update and from the DAModder update. I've also included the DAModder.xml file, although that was the same for both updates.
Support Staff 29 Posted by jwvanderbeck on 17 Dec, 2009 06:05 PM
Thanks for the report. There was an issue with earlier versions of 2.2 causing this issue, so its possible something is still wrong.
If you can, try installing it with DAModder 2.1and it should work fine.
30 Posted by maddbomber83 on 17 Dec, 2009 06:06 PM
I posted in #29 about a problem. I forgot to also include the backup .xml file that has the Advanced Tactics 2.3 in it. This would be the .xml file that I started with, and then installed the dazip file on. The Bioware file is what the Bioware update program changed it to. The DAModder file is what DAModder changed it to. The Bioware one works where the DAModder one does not.
I also forgot to once again thank you for this incredible mod manager.