Jump to content

JUNKdeLUXE

Citizen
  • Posts

    323
  • Joined

  • Last visited

Everything posted by JUNKdeLUXE

  1. Red emphasis mine Is anything else needed than the following steps explained here: I'm left a bit confused from this. Following these instructions I have 2 files left in Optional Files: Enhanced Weather - Rain and Snow.esmEnhanced Weather - Weather Sounds In Interiors.esp Can both of these files be activated in the right pane of Mod Organizer?
  2. A World Of Pain for Fallout 3 AWOP4FO3 RR Expanded Mothership Zeta Crew All these 3 mods have the Cleaning tag, but LOOT doesn't indicate if these are ITMs or UDRs. Is it safe to clean for both?
  3. Boyaaa.. Great work s4n
  4. I'm not questioning that the order the mods are installed is correct, as I'm sure you are way more experienced in this than me. I only highlighted a sentence a novice modder might be confused by :)
  5. I only mention it because you usually have written it like this: A person with lesser understanding could possibly be a bit confused when he is asked to: There are no files called this in the files page on Nexus. Again - I'm just trying to go through your guide a second time and mention the things that a new user could possibly misunderstand, miss completely or might confuse him/her. What you do with the information is totally up to you.
  6. Red emphasis mine As of the current guide, this step is not immediately before UIO. Both aHUD and iHUD are between this step and UIO.
  7. it is.. for me. A user that might not have modded before, would expect the guide to mention a file to install as all previous steps has done this. I'm just pointing out all the potential problems with the guide that some might stumble over, so it's easier for the next modder.
  8. It's not mentioned what file to download as per your usual habit.
  9. In the next step (FWE) we're instructed to download - and a few steps later install - "DarnUI_Support_for_FWE". It's mentioned that this plugin is used instead of the Darnified UI one. If it overwrites the original, won't be be "optimal" to move the "DarNifiedUIF3.esp" to Optional ESPs? This critical information is not mentioned in the "Creating a Bashed Patch" much later in the guide. Many people (myself included) would not have remembered this step many hours later when finally reaching the ending of the guide.
  10. Ye.. I'm getting 504's now as well (Gateway Time-out)
  11. Not to be a doomsayer, but I'd recommend getting any mods you'd wish to try now, before mods are usable on consoles. If the current troubles with mod stealing continues, expect a lot of Skyrim mods that are gonna be hidden.
  12. meeeh.. I guess the Fallout 4 stuff was... something? But no Elder Scrolls? sad panda :(
  13. This might just highlight my missing knowledge about modding, but I don't understand why the guide(s) is set up like this. If I have to do something else first, why not have that section earlier in the guide? I believe I've seen the same procedure in one of the Skyrim guides (can't remember if it was STEP or SR:LE) but both times it seems as if I'm missing some critical clue as to why it's done like this :)
  14. Hey Kelmych, sorry for all my spamming :) I'm adding "topics" as I encounter them. Having just done the fINIp3 (I'm still in the process of the installation procedure), it could be moved. On top of my head I think this would require changes to other sections that also mention the ini files and changing/copying/backup these. But as this is still fairly early in the guide, I don't think it would be too difficult to ensure no redundancies. Sounds great that the bashed patch section is in for an update. I've finally gotten "some" understanding to xEdit (been modding Skyrim for some time now) but bashed patches, and bash tags are still very much alien to me, not knowing what they do and how I can "mold" the experience. When it comes to bash tools I just follow the steps and cross fingers :) My earlier mentions regarding the lock times was mostly just a jab on how this was a fun/strange way to do things, but if it works, it works! ;) I'm no developer and most of the stuff I learned when studying Computer Science, are various tidbits that help me understand some things more in depths than a non "computer savy" person would. And just so I've said it.. my mentions in this (and other) posts are not an effort to undermine your obviously huge and great work with this guide. A guide of this magnitude is not something I would be able to do with my current knowledge. I just hope that with the mentioning of my experiences and how I understand the guide (as a fairly outsider to Fallout 3 modding) that it would help in making the guide even better. I also fully understand the plights of a guide author. This is your free time and hopefully you enjoy it, and as such I don't expect you to change everything I mention and I'm also not expecting day to day changes. I just hope that some of my experiences would help you or fellow modders using this great guide.
  15. FOSE Installation: Download v1.3beta2.7z . Extract the files from the archive into the Fallout 3 goty folder, NOT into the Data folder. The src folder and text files are not needed.There are no v1.3beta2.7z files. There are 2 other files available though. fose_v1_2_beta2.7z this is the current stable version fose_v1_3_beta.7z this is the current beta version I have no idea what to install.
  16. Wrye Flash the link for the github version doesn't work anymore.
  17. Perfect! :) thanks for the clarification.
  18. so just to be clear... In Nvidia Inspector: Anisotropic filtering mode should be set to?In Nvidia Inspector: Anisotropic filtering setting should be set to?Enblocal.ini: ForceAnisotropicFiltering=false
  19. Just a pet peeve of mine, but to me an install guide should be short, precise, have no redundant info and easy to read/follow. Here is an example of when I don't feel this guide is: I don't need to know about how earlier versions were working or the changes from 1 version to another. And in continuation of this: Here my mind (and subsequently my page as I'm scrolling) jumps back to a previous step. This step was not something that was important to my current step (the installation of LOOT) and as I read further it seems as if my current step will be completed in a later step. Also, I don't find it important to know what LOOT was called before, unless you would also support BOSS (which I guess you don't). If you need LOOT and not BOSS, no need to mention an earlier branch. Had it been me I would have changed this section to only read:
  20. Red emphasis is mine. Are there any documentation on what bash tags are appropriate for various mods or types of mods? If not, is this trial and error or only for advanced users? If it's only for advanced users and/or testing, a note about this should be added. If average or novice modders should be able to use this valuable tool, information on how to use it properly should be added.
  21. TES5EditScripts following the link, there is only 1 release - nothing indicates it's been updated 1/11/2016 though.. latest change (commit) was January 2nd 2016. No other branches than master branch available.
  22. Merge Plugins Problem: Link is pointing to the TES5edit scripts Solution: Change link to https://www.nexusmods.com/skyrim/mods/69905/?
  23. Fallout Mod Manager - FOMM - Fork Should not be optional or recommended if the newest version of Mod Organizer can install all mods in the guide. It only adds to the confusion of the reader new to modding Bethesda games.
  24. Well.. then the STEP guide is even more wrong as it tells the user to set AF to TRUE (as quoted in the first block). The STEP guide might later change it back to FALSE, but that is just a redundant step then :) Btw.. my quoted blocks have nothing to do with Boris. They are from your own guide. The only change I made between your S.T.E.P guide and my recommendation is to move the notice (in red) up before the steps changing something that you were not supposed to do :)
×
×
  • Create New...

Important Information

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