Jump to content
  • 0
Sign in to follow this  
ilkay01

FO3LODGEN help

Question

Hey guys

I need some help using FO3LODGEN through MO.I followed the S.T.E.P. instructions but after i select all available worldspace and start generating lod it begins to generate the first worldspace then after 30 seconds it stops and the LODGen options pop up again

here is a picture

fo32.jpg

 

Any idea whats the problem?

Edited by ilkay01

Share this post


Link to post
Share on other sites

6 answers to this question

Recommended Posts

  • 0

Strange, looks like there is some problem running lodgen.exe (command line is shown in the last log lie), make sure that it exists.

Share this post


Link to post
Share on other sites
  • 0

It exists and it generates some txt files but thats all it doesnt finish the process in FO3LODGEN

if i press ESC it gives an error and skips to the next worldspace

here is a pic

Capture.jpg

Edited by ilkay01

Share this post


Link to post
Share on other sites
  • 0

Something prevents LODGen.exe from running in your system. Try to execute just that command line outside of FO3LODGen since all necessary data is already exported and prepared for lod generation (execute from within MO of course).

Share this post


Link to post
Share on other sites
  • 0

It just generated the log file

The weird thing is the log

============================================================
Skyrim Object LOD Generator v0.8
Created by Ehamloptiran and Zilav
Updated by Sheson

Log started at 11:33
Nothing to do
Log ended at 11:33
============================================================
Skyrim Object LOD Generator v0.8
Created by Ehamloptiran and Zilav
Updated by Sheson

Log started at 12:06
Nothing to do
Log ended at 12:06
============================================================
Skyrim Object LOD Generator v0.8
Created by Ehamloptiran and Zilav
Updated by Sheson

Log started at 12:07
Nothing to do
Log ended at 12:07

It doesnt matter if i start it from FO3LODGEN or straing from MO it writes nothing to do in the log

altough if i start it from FO3LODGEN it generates LODGen.txt and LODGenAtlasMap.txt and if i start LODGen.exe straight from MO it doesnt generate those.

Edited by ilkay01

Share this post


Link to post
Share on other sites
  • 0

Looks like i managed to fix it

The problem was the location of the FO3LODGEN folder.

I was using it in the same directory as FO3edit but now that i put it in the fallout 3 root folder it works.

Share this post


Link to post
Share on other sites
  • 0

