Jump to content


Photo

Clean-up.bat


  • Please log in to reply
63 replies to this topic

#1 Ithildur

Ithildur
  • Member
  • 179 posts

Posted 16 January 2016 - 01:33 PM

So...

 

I mentioned in another post I took the risk of running this option after a successful BWS install, and it seemed to confirm that this feature is not working as intended (agb1 confirmed this). But it seemed largely harmless.

 

However I just discovered that in my install, every SCS bcs script that starts with the designation 'dw#' seems to be missing. Essentially there are dozens, possibly hundreds of spellcasters that are missing their main casting scripts.

 

On a hunch I looked through the clean-up.bat file and found this:

 

 

:: Step 1
:: Now files that should not be in the override will be deleted. Don't worry about the "not found" messages!
:: Some of these files are markers that are needed for uninstall/re-install that not do any harm.
FOR %%f IN (
%OV%z#misc.*
%OV%*.aup
%OV%*.B
%OV%*.baf
%OV%*.bak
%OV%*.bat
%OV%*.d
%OV%*.exe
%OV%*.g3
%OV%*.ks
%OV%*.mp3
%OV%*.mrk
%OV%*.ogg
%OV%*.rpgd
%OV%*.RR
%OV%*.sfk
%OV%*.slh
%OV%*.tiz
%OV%*.txt
%OV%*.UB
%OV%*.xxx
%OV%.DS_Store
%OV%AR0500-bcs
%OV%fhlplay.fh
%OV%BBlade1
%OV%BBlade2
:: %OV%BP-BGT_WM6.wm6
%OV%CELES
%OV%chitem.log
%OV%CLOUDKA
%OV%Desktop.ini
%OV%DFOGA
%OV%dummy.blarg

:: %OV%dw#*

%OV%ESHIELC
%OV%f_dagaxe
%OV%firebrn
%OV%ICARMOR
%OV%ICINHIT
%OV%ICWRATI
:: %OV%ION*
:: %OV%IOUNX*
%OV%KRDL1
%OV%KRGLOBD
%OV%LPOOMV
%OV%otthelm
%OV%PGDARN.bam.gif
%OV%PSHELLC
%OV%RPGSolaFlirtPack
%OV%S#Eye
%OV%sharea
%OV%spheart
%OV%spwi910cre
%OV%spwm104
%OV%SSHELLC
%OV%TRBLOBA
%OV%tz25mnds.tmn
%OV%va#tod.nul
%OV%"Service-Version 1.txt"
%OV%The_Lady's_Shadow.rar
%OV%b!romkil.x
) DO del %%f 2>nul

 

 

I'm not familiar with the syntax here so I cannot be certain, but it looks awfully suspicious, the bit that I bolded/highlighted (or tried to, forum isn't very helpful and keeps reverting to standard text)... Please tell me this didn't actually erase every file whose name started with dw#... I'm hoping the :: in front of that particular line means skip deleting those files...
 


Edited by Ithildur, 16 January 2016 - 01:38 PM.


#2 agb1

agb1
  • Member
  • 1623 posts

Posted 16 January 2016 - 01:36 PM

That looks like exactly what it does. No clue why!

Edit: you are correct, the :: disables the line. http://www.robvander...om/comments.php

Edited by agb1, 16 January 2016 - 01:45 PM.

BiG World Fixpack (community collection of mod fixes and compatibility patches, with user-friendly cross-platform script)

 

BiG World Setup (tool to automate best-practice installation of Infinity Engine mods on Windows, with conflict analysis)

Latest version:    https://bitbucket.or.../get/master.zip


#3 Ithildur

Ithildur
  • Member
  • 179 posts

Posted 16 January 2016 - 01:44 PM

I am.. speechless. Utterly speechless right now.

 

I'm trying to decide whether I should attempt a third go at a working installation, this time manually without BWS, or with BWS just without letting it install any of it's own special components/tools like this one and LOLFixes. Or if I should just forget about this game for a good long while, and take many long breaths and a long walk for now.

 

 

[edit] Ok, then this isn't the culprit, hopefully. I've no idea what happened then. I can't find a single bcs that begins with the DW# designation in my game, and there are plenty of cre files (LOLFixer didn't change this at least) that have them in their script slots. I've already found 2 spellcasters that just stand there or move around without attacking during combat, and I'm sure I'll find many, many more.

 

