seekles

Ehhh.... you realize that the DLC Wiki is useless now don't you, it request you to unpack the fix files into a directory and them immediately delete that directory in the next step. I'm retyping it cause you asked me to look into the Wiki (see previous posts) and I think it could use some clarification for the noob user. As it stands now there is no conflict anymore cause well, the Wiki is not useable atm to install DLC.

@frishyland I'm retyping the DLC wiki and noticed that after step 3 you cut out a large part of the text. Could you please fix this so I can continue. Also I would like to point out again that the Wiki and STEP guide contradict themselves on the need of fixing the HRDLC since in the guide you do deactivate the HRDLC mods int he first steps.

That reminds me, when is the new version coming out (I prefer not to do things double :p) and what you prefer me to check first STEP .pdf guide or the wiki page? In my opinion these two could best be merged btw. Also this might sound stupid but is there a .doc version somewhere or (.odt if that suits you, not to hard to install Ooo again)?

Okay, I had a look yesterday while trying to get NMM to download and install the first Mod in the STEP guide, cause it happily kept crashing on the last 1% of the download I got enough time in. I noticed that the step we discussed in this mail is listed in the wiki page but not in the STEP manual itself. I assume this is cause the HighRes mod makes that step of the wiki obsolete but I couldn't find out for sure. If I run in this kind of things where best to raise these questions and if I am allowed to make some small images which format would you prefer (cause you're right that two lines of text and one image of how BSAOpt should have looked like in this thread would have been enough). All in I think I found some points I could clarify for the manual and I'll see if I can put in some time the next 10 days. I'll put it in .doc format.

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.

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 buttonIn the pop up menu select the directory you want to pack (HRDLC1 or HRDLC2)Click the Use Folder buttonCheck 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 directoryClick the bottom right Browse buttonIn the File name section select and overwrite "out" with HighResTexturePack01 or HighResTexturePack02Check if the Save as type section is set the Bethesda Softworks Archive (*.bsa)Click the Save buttonClick the Pack buttonRepeat the process for the other directory (HRDLC1 or HRDLC2) that needs to be packedDelete the HRDLC1 and HRDLC2 directories

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.

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.

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.

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

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?