Jump to content

Nearox

VIP-Supporter
  • Posts

    1,391
  • Joined

  • Last visited

  • Days Won

    13

Everything posted by Nearox

  1. I haven;t used any of them specifically, but have never seen a breezehome/player home mod with ELFX compatibility. However I believe there is an ELFX version that excludes the player homes. The same for Skyrim Project Optimization. With regards to compatibility with Whiterun overhauls: as long as the breezehome mod in question does NOT alter the exterior around it, then compatibility should be fine. If it does, then you have to check if the author also modified the navmesh. If no navmesh was modified then the only thing to check for is potential clipping issues. But I believe JK's whiterun has quite some room around Breezehome. Personally I dont like the big breezehoe overhauls Instead I'd consider trying a mod like Simply Improved Breezehome
  2. Technically, yes you can. The original esp is being overwritten by CCO's compatibile version. The end-result is the same though.
  3. Ahh I see, thx. Also SRB the horizontal 'forum thread' link is looking nice. I am thinking though, now that that info block has become relatively small. Why not center it at the pack page? That way it'll jump out more. Maybe just try it and see if you/we like it.
  4. @keith: Thanks to you too for sharing your knowledge on merging REGS esps, and for the detailed report! @everyone: I know the conflict resolution section of REGS-SRLE Compatibility Guide needs updating, but I don't have the time during the next few days. I also cannot give you my own .esp at the moment because a lot of non-SRLE/REGS mods are also in the compatibility file as masters. I had used it some weeks ago for testing some things and wasn't paying attention to saving it to a new esp. Either way, at some point I'll remove the conflict resolution part and simply provide an esp because 1) I personally CBA to write it all down and 2) many people prefer an esp anyways. Just know I can't do it right now, so please don't send me PMs anymore about it :P
  5. That scope would be great as I plan to provide it as part of srle-regs comp section
  6. Just release a new final fantasy sword replica or a bikini mod and you'll be file of the month in no time
  7. WOM used to be in REGS but was removed. It is currently incompatible with REGS - Cities.
  8. We looked at UW back in february/march, but IIRC there were a range with issues with it and we decided to ditch it in favor of DoW. JK's WHiterun generally just looks so good, plus it has DoW compatibility so having 2 mods there will probably be enough. Thank you too for your willingness to look at the CK. It seems we have a few people here who'd be interested in doing it for REGS, which is just fantastic. Indeed I recall CJ making a navmesh tutorial before. Have you found it yet?
  9. Thanks for sharing :) Yeah CK knowledge will mostly be necessary when adding new conflicting mods and when arthmoor decides to change the CRF navmesh once again :D. Generally mod updates dont require us to look at them in the CK for REGS compatibiltiy, but when they do it is critical. I'm uslally not a big fan of mods that revolve around hundreds of mannequins... Feels like a big player home disguised as a museum. And REGS so far has had a strict no-player-housing rule. Reading the description though apparently everything is tied to ane xtensive quest, going through 4 dungeons and a new worldspace. Hmmm. Still seems like the description doesn't tell everything. I'd love to see a video before I try it out, but there is none linked at the page and I cannot find a decent youtube vid on it. Also in the solitude world space, there is already Nernie's cities. SRLE however puts Book Library there, so Gandaganza and I will look at whether we are gonna keep Nernie's or whether we go for the Book Library mod.
  10. Great, thanks. Glad to hear it's not complicated.
  11. You got my BIG thanks for sharing! Just wondering why you opted not to renumber FormIDs, since the author of the merge script says that they should be for 99% of cases. What I never understood is: What determines whether you need to disable renumbering or enable? If the mod contains scripts that refer to, or are referred by, specific formids? Also have you run into any issues while playing the game at those locations?
  12. Steam always seems to find 1 such file too on my system. I dont think it is the cause of the issue.
  13. Thanks, let me know if you encounter any hurdles on the way.
  14. I see. If you would be willing to make a REGS profile version, that'd be great! Then I will take a look at your esp too and see if anything catches my eye that hasn't catched yours. Double check is best :)
  15. Thanks. Yes, partially. But I figured out who I meant: redirishlord . On his profile he a has a couple of huge lists with esps he merged. Redirishlord if you are reading this, do you happen to have a merge that is specifically for REGS mods only?
  16. Ooh so that is what you meant with collapse functionality earlier in the thread. Thanks :)
  17. Edit: link doesn't work directly. Use this instead: https://forums.nexusmods.com/index.php?showtopic=834995 and search for Helgen, there are some answers there. I always use AS-LAL though so I never go through that intro scene again.
  18. Oh yeah also, is it possible for the ToC to include numbers in both the ToC and in the headings that are on the page? I think back when we made REGS we weren't able to do it, and only have numbers in the ToC.
  19. Just had a look at it... Nah. There is plenty of space (on my 1080p screen) for it to be horizontal. Also I would have it read Forum Thread or Support Thread just so that it sticks out a bit more. By the way can you use spoiler tages or something else so that the user has to click on it and then it opens a box with text? It doesn't seem to work for me at the wiki. Much like you can on forums: For instance, instead of the seperate REGS - SRLE compatibility section, I want to include these instructions at the REGS page but only if they are initially hidden and can be viewed by users when they click a box or something like a spoiler tag. If spoiler tage is the way to go, is it possible to change the titel from 'spoiler' to 'instructions for SRLE users'.
  20. Thanks for these reports and the suggestions, guys. I also got some news here: Gandaganza has benevolently offered his assistance with REGS, so please welcome him on the team! JK's Whiterun will most likely be implemented once it starts to look like he finishes.And I have 2 requests: In the absence of CJ2311, who will be missed dearly, we are in need of someone with CK knowledge, especially in navmeshing. CJ2311 learned it himself back in february by watching videos and reading some guides, so even if you do not currently have this knowledge but if you are interested in it, contact me or Gandaganza! I unfortunately do not have the time right now, or even the skills, to embark on this myself. Someone in this thread posted before which REGS mods they merged. But I cannot find it anymore. If you know who it is or if you have succesfully merged some REGS esps, please contact me in this thread!
  21. Nice stuff. I'd just keep everything horizontal though imho. I tend to skip over or not notice vertical text. Might just be me :)
  22. Keith I am still waiting for that document you promised with a collection of Boris quotes
  23. Have you tried the brighter version from the vividian installer? That should lighten up stuff a lot.
  24. I'd say it is sort of like an LOD mod. I've used it before without issues, but the smoke never seemed to fit any ENB I used. Not really a REGS mod imho, but it can be a good addition depending on you particular setup.
  25. There's actualyl a more recent guide (than the FNV pdf) for tes5edit conflict resolution, which you can find here: https://www.scribd.com/doc/235574282/Guide-to-Make-a-Patch-for-Solving-Conflicts It's not as complete, but it explains some things in a much easier for fashion for those just starting out.
×
×
  • Create New...

Important Information

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