Jump to content


Photo

BiG World Setup Beta-Testing


  • Please log in to reply
928 replies to this topic

#301 Fouinto

Fouinto
  • Member
  • 458 posts

Posted 09 November 2010 - 02:05 PM

Seems like I was too absorbed to fix the selection so I had forgotten to remove my test-entry that stops the BWS after the mentioned position.
I've also found a few errors while running an installation.

Please fetch the re-uploaded file.

I get an 404 error on your site at the moment, so I will try again tomorrow.Your site is up again :Bow:

@Fouinto: I cannot reproduce the export > import error.
Could you upload the compressed export-file and tell me your language-selection so I can try to do that?

I uploaded the file (zipped 'cause I can't upload INI file) and my language-selection is FR EN

Thank you

Attached Files


Edited by Fouinto, 09 November 2010 - 02:18 PM.


#302 dabus

dabus
  • Member
  • 1982 posts

Posted 09 November 2010 - 02:28 PM

@max: Huh?

Please check that your BiG World Setup\Config\Setup.ini has a section that looks like this:

[Order]
Au3Detect=1
Au3BuildGui=1
Au3Select=1
Au3GetVal=1
Au3CleanInst=1
Au3PrepInst=1
Au3Net=1
Au3NetTest=1
Au3NetFix=1
Au3Extract=1
Au3ExFix=1
Au3ExTest=1
Au3RunFix=1
Au3Install=1
Au3Exit=1

The behavior described above would happen if Au3Exit=1 is placed after Au3GetVal=1, which was the case in the old build.

Edited by dabus, 09 November 2010 - 02:28 PM.

THINK! - It's not illegal.

#303 Fouinto

Fouinto
  • Member
  • 458 posts

Posted 09 November 2010 - 02:38 PM

I can tell you it works now :cheers: currently extracting on my computer (I had already downloaded most of the mods :D ).

Thank you :Bow:

#304 -max-

-max-
  • Guest

Posted 09 November 2010 - 02:48 PM

Ok, what I did was click on the link a few posts above and just deleted the BWS 9-20101108 from yesterday. Now I modified the .ini file as you described. This is what I have, and then made changes in parentheses.


[Order]
Au3Detect=1
Au3BuildGui=1
Au3Select=0 (changed to 1)
Au3GetVal=1
Au3Exit=1 (just deleted this one)
Au3CleanInst=1
Au3PrepInst=1
Au3Net=1
Au3NetTest=1
Au3NetFix=1
Au3Extract=1
Au3ExFix=1
Au3ExTest=1
Au3RunFix=1
Au3Install=1
Au3Exit=1


I'll try it out again.

#305 -max-

-max-
  • Guest

Posted 09 November 2010 - 03:03 PM

Aha it works! I'll try to report back after the install to see if there were errors. Thanks again Dabus, you are a genius. :cheers:

#306 -max-

-max-
  • Guest

Posted 09 November 2010 - 08:42 PM

Oh boy, this is interesting. The bws downloaded the mods, unpacked the mods and started installation ok. I only had to hit ok for 4 or 5 ncis mods. 5 minutes later the install was finished ( a tactics install ).

// Log of Currently Installed WeiDU Mods
// The top of the file is the 'oldest' mod
// ~TP2_File~ #language_number #component_number // [Subcomponent Name -> ] Component Name [ : Version]
~SETUP-WEIDU.TP2~ #0 #0 // WeiDU-Windows-224.zip
~SETUP-BWS.TP2~ #0 #0 // bws_program.7z
~SETUP-BWS-URL.TP2~ #0 #0 // bws_link.7z
~SETUP-BWFIXPACK.TP2~ #0 #0 // BiG World Fixpack v9.5.1.7z
~SETUP-BWTRIMPACK.TP2~ #0 #0 // BiG World Borkpack v9.5.7z
~SETUP-BWINSTALLPACK.TP2~ #0 #0 // BiG World Installpack v9.5.1.7z
// Recently Uninstalled: ~SETUP-BWS_FINAL.TP2~ #0 #0 // Make quick-logged WeiDU-entries visible


Thats it, what went wrong? I tried to open up the log but bws says there is no error log.

#307 -max-

-max-
  • Guest

Posted 09 November 2010 - 11:19 PM

I watched the install for a while, after the cre checker ran the bws just ran through the mods saying ##the condition to install the mod at this time has not been reached# (or something like that)on each mod. If it matters I checked the box install in batches, will try without that checked.

#308 dabus

dabus
  • Member
  • 1982 posts

Posted 10 November 2010 - 12:14 AM

