PhxFuryKnight
-
Posts
17 -
Joined
-
Last visited
Everything posted by PhxFuryKnight
-
Thank you so much for the Alpha 115 update! DynDOLOD is working normally again.
-
Sorry, here it is on this website as it is just over 7MB! https://ufile.io/vhz4uq0x
-
Same issue for me, once again. I have been at this all night. Attached is my current log from my last run about 30 minutes ago, as well as my DynDOLOD.esm that has been generated, and that has apparently also added DynDOLOD.esp as a master by mistake. DynDOLOD_SSE_log.7z DynDOLOD.esm.7z And the .esp to view, could not meet max file size, so it's on a seperate post. DynDOLOD.esp.7z
-
Thanks. Now it's 3DNPCs I am worried about, because there are roughly triple the missing scripts in that mod than there are in the synthesis patch. x.x I have chosen to forgoe DynDOLOD for the time being until I can resolve this issue. Edit: I have found that the 3DNPC Update file did not get properly merged, it simply replaced the main file, hence THOSE missing scripts. I will also correct Synthesis and try this again now.
-
https://ufile.io/lt77q3hz Oh, here is another upload of two screenshots from SSEEdit, showing that it is entirely your plugins at fault for a cyclical error, because you can see them referencing each other without an ending. I could take more screenshots of this, but I think you understand me by now.
-
I have re-ran TexGen and DynDOLOD, using DynDOLOD 3 Alpha 114 as previously stated, using the pathway "C:/DynDOLOD" for my executables, and I have still received the same error when I go to sort your plugins within LOOT. https://ufile.io/jb23w8ep Above I have provided both the DynDOLOD_SSE_Debug_log + DynDOLOD_SSE_log as stated in the OP. Just like I did the first time I posted this, but this time with the debug side. There is no bug report.txt within the DynDOLOD folder. https://ufile.io/ypnqs8oe Here is the error I am seeing within LOOT. Both files have added each other as masters automatically. Your turn.
-
You haven't listened to a word I have said since I got here. I am regenerating now with DynDOLOD located in C:/DynDOLOD, very simply. Will update soon!
-
You have yet to describe to me the simplest answer that I have asked a question about: Why would DynDOLOD.esm ever make DynDOLOD.esp a master? This is all I am here for. Literally the only thing I have asked. Your tool runs successfully where it sits, and I will get the same result if it is installed in "C:/DynDOLOD". You are simply dodging the problem, when if you scroll to the bottom, you will get the confirmation for the question that you have asked me. DynDOLOD completed without error. I have the game installed through Steam, and the Stock Game route is a well-known way to organize the game files as spoken on the wabbajack page. This is the first time this issue has ever happened to me, and did not happen to me 24 hours ago when I regenerated DynDOLOD. I do this a lot, I know you're wrong. lol.
-
Question 1: yes Question 2: yes Question 3: no, and it succeeded without error. I have already taken these steps. The issues lie within your plugins, and nowhere else. DynDOLOD.esm has added DynDOLOD.esp as a master, and this is causing a cyclical interaction across 2 tools, so you are at fault. Here is proof that DynDOLOD succeeded without error. DynDOLOD_SSE_log.txt
-
Hello!! I don't really have any error log, but for some reason DynDOLOD.esm has added DynDOLOD.esp as a master while it was generating itself, and I can't get LOOT to sort these plugins, due to a cylical interaction detected between the two. I just used this yesterday without issue. My esps + esms are at 243 including DynDOLOD's plugins, and I have never had this issue before. I received it while I was still using DynDOLOD 3 Alpha 111, and since then I have updated to DynDOLOD 3 Alpha 114, the latest version, and have double checked that LOOT is in fact up to date, and am able to sort plugins normally without DynDOLOD present. I even took the liberty to clear ALL metadata from the LOOT tables in case it was user error. I wasn't that. I am also unable to open either esm nor esp in the creation kit as it causes it to crash immediately. I am not able to load either plugin in SSEEdit due to the plugins containing cyclical references. What can I do about this new problem?
-
Nevermind, I had tried 3 times, restarting my PC after the first encounter, and then again after the 3rd encounter with this same error message. On the 4th try, 2 computer restarts in total, it finished flawlessly?? xD Thanks man!
-
"The process cannot access the file because it is being used by another process" error when running on Wizard Mode - High Settings. I do not have any other programs open besides Mod Organizer 2 to launch DynDOLOD. DynDOLOD_SSE_log.txt
-
Yeah, the problem is that there AREN'T errors. I came home after letting DynDOLOD run for 9 hours straight, calling someone to check for crashes (error messages) every 2 hours, and when I got home Alpha 111 had been frozen at the 3 hour mark within the main window, approximately on world 3 out of 22. I know there may be an issue with crapware or whatever, but I was having those OpenGL errors on the previous two drivers. No.. I cannot install 22.5.1 on a 7900XT, it is incompatible. So the newest version of DynDOLOD with the newest version of Adrenalin drivers has the ability to RUN DynDOLOD, but it doesn't quite have the ability to finish with this configuration.
-
I have successfully used an AMD 7900XT to generate DynDOLOD in just 27 minutes for an 830 mod load order. The problem was with Alpha 111, as I have successfully used 2.98 to complete this process. This narrows it down to the ongoing OpenGL issues with the latest AMD Adrenalin drivers, the ones that are ONLY for the 7000 series, and their OpenGL compatibility with your software. The only other potential issue was trying to use Folkvangr, Origins of the Forest, and Cathedral 3D pine grass, which all have Root Blocks of NiNode by default. I know there is a process to bypass this and convert them to BSFadeNode, but pre-caching your grass doesn't allow it to be loaded by the game engine anyway, preventing any CTD's that this website says they may have in this format. Wish I had a log for you, but my suggestion is to look into OpenGL on AMD drivers 22.2.1, 22.2.2, and 23.1.1. (The 7000 series-specific drivers). Thanks so much!
-
I'm having a huge issue with Alpha 111. I am able to process Texgen, but it now takes 1 hour and 17 minutes, versus 20min before I added parallax to the game. Texgen completes without errors. DynDOLOD on the other hand, lists missing meshes and textures from Beyond Reach and Beyond Skyrim - Bruma (arnima worlds and bsheartland/cyrodill respectively), as well as NiNode Root Blocks on QW's Grass Patch 2 found on nexusmods. I cannot get these textures or meshes because they simply don't exist on the mod author's respective pages. I run it anyway. DynDOLOD proceeds to generate Object LOD textures as normal, but it moves a grueling pace. It takes around 45 minutes to process all records and begin Object LOD for Tamriel, and then it takes around an hour for the basic Object LOD textures to compile before it tries to begin the Tamriel world itself. This would be perfectly fine, except I have spent two nights now just letting DynDOLOD run, separately, once per night, and each time it will freeze around the 3hr mark, sometimes at the 5hr mark. I have deleted all DynDOLOD output each time, but I cannot provide the logs because I have uninstalled this version. Do you recommend I try regenerating a grass cache, DynDOLOD mode = 0, with DynDOLOD 2.98 instead? System specs: 5700X 7900XT 32GB 3600MHz RAM 20GB-40GB page file.
-
You already solved my problem when someone else made a post with the same error on a 7900XTX. You uploaded a stitched.frag file which I used to successfully use Dyndolod on the latest Adrenalin driver.
-
Helloooooo! Does anyone know any workarounds for generating LOD through DynDOLOD with the new 7900XT graphics card? As suggested, AMD Adrenalin Driver 22.5.1 is unsupported for this specific GPU, as it will not even install. I continually receive the OpenGL Invalid Operation error with this graphics card, but it did work when I had a Strix 3080.
