Daemonjax

For Kotor2 when  converting .wav files in StreamSounds, I needed to use skip=470 in the batch file. 

I used a hexeditor to ensure it was removing the correct number of bytes, and a value of 470 produced the correct result.  Which makes sense, because the header is 470 bytes long (for the files I needed to modify anyways).  

I created my own batch file that simply outputs the header-less .wav into a folder named "output" without changing its name:

for %%F in (*.wav) do ddrelease64 if=%%~nF.wav of=output\%%~nF.wav bs=1 skip=470
pause

And I (of course) had to create my own header file for the conversion back (again by using a hexeditor to copy paste the 470 byte header):

FF F3 60 C4 00 00 00 03 48 00 00 00 00 4C 41 4D 45 33 2E 39 33 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 4C 41 4D 45 33 2E 39 33 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 FF F3 62 C4 8F 00 00 03 48 00 00 00 00 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 4C 41 4D 45 33 2E 39 33 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 FF F3 62 C4 FF 00 00 03 48 00 00 00 00 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55

I created and used the following batch file to add the header back (it simply outputs the re-headered file into a folder named "with-header" without changing the filename):

for %%F in (*.wav) do copy /b "header.bin" + "%%~nF.wav" "with_header\%%~nF.wav"
pause

I did the above because I found myself needing to replace THE MOST ANNOYING SOUND EFFECTS EVER IN A VIDEO GAME: amb_elecwire_A and amb_elecwire_B

Holy crap those sounds sucked so bad I thought it was a bug because it sounds like corrupted white noise. Those files both had a header 470 bytes long.  I don't know if every .wav file's header is 470 bytes long, but it's easy enough to confirm using a hexeditor. 

These weren't raw wav files or mp3 files disguised as wav files... they were just straight up normal wav files with a normal wav file header that starts with RIFF -- they just originally had an additional bullshit 470 byte header.

If I was going to write a tool to do all this for me, I'd do it in java...  If the file starts with the magic bytes FF F3, then it has a header that needs to be removed.  Then, I'd find the first instance of the magic bytes 52 49 46 46 to indicate the start of the sound wav, while storing the header in another file named original_filename.header.  But maybe all the headers in StreamSounds ARE the same, which would simplify things a little bit by hardcoding the header -- but I'd still code want the code it to double check that assumption. 

On second thought, I'd still code it without baking in the assumption that it knows what the header bytes/length are and just figure it out programmatically on a per file basis and store the header info as header_length.extension (instead of file_name.header) to greatly reduce the number of extra files created -- best of both worlds.

Tangential thought: Some sounds effects "pop" ingame when they start playing or when panning the camera near the output source (not the files I made to replace the above two, those work perfectly!), and I have wonder if it's related to their headers.

On 4/8/2021 at 6:57 AM, M'aiqTheLiar said:

...  "TSL Modern Camera Overhaul" over at NexusMods (I'm using the 90 degree FOV). I don't know if there is anything that can be done about this.

 

You can extract the vanilla camerastyle.2da using Kotor Tool, and edit it yourself to make your own camera mod that only affects what you want. 

Going purely from memory... You should only need to increase the fov (the "viewangle" column) on the "Default", "Ebon Hawk", "Outdoors", and "Combat" rows.

I don't use that mod because reasons, but it's easy enough to make your own camera style that does the minimum amount of edits needed.  And anything past ~70 viewangle  (remember this is vertical FOV, not horizontal) causes fishbowling, but I guess some people like that?  Weird.

Here's the best link on the topic:

https://www.pcgamingwiki.com/wiki/Star_Wars:_Knights_of_the_Old_Republic_II_-_The_Sith_Lords#Full_Screen_Movies

When you hexedit the .exe file, be sure to match your screen resolution exactly -- otherwise, it won't work.  For example, you can't use the hexedit code for 1920x1080 res when your screen is actually 1920x1200 -- close enough won't work in this instance and it'll have no effect whatsoever --  this happened to me and it left me scratching my head for a bit.

Note: It'll make the videos stretch to fit your screen no matter what res the bink videos are so you can do this even without downloading the AI upscaled widescreen  bink videos and it'll still work and look OKish.

Will you guys allow KOTOR 1 Bug Fix v1.0 be compatible, or did you guys at least fix the most notorious bug in KOTOR called "Bastila Romance Bug"?

 

Random Hater: I'm going to kill you! You just turned this website into a M+ Video Game!

 

Me: Oh, please. Is that an actual sin?

 

Random Hater: YES!

I'm using the KOTOR Bug Fix Attempt 1.0 mod you're referring to, and the only conflicting file was bp_calo_ambush_2.utc.

I don't know for sure if everything is working as intended, but so far it seems to and I haven't seen anything that would make me suspect otherwise. That bugfix mod just replaces a few scripts and dialog files (and that one utc file)... those other files aren't touched by K1R.

First of all congratulations for this release.

 

I assume that for the K1 Overhaul mod work with the K1 Restoration I must first install the Overhaul and then the KOTOR Restoration?

That's the way I did it.

This is for informational purposes:

Running the installer (while sandboxed using sandboxie) onto my heavilly modded (over 60 mods) kotor game folder produced the following warnings, along with the names of the mods which contain the conflicting file(s):

Merged BOS SR + K1R global.jrl (untested): https://dl.dropboxusercontent.com/u/32777109/kotor/global.jrl

Update3:

Ok, so I think I got everything merged.  Time for a new playthrough!  Wish me luck!  

I hope the above was useful to someone else!