Jump to content

Vonklinkenhoffn

Citizen
  • Posts

    18
  • Joined

  • Last visited

Everything posted by Vonklinkenhoffn

  1. Wow, this says so much for me, omg I've been living a modding-lie, kind of. In the beginning I used to be very thorough with my mod cleaning, but then I saw these mods and comments where people, and sometimes even the description pages for some mods said "do not clean this mod!" or stuff like that. I started fearing the cleaning. Now this however really puts things into perspective. I read the link for "There is no intentional ITMs", incredible. When you say "Clean every plugin that LOOT suggests to clean - ignore misinformation that cleaning any plugins is not needed, does not do anything or causes problems." That gives me relief, now I know I can safely clean all my mods that LOOT tells me to again. It was VERY useful to read that I should clean one at a time though, I didn't know. I will go ahead and see the vid about cleaning DLC with xEdit now. I learned so much important stuff just from your one respond I feel, thank you!
  2. Hi I've gotten the error message from DynDOLOD that deleted large references are found. I have looked this up in the DynDOLOD info page, and I quote: "In case deleted large references are found and the log reports Deleted references: yes, there will be a message prompt and log message, which lists all plugins that need to be cleaned. For example: Error: Deleted references found. The following plugins need to be cleaned: Update.esm, Dawnguard.esm, HearthFires.esm." Now, I just have to check in here to make myself absolutely sure that I'm about to do this correctly. I've always read that no matter what, I should never clean these particular esms, so I'm very uncertain when I get this message. I of course always listen to the experts, so if you would tell me that it is okay to clean these, than I will go ahead and do it. Are you certain I can do this? If so, I suppose I just clean it like any other esm/esp through qac in Loot? Thank you!
  3. Okay, I know I promised I would let you go, and I kinda did, but I just wanted to give you a heads up and at the same time ask if it's okay with you that I dropped your name and gave you some cred in an article over at my newly released mod? It's my first ever released mod, or rather a port of a mod that Zorkaz made and I ported it to VR using only the knowledge I got from you. I just wanted to pass it on. Here is the article, hope you find it to be fine: https://www.nexusmods.com/fallout4/articles/4985 And if you don't of course just let me know and I'll edit it in a heartbeat. Thanks again for all your help Sheson
  4. I see, so I guess if it all comes crashing down, I'll go over to x64 then. Thanks so much for all your help! I'll let you fly now 😄
  5. Great! but x64 though, should I actually just use the x64 version like in general perhaps? I have used 32, because xEdit recommended it in some pop-up message or something like that. I realize that was yet another question, but I'll let you go after that, I swear 😅
  6. It's very much deserved. Can I just ask one more thing, and I'm able to fly on my own; I'm going to do the whole renumber/header version thing on all the mods that needs it. I was thinking I'd just load up the entire mod list into xEdit, and just go ahead and do it, so that I can be sure to catch any and all patches etc. There isn't any problems loading the whole modlist when doing the renumbering/version thing, like I'm thinking of, is there?
  7. I'll do the same renumbering procedure for the other two mods that also had this issue, and I'll have some time tomorrow to test it out thoroughly. I'm so happy to hear the other warnings are of no concern! Thank you so much again for helping me! I bought you a couple of coffees for your trouble https://Ko-fi.com/home/coffeeshop?txid=9c5cd199-12d8-4a0e-b5aa-79ef3967e609&mode=public&img=ogiboughtsomeone
  8. Holy smokes it worked! You are a genious, thank you so much for helping me! I've really learned so much from this. Now I know what I did wrong, and I also know how to do it right for other mods as well, this is awesome. I did what you said, and the results from renumbering the "Fallout 4 AI Overhaul" mod looked very different. I have saved the messages logs from both the renumber/version change I did in FO4Edit, and the check I did after in FO4VREdit. I also Have the log from TexGen when I ran it to check everything. It did not give me any error messages this time, which is fantastic! I did however notice some warnings in the logs; "Warning: File contains duplicated top level group: GRUP Top "WEAP" I don't know if this is very serious or not, but I reckon it's not that serious since TexGen didn't bother to give a specific error message from it? Anyways, I have the logs here, if you would like to just glance over them to see that I really actually managed to fix it? FO4Edit Log: https://paste.ee/p/tfFqI FO4VREdti Log: https://paste.ee/p/HDOwN TexGen Log: https://paste.ee/p/TKZvG
  9. This was a very good idea! I haven't thought about this, thank you! I also see I've made a big mistake with the message log I uploaded though, I actually restarted after I had done the renumbering, and then I copied in that log. What I should've done was of course upload the same log from when I did the actual renumbering. Instead now you cannot see those messages, so the log I uploaded is kinda deceiving. I didn't think of that before I uploaded, sorry for "deceiving" you. I will anyway do what you suggested, I'll get to it as soon as I get the chance later today. At least it seems from the discord that how I did renumbering was correct though. Only thing is apparently any dependent patches will brake when I renumber a mod, but I've read somewhere that if I also load the patches into xEdit when I do the renumbering, then the patches would be included and it should be okay. I hope to get more feedback from the discord on this matter too.
  10. Hi again. So I downloaded the latest xEdit from discord, did the "renumber from" for the formIDs and set them from 000800, then I edited plugin version to 0.95. Unfortunately that didn't do much difference. I feel like this is never going to get fixed, I'm starting to think that maybe these mods with these error messages simply can't be used for VR at all. At least I now understand better the connection between TexGen and xEdit, so thank you so much for the knowledge! I have at least the latest background message log here though, in case you would have the time to look over it if there would be anything new, but I doubt it. I appretiate your efforts so much! I will take this to the xEdit discord as well. https://paste.ee/p/yGBUJ Best Regards!
  11. I see, that's very good to know! Yes indeed, I've asked the question about this on the xEdit Discord for FO4 now, so crossing my fingers someone will have some good intel for me there. So maybe, if I'm lucky, then when I test TexGen with the newest xEdit later today, it might be working better, if I misunderstand you correctly so to speak. I'm very much hoping so. Thank you again for all your help, I appreciate it so much!
  12. I see.. ah, yes it's from xEdit 4.0.3, sorry I didn't think you needed the other stuff with where it was located and such. So you're saying that the latest TexGen is based on the latest xEdit, which would be 4.1.5? I haven't downloaded that one yet because it says "experimental", so I figured I'd wait it out. I'll go ahead and try it as soon as I get the chance today. I also know that the original plugin as it is now has a header version of 1.0, which also would mean that there would be records that needs to be changed as well, doesn't it? I've learned that this has to be 0.95 for VR. But I also have to change the records before changing version header. I've previously just done this with the script "Renumber FormIds from..." option and set it to 0008000. I haven't done anything with the current version of the mod though, I just wanted to keep it "clean" so I could see if TexGen reacted to it or not without my meddling. I can try and edit it again with the latest xEdit too and see if I get a different outcome.
  13. Ah dang it... I was hoping there might be some light in the end of the tunnel for me finally. Well, now I've downloaded xEdit 4.0.3 and reverted the plugin back to the original ESP. What was strange was that xEdit didn't seem to have any issues, so I ran TexGen, but then the error message came again. I then went into xEdit to check and this time the log was different, it suddenly had these errors again, however it doesn't seem to be the same kind of errors. Originally the errors were about records being overwritten, but this time it seems to be "Warning: File contains duplicated top level group:" kind of messages. I don't know if they are the same kind, but they don't seem like it. I just wonder though, why does TexGen give the same "records bein overwritten" error if xEdit does not? Here is the new log from xEdit 4.0.3 and the original plugin: https://paste.ee/p/SemeG
  14. I see, so there might not just be the mod that is faulty, it can be other things as well, like my xEdit version as you say. I will try to download a different version and see if that helps. I was just a bit scared to just go ahead and use the mod after I got the error message, on the support page it sounded so clear that I shouldn't use "a broken mod" and such. Maybe it is safe after all then, I hope I will get a different result with a different version indeed. Thank you again!
  15. I see, I didn't know that, thanks for the clarification! I have loaded it up in xEdit but haven't seen any error messages, however I'm also not exactly a very experienced user when it comes to xEdit. I didn't understand I had to check for this in xEdit, I'll go se if I can find a background loader log message right away. I wasn't too sure where I would find the output, so I just copied the background loader in here: https://paste.ee/p/EQ9hO I hope it will provide some insight into this. Thank you again for your help!
  16. Sorry, but I didn't provide it because I already did in the first post I made. It's the same error message still you see. It's not from xEdit however, it is TexGen that comes up with this message. xEdit doesn't say anything actually, not as I can see. In fact, everything in my MO2 load order as well as from xEdit seems totally fine for me. It's not until I try to run TexGen I get error messages. I will paste in the error message again here: "TexGen [Main Instruction] Record [DOOR:00000004] in file Fallout4.esm is being overridden by record [GMST:00000004] in file Fallout 4 AI Overhaul.esp. [Content] These errors can cause CTD and other serious issues and need to be fixed." So you see, this appear to have nothing to do with xEdit, however I just use xEdit to further try and see whatever TexGen might be talking about. So far I haven't been able to fix this. TexGen also provides a link to the guide for this issue, which is what I've been following when I've been trying to fix the issue. The link TexGen gives me is this: https://dyndolod.info/Messages/Record-Is-Being-Overridden So this is all TexGen finding an issue, I have tried using xEdit only as a tool for alleviating these issues, but it is only TexGen that reports on this apparent issue. This is also why I have to ask you about it, because nowhere else have I seen or heard about this, only from TexGen. Also if I press "Ignore" in the TexGen menu, it just pop up another message with the same issue with the same mod, but a different record. It apparently has problems with a lot of records in that mod, I counted over 20.
  17. Thank you for getting to me so quickly, I really appreciate it! The part I mention about xEdit is just to inform of the steps I've taken to try and solve my issue. The issue itself stems from TexGen giving the error message, that's why I ask here. In the xEdit Disc they send TexGen questions here. I'm aware that ESL is not supported in VR, that's why I got the mod author to upload a no forms compacted ESP version of the mod. The mod in question is "Fallout AI Overhaul" btw. However, this didn't seem to solve the problem, even though the mod is not an ESL, but a regular ESP, TexGen still gives the same error. This is when I went into xEdit and tried to further fix this myself, by "Renumber formIDs from" 000800 and change the header version too, as I explained earlier, since I also know that VR doesn't support header versions of 1.0, but it has to be set at 0.95 and formIDs changed too. So I did these things accordingly, and rerun TexGen in hopes that it now should run without issues, but it didn't. The same error message still comes up. At this point I can't see what the problem is, the mod is clearly an ESP, the formIDs and header version are within what VR needs too, but TexGen still doesn't like it, so I was hoping you'd might give some insight into what else might be wrong?
  18. Hi, I got the following error when trying to start TexGen, it's happening in 3 mods I have installed: "TexGen [Main Instruction] Record [DOOR:00000004] in file Fallout4.esm is being overridden by record [GMST:00000004] in file Fallout 4 AI Overhaul.esp. [Content] These errors can cause CTD and other serious issues and need to be fixed." I've read the provided info on the support page for DynDOLOD, and I see it says amongst other things that "In the best case scenario these errors cause CTD. In the worst case scenario these errors cause mysterious and hard to troubleshoot issues only once the affected records are used dozens of hours into the game." What I find a bit strange though, is that on the Nexus page of these mods, there's no mention of any such issues from other users. I don't understand how this can be. I did let the mod authors know, and one responded that this has to do with the ESP being ESL flagged, when I can't use ESL because I play in VR. The explanation was that "some mods you can flag and unflag without problems but this has forms compacted from the CK to allow it to be ESP-FE. If that is removed it will try looking for the compacted form IDs that can cause those serious issues to happen." The mod author was kind enough to upload a no forms compacted ESP file, for VR users like myself. However, after testing it yet again with TexGen, it still gave the same error message. I then loaded the mod into xEdit and noticed that the Header Version was at 1.0, I believe for VR it need to be 0.95. I know that in order to change that, I had to change FormID first, so I right clicked the mod and selected the "Renumber formIDs from", I've heard that is the way to do it, but I'm not sure about what it should "start from", I believe it is 000800, but I'm not sure. Anyway I just tried 000800 and then I set the Header Version to 0.95 after and saved. Unfortunately that didn't do much for TexGen. Now I am at my wits' end, I have no idea what to do next. Do you think I did it wrong? Could there be something else going on? I have notified the mod author again, but have yet to see what new solutions may come.
×
×
  • Create New...

Important Information

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