It's still rather disturbing to see that line in there, which probably means at some point someone working on BWP/BWS thought about deleting these scripts...


Edited by Ithildur, 16 January 2016 - 01:50 PM.


#4 agb1

agb1
  • Member
  • 1623 posts

Posted 16 January 2016 - 01:57 PM

Well, this is assumed to run after generalized biffing. Doesn't that take all of the bcs files from the override folder? So whatever is left with dw# prefix might not have been important at the time when the script was originally written. I think that is Leonardo Watson (BWP author)'s script.

BiG World Fixpack (community collection of mod fixes and compatibility patches, with user-friendly cross-platform script)

 

BiG World Setup (tool to automate best-practice installation of Infinity Engine mods on Windows, with conflict analysis)

Latest version:    https://bitbucket.or.../get/master.zip


#5 Ithildur

Ithildur
  • Member
  • 179 posts

Posted 16 January 2016 - 01:59 PM

Well, after taking some deep breaths, I thought of a rather ironic 'solution': I still have the intact directory of the other 1st install that got borked. That install still has all the dw# bcs files in there intact, so I'm going to attempt cannibalizing the dead install's files and copy them over into the current install's override folder.

 

Interestingly enough, that install I did not run clean-up.bat; in fact I didn't let BWS finish out it's entire install process because I wanted to manually add a few mods that aren't on BWS's list. Something along the way definitely seems to have deleted these files, and seeing that snippet commented out above doesn't help my suspicions.



#6 The Imp

The Imp

    Not good, see EVIL is better. You'll LIVE.

  • Member
  • 5155 posts

Posted 16 January 2016 - 01:59 PM

[edit] Ok, then this isn't the culprit, hopefully. I've no idea what happened then. I can't find a single bcs that begins with ...

What are you using to search for them ? Moding tools, or just file browser ?
Cause if you used the Generalized Biffing, well they are all in the data folder's .bif files. And note, all those files, well they are not usable in game(non-EE BG2 game). .g3, .mrk are marker files, .ogg are sound files that need to be converted to be .wav files, .d files are uncompiled dialog files, .baf are uncompiled script files(.bcs) ... list goes on.

 

So I would consider that, the only thing you have done so far, is thrown good installs away. You had a few errors, yeah, but proper solution to those is to actually have a live and reliable install, aka one that has the correct install folder setting in the baldur.ini file when you start megamoding it, and not switching it as the middle ... next error, check before you actually start the moding still that the game actually works and start a new game in the Amn and ToB regions. This helps you to get the graphical errors under control and see what you wish to adjust... disable the virus control, UAC etc etc and then start the BWS... let it finish all on it's own. re-enable the disabled things(restart the computer), and start the game via the BGMain.exe, or the quick icon made from it in your desktop.


Edited by The Imp, 16 January 2016 - 02:08 PM.

Yep, Jarno Mikkola. my Mega Mod FAQ. Use of the BWS, and how to use it(scroll down that post a bit). 
OK, desert dweller, welcome to the sanity, you are free to search for the limit, it's out there, we drew it in the sand. Ouh, actually it was still snow then.. but anyways.


#7 Ithildur

Ithildur
  • Member
  • 179 posts

Posted 16 January 2016 - 02:01 PM

