Jump to content

sheson

Mod Author
 View Profile  See their activity

  • Posts

    13,181

  • Joined

  • Last visited

  • Days Won

    431

 Content Type 

Everything posted by sheson

  1. sheson
    Those EditorID changes seem to be to cell records and not wrld worldspace records. Occlusion generation uses the record and data from the winning plugins. Make sure the winning plugin contains all the desired records, data and conflict resolution you desire. Occlusion generation will only update the records and data that are relevant for LOD occlusion and nothing else. Use the appropriate and specialized tools or scripts to merge and conflict resolve the entire load order. Feature requests should go towards tools that already do similar or related work to the desired feature.
  2. sheson
    Great. Now generate terrain LOD meshes for all worldspaces to see if it has no errors as well.
  3. sheson
    Try generating a new LOD patch from scratch instead of trying to update existing plugins.
  4. sheson
    Download this .NET 6 version of LODGenx64 https://mega.nz/file/gIBgjTTL#cLvVIkbIHdN9qNdoefVhvl9BDQfOrKh5KWbdQxHiIPE Rename it to LODGenx64.exe and place it into the Edit Scripts folder. Then do the same run as before, delete old logs, run xLODGen and just select the one worldspace and terrain LOD meshes selected. Once the LODGen part starts to show in the messages log you will see it reporting .NET Version: 6.0.x instead of .NET Version: 4.8 Upload new FNVLODGen_log.txt
  5. sheson
    It might be possible this happens because the LOD patch is outdated because the load order changed or plugins got updated. You or a mod you installed added a mesh mask rule that instructs the full model of chest01\chest01 and similar to be used for LOD. I suggest to remove those rules, then generate LOD again. They also do not really make sense in the grand scheme of things. The Papyrus log does not show any log messages from the DynDOLOD scripts registering the MCM initializing. I suggest to investigate and fix the cause stacks being dumped. That many script errors make me wonder if maybe some requirement is missing or the quality of some mods.
  6. sheson
    https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text Copy and paste text instead of making screenshots of text. Text can be indexed and searched so posts can be found more easily. If the option Copy message to clipboard is available on a message prompt, use it to copy and paste the text. Screenshots of text means it can not be searched, copied or pasted. Screenshots of text means the text can not be read by screen readers. Screenshots of text makes it hard to read on small screens. Text needs less space compared to images. Copy pasting text is easier to do than taking screenshots and uploading images. Download this test version https://mega.nz/file/hZpkTQIb#1citFVdLgiaQcWzfVQxZZpp3Clw6gC25mRDqhHuU8QU
  7. sheson
    An OpenGL error is a different error than the range check error from other earlier test version. Delete all files in the log folder, run new test version from this post https://stepmodifications.org/forum/topic/20153-error-opengl-framebuffer-objects-unsupported/page/2/#findComment-282545, upload new logs.
  8. sheson
    https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text Copy and paste text instead of making screenshots of text. Text can be indexed and searched so posts can be found more easily. If the option Copy message to clipboard is available on a message prompt, use it to copy and paste the text. Use the Texconvxe64.exe form this post https://stepmodifications.org/forum/topic/20153-error-opengl-framebuffer-objects-unsupported/page/2/#findComment-282545
  9. sheson
    Try with the test version from this post https://stepmodifications.org/forum/topic/20153-error-opengl-framebuffer-objects-unsupported/page/2/#findComment-282545
  10. sheson
    What proton version are you using? Have you installed dotnet48 through winetricks or are you using mono (which version)?
  11. sheson
    Remove all old logs and bugreport.txt. Run this test version https://mega.nz/file/hZpkTQIb#1citFVdLgiaQcWzfVQxZZpp3Clw6gC25mRDqhHuU8QU If there still is an exception, upload new log, debug log and bugreport.txt (if it exists).
  12. sheson
    Thanks. Is there really no bugreport.txt?
  13. sheson
    Run1 with the test version shows this error message: [02:56] Range check error while processing E:\Games\Mods\Tools\DynDOLOD\TexGen_Output\textures\terrain\lodgen\strongholds - largashbur.esp\dlc01ancestorgladetree01_00000c52 That is now a different problem compared to the OpenGL framebuffer error. As explained in the post https://stepmodifications.org/forum/topic/20153-error-opengl-framebuffer-objects-unsupported/page/2/#comment-282545 that has the link to the test version, if there is a problem with the default settings, add GLDebug=1 to TexGen_SSE.ini. If there still is a problem with that setting added, upload that TexGen log and debug log and bugreport.txt in case it exists.
  14. sheson
    Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Posy-Logs which entire DynDOLOD debug log to upload as requested.
  15. sheson
    https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text Copy and paste text instead of making screenshots of text. Text can be indexed and searched so posts can be found more easily. If the option Copy message to clipboard is available on a message prompt, use it to copy and paste the text. https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs When making posts to report problems or to ask any questions, always zip and upload or paste these entire log files from the DynDOLOD Standalone folder to a free file upload service or text sharing service: ..\DynDOLOD\Logs\[DynDOLOD|TexGen]_[GAME MODE]_Debug_log.txt Upload the entire debug log. A plugin that is not flagged ESM can not be a master or load before a plugin that is flagged ESM in the game. Something is going wrong with the internal patching process. Provide a link where Parallax TXST Fixes.esp can be downloaded.
  16. sheson
    The log is saved when the tool closes. We will have to try to troubleshoot one problem at a time. Delete all old logs. Download this test version of LODGenx64.exe https://mega.nz/file/wVhggDYQ#08l3-DoknmG_Np3A-sseu_GQjDPg77P4rNZzExBOwmg and replace the one in the Edit Scripts folder. Start xLODGen, only select WastelandNV and select to generate terrain LOD meshes only. Do not check to generate any terrain LOD textures or any object or tree LOD. Upload new FNVLODGen_log.txt.
  17. sheson
    There will be more than one cell having the same problem. Generate LOD / Occlusion.esp with this DynDOLOD test version https://mega.nz/file/BQZT1IIA#50PA6b--RUG3WL3VrE1CJ3sbjWWJ1g5ROXECOyqoPdI as it should properly forward the Parent->Child cell updates.
  18. sheson
    Download this test version https://mega.nz/file/0Jwj1SbQ#hRS13oCP3Wz1_owUhBLGmy-bOa2tiC-jbHLOugVmy8E of LODGenx64Win.exe and replace the one in the Edit Scripts folder. Then generate LOD or Execute LODGen for Tamriel in Expert Mode to just update the object LOD meshes. See https://dyndolod.info/Help/Expert-Mode Report if it makes any difference.
  19. sheson
    The plugins being broken and the OpenGL error are different unrelated problems. Now that you know which plugin is broken and needed fixing, download the latest test version from that post and run it with default INIs.
  20. sheson
    If you have a problem with TexGen reporting OpenGL: framebuffer objects unsupported, then download the latest test version from this post https://stepmodifications.org/forum/topic/20153-error-opengl-framebuffer-objects-unsupported/page/5/#findComment-283259 and run it without any TexGen INI changes as it explains to test if it works.
  21. sheson
    You did not upload the xEdit log. You seem to be using an unreleased and older test version of TexGen. The message itself names the wrong plugin, while the last plugin loading before the error is actually Arise - Son of Cyrodiil (Standalone).esp. The xEdit log probably reports an invalid object ID for it.
  22. sheson
    https://dyndolod.info/Help/Grass-LOD#https://dyndolod.info/Help/Grass-LOD Error reading grass [worldspace] [x,y] Delete the *.CGID file. Load the game, open console and type "cow Tamriel x y" without the quotes and the values for x and y from the *.CGID filename to load directly into the cell. No Objects In Grass should then generate the file anew, which hopefully can then be read next time DynDOLOD is run to generate LOD. https://dyndolod.info/Messages/Exceptions#Error-reading-grass-worldspace-x-y There is a problem reading a grass cache *.CGID/*.GID file. It is probably corrupted and should be regenerated. It could also be in the vanilla Skyrim LE format (Skyrim SE vanilla BSA ship with the Skyrim LE format, hence the vanilla grass cache files do not work). Find the file in the ..\Data\Grass\ folder and delete it. The filename is of the form [worldspace]X[x]Y[y].CGID with leading zeros to pad up to 3 digits. Start the game, open console with ~ and type cow [worldspace] [x] [y] to load into the worldspace and cell so that No Grass In Objects generates the *.CGID file on-demand. Delete ..\Grass\arnimaDUPLICATE003x0044y0016.cgid Start game, open console and enter cow arnimaDUPLICATE003 44 16 to generate the cgid file anew. Generate LOD.
  23. sheson
    Get this test version of xLODGenx64.exe https://mega.nz/file/8Y4iULAT#XrL2rY4lHRkXd1x8u_fqXCQwhaBNZMHqd_n49KtY8dI and upload new logs.
  24. sheson
    Upload a LOD level 4 and 8 *.BTO that has such waterfalls in them.
  25. sheson
    See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs and https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots
×
×
  • Create New...

Important Information

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

  I accept