1025 replies to this topic

[Leomar]

This is either here or to the BiG World Install.bat, as one of the edits the baldur.ini file;
Add these lines into the baldur.ini's after the [MOVIES] header:

...

So they can be skipped by pushing the Esc key without the need to see them the 1000 first times.

O.K. if we include this as default to the baldur.ini, then the movies will play as normal, but with the entries you can skip them with ESC. Is that correct? Or if the entries are made into the baldur.ini, the movies will not shown up only if you go to the movie section and choose which movie you want to see afterwards?

I've not tested this. Therefore I ask.

Greetings Leomar

Attached Files

•  scs I + II german.7z   41.79K   291 downloads

Edited by Leomar, 07 May 2010 - 05:44 AM.

[Lollorian]

If you add Jarno's entire codebox to the .ini, all the movies show up in the movie selection screen (whether you played the mod or not ) And when they play in the game, they can be skipped by pressing any key/clicking the mouse

(btw, since the Recommended/Minimal version of the BWP is supposed to be for firsttime gamers, I suggest this ini change to be made only if you chose a Standard install or greater Otherwise, we'd spoil stuff for guys like this ...)

[Jarno Mikkola]

Runaway Aerie from level 1 NPCs.
Fixed by the usual download from here(level1npcs.tp2).

[Miloch]

Might as well include this since it's confirmed as working, unless I beat you guys to a new release (but I dunno, you guys are pretty fast).

Also, take a look at your install routine and make sure you don't install Infinity Animations subcomponents if the main component fails, or it will cause crashes as noted here (this is a WeiDU bug that will be fixed in the next WeiDU and the next IA, but you still need a workaround, or you need to make sure IA's main component is installed somehow).

[Lollorian]

DSotSCv215 fixes
Fix: here (and Miloch's post too )

[Leomar]

Might as well include this since it's confirmed as working, unless I beat you guys to a new release (but I dunno, you guys are pretty fast).

For us it is easier to have the corrected files, which we can put into the BW Fixpack. Can you upload the corrected files? I think in this case it is a corrected TP2.

Also, take a look at your install routine and make sure you don't install Infinity Animations subcomponents if the main component fails, or it will cause crashes as noted here (this is a WeiDU bug that will be fixed in the next WeiDU and the next IA, but you still need a workaround, or you need to make sure IA's main component is installed somehow).

Hmmm, how we can do this with only our batch tools? I've no idea, at the moment. Any suggestions?
The batches can only check, if it is a mod or file present, but not, if a component is installed?!

Greetings Leomar

Edited by Leomar, 22 February 2010 - 04:53 AM.

[Jarno Mikkola]

Hmmm, how we can do this with only our batch tools? I've no idea, at the moment. Any suggestions?
The batches can only check, if it is a mod or file present, but not, if a component is installed?!

You should be able to check for the infinityanimations/backup/0/ -folder or it's content if the primary component was installed.

Edited by Jarno Mikkola, 22 February 2010 - 05:00 AM.

[dabus]

Live can be so easy with regular expressions.

@echo off
SET RETURN=0
set /P MOD=Set your setup here:
set /P COMP=Set your component here:
For /f "delims=" %%i in ('findstr /I "%MOD%.tp2~.*#.*#%COMP%" weidu.log') DO (SET RETURN=1)
If %RETURN%==1 (echo Found) else (echo Not Found)                            

Put this in a batch-file and have fun.
Cute, isn't it?
You should know what to put for IA.

At least that's one method I use in my BWS (beta) and weidu won't lie to you unless you edit the file manually.

Edit:

Geez. Tried to ask for several components in one go.

@echo off
SET RETURN=0
set /P MOD=Set your setup here:
set /P COMP=Set your component(s) here:
For /d %%c in (%COMP%) DO (
	SET RETURN=0
	For /f "delims=" %%t in ('findstr /I "%MOD%.tp2~.*#.*#%%c" weidu.log') DO (
		echo %%c was really found, but it RETURN is not set. Why?
		SET RETURN=1
	)
	If %RETURN%==1 (echo %%c was found) else (echo %%c was not found)
)

I would expect that RETURN is set, but it's not. WTF?

Edited by dabus, 22 February 2010 - 07:20 AM.

[Miloch]

Might as well include this since it's confirmed as working, unless I beat you guys to a new release (but I dunno, you guys are pretty fast).

For us it is easier to have the corrected files, which we can put into the BW Fixpack. Can you upload the corrected files? I think in this case it is a corrected TP2.

