Jump to content

TechAngel85

Administrator
  • Posts

    14,559
  • Joined

  • Last visited

Everything posted by TechAngel85

  1. Yes, you can just drag them. It's a simple fix.
  2. Shame on him! ...leaving out those spans like that. Haha! Thanks for the fix.
  3. That's not something we have our users do. Hence why we provide the STEP Patches. We will forward what is necessary in those patches; however, getting the actual mod updated is the best solution for all users, not just STEP.
  4. Teams can form up or individual users can do this on the mod's thread like this one. STEP is a small team when it comes down to the nitty-gritty stuff like mod testing, load orders, and getting releases out the door (this is mainly all done by 2-6 STEP staff members...testing is about the only aspect that the community gets involved in and that's only testing for STEP-included mods). We honestly do not have the time. STEP is suppose to be community driven so if members of the community want to step up and do such things, they are more than welcome to do so! Create mod pages, test mods, make Packs, help with load orders...all these things can be done by normal members.
  5. Sounds like something we might want to stay away from as well. Though I'll admit that I'm not familiar with how the game works in the way Arthmoor is describing.
  6. Looking at this (interior lighting version) in TES5Edit, it looks like it needs some USKP forwards. Is that planned in the next update, JawZ? As for STEP, we'll probably need to forward some of the changes from ELE into the STEP Patches as to not undo what it's doing. There are several mods that conflict, especially with fog distances and some water heights. Those water heights look like they need to be forwarded into ELE by JawZ, though.
  7. OP updated and wiki page finished. Accepted for v2.2.9.1
  8. Updated OP/changelog/Guide. Relighting Skyrim and ELE - Lite (interiors) accepted. Placed both in fixes because...well, they fix the vanilla lighting issues.
  9. Awesome, just verifying! Might want to update the description, though. The load order section still has the old reference. to _DLC.esp. Looks like it's "Legendary" now. Update: I've updated the OP with the boilerplate and finished up the wiki page. This mod has now been accepted for v2.2.9.1!
  10. Just as the title says, the Supported DLC options in the form on mod pages is not working properly. I can select the options (using Firefox) and submit but they are never displayed on the mod page. Example: https://wiki.step-project.com/Relighting_Skyrim Relighting Skyrim supports all three DLCs and all three are selected in the form, however, none are presented on the mod page. I've looked at the form myself but...
  11. That is not why they wouldn't be considered. They can be compared against this mod but from what I've seen. This mod is better. This mod also goes down as far as 1K, whereas, Gamwich states plain as day on his mod page the giants where left at 2K diffuse and 2K normal. So if performance is all you want, this mod would be the better go at the 1K resolution. Just putting that out there for where the giants are concerned.
  12. I take it with the new merged options the Relighting Skyrim - DLCs mod is no longer needed. Correct?
  13. The RWT patch was/is probably in the STEP Patch. However, EssArrBee has yet to get them updated for the new AOS version.
  14. Hmm...I just seen this, but posted a bug report before doing so about something similar with the conflict flags. I suppose the behavior I described could be intentional as well, but if it is it's confusing users and I think the grey lighting bolt icon is more informative than the +/- flag in cases where mods are being completely overwritten.
  15. I have posted a report: https://issue.tannin.eu/tbg/modorganizer/issues/1214 Please add any relevant information to the report for Tannin.
  16. The flag seems to only show when there is one mod overwriting it. If there are several, the +/- flag is shown instead. Looking in the conflicts tab, you can see there the mod is providing no files and being completely overwritten; however, it doesn't show the proper flag for that.
  17. I noticed this as well about the flags but on other mods I've been testing. Can someone report this as a bug? I'm at work and can't
  18. Most users don't care about the why's. The Guide is simple in the way DY stated, you install it and done. Those that want to know the why's can research further, but to keep the Guide simple and neat this information is kept in the threads. That's why there are links provides to the forums and other sources from the mod pages.
  19. Seems we've made a mess out of this mod page. If another Staff doesn't fix it, I'll do it when I get home from work and tennis.
  20. I reversed it already. Just forgot to post so the instructions are back.
  21. Right now there isn't much to be done. We're finishing some things up behind the scenes and once that is done there are a few mods pages to add instructions to and tighten up. After that the release will be ready. I'm hoping it'll be out this week, but no promises.
  22. I'm trying to get this sorted out with EssArrBee, but he's not online atm. STEP has never used the Skyforge Weapons before and it's related ESPs so I'm looking into if something has changed. I'd skip it for now.
  23. Looks like EssArrBee removed that line about move the aMidianBorn_Skyforge_Weapons.esp to the optional ESPs back in Feb. I think this was by mistake so I'll send him a PM asking. EDIT: Also, loading up aMidianBorn_Skyforge_Weapons.esp in TES5Edit will reveal some issues of USKP not being forwarded as well as conflicts with the Content Addon.
  24. You should not be able to edit some of those aspects on the mod pages. Please do not make changes without asking first.
  25. If you're running the beta, try out the current version 1.7.2
×
×
  • Create New...

Important Information

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