Jump to content

z929669

Administrator
 View Profile  See their activity

  • Posts

    13,086

  • Joined

  • Last visited

 Content Type 

Everything posted by z929669

  1. z929669
    You are in borderless on a 60 Hz monitor on Win 10 and can get > 60 FPS?
  2. z929669
    Good tip'o the day
  3. z929669
    The INI doesn't just disappear. If you are using MO, the INI and SKSE folder should be inside of the SKSE64 mod in MO. Only the runtime DLLs go into your game folder. Be sure you followed the instructions. This error says you are running an incompatible SKSE plugin called ItemStealPlugin.dll. It's for LE and not SE as the error says. In MO 'Data' right pane, type in the name of this file in the filter at bottom. This will show the SKSE folder. Expand this to reveal the file and the mod name providing it. Uninstall this mod. Find the correct version and install that instead or don't use the mod. Always click 'yes' to that dialog.
  4. z929669
    If you followed the instructions I linked, you would have an SKSE.ini. Maybe follow those instructions again and pay attention to everything?
  5. z929669
    I believe this update fixed an issue I was having with LOOT not applying my sort order to MO. I would run LOOT, sort and get no apply confirmation and no change to plugin order. I discovered that if I dragged a plugin to a different position in MO, the plugins would magically sort. Then I would run LOOT and get the apply confirmation again after sorting. I suspect the regex fix and or the plugin content filters fix resolved it for me. Wondering if anyone else had my issue? Or it's possible that most people didn't notice, because LOOT didn't used to always show the 'Apply' button in previous version.
  6. z929669
    Thanks. I had missed that completely. ... I wasn't running the correct version myself. EDIT: well, I see it's new, so that's why. Funny it isn't in main files.
  7. z929669
    @Mousetick Thanks for the insights. It is now clear, sensible, and will 'stick' to my brain. @DoubleYou I think we should consider changing to Fullscreen mode in the initial BethINI setup and later instruct to switch to borderless as desired (with very brief explanation of the advantages). This alleviates the issue with the least disruption, I suspect. I have a 144 Hz monitor and my fully modded setup doesn't achieve that frame rate even with my decent hardware and no ENB/DynDOLOD (112 FPS peak), so I never experienced this issue in my testing. You didn't, because you were in fullscreen mode due to this issue. @TechAngel85 didn't, and I am not sure why.
  8. z929669
    SKSE install/config instructions for MO: for Skyrim 1.6.xxx for Skyrim 1.5.97
  9. z929669
    As I mentioned in that post, you must first open enbseries.ini and set EnableDepthOfField=true under [EFFECT] Those are just modifiers of DoF once it is enabled.
  10. z929669
    woohoo!
  11. z929669
    I guess I should clarify: I mean the mod you just linked ... since I see now it's a synth patcher, I would assume its a resource for us to create a Step version to incorporate into out patches. I may try it out.
  12. z929669
    Got it. I thought you had said you used vertex colors for painting the paths in SLSR. This mod sounds like something we should be testing at some point then.
  13. z929669
    Then could you go back to borderless? Or are you stuck with fullscreen?
  14. z929669
    Wouldn't this (visually) break Snowy Landscapes in Snowy Regions?
  15. z929669
    Alternatively, go to the location and pull up the map, zoom all the way out and capture/post a screen of that
  16. z929669
    It's explained at the top of the guide. We don't support anything but what it says; although, it's certainly possible to run with 1.6.xxx. We just don't offer guidance on that. The CC DLC costs $20 I think.
  17. z929669
    DynDOLOD presets simply have the current mesh rules in the window along with all of the other GUI settings. If you don't load one, a 'default' preset is still saved and loaded each run for subsequent run. If you save a preset, then it allows you to load a known preset rather than the default. If you go through the process of toggling DynDOLOD settings in the GUI and hitting the low/med/high buttons, then run DynDOLOD, you will see all of these exact same settings and mesh rules are loaded next run. It only changes on loading a preset if you have a different preset. Just run DynDOLOD and play with it, running DynDOLOD and immediately quitting. When you reload, the settings will be the same.
  18. z929669
    Check you video driver software for anything related to 'sync'. There may be a proprietary name for it. Hover over settings and note descriptions. Then also be sure that SSE Display Tweaks is configured for the performance test by disabling vsync as we describe. Also be sure that EnableFPSLimit=false in enblocal.ini. There are at least four places where frame rate limiting can be enabled ... at least two places vsync can be enabled. It caps frame rates to your monitor refresh (most often 60). You only need the set in SSE Display Tweaks, where you can toggle it.
  19. z929669
    See the instructions for the launch test after 02-Extenders: As you can see, there is no mention of starting a new game. All you are doing is loading the menu to confirm things are working as they should be at this point. If you use the console command, you should be able to load Riverwood. If not, then there is an issue. You cannot start a new game because the mod environment is not configured entirely. I suggest you check that you complete steps 1-3 above exactly and didn't break anything by messing with reinstalling and changing things. From here, simply continue with the mod list. Also see the warning box following this instruction. Remember that each guide is different and the mod list and procedures change accordingly. Just because it worked in past guide iterations doesn't apply. You should not get the cart ride with this guide when completed.
  20. z929669
    Glad you got it sorted yourself. thanks for posting your follow-up. ... and Welcome to the Step forums
  21. z929669
    Still a persisting question I have: Hitting one of these preset buttons loads up all relevant rules from relevant paths, but once done, this shouldn't be required in subsequent runs unless the underlying rules change 9DynDOLOD update, mod list changes, mod updates, etc.). DynDOLOD always loads most recently-run rules config, and if you save the preset, you can always retrieve it. I have always done this, but I thought you said that one must hit the preset button every time. Since you have tested this piece more extensively than me, I just want to confirm that you agree/disagree. All data for rules from all possible paths in DynDOLOD install location and mod list are applied on hitting the preset. Once applied, they all 'stick' in my XP (I have diff'ed presets in ..\DynDOLOD\Edit Scripts\DynDOLOD\Presets\. to confirm that this is true. Maybe I'm missing something less obvious though.
  22. z929669
    Open enbseries.ini and set EnableDepthOfField=true if you want to play with DoF. You can also see settings further down once that's done. [DEPTHOFFIELD] ApertureTime=5 FocusingTime=0.5
  23. z929669
    Tons of work to mod this one. Tons. Great concept though
  24. z929669
    Could be, but I still suspect not. It looks like ENB effect ... but maybe exacerbated by RWT normals
  25. z929669
    Seems right, but I haven't gotten into SoS
×
×
  • Create New...

Important Information

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

  I accept