I guess the the BiG World Setup\Includes\09_Install.au3 also is an old version.

Line 244 onward looks like this:
$Setup[0]=StringMid($Array[$a], 1, 3); LineType
$Setup[2]=StringStripWS(StringMid($Array[$a], 5, 25), 3); SetupName
$Setup[3]=StringStripWS(StringMid($Array[$a], 30, 9), 3); CompNumber
$Setup[6]=StringStripWS(StringMid($Array[$a], 49, 49), 3); $CompReq

The old is a bit different:
$Setup[0]=StringMid($Array[$a], 1, 3); LineType
$Setup[2]=StringStripWS(StringMid($Array[$a], 5, 25), 3); SetupName
$Setup[3]=StringStripWS(StringMid($Array[$a], 30, 9), 3); CompNumber
$Setup[4]=StringMid($Array[$a], 41, 4); CompType
$Setup[6]=StringStripWS(StringMid($Array[$a], 45, 49), 3); $CompReq

I bet you have the old version since you had the issue with the setup.ini and I had exactly the same experience before fixing the error and releasing fixed package. (Notice that the components requirements are read from a different position, which is the cause for this behavior.)

You can replace or edit the file, replace the [Order]-section in your BiG World Setup\Config\Setup.ini so it looks like this:
[Order]
Au3Detect=1
Au3BuildGui=1
Au3Select=0
Au3GetVal=1
Au3CleanInst=0
Au3PrepInst=0
Au3Net=0
Au3NetTest=0
Au3NetFix=0
Au3Extract=0
Au3ExFix=0
Au3ExTest=0
Au3RunFix=0
Au3Install=1
Au3Exit=1

Also make sure you've got a Start=1 underneath the [Options]-section and run the BWS to resume the install. This will start the install at the beginning (installing weidu-setups) again.

Edited by dabus, 10 November 2010 - 12:17 AM.

THINK! - It's not illegal.

#309 -max-

-max-
  • Guest

Posted 10 November 2010 - 08:36 PM

Still having a problem. I have done the 2 things you have posted above with install .au3 and the setup .ini. But now it freezes here-(the last line is where it stopped) On the top it says running batch command and had to exit program.

SUCCESSFULLY INSTALLED BiG World Installpack v9.5.1.7z

D:\Program Files\Black Isle\BGII - SoA>cd /D "D:\Program Files\Black Isle\BGII - SoA"

D:\Program Files\Black Isle\BGII - SoA>BiG World Install
IF EXIST ".\override\override" move ".\override\override\*.*" ".\override"
IF EXIST ".\override\override" rmdir /s /q ".\override\override"
IF EXIST ".\BiG World Installpack\BiG World Smoothpack" move ".\BiG World Installpack\BiG World Smoothpack\_modify\*.*" "."
IF EXIST "Big World Fixpack\_aD&L" ren ".\BiG World Fixpack\_aD&L" "aD&L"
IF EXIST "Big World Fixpack\BW_Herbs\_optional\Improved Animations\_copy" move ".\BiG World Fixpack\BW_Herbs\_optional\Improved Animations\_copy" ".\BiG World Fixpack\BW_Herbs\_copy"




By the way I deleted the old BWSetup folder and bws 9-20101108.exe. And redownloaded from the link one page back, as well as the link on the first page of topic, and I keep getting the older version. I had to make the changes you mentioned both times.

#310 -i30817-

-i30817-
  • Guest

Posted 11 November 2010 - 12:51 PM

In Morrowind modding people use a specialized expert system - mlox - maintained by a project apart and contributed to by the mod authors themselves to keep mods from clashing.

I think a separation like that (a different project for the rules) could be helpful here too, so the evolution of both could be made appart (and the code isn't a spaghetti mess).

#311 dabus

dabus
  • Member
  • 1982 posts

Posted 11 November 2010 - 01:27 PM

@max: I can download the correct file via ftp and http.
So maybe it's some kind of caching-error with your browser, proxy or whatsoever.

@i30817: Uh, I don't know exactly what you're saying.
I understand that you suggest to use a system to sort the mods install-order.
The mods authors should contribute their opinions. Right?

And what's done with that?

I don't know how that works exactly but what I do now is basically creating a copy of the BiG World Install.bats order, which is maintained by Leonardo Watson. So the BWS might probably be the wrong place to use that system... (I don't really know about the order, either...)
THINK! - It's not illegal.

#312 -i30817-

-i30817-
  • Guest

Posted 11 November 2010 - 02:02 PM

Well i was thinking about the ways that your tool seems to indicate the conflicts in the mods : the green, orange and red colors. You meant that is not dynamic?

