*** This mod is made with the new Creation Kit and & xEdit. This means it has a new plugin header and won't work on older versions of the game. If you don't run 1.6.1130+ Skyrim.exe, you have to install Backported Extended ESL Support.
If you want to mess with it in xEdit, you'll need the newest version 4.15c from the xEdit discord.
I apologize upfront for being a continued annoyance, but, this mod, as well as every update or mod you've released post Jan 19th, 2024 show as incompatible with VR; with our ESL support mod, xedit 4.1.5c and 4.1.5d both show 505 errors--mostly HITME's. I'm not sure what you are doing differently from everyone else, I put together a group of VR users to scan their mod lists with xedit and this really only affects your mods, and two other individual mods: Abstract Falkreath and Skyrim Food Expansion. It is quite odd. I only bring this up once more because I love your work and really want to use your new mods in VR where they really shine.
I'm doing it the way it was recommended using new CK/xEdit, but let me consult the smarter people on discord and see if I can get u a better answer. Hang tight
From the non-VR side, xEdit doesn't show any issues with any of the mods mentioned in your post. Most mod authors aren't taking advantage of the expanded record range for .ESL-flagging, which is probably why you're seeing this issue with only select mods. Gutmaw's recent releases (including this mod), as well as Abstract Falkreath and Skyrim Food Expansion, all use records from the 000 to 7FF range; if you're using the VR ESL support mod, that shouldn't be an issue, as xEdit should be detecting the .dll and enabling ESL support, but it seems like something there may not be working as intended, given your experience. As the mods themselves appear to be fine, I'd suggest raising this issue on the xEdit server.
(FWIW, testing on an older version of SSEEdit (4.0.4) does show the HITMEs you referenced, which makes sense, as that version didn't support the expanded range.)
Thank you, I really appropriate it. Again, I apologize for being a nuisance. I figured it would take a few months to iron out all the complexities with the new header id and VR esl support. It may be the biggest breakthrough ever achieved by the Skyrim modding community--at least neck and neck with CS. Everyone is doing such impressive work at such a rapid pace, it was inevitable that we'd hit a few bumps along the way.
And DrMonops, I tried to post on their discord, it wouldn't let me. I posted here as a last recourse. I don't blame them though. I could only imagine the amount of insanity they'd get flooded with if they left things open to the public. You are right though, there are no errors in SE, or if we (VR Users) spoof SE. I did extensive testing on this and enlisted others to verify my findings, because I thought that I had messed something up porting the AE DLC to VR. So it is most likely either an error with how xedit and the vr esl dll are interacting, or some other VR specific bug in xedit. They are quite clear about 4.1.5 being extremely experimental, but discerning that is also vastly above my level of modding capabilities. Xedit is like magic to me, the people who work on that are all straight up geniuses.
I am happy to report, it was a bug in xedit and they have fixed it with 4.1.4f! I'm so hyped to finally get to check these out! Sorry for being such a pain!
*If you want to mess with it in xEdit, you'll need the newest version 4.15c from the xEdit discord.*
Hi, i really like your mod. The only thing that is a bit uncomfortable is that after installing your mod you definitely need the xEdit version from Git, or you have to disable the mod if you have to look something up (and to remember that this is the mod that is causing the access violation)
Is there another solution (not using your mod does not count)?
Any mod that uses the new Skyrim that takes advantage of the new esl range will need the newest version of xedit. So u can a avoid it for now, but more and more mods will end up requiring it. So just bite the bullet now :)
3DNPC does a weird thing. It replaces Drelas with another 3DNPC character until that quest is completed, then the real Drelas is brought back and can be killed.
so to do it legitimately, u need to first complete the 3DNPC quest, then kill the real Drelas to get his house.
I was worried about that! I'll see what I can do then. if i can't resurrect him properly well...I already changed ownership of everything in the house and I can technically sleep in the basement lmao.
I like the redesign. The new furnishings lean into the fact that Drelas is a Dunmer, so we get a lot of changes that reflect this. This is great "environmental storytelling!" The fact that you can harvest many of the ingredients inside rather than just take them also raises the value of the home. I'm wondering about something in the description however, that Hearthfire ingredients are plantable outside. I didn't see any patches of soil available, and I've never seen way to replace a cabbage with an imp stool (for example). Did I miss something? Being able to plant ingredients is a big selling point of the home.
Here's a thought - an Ash Guardian outside the home.
EDIT: Everything turned out to be fine with the plugin, false alarm ^.^
Looks really great, but is everything alright with the plugin? I get ton of errors when i try to open it in xEdit. I ain't no expert, but it looks like you injected references into Skyrim.esm. Whenever i see such construction, the references are injected into Update.esm, so that may be it? Either way, you might wanna take a look at this in case it's something serious.
Yes, pre 1.6.1130 Skyrim had FormIDs <800 reserved by the engine, and as such xEdit pre 4.1.5c treated them as such. New 1.71 HEDR changed that behavior to allow FormIDs to be <800 and xEdit <4.1.5c assumed they were engine reserved.
21 comments
If you want to mess with it in xEdit, you'll need the newest version 4.15c from the xEdit discord.
(FWIW, testing on an older version of SSEEdit (4.0.4) does show the HITMEs you referenced, which makes sense, as that version didn't support the expanded range.)
And DrMonops, I tried to post on their discord, it wouldn't let me. I posted here as a last recourse. I don't blame them though. I could only imagine the amount of insanity they'd get flooded with if they left things open to the public. You are right though, there are no errors in SE, or if we (VR Users) spoof SE. I did extensive testing on this and enlisted others to verify my findings, because I thought that I had messed something up porting the AE DLC to VR. So it is most likely either an error with how xedit and the vr esl dll are interacting, or some other VR specific bug in xedit. They are quite clear about 4.1.5 being extremely experimental, but discerning that is also vastly above my level of modding capabilities. Xedit is like magic to me, the people who work on that are all straight up geniuses.
Hi, i really like your mod. The only thing that is a bit uncomfortable is that after installing your mod you definitely need the xEdit version from Git, or you have to disable the mod if you have to look something up (and to remember that this is the mod that is causing the access violation)
Is there another solution (not using your mod does not count)?
happy modding
the Version from Git runs welll for me (the 64 bit)
I love Drelas cottage
drelas is dead. i have interesting NPCs, so i did so by console since he's essential by default.
how or when does the "ownership" of the house transfer to the player? or is it supposed to? do i need to do...something else?
Oh yeah
Skyrim AE 1.6.640 (BEES installed) FWIW
so to do it legitimately, u need to first complete the 3DNPC quest, then kill the real Drelas to get his house.
Thank you!
I'm wondering about something in the description however, that Hearthfire ingredients are plantable outside. I didn't see any patches of soil available, and I've never seen way to replace a cabbage with an imp stool (for example). Did I miss something? Being able to plant ingredients is a big selling point of the home.
Here's a thought - an Ash Guardian outside the home.
Looks really great, but is everything alright with the plugin? I get ton of errors when i try to open it in xEdit. I ain't no expert, but it looks like you injected references into Skyrim.esm. Whenever i see such construction, the references are injected into Update.esm, so that may be it? Either way, you might wanna take a look at this in case it's something serious.
Now i wonder what have caused this. Is that because of extended ESL range? Thought that one was fixed in xEdit 1.5 already