Jump to content
  • 0
Sign in to follow this  
marieruth

LOOT fails to run through Mod Organizer.

Question

I'm using MO for Fallout 3, and I use the external most recently updated version of LOOT on my computer. Yesterday, I could run LOOT successfully through MO with no issues at all. Today it is not functioning as it did yesterday. The only difference from today and yesterday is that today I installed a pip-boy retex mod, but I don't think it's related to my toubles. The error log that Mod Organizer displayed is this:

 

DEBUG (14:47:03.0361): get file attributes: D:\Steam\steamapps\common\Fallout 3 goty\Data\JIP Companions Command & Control.esp -> D:\Steam\steamapps\common\Fallout 3 goty\Data\ModOrganizer\mods\JIP Companions Command & Control\JIP Companions Command & Control.esp: 20
DEBUG (14:47:03.0361): first access to Storage for Craterside Supply in Megaton
DEBUG (14:47:03.0361): get file attributes: D:\Steam\steamapps\common\Fallout 3 goty\Data\CratersideSupplyStorage.esp -> D:\Steam\steamapps\common\Fallout 3 goty\Data\ModOrganizer\mods\Storage for Craterside Supply in Megaton\CratersideSupplyStorage.esp: 20
DEBUG (14:47:03.0428): create process (w) null - "D:\Bethesda Programs\LOOT 0.7.0b4\wow_helper.exe" 0x9b0 0xf60000 (in null) - hooking
ERROR (14:47:03.0430): failed to inject into (null): failed to access thread context. Please note that Mod Organizer does not support 64bit binaries! (The parameter is incorrect. [87])
DEBUG (14:47:06.0102): sh file operation w 3: C:\Users\Marie\AppData\Local\Temp\scoped_dir4676_1254 - nullptr
DEBUG (14:47:06.0130): hooks removed
----------- LOG END -----------

 

I don't understand what I did wrong to cause that error, since it worked fine yesterday. I thought that running LOOT in compatibility mode to Windows XP SP3 would help, thinking that would put it in 32-Bit mode or something, but that did not make anything better or worse. I also tried running LOOT as Administrator, which also didn't do anything. Any help would be appreciated.

Share this post


Link to post
Share on other sites

5 answers to this question

Recommended Posts

  • 0

Have you changed any permissions on the LOOT executable or made it to run in compatibility mode or any such action?

There should be no reason why wow_helper.exe is being called. That is a utility designed to run programs in a certain mode inside Windows, the naming schema is: Windows on Windows helper.

I have never seen the need to call either LOOT or MO via this method as they will 'just work'.

 

The actual file in the LOOT folder that the error message is referencing is a 64bit exe, hence the error.

 

I can't see why this is being called so these next steps are just a shot in the dark.

Rename the folder where LOOT is stored to remove any periods in its name, call it just LOOT, not LOOT 0.7.0b4 and remove the 'Start in' field entry.

 

Oh, well shoot. I guess the problem was me running Mod Organizer in compatibility mode. I must have forgot to disable it after I figured out why Fallout 3 kept crashing at launch.

 

Thanks for trying to help me anyhow. :)

Share this post


Link to post
Share on other sites
  • 0

Check the settings in your 'Executables' list, is the LOOT setting actually running LOOT.exe or the wow_helper.exe?

 

Ensure it is pointing to LOOT.

Share this post


Link to post
Share on other sites
  • 0

Check the settings in your 'Executables' list, is the LOOT setting actually running LOOT.exe or the wow_helper.exe?

 

Ensure it is pointing to LOOT.

 

The executable points to LOOT.exe

https://www.dropbox.com/s/h49suye6dhjblhs/Screenshot%202015-06-21%2020.36.50.png?dl=0

 

Also where is loot installed?

 

LOOT is installed under the D drive on my computer. The C drive is where the Operating system is installed, Windows 8.1

Share this post


Link to post
Share on other sites
  • 0

Have you changed any permissions on the LOOT executable or made it to run in compatibility mode or any such action?

There should be no reason why wow_helper.exe is being called. That is a utility designed to run programs in a certain mode inside Windows, the naming schema is: Windows on Windows helper.

I have never seen the need to call either LOOT or MO via this method as they will 'just work'.

 

The actual file in the LOOT folder that the error message is referencing is a 64bit exe, hence the error.

 

I can't see why this is being called so these next steps are just a shot in the dark.

Rename the folder where LOOT is stored to remove any periods in its name, call it just LOOT, not LOOT 0.7.0b4 and remove the 'Start in' field entry.

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 86 - based on 4.1.4b
      Unzip into a dedicated folder outside of any Steam, game or mod manager folders or special Windows folders like Program Files.
      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.
      Do not generate into any game or any mod manager folders.
      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 (Mega), SSE-Terrain-Tamriel.esm (Mega)
      TES5-Terrain-Tamriel-Extend.esm (Mega), SSE-Terrain-Tamriel-Extend.esm (Mega) - These extend the sea of ghost further to the north (see screenshots)
      SSE-Terrain-Tamriel-Full-Extend.esm (Mega) - 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 dicksuckme
      [info] Attempting to create a game handle with game path "D:/steam/steamapps/common/Skyrim Special Edition" and local path "D:/skyrim/profiles/Default"
      [info] Initialising load order data for game of type 5 at: D:/steam/steamapps/common/Skyrim Special Edition
      [info] Attempting to open Git repository at: C:\Users\cabca\AppData\Local\LOOT\Skyrim Special Edition
      [info] Setting URL for remote origin to https://github.com/loot/skyrimse.git
      [error] A firewall may be blocking LOOT.
      [error] Git operation failed. Details: -1; failed to send request: A connection with the server could not be established\r\n: libgit2 error
      [error] Loot failed. Exit code was: 0x1

    • By NuroDragonfly
      HI peoples;
      As much a ted-talk as qanda, but the concept of Merging updates or other files into a main file has come up in my current re-installation of SSE and modding of it:
      that being when the STEP says to merge files when you did not download them from the Nexus, but like me, have system stored mods from various games that you are simply re-installing in many ways back into a MO2 Profile for what ever game...
      and the option to Merge, Replace, Rename, or Cancel does not appear...
      which is because the meta-data does not exist within the Download folder you (should) have set up in your MO2 installation and instance of said game...
      Well, the best choice is to simply name the update/optional file exactly as the one it is meant to merge with - which means that when you know your going to be installing various files for the same mod, you need to choose what it is going to be called as a whole - and these options will appear again and this part of the STEP can be achieved easily and as the STEP instructs.
      I realise some of you may already know this, but this conversation was begun on another mod forum here on STEP and needed to be continued here instead, so this is for those that may come across the same issue or confusion momentarily.
  • 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.