Jump to content

plgdctr

Watcher
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About plgdctr

  • Rank
    Citizen

Contact Methods

  • Discord
    plgdctr

Profile Information

  • Preferred Pronoun
    He/Him/His/Himself
  1. Seems that it worked I guess you will include this into the next DynDOLOD version?
  2. Hell yes, it worked! I was able to run TexGenx64 and DynDOLODx64 successfully You did it! Finally I finished Lexy's Guide Would be interesting to hear, what you did to the test version, if you wanna tell.
  3. When switching to slod03.nif it raises from ~400MB VRAM base usage to ~1100MB. When switching from slod03.nif to dlc01icewalllod.nif or another simple nif it falls back to ~450MB.
  4. Yes, it is the one included in Adrenalin 21.5.2 from June 2021. Isn't it weird, that the process reaches 98% of my 16 GB RAM? Is there a possibility to reduce the size of slod03.nif? It is the biggest file with round about 16 MB, maybe we could split it into 2 smaller files to come over the RAM issue?
  5. Ok, it seemed that my AMD Software didn't update itself for about a year. I updated it, it downloaded the latest driver, but unfortunately the "not enough RAM" while processing slod03.nif still appeared.
  6. Oh yes, you're right. I also tried DynDOLOD Standalone 3.00 Alpha-44, same result. From windows 10 device manager I have a AMD Radeon R9 200 Series (4GB Sapphire Radeon R9 290 Vapor-X OC) with a driver version 27.20.1034.6 from 21.08.2020 without any updates available. The Radeon Software itself has some different information: driver version: 20.10.35.02-200821a-360470C-ATI Direct3D® Version: 9.14.10.01443 OpenGL® Version: 26.20.11000.13596
  7. The latest standalone version DynDOLOD Standalone 2.96 beta does not contain any ..\Edit Scripts\DynDOLOD\Render\Objects\lod\ files. There even is no Render folder. I tried to replace these 4 files with the ones I already downloaded (latest alpha) and sometimes TexGen was able to process some of them. BUT then, after a few tries, I got a new error message, that there is not enough RAM, so TexGen had to exit while processing slod03.nif. bugreport.txt: https://paste.ee/p/n0fjI
  8. It worked, TexGen finished successfully! thank you very much for your help! I had to remove rtbuildingslod01.nif rtbuildingslod02.nif slod03.nif ridgedmossstone08lod.nif Are there any sideeffects from removing them? I guess, the files have any reason for being processed, don't they?
  9. Oh yes, it is. Didn't see it cause it was in the directory above. https://paste.ee/p/9KMQ9
  10. Both are here: https://paste.ee/p/rav6V
  11. I got a problem with DynDOLODx64. After running TexGenx64 (which created textures inside my specified TexGen Output folder), copying the TexGen Output folder to MO2/mods/ and activating the mod inside MO2, DynDOLODx64 does not find these textures. It stops with the message "No TexGen output detected. Consider generating updated object LOD textures with TexGen first." https://paste.ee/p/PUp2c It seems that TexGenx64 stopped correctly with the exit dialog. I reviewed my RAM usage while TexGenx64 ran and it raised up to 97% in about 2 minutes when it finished.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.