Jump to content

z929669

Administrator
  • Content Count

    7,294
  • Joined

  • Last visited

Community Reputation

9 Good

About z929669

Profile Information

  • Gender
    Male
  • Location
    Nebraska, USA
  • Interests
    Beer, wine, sci-fi/fantasy, end of the world as we know it, going very fast.
    ... more later
  • Favorite Mod
    Requiem

Contact Methods

Recent Profile Visitors

1,618 profile views
  1. @Greg Thanks for adding that bit. I didn't think of it, and it could be the issue. Much faster to resolve than perusing each of the sources. Also, did you know MO has a theme switcher now with at least one dark theme? No need for that horrific white nonsense anymore
  2. It sounds like you grabbed the wrong version(s) of the software. Exactly what part of LODGen process is failing? There are 4 steps (terrain [xLODGen64.exe], TexGen [TexGen64.exe w/DynDOLOD], DynDOLOD [DynDOLOD64.exe], Occlusion [xLODGen64.exe]), and all of them rely on the 'LODGen' app but come packaged with their own compatible versions of that. These downloads also can have multiple versions specific to different games (SE/LE/FO4/etc.) Please look back at each section under LODGen in the guide (and 03-Resources and Tools in the Skyrim Sertup Guide) and follow those links to the Nexus or posts with the software. Some of the sources have multiple downloads, so you need to carefully read the instructions/links.
  3. Damn. I missed that update. I will test again with that. I was using what you last linked me to a few days ago.
  4. I don't think #2 is possible, but I haven't researched.
  5. So it happened again first during DLC2SolstheimWorld ... event: Faulting application name: xLODGenx64.exe, version: 4.1.3.1, time stamp: 0x6075af33 Faulting module name: xLODGenx64.exe, version: 4.1.3.1, time stamp: 0x6075af33 Exception code: 0xc0000005 Fault offset: 0x00000000013e6ef9 Faulting process id: 0x43e4 Faulting application start time: 0x01d742d3018be86e Faulting application path: C:\Modding\Tools\xLODGen\xLODGenx64.exe Faulting module path: C:\Modding\Tools\xLODGen\xLODGenx64.exe Report Id: f4007d5d-7708-4b79-a39e-22136aa898e1 Faulting package full name: Faulting package-relative application ID: ... so I deleted log and tried again. Then it quit during DLC2ApocryphaWorld. LODGen_log.txt ...and here is the event for that: Faulting application name: xLODGenx64.exe, version: 4.1.3.1, time stamp: 0x6075af33 Faulting module name: KERNELBASE.dll, version: 10.0.19041.906, time stamp: 0x2f2f77bf Exception code: 0x0eedfade Fault offset: 0x0000000000034b59 Faulting process id: 0x4c3c Faulting application start time: 0x01d742d62b3eee1d Faulting application path: C:\Modding\Tools\xLODGen\xLODGenx64.exe Faulting module path: C:\Windows\System32\KERNELBASE.dll Report Id: 898e25e3-3dfe-4676-8526-54fc327ae45f Faulting package full name: Faulting package-relative application ID: I'm not seeing a bugreport.txt
  6. Ahh, makes perfect sense. Virtually earmarked to remove the unneeded config file from the CR Patch mod.
  7. Agree with your conclusions ... so the INI in the Step patch is neither a gain or a loss, but redundant. Interesting that we have 13 NPCs total without Step/Step patch/mod and 8 total with in both cases. This may indicate that the mod/Step/Step patch prevents 5 NPCs from coming to the inn at all during your testing time frame.
  8. I have reported your comment so that TechAngel85 can chime in here. I'm no xEdit guru myself and cannot speak to these switches. In the meantime, some illumination or a pointer to relevant sources would be much more helpful than a curt statement. There is mention from other non-authoritative sources like this. Being rid of the 4 sec warning is a boon in and of itself, which seems to be why most people use it and probably why it was added to the guide. I never saw any value in the added barrier. Indeed, even more official doc doesn't describe the risks. I assume that one could break the plugin or the game and cause undue support queries ... but does the gate REALLY prevent this? EDIT: sorry, I was composing this as Tech was responding ... obviously, I echo his sentiment.
  9. Agree, but it's not the light source but the particle aura that is perplexing. We both have the light sources but not the aura. Are such lighting auras dictated by the plugin or the mesh or both?
  10. @Greg Agree. The only things that could be causing the aura are the game INI settings or more likely the Texture Filtering in the display-soft settings. Maybe try turning them all off if possible to see if the aura disappears. Otherwise, I'm stumped.
  11. Check my previous post, and examine your LOD distance settings as described.
  12. First, follow all of the instruction sheson advised, but do note that some of your Skyrim INI settings are pretty far off from what we recommend in our guides. DynDOLOD MCM uses [terrainmanager] settings from the game INIs at first load of a new DynDOLOD under a new game in my XP. The LOD distances you have set are significantly lower than my own in some cases, and your multiplier is 1/8 of what we recommend (4.00, which I think is also mentioned somewhere in DynDOLOD doc). Please try following our BethINI instructions for basic game INI setup so that that is not a contributing factor. This will get your view distances set at a reasonable 'medium' baseline (you can fine tune later). We also have basic guidelines for LODGen using DynDOLOD 2.xx. The general principles and UI are very similar under DynDOLOD 3 alpha. None of this instruction pertains to grass LOD, but it should help you get the basics situated and reduce the 'noise' of these other issues so that you can focus on your original grass problem.
  13. I'm not sure if the version of that mod that was available when we constructed the current guide and if it was fully compatible with AI Overhaul at the time. There could be other reasons why @TechAngel85 added the compatibility INI to the patch. Either way, I suspect this will not harm anything, but you can obviously disable the compatibility INI if you want to verify it fixes your issue. Please post back to confirm if that's the case, and we'll then have a good reason to remove it.
  14. Could be the texture. We don't use that mod for various reasons. One reason is that whenever all textures are batch reprocessed, there are inevitably artifacts introduced here and there. I still think it could the mesh though, and a mod could be adding the mesh to the vanilla object. It can be tricky to click what you intend with More Informative Console in certain situations. Get really close and crouch if that may be the case here. The mesh name should show up at upper left in MIC. Then you can search for it in the right Pane of MO under Data tab. If it's in the BSA, it won't show up here, so try disabling the mod to confirm.
  15. Cathedral Weathers works fine, but some mods may use meshes that look strange under certain weathers and/or under ENB. This can happen with any weather mod. It's probably more of an issue with the mod mesh. That doesn't look like a juniper to me, so use More Informative Console to determine the mesh and find source in MO Data tab of right pane. The mod author may provide ENB-friendly meshes
×
×
  • Create New...

Important Information

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