Trust me, I've looked everywhere. I looked with NI, I looked with Windows Explorer, I looked in all the Gen Biff's folders. They got deleted somewhere along the way... I did reinstall widescreen (and hence gen biffing as well since it's required) a couple of times today to try different resolutions, but there was nothing unusual, no error messages, etc.; that shouldn't have made files disappear.


Edited by Ithildur, 16 January 2016 - 02:14 PM.


#8 agb1

agb1
  • Member
  • 1623 posts

Posted 16 January 2016 - 02:04 PM

If they are not in the backup folders in gen biff then are we sure they were ever in the override? Were there any errors during SCS installation?

BiG World Fixpack (community collection of mod fixes and compatibility patches, with user-friendly cross-platform script)

 

BiG World Setup (tool to automate best-practice installation of Infinity Engine mods on Windows, with conflict analysis)

Latest version:    https://bitbucket.or.../get/master.zip


#9 The Imp

The Imp

    Not good, see EVIL is better. You'll LIVE.

  • Member
  • 5155 posts

Posted 16 January 2016 - 02:11 PM

So what did you actually install ?

Weidu.log's content, open the file with Notepad, and copy paste the text to a post ... that's everything you have installed just so you know.


Yep, Jarno Mikkola. my Mega Mod FAQ. Use of the BWS, and how to use it(scroll down that post a bit). 
OK, desert dweller, welcome to the sanity, you are free to search for the limit, it's out there, we drew it in the sand. Ouh, actually it was still snow then.. but anyways.


#10 Ithildur

Ithildur
  • Member
  • 179 posts

Posted 16 January 2016 - 02:13 PM

No error messages in SCS logs; the respective baf files compiled without issues it seems, I see multiple lines like this:

 

[stratagems_external/workspace\ssl_out\dw#priest.baf] loaded, 301370 bytes
Copied [stratagems_external/workspace\ssl_out\dw#priest.baf] to [stratagems_external/workspace\ssl_out\dw#2gcl4.baf]
Compiling 1 script ...
[stratagems_external/workspace\ssl_out\dw#2gcl4.baf] loaded, 301370 bytes
Processing 1 dialogues/scripts ...

 

etc etc

 

[./override/dw#2gcl4.bcs] loaded, 541726 bytes
override/PRIES8C.CRE copied to stratagems_external/backup/stratagems/6041/PRIES8C.CRE, 1196 bytes
Copied [PRIES8C.CRE] to [override/PRIES8C.CRE]
[./override/PROPHET1.CRE] loaded, 1408 bytes
Copying and patching 1 file ...
[./override/PROPHET1.CRE] loaded, 1408 bytes

 

where a dw# bcs file seems to have been compiled into the override folder and then subsequently applied to a cre file by without any issues.

 

 

 

Pretty sure I posted my weidu file in the other thread, here it is again.

 

Spoiler

 

I'm not looking for a fix at this point honestly, this is getting way too tedius (I've spent more time bug fixing than playing since I got this installation to work); I'm just going to copy the bcs files from the other installation into this one (all the settings for SCS are exactly the same between the 2 installs).


Edited by Ithildur, 16 January 2016 - 02:20 PM.


#11 The Imp

The Imp

    Not good, see EVIL is better. You'll LIVE.

  • Member
  • 5155 posts

Posted 16 January 2016 - 02:23 PM

I have no idea how the hell the Near Infinity can't find the files, but try to get a newer version, like the 1.36-20160112 from here.

... but that game is ok, just start it, you have everything in the data folder's tb#****.bif files.


Edited by The Imp, 16 January 2016 - 02:25 PM.

Yep, Jarno Mikkola. my Mega Mod FAQ. Use of the BWS, and how to use it(scroll down that post a bit). 
OK, desert dweller, welcome to the sanity, you are free to search for the limit, it's out there, we drew it in the sand. Ouh, actually it was still snow then.. but anyways.


#12 agb1

agb1
  • Member
  • 1623 posts

Posted 16 January 2016 - 02:23 PM

I will take a look at the cleanup batch script tonight to see if some other part of it could be responsible for this.

BiG World Fixpack (community collection of mod fixes and compatibility patches, with user-friendly cross-platform script)

 

BiG World Setup (tool to automate best-practice installation of Infinity Engine mods on Windows, with conflict analysis)

Latest version:    https://bitbucket.or.../get/master.zip


#13 Ithildur

Ithildur
  • Member
  • 179 posts

Posted 16 January 2016 - 02:24 PM

I have no idea how the hell the Near Infinity can't find the files, but try to get a newer version... but that game is ok, just start it, you have everything in the data folder's tb#****.bif files.

 

 

Because they're GONE, deleted. That's why.

 

 

Trust me, I've looked everywhere. I looked with NI, I looked with Windows Explorer, I looked in all the Gen Biff's folders.

 

 

 

For crying out loud, you want me to post a screenshot of which folders I looked at as proof??? The affected NPCs do not cast spells ingame, the scripts are NOT THERE.


Edited by Ithildur, 16 January 2016 - 02:28 PM.


#14 The Imp

The Imp

    Not good, see EVIL is better. You'll LIVE.

  • Member
  • 5155 posts

Posted 16 January 2016 - 02:28 PM

I will take a look at the cleanup batch script tonight to see if some other part of it could be responsible for this.
It just deletes unneeded files.
I looked in all the Gen Biff's folders.
So, but did you look into the data folder ? This in a game that didn't have the fuckup wrong path info in the baldur.ini before you start-ed the mega install ?
That might be the reason why the whole thing is off.
AKA, just do the install like it's supposed to be done normally.

Yep, Jarno Mikkola. my Mega Mod FAQ. Use of the BWS, and how to use it(scroll down that post a bit). 
OK, desert dweller, welcome to the sanity, you are free to search for the limit, it's out there, we drew it in the sand. Ouh, actually it was still snow then.. but anyways.


#15 Ithildur

Ithildur
  • Member
  • 179 posts

Posted 16 January 2016 - 02:30 PM

Ok, this is the part where I walk away from trying to communicate with you.

 

I do appreciate your help and efforts, agb1. Just.. probably best I stop going back and forth with the other guy.



#16 agb1

agb1
  • Member
  • 1623 posts

Posted 16 January 2016 - 09:29 PM

Okay, I looked through the script and so far I don't see anything that would have deleted all of the bcs files. Could be I missed something though, so I will run some tests.

 

Edit:  I can't tell from the WeiDU log because it is a sub-component prompt:  did you choose "biff all files" for generalized biffing or did you choose "only wav&tis&bam files"?


Edited by agb1, 16 January 2016 - 09:33 PM.

BiG World Fixpack (community collection of mod fixes and compatibility patches, with user-friendly cross-platform script)

 

BiG World Setup (tool to automate best-practice installation of Infinity Engine mods on Windows, with conflict analysis)

Latest version:    https://bitbucket.or.../get/master.zip


#17 Lollorian

Lollorian

    smiley addict

  • Member
  • 4150 posts

Posted 16 January 2016 - 10:08 PM

Could you attach your Big World Debug.7z (txt?) and setup-generalized_biffing.debug please?


"I am the smiley addict, yellow and round, this is my grin :D when I'm usually around :P.
When there's trouble brewing, see me post, cuz it's usually a wall o' yellow and your eyes are toast!!!"

BWP GUIDE - BWP FIXES - impFAQ - NPC LIST - KIT LIST - AREA LIST

GitHub Links : BWP Fixpack | Lolfixer | BWP Trimpack | RezMod


#18 agb1

agb1
  • Member
  • 1623 posts

Posted 17 January 2016 - 05:50 AM

It would be BiG World Upload.7z in the game folder.

BiG World Fixpack (community collection of mod fixes and compatibility patches, with user-friendly cross-platform script)

 

BiG World Setup (tool to automate best-practice installation of Infinity Engine mods on Windows, with conflict analysis)

Latest version:    https://bitbucket.or.../get/master.zip


#19 Ithildur

Ithildur
  • Member
  • 179 posts

Posted 17 January 2016 - 02:24 PM

Yes, I chose the biff all files option.

 

I don't see an option on these forums for attaching files to posts

 

[edit] I'll see if I can provide some options to link to the relevant files.

 

The 'fix' I had to resort to (copying over the dw# files from the first installation; btw there were a total of about 931 files: bcs, itm, cre, etc so these files getting deleted was disastrous) is a less than ideal solution as it turns out due to the fact that various strings don't exactly match up from the other install's dlg.tlk with this one's dlg.tlk file (which is not surprising, even with the near exact same mods/components installed there can be slight variances with the two tlk files). It's not a major issue, more cosmetic (various creature names being a long dialog string, item descriptions also, etc) but still annoying/distracting.

 

I'm starting to think if it's not clean-up.bat or similar, reinstalling widescreen (which uninstalls gen biff and reinstalls it automatically; somehow files might've gotten lost during that process) might be the other factor that might've led to trouble. I can think of nothing else that might've caused 900+ files to vanish... but the fact that these files all have in common the fact that they start with dw#... and seeing that at some point in the past clean-up.bat seemed set up to delete dw# files, is what makes things rather suspicious...


Edited by Ithildur, 17 January 2016 - 02:44 PM.


#20 agb1

agb1
  • Member
  • 1623 posts

Posted 17 January 2016 - 02:45 PM

Attaching files can be done by clicking 'More reply options' in the lower right corner when replying to a post and then clicking 'Choose files' button at the bottom of the advanced reply box.


BiG World Fixpack (community collection of mod fixes and compatibility patches, with user-friendly cross-platform script)

 

BiG World Setup (tool to automate best-practice installation of Infinity Engine mods on Windows, with conflict analysis)

Latest version:    https://bitbucket.or.../get/master.zip