After choosing and "installing" (either manually or with wrye mash, installing is a euphemism for unzipping in the mod dir), you run mlox to see the mods that are outdated - relative to the current version in the rule database - those that have conflicts, those that can be reordered to get conflict less installs, and it does that for you. The order is not fixed (how could it be), but a kind of "total order" if you're into computer science. If it finds a unresolvable conflict, or require other mods et, it warns you (the warning is a string the maker of the rule put in ofcourse).

If you could find a way to adapt and extract info of a specialized tool like that, say, passing the list of selected mods in, report the warnings out (maybe even with the color coding on the offending mods, if it is structured enough), and possibly free Leonardo Watson, from dealing with a canonical list, that people might add or remove things of (and fuck it up naturally).

#313 -i30817-

-i30817-
  • Guest

Posted 11 November 2010 - 02:07 PM

And it's not only mod authors reporting bugs naturally. I myself reported 6 a while ago, and now they are in the database, so that anyone that use mlox doesn't have to wonder anymore. It does need quite a bit of expertize to make the rules, but certainly not more than the abomination that iescript is.

#314 dabus

dabus
  • Member
  • 1982 posts

Posted 11 November 2010 - 11:40 PM

There already is a basic rule for installing mods, so I don't know if that mlox-system would fit into that.

The colors of the items are based on the in-game-experience (is it worth playing or will it disappoint you or ruin your game literally by causing crashes and such). There is no database or whatsoever to rely on that information nor install-order either.

So there was no need for the BWS to fetch that data from the net/some voting-system. It fetches updates from some files which I update from time to time, updates ini-files but that's it.

The BiG World Setup\Config\Mod.ini contains information about the mods and the basic "rating", which are fixed, recommended, standard, tactical, expert. It's not really a rating but as said, there is no site that has that information put up in some kind of database. The Setup.ini, contains the connections between the mods, like a conflicts with b, b needs c, a needs c only if installed with b and so on.
THINK! - It's not illegal.

#315 Hellcommander

Hellcommander
  • Member
  • 34 posts

Posted 18 November 2010 - 09:31 AM

Ive have encountered an error in setup Ive not got before please see look at attached file. :doh:

Attached Files



#316 dabus

dabus
  • Member
  • 1982 posts

Posted 18 November 2010 - 10:26 AM

I've heard that some guys had no kit-problems with 2.23 but with 2.24. So for the fun of it you could try to use WeiDU 2.23...

The line you'd want to try would be
Setup-Ebg2.exe --noautoupdate --language 0 --skip-at-view --quick-log --force-install-list 0 1 2 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 --logapp

By the way, here's the error:

ERROR: Failure("resource [KITLIST.2DA.IDS] not found for 'get_ids_map'")


Edited by dabus, 18 November 2010 - 10:28 AM.

THINK! - It's not illegal.

#317 Miloch

Miloch

    Barbarian

  • Modder
  • 6579 posts

Posted 18 November 2010 - 11:37 AM

By the way, here's the error:

ERROR: Failure("resource [KITLIST.2DA.IDS] not found for 'get_ids_map'")

Not a valid file - it should be either kitlist.2da or kits.ids in the tp2 (offhand I don't know without looking at it).

Infinity Engine Contributions
Aurora * BG1 NPC * BG1 Fixpack * Haiass * Infinity Animations * Level 1 NPCs * P5Tweaks
PnP Free Action * Thrown Hammers * Unique Containers * BG:EE * BGII:EE * IWD:EE
================================================================
Player & Modder Resources
BAM Batcher * Creature Lister * Creature Checker * Creature Fixer * Tutu/BGT Area Map & List * Tutu Mod List
================================================================
"Infinity turns out to be the opposite of what people say it is. It is not 'that which has nothing beyond itself' that is infinite, but 'that which always has something beyond itself'." -Aristotle


#318 Wisp

Wisp
  • Modder
  • 1353 posts

Posted 18 November 2010 - 01:23 PM

I've heard that some guys had no kit-problems with 2.23 but with 2.24. So for the fun of it you could try to use WeiDU 2.23...

It's actually 223.00 and 224.00, unless it's a beta version, which are e.g. 223.01 or 223.03.

#319 Hellcommander

Hellcommander
  • Member
  • 34 posts

Posted 18 November 2010 - 10:46 PM

Thanks I look at the code and try to fix it. :)

#320 Hellcommander

Hellcommander
  • Member
  • 34 posts

Posted 18 November 2010 - 10:59 PM

I just skip the 2 kits and install them later if I can figure out how to fix it. :wacko: