Jump to content
  • 0

DLC Wiki leads to CTD causing .bsa files


seekles

Question

I've been playing Skyrim for a while now in it's vanilla glory (I prefer to play games vanilla) but ran in to a number of disturbing resolution problems so I thought about installing the highrespackages finally. To do this properly I found your nice STEP project and tried to execute everything described in it.

This led to Skyrim actually CTD-ing directly after it went fullscreen (so before the Bethesda logo pops up).

 

After a day of testing I came to the following conclusion:

 

Using a clean install of Steam and Skyrim following the STEP DLC section described to the letter leads to two HighResTexturePack0x.bsa files being created that will cause a CTD on startup of Skyrim. Running the system with vanilla steam downloaded HighRes files will work like a charm however.

 

Now the only issue I ran into was 4 placeholder files copy exceptions during the unpacking of the HighRes files but since these files do not seem to be needed as they are removed by the .bat file I do not see why that could cause the error.

 

The only other oddity I face is that allowing TESV.exe to run as administrator puts you in a launcher and Win7 allowance loop (hitting play in the launcher, generates the Win7 security question you need to OK which then again starts the launcher, etc) thought his happens when using vanilla and adapted HighRes files

 

Anyone has a clue to what is happening here or is there an error in the DLC section's text?

Link to comment
Share on other sites

Recommended Posts

  • 0

My guess is that you have an issue with the BSAs taht you created. If they were not packed correctly, this could cause the problem. Look at the BSA structures in DDSopt or BSAopt and compare to vanilla.

 

If I understand correctly, if you use the default HRDLCs, you can run Skyrim, but if you use those that you newly created, you cannot?

 

I personally used the same methodology accept that I packed my loose files into an archive and posited into my Data directory (via Wrye Bash). I avoid BSAs.

 

It is pretty easy to mess up a BSA repack if you don't create the right source and target directories.

Link to comment
Share on other sites

  • 0

I tend to agree with you on the incorrect packing z929669 when it comes to a faulty file but my issue is that I followed the manual of BSAOpt to the letter (especially my test with a clean install). I could try to unpack and repack the vanilla HighRes to see if BSAOpt is an issue in the unpacking/packing part if that helps.

 

I glanced over the bsa created with the corrections and the vanilla but I'm to noobish to draw any conclusions apart from them looking the same.

 

I piece of text on how to pack properly would be appreciated frihyland

Link to comment
Share on other sites

  • 0

Both files remain below the 2G limit (didn't know it existed) though the HRDLC2 to HighResTexturePack02.bsa just barely manages, this should be the case I assume cause the .bat file mainly removed some files hence a smaller repacked HighResTexturePack0x.bsa file.

 

Could you write a small piece on how to use bash to create the appropriate HighResTexturePack0x.bsa files then I'll install bash and try that approach next to the test with unpacking and repacking the vanilla HighRes files with BSAOpt.

Link to comment
Share on other sites

  • 0

The point about correct BSA structure is that within the BSA, you should see a directory structure like:

 

textures/landscape/trees/*.dds and NOT

 

landscape/trees/*.dds OR

 

 

out/textures/landscape/trees/*.dds

 

 

Both of the latter two structures will effectively eliminate all texture assets and crash the game (assuming that these are the only texture BSAs available and they are named correctly).

 

The way Fri and I do it is by compressing the textures folder into a ZIP archive (or RAR or 7z). Then it is available for management using Wrye Bash, MO or NMM. Alternatively, you can simply paste the textures folder into your data directory (this is the manual install method used by TheCompiler). In fact, pasting each of those texture directories under skyrim/Data would be an easy way to verify that you have a BSA issue and not some other issue.

 

The point is that you may have followed the guide, but clearly, you misunderstood one or more of the guide's instructions (or altogether missed some other, ancillary instruction).

Link to comment
Share on other sites

  • 0

Just mix a vanilla gamer with a 15 year ago advanced Unix user and et voila you got the nightmare that's me, I understand file structures etc and can understand most things you will write down but I have no clue how this BSAOpt/Skyrim modding etc works beyond the manual you write. So I will follow it to the letter and then report if something is wrong, with some pointers I can tell you where it went wrong and since I get the idea your targetting a broader audience hope you use the info to improve your project.

 

There might be a misunderstanding from your point of view but I literary execute what is written down hence from my point of view that means there is something not written down clearly enough or wrong for that matter. Let figure out what it is shall we.

Link to comment
Share on other sites

  • 0

I agree that we may have something worded in a confusing way, or possibly even overlooked something that we normally take for granted. It would be very helpful if you could identify the specifics of where you think that you deviate from what you think to be the intended course.

 

Ultimately, you will want to have created two BSAs that match the respective structures of the original DLCs (less the bloat). Check this by opening each in DDSopt and selecting the respective BSA as the target "directory". Just cursorily examine the tree structure. Each should contain one branch called "textures" with many additional sub-branches.

 

I made a couple of minor changes to the guide that may have been confusing previously.

Link to comment
Share on other sites

  • 0

I think I found out what is wrong and it's a setting problem in BSAOpt on my side. Is there a good way to check in game if the HighRes packages did load properly btw?

 

You might want to add to the guide that you have to check and set the Game menu to Skyrim each time you open or refresh BSAOpt. In my case this solves the loader CTD.

 

On a side note, I checked both files (corrupt and new) and the structure seemed solid, as in the same. Where does the Skyrim setting of BSAOpt kicks in in the file structure?

 

Also I think you could mention that the 4 errors you get when unpacking the .bsa's to the HRDLC directories (1 for HRDLC1 and 3 HRDLC2) about the placeholder not being able to be unpacked correctly (want a screen?) can be ignored cause the .bat file removes mention fo them anyway.

 

If you want me to write a small bullet section for using BSAOpt to pack correctly for this (12 bullets or so) I can do that, used up enough of your time for something stupid.

Link to comment
Share on other sites

  • 0

Sure, go ahead and post whatever changes you think might be applicable to that section of the guide. We will incorporate if we agree (and possibly recruit you to wiki editor ;) if you are interested.... always in need of descent tech writers).

 

I think that XXXopt writes BSAs in different format with respect to game type, but otherwise, they would look the same from the app.

 

I have never had a problem with these apps not remaining 'fixed' to the game format I set them to, so I will pass the buck on that one.

Link to comment
Share on other sites

  • 0

yeah, the automatic setting doesn't work when writing files just opening and the default is oblivion format. Set it to skyrim and forget it. The only changes are a few bytes in the header but it is enough to crash skyrim :(

I had that in the wiki at one point, I'll put it back in.

Link to comment
Share on other sites

  • 0

Hereby my improved version of the BSAOpt packaging line:Using BSAopt (or DDSopt), recompress the two remaining directories

(e.g., c:\HRDLC1 & c:\HRDLC2) back into HighResTexturePack01.bsa and

HighResTexturePack02.bsa, respectively (CAUTION: make backups of these,

because Steam can overwrite! Also, be certain that the directory

structures within each BSA match the textures\ directory structure under the skyrim\Data directory), OR

I suggest changing it into:

Using BSAOpt:

  • Start BSAOpt (pick the correct version, x32 or x64) and check if in the Game menu Skyrim has been set as option (this option might have reset which will generate CTD causing .bsa output files)
  • Click the top right Browse button
  • In the pop up menu select the directory you want to pack (HRDLC1 or HRDLC2)
  • Click the Use Folder button
  • Check if the directory tree that is listed in the top section of BSAOpt lists the structure (..\, textures and then the sub-files) anything else is wrong and you need to reselect your input directory
  • Click the bottom right Browse button
  • In the File name section select and overwrite "out" with HighResTexturePack01 or HighResTexturePack02
  • Check if the Save as type section is set the Bethesda Softworks Archive (*.bsa)
  • Click the Save button
  • Click the Pack button
  • Repeat the process for the other directory (HRDLC1 or HRDLC2) that needs to be packed
  • Delete the HRDLC1 and HRDLC2 directories
Link to comment
Share on other sites

  • 0

I'll see if I can free some time from gaming and that general thing I try to maintain next to it called life to see if it is worthwhile to overhaul some other pieces of text.

 

Can you or better do you want to create a table structure to clean things up and make it more readable. You could cast everything in a procedure mold then, will make it a lot more easier for "stupid" people (a.k.a. me) to execute the plan and owners to maintain it.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.