I'll revise the guide to make it clearer that if it is installed as a separate mod it should be in the the same directory as the FO3Edit or xEdit folder but not in the FO3Edit or xEdit folder itself. As noted in the guide, the recommended way of using does not require a separate folder, it is just entered as a separate executable in MO with different parameters than FO3Edit.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Similar Content

    • By sheson
      This is a beta of [FNV|FO3|FO4|FO4VR|TES5|SSE|TES5VR|ENDERAL|ENDERALSE]LODGen/Edit with terrain LOD meshes and textures generation.
      This is for experienced mod authors and users that know how to use xEdit, xLODGen or DynDOLOD already.
      Installation and Setup
      Download
      xLODGen beta 83 - based on 4.1.3g
      Unzip into a dedicated folder outside of any game and Steam folders or special Windows folders like Program Files.
      (Pro users can merge with existing xEdit installation. Make sure to overwrite older LODGen.exe/LODGenx64.exe TexConv.exe/TexConvx64.exe in Edit Scripts. All other files with the same filenames are the same as the latest version of xEdit.)
      Rename xLODGen.exe to [game mode]LODGen.exe (TES5LODGen.exe for example) or start with command line parameter -fnv, -fo3, -fo4, -fo4vr, -tes5, tes5vr, -sse, -enderal, -enderalse
      Use -o:"c:\OutputPath\" command line parameter to change where files are generated to, default is the game folder. Use this if a mod manager with a virtual file system (like MO) is used.
      Do not generate into any game or any mod manager folders that are part (direct or indirect) of the virtual file system.
      Requirements
      Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 - Required by LODGen.exe/LODGenx64.exe and Texconv.exe/Texconvx64.exe. Get matching platform x86/x64 depending on which xLODGen.exe (x86) or xLODGenx64.exe (x64) is used.
      RTFM and Share Results
      See the included Skyrim-Occlusion-Readme.txt for a brief explanation of the Skyrim TVDT Occlusion data generation. Read the hints that are shown when the mouse pointer rests on a setting. Ask specific questions or give feedback in the dedicated Skyrim TVDT - Occlusion Data thread.
      See the included Terrain-LOD-Readme.txt for a brief explanation of the settings for terrain LOD generation. Read the hints that are shown when the mouse pointer rests on a setting. Ask specific questions about terrain LOD in this thread for a more in-depth explanation if required and share feedback (with screenshots) about results or problems.
      These tools generate LOD meshes and textures "exactly" like CK, but not like the meshes and textures which are shipping with the games (they are often manually edited).
      However, these tools provide more options and higher resolutions (use the x64 version if there are memory errors because you believe you require 4k or higher) and can be updated to add more useful features and options.
      I did some testing in the different games, but finding the best combinations of options and settings requires lots of testing and are a matter of personal opinion and which game is used, the load order, mods, even different worldspaces probably.
      That means, I am only able to give generic guidelines and hints to send you off to find and test for yourself and share your results. My main interested is that generations works correctly and without problems for now.
      Check out the thread xLODGen Terrain Settings Compare. Also refer to any modding guide which has a list of relevant mods close to your load order.
      The object and tree LOD generation is the same as the current versions of xEdit / xLODGen. Refer to their respective descriptions and explanations.
      Obviously, users of Skryim/Enderal/Skyrim SE/Skyrim VR/EnderalSE continue to use the easier and more comprehensive DynDOLOD for drastically improved object and tree LOD generation and only use xLODGen for terrain LOD (and maybe Occlusion) generation.
      First Time
      Here are suggestion to start without going crazy and that should be quick enough to generate:
      Set quality of meshes for LOD4 to 5 and then +5 for each next level. Or just set levels 8/16/32 to 10.
      Check protect cell borders (yes it fixes the ugly terrain drops at outer cell borders that still exist in Fallout 4).
      Use the max vertices setting only if you want to hard limit max file size.
      In Skyrim Special Edition or Skyrim VR, if you notice terrain briefly flickering when new areas are loading in, set [Display] bEnableLandFade=0 in Skyrim.INI
      Set Optimize Unseen to off for LOD4 for first generation. Start experimenting with a value of 550 with a quality setting of 10 or lower for LOD32 (used for map) and compare coastlines and file size to other settings.
      To quickly generate terrain LOD meshes just for the map, check only terrain LOD Meshes, check the Specific Chunk checkbox and set drop down to 32. Leave SW fields empty for complete map or set SW cell coordinates to same values as a *.btr filename to test a specific area with lots of water, river etc.
      Set texture sizes to 512 for a start. Larger sizes and large world spaces will take a considerable time (like 15 to 30 minutes or more easily). Each higher resolution means quadruple the work.
      Use DXT1 for diffuse and 565 (DXT1 if on Windows 7) for normal maps. If generating for Skyrim Special Edition use BC7. Uncheck mipmaps, raise steepness and Bake normal maps.
      For now, leave the Brightness, Contrast and Gamma at 0 and 1.0 respectively. It seems that only Skyrim CK and Skyrim SE CK are manipulating the intensity of the textures to adjust for the noise.dds and the god awful "improved" snow shader of Skyrim SE (just turn that thing off, really). If textures seem too dark in the game, brighten the noise.dds instead or vice versa. That way you can get perfectly matching LOD textures that look just like the textures in the loaded cells. For Skyrim a good average color of the noise texture seems to be around #C0. See below for a couple noise texture downloads.
      If you want to test larger texture sizes, use the chunk option to limit the number of textures that need to be generated. For example, check [x] Specific chunk, leave the drop down empty and set WS to the lower left cell coordinate of an 32x32 area, like 0, 0. It will then generate all textures up to 31,31. Not all worldspaces have their origin at 0,0 so you will have to check already generated meshes/texture filenames for their lower left coordinates.
      Questions and Feedback
      Obliviously anything related to terrain LOD should be posted in this thread.
      Posts related to Occlusion should be made here.
      Recommended Optionals
      TES5-Terrain-Tamriel.esm, SSE-Terrain-Tamriel.esm
      TES5-Terrain-Tamriel-Extend.esm, SSE-Terrain-Tamriel-Extend.esm - These extend the sea of ghost further to the north (see screenshots)
      SSE-Terrain-Tamriel-Full-Extend.esm - Entire map from -96,-96 to 95,96 with northern ocean extension. Useful for mod authors.
      Put in game data folder obviously. Adds back terrain for Skyrim (Tamriel worldspace) at the outer edges so there is no missing terrain meshes/textures when generating terrain LOD for Skyrim.
      Load as early with lowest priority as possible, so that any other plugins overwriting or adding land records or cells with the same coordinates take precedence.
      Only required to be loaded when generating terrain LOD. No harm done when loaded in-game but typically the player can not get close to these areas. There are no effects outside the far away added cells.
      Noise
      Single color flat noise, Adjusted vanilla noise, HD Terrain Noise Texture SE
      Examples for Skyrim. Install to game folder like any other texture mod. The noise texture is applied in-game on top of terrain LOD textures, so no effect for LOD generation.
      Only the red channel is used in case the textures is not a grey channel format. MipMaps are ignored. The textures is tiled 3x3 per LOD quad, e.g. for LOD level 4, the noise texture is repeated 3 times to cover 4 cells, for LOD level 8, the noise texture is repeated 3 times to cover 8 cells and so on.
      Test-Terrain-Tamriel.7z
      For testing terrain LOD distances. Plain color terrain LOD textures for Tamriel with coordinates for every LOD quad. Green for LOD 4, yellow for LOD8, blue for LOD 16 and red for LOD 32.
    • By z929669
      The following was preliminary testing. Jump to the most current testing results in this thread.
       
       
       
      I am testing various xLODGen settings for "Terrain". I compare the same two areas (snow/no snow). So this is not comprehensive, but gives people some ideas of settings results (on my system) with STEP 0.3.0b. It is a relative compare of different terrain LOD results, all else remaining equal.
       
      skyrimprefs.ini LOD settings:
      [LOD] fLODFadeOutMultActors=15.0 fLODFadeOutMultItems=10.0 fLODFadeOutMultObjects=30.0 fLODFadeOutMultSkyCell=1.0000 [TerrainManager] bShowLODInEditor=1 fBlockLevel0Distance=50000 fBlockLevel1Distance=72500 fBlockMaximumDistance=94000 fSplitDistanceMult=4.000 fTreeLoadDistance=72500  
      Settings Rationale
      Based on my review of sheson's xLODGen thread and documentation, it looks like we should be using best quality and largest textures at LOD4, baking normals for best result (only if normals size ≥ 512 at a given level). Why? Because, in RL, resolution of our environment increases as it gets closer. Also, sheson recommends not tweaking brightness/contrast/gamma without good reason: he suggests lightening/darkening the noise map instead. I have confirmed that changing gamma between 0.97 and 1.10 has no apparent impact in game (data not shown). Lastly, raise steepness should be a good add for LOD8/16/32, since it increases bump effects for mips (probably not necessary at LOD4, due to higher quality textures, and closeness of these textures). I did compare using/not using raise steepness, and I didn't find any really noticeable difference (Lo setting does not include at LOD32, but all others do), so I am including it simply because it sounds rignt "just in case". Compression type does have a significant impact on quality, even for diffuse. BC7 is observably superior to DXT1, particularly with respect to shore-line jaggies around water.
       
      Compare order: Optimal settings (my system, my opinion) > lo settings > hi settings > ultra settings. Links to the settings are also below.
       

      My system is agnostic of these settings. I take no detectable performance hit either way, but I expect that typical PCs will see some difference of more/less significance (system specs in sig).

      Optimal Settings - LOD data ~ 5 GB, gen time ~ 45 min
      Lo Settings - LOD data ~ 2.5 GB, gen time ~ 25 min
      Hi Settings - LOD data ~ 9.5 GB, gen time ~ 45 min
      Ultra Settings - LOD data ~ 33.5 GB, gen time ~ 45 min
       
      It would be great if someone with a PC closer to that recommend for STEP and also running STEP would test xLODGen and let us know about performance impact and time to generate.
       
      UPDATE:
      After getting some feedback from sheson:
      Added Solitude (looking South from near the main gate) Increased quality on Lo settings to '10' for LOD16 and LOD32 Examined VRAM usage in all scenarios and include a compare of with/wo mipmaps in the 'optimal' settings (apparently, it's not clear if mipmaps are used at all by LOD. sheson confirms that diffuse does not use them, but normals might) Updated Lo Settings (else they are same as linked previously)
       
      Compare order: Lo > Hi > Ultra > Optimal > Optimal (without mips)
       

      Optimal Setings (no mips)
       
      Findings:
      FPS stats are largely unaffected by terrain LOD quality on my PC. VRAM usage was consistently lower for Lo settings relative to all others and no-mip-Optimal settings (versus Optimnal WITH mips). Not a huge diff, but lower well beyond the +/- 200 MB variation in reported VRAM usage. Optimal (no mips) was comparable to Lo in terms of performance but noticeably better in terms of quality. VRAM usage stats are not entirely reliable, because they varied by +/- 200 GB on my PC on any given save-game load once stabilized. This is consistent with how VRAM (and RAM) behave. Algorithms are being employed at any given time in any given system that govern use of RAM. It depends on what the GPU is 'thinking' at the time a save game is loaded: are you loading from a fresh game boot via MO? Did you recently reboot your PC? Are you loading one save game after another? .. it is inconsistent, but not wildly so. My findings are that VRAM usage is a bit less with Lo settings and by NOT enabling mipmaps/raise steepness. Based on the screen compares and VRAM usage, there is no reason to enable mipmaps or "Raise Steepness" on my system. Simple Summary (for my PC)
      Use Optimal Settings (no mips) or some proportionate deviation from that: LOD data ~ 4.2 GB, gen time ~ 36 min
      This takes a bit less time to generate LOD, probably decreases VRAM usage to a marginal extent, and results in quality that is all but indistinguishable from Ultra settings. DXT1 compression does not appear to save much besides disk space and costs in quality, so use it on diffuse maps ONLY if disk space is a major issue.
    • By KnowChillx
      So after following the guide I ran over to Markarth to get a that sweet sweet free haunted house when I noticed that the rock walls around town were black from afar. As I approached them they rendered into this odd glassy low res texture. Pre-update everything was pretty much kosher. Not sure what changed but I'll try it again to see if it's on me and where I may have botched. Any help would be great. Thanks. 


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

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