It is a patch, not a corrected tp2 (the affected components aren't in the main tp2 anyway). Just install it after Aurora v5 until v6 is out.

Hmmm, how we can do this with only our batch tools? I've no idea, at the moment. Any suggestions? The batches can only check, if it is a mod or file present, but not, if a component is installed?!

I don't know, I guess I will have to make an IA update a bigger priority (sigh).

[dabus]

@Miloch:
Errm, I did post a solution, just look a post above yours.

You would only install the main-component.
Then run the test on it.
Only install the sub-components if the test returns a 1 for installed.

The example works on any mod/component-combination and may be useful for other stuff as well.

[Miloch]

@Miloch:
Errm, I did post a solution, just look a post above yours.

Oh, ok. I assumed by the "WTF" it wasn't working as you intended. I'd have to go digging for the DOS manual to figure out that kind of code .

[dabus]

The first part works as expected.

Example test for TDD:

L:\Games\Big World Project\BIGWOR~2>findstr /I TDD weidu.log
~SETUP-EXNEM.TP2~ #0 #2 // Add items to areas (affects SOA areas only - not BGT, TDD, CtB, etc. areas)
~SETUP-TDD.TP2~ #3 #0 // Der Dunkelste Tag, v1.12: v1.12 BWP Fix

L:\Games\Big World Project\BIGWOR~2>test
Set your setup here:TDD
Set your component here:0
Found

L:\Games\Big World Project\BIGWOR~2>test
Set your setup here:tdd
Set your component here:1
Not Found

L:\Games\Big World Project\BIGWOR~2>

findstr ships with windows and is also used in the Fix-Batches.

The second part of the post is for those that understand batch better than me.

Edited by dabus, 22 February 2010 - 01:25 PM.

[Fouinto]

The second part of the post is for those that understand batch better than me.

I don't know batch better than you (I barely know how to read them), but I know how to test stupid behavior. Try this (note SET RETURN=42 at the beginning and the echoing of %RETURN% in the last line) :

@echo off
SET RETURN=42
set /P MOD=Set your setup here:
set /P COMP=Set your component(s) here:
For /d %%c in (%COMP%) DO (
        SET RETURN=0
        For /f "delims=" %%t in ('findstr /I "%MOD%.tp2~.*#.*#%%c" weidu.log') DO (
                echo %%c was really found, but it RETURN is not set. Why?
                SET RETURN=1
        )
        If %RETURN%==1 (echo %%c was found %RETURN%) else (echo %%c was not found %RETURN%)
	
)

I've heard about this kind of behavior in specific language but I did'nt know DOS was part of them. If I remember well, this has something to do with the way the language manage varname in different code block when different vars have the same name.
I guess this as something to do with "/V in CMD.EXE" in set help (set /?) but even with DOS help in French, I'm not sure to understand it .

Hope this helps.

[dabus]

Well, I had tested it before posting and you can't even set this in the loop itself.
But I just don't get it why anyone would like the cmd/batch to behave like that.
To me, it's just rather stupid.

[Fouinto]

Well, I had tested it before posting and you can't even set this in the loop itself.
But I just don't get it why anyone would like the cmd/batch to behave like that.
To me, it's just rather stupid.

I spend more than 1 hour to "understand" the problem. Even now, I am not sure if I have succeeded
I also think it's stupid and I can't remember when this kind of behavior can be useful, however, it's seems to me than changing %var% to !var! should cancel this stupid behavior.

Hope this helps.

[dabus]

Post the example if you have it running please. It doesn't change a bit for me.

[Fouinto]

Post the example if you have it running please. It doesn't change a bit for me.

@echo off
SET RETURN=42
set /P MOD=Set your setup here:
set /P COMP=Set your component(s) here:
For /d %%c in (%COMP%) DO (
        SET RETURN=0
        For /f "delims=" %%t in ('findstr /I "%MOD%.tp2~.*#.*#%%c" weidu.log') DO (
                echo %%c was really found, but it RETURN is not set. Why?
                SET RETURN=1
        )
        If !RETURN!==1 (echo %%c was found !RETURN!) else (echo %%c was not found !RETURN!)
        
)

Well, I don't understand, It does not work for me at home ! Indeed, at home, I have to use "cmd.exe /V:on" for this to work (I don't know if it's related but I use Win 7)...
Before my previous post, I had tried on a simpler example and on another computer where it worked (where I have used Win XP) without "cmd.exe /V:on"...
I REALLY don't understand

[dabus]

Well, it's nothing serious if the loop does not work. I just thought that a checks of all components that are installed by a force-parmeter would be nice to have if you use the batch. That's all.

[Miloch]

Can you also make sure any INSTALL_BY_DEFAULT components actually get installed with the batch setup. For some reason, this isn't happening either.

[dabus]

Oh, it's getting interesting: So I would just have to parse the TP2 for those to make it more secure and find out about dependencies and in that context maybe conflicts? Good. So I think I'll add that to my tool and see if we can do anything like that for the Install.bat.
(Yes, I did not really had a chance to look at the documentation, tutorials nor examples.)

But please remind that this will blow up the work and the code for the batch as it is currently structured. (But still walking blindfolded is not good either, I know.)

Edited by dabus, 23 February 2010 - 09:49 PM.