928 replies to this topic

[Fouinto]

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

@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

•  BWS-Selection.zip   4.74K   165 downloads

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

[dabus]

@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.

[Fouinto]

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

Thank you

[dabus]

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.

[dabus]

@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...)

[dabus]

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.

[Hellcommander]

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

Attached Files

•  BiG World Install Debug.7z   493.76K   269 downloads

[dabus]

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.

[Miloch]

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).

[Wisp]

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.

[Hellcommander]

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

[Hellcommander]

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