Jump to content
  • 0
Omniguous

Remove Unneeded xEdit Arguments

Question

the arguments '-iknowwhatimdoing' and '-allowmasterfilesedit' should NOT be entrenched into the STEP guide.

for starters: nothing you do with xEdit actually requires the latter one.

and the first is NOT meant 'simply for disabling a single pop-up': it does much more and the user is /meant/ to -ahem- KNOW WHAT IT IS and WHAT THEY DO. hence, the name.

This applies to SSE, as well.

thanks.

Share this post


Link to post
Share on other sites

12 answers to this question

Recommended Posts

  • 0

For starters, documentation: https://stepmodifications.org/wiki/Guide:XEdit#Launch_Arguments

I think I originally had some text saying they were optional, but it's been edited so many times, who knows. Do you need them for just the Guide? No, not really. We're not instructing users to do anything that requires them.

Honestly, the concern just sounds like over-zealous caution, but if the staff want to remove the arguments, they can have at it. However, if you don't know what you're doing...learn? There's nothing that you're going to do that isn't fixable. You're not going to learn anything without breaking some things first, but to each their own. :laugh:

Share this post


Link to post
Share on other sites
  • 0
1 hour ago, Omniguous said:

the arguments '-iknowwhatimdoing' and '-allowmasterfilesedit' should NOT be entrenched into the STEP guide.

for starters: nothing you do with xEdit actually requires the latter one.

and the first is NOT meant 'simply for disabling a single pop-up': it does much more and the user is /meant/ to -ahem- KNOW WHAT IT IS and WHAT THEY DO. hence, the name.

This applies to SSE, as well.

thanks.

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.

Share this post


Link to post
Share on other sites
  • 0

evidence.thumb.png.98c760a384cc4047fa6dde2d587a86b5.png

straight from the xEdit discord.

and again: the allowmastersedit has absolutely no reason.
if you want to skip the 4second wait, cool beans.
but nothing in the entire STEP guide, either LE or SSE even REQUIRES that argument to be enabled.

that argument doesnt prevent/allow 'Quick Auto Clean' from cleaning masters.

it is for much more in-depth edits.

Share this post


Link to post
Share on other sites
  • 0
8 hours ago, Omniguous said:

evidence.thumb.png.98c760a384cc4047fa6dde2d587a86b5.png

straight from the xEdit discord.

and again: the allowmastersedit has absolutely no reason.
if you want to skip the 4second wait, cool beans.
but nothing in the entire STEP guide, either LE or SSE even REQUIRES that argument to be enabled.

that argument doesnt prevent/allow 'Quick Auto Clean' from cleaning masters.

it is for much more in-depth edits.

That's my issue with Discord for content that is static and always applicable (like a manual or instructions). Discord sucks for that, even with pinning. No reason for all users needing to sift through conversations to find what should be in the manual.

OK, I totally see the reasoning for excluding -allowmastersedit in that case but will let @TechAngel85 qualify if there was any historic reason to do so.

-iknowwhatimdoing switch makes sense for us though.

  • Upvote 1

Share this post


Link to post
Share on other sites
  • 0
8 hours ago, z929669 said:

OK, I totally see the reasoning for excluding -allowmastersedit in that case but will let @TechAngel85 qualify if there was any historic reason to do so.

There's no reason for the Guide to have it. Most of what I do is to reduce support, in all honestly, and I've seen no additional support from having it in the Guide...so I have no idea why it's such as issue for @Omniguous:ermm: Obviously, I still see no point in dropping it. Removing it really only prevents accidental edits to masters, and again, no additional support has resulted. I've run with it since it was available and will continue to do so on my end. You guys do what you want.

Share this post


Link to post
Share on other sites
  • 0

It's not like modding Skyrim is dangerous. We're not teaching people how to disable the safety on a firearm.

If those switches provide more power to the user without creating headaches for others, I am all for it.

Share this post


Link to post
Share on other sites
  • 0

I was going to bring this up myself.  I think it's okay to include -IKnowWhatImDoing, but there is absolutely no need to directly edit the game's master files, and it's dangerous to have option on, since it is easy to do so by mistake when it is enabled.  However, the first flag given, -TESV, is not needed either, because you're telling people to call the executable as TESVEdit.exe, not as xEdit.exe.

Share this post


Link to post
Share on other sites
  • 0
45 minutes ago, Darklocq said:

I was going to bring this up myself.  I think it's okay to include -IKnowWhatImDoing, but there is absolutely no need to directly edit the game's master files, and it's dangerous to have option on, since it is easy to do so by mistake when it is enabled.  However, the first flag given, -TESV, is not needed either, because you're telling people to call the executable as TESVEdit.exe, not as xEdit.exe.

See previous comments. There is nothing 'dangerous' here. If you disagree, then we need to provide a glaring warning on all modding tools, mods, resources, etc.

"Modding is dangerous to the functionality of your game". ultimately, everything is recoverable, so ... meh.

Share this post


Link to post
Share on other sites
  • 0

That's a semantic quibble. The point is, STEP does not instruct users to change records in the main game files (other than by TESVEdit's auto-cleaning procedure), so there is no reason or rationale to recommend this option.  It's trivially easy to accidentally change master-file records with that option on, and if you do that you'll have to restore the originals from a backup or by having Steam re-install (which is a different kind of hazard, more so in SSE than SLE since you might get newer SLE files that what you had, and end up with savegames that are no longer usable).  It's what en.Wikipedia would call a WP:BEANS ("Don't stuff beans up your nose") matter, a particularly pernicious form of "instruction creep".  Anyway, as noted the -TESV flag is also pointless to recommend, since we're not starting xEdit in a way that needs it.

Share this post


Link to post
Share on other sites
  • 0

I have removed that argument from both Guides since it seems to be a point of controversy. The gamemode arguments are included because we don't know if users are installing fresh or coming from another game. So if a user already has xEdit installed from FO4, they don't need to install it again. They can just launch it using -SSE or -TES5 (not -TESV), then xEdit will load for that game regardless if the EXE is named for FO3Edit, FNVEdit, SSEEdit, etc.

Share this post


Link to post
Share on other sites
  • 0
29 minutes ago, TechAngel85 said:

I have removed that argument from both Guides since it seems to be a point of controversy. The gamemode arguments are included because we don't know if users are installing fresh or coming from another game. So if a user already has xEdit installed from FO4, they don't need to install it again. They can just launch it using -SSE or -TES5 (not -TESV), then xEdit will load for that game regardless if the EXE is named for FO3Edit, FNVEdit, SSEEdit, etc.

Absolutely necessary to keep these args for all xEdit apps in all guides. This is how we reuse tool instructions across Bethesda games and is not up for debate for that reason.

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

  • Similar Content

    • By SpookyMrSkeltal
      After installing DynDOLOD I noticed a few floating items above bleakwind basin, a barrel, a door and some wheat. These objects don't load in till up close and are from what I believe to be some errors within their respective mods, they can also be disabled.
      However, a stone pillar is also floating there that I can see from at least as far away as the other side of whiterun.
      The object id is 5D005FC4. My dyndolod esp id is 5d. 
      I can't disable the pillar as it simply respawns when far enough away. I tried to use sseedit to remove it but it does not exist within sseedit. I have tried deleting and resetting up dyndolod to no avail. The only thing that removes it is turning off dyndolod but I still want to use it if possible.
      I am new to modding so I may have missed an obvious solution. 
      Any help would be much appreciated.
    • By z929669
      Discussion topic:
      Aspens Ablaze by mindflux
      Wiki Link
      See mod page for screen compares for all versions. Those screens were created under Step WIP 2.0.0.
      I think "Autumnal" is the most vanilla-friendly option, and I think it is also the most realistic.
    • 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.
  • 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.