Jump to content
Sign in to follow this  
Ragemoody

Problems with my 'skeleton'

Recommended Posts

Hey guys, so i managed to complete the Fear and Loathing in New Vegas guide today and it seems like everything but my skeleton is working as intended (for now). This is my problem: https://imgur.com/a/BoaY1

 

I tried to fix this for a few hours but couldn't manage to figure out whats causing this.

Any help would be really appreciated!  :unworthy:

 

Edit: I also tried this fix:

 

 

 

  • Note: If black bars are showing on male bodies in game, try ticking or unticking the BSA for Roberts Males. If that does not work check that no other mod than aMidianBorn Book of Water, ALR - Aptom's Legion Retextured, Ghouls Hires retexture, or Wasteland clothing Hires retexture overwrite Roberts Males.

Roberts Male Body doesn't have a BSA in my Filetree and no other mod than those mentioned above is overwriting Roberts Males.

Edited by Ragemoody

Share this post


Link to post
Share on other sites

That's strange, have you seen any other Texture related issues in you game, say on NPC's, or creatures. If I were you I would try COCing to goodsprings and turn on god mode and travel around for a bit to see if you spot any other issues. 

Share this post


Link to post
Share on other sites

There is a minor issue with AI implementation that is being addressed. Read this post and see if the steps outlined fix the issue, if it is BSA related.

Share this post


Link to post
Share on other sites

@predator42393n

 

Okay so i did what you suggested and travelled around for a bit. I actually managed to spot another issue: People who do not have white skin DO have a white face! Everything else seems to be okay tho.

 

Edit: 

 

 

There is a minor issue with AI implementation that is being addressed. Read this post and see if the steps outlined fix the issue, if it is BSA related.

It worked! Thank you so much!!  :gnome:  :gnome:

Edited by Ragemoody

Share this post


Link to post
Share on other sites

The old white face on a black body issue? That can be fixed by setting bLoadFaceGenEGTFiles to 1 in the inis. I have it in both inis to be safe. If it's not there just type it in.

  • Upvote 1

Share this post


Link to post
Share on other sites

The old white face on a black body issue? That can be fixed by setting bLoadFaceGenEGTFiles to 1 in the inis. I have it in both inis to be safe. If it's not there just type it in.

This worked as well, thank you! However, i ran into another problem. It looks like something is wrong with the eyes from FCO. I looked for some fixes on FCO's nexus page but couldn't manage to find a working one yet. Any suggestions on how to fix this?

 

Edit: Okay it looks like NVR3 has conflicts with FCO eyes. Putting FCO below NVR3 in my load order fixed it. Are there any known conflicts i should know about if i keep it that way?

Edited by Ragemoody

Share this post


Link to post
Share on other sites

It's usually adding Eyes tag to FCO and NVR3 (ESM and ESP) in Wrye Flash. Then rerun the bashed patch.

Share this post


Link to post
Share on other sites

It's usually adding Eyes tag to FCO and NVR3 (ESM and ESP) in Wrye Flash. Then rerun the bashed patch.

To every single ESP and ESM? I've got 6 for FCO and 2 for NVR3

Edited by Ragemoody

Share this post


Link to post
Share on other sites

Just the FCO.esm and the two NVR3 plugins. 

That doesn't work for me. I guess i'll just keep FCO below NVR3 in my load order for now.

Share this post


Link to post
Share on other sites

Another option is to go to the conflicts tab on the NVR3 mods and checking for anything from FCO that overwrites NVR3 with respect to eyes. If there's anything there, (and there will be) try hiding those files.

 

(This is assuming you preferred the NVR3 look to the FCO look. It's a bit of a judgement call. If you're happy with FCO under NVR3 and all works happily for you like that then just go with that)

Edited by Nozzer66
  • Upvote 1

Share this post


Link to post
Share on other sites

Apparently the author of FCO has fixed the eyes problem with custom races, for his next update, when ever that is coming out, however I'm unsure if that would fix this particular problem. From what I understand it has to do with the texture itself and how he put two eyes on a single texture, where as most custom races only have one eye on a single texture, thats why it looks like there are two eyes in each eye socket.

Edited by predator42393n

Share this post


Link to post
Share on other sites

Another option is to go to the conflicts tab on the NVR3 mods and checking for anything from FCO that overwrites NVR3 with respect to eyes. If there's anything there, (and there will be) try hiding those files.

 

(This is assuming you preferred the NVR3 look to the FCO look. It's a bit of a judgement call. If you're happy with FCO under NVR3 and all works happily for you like that then just go with that)

I tried this fix and it seems like everything is working as intended now. Thanks to all of you for your help!

 

Oh and i'm sorry this is not in the support forum. I somehow failed to see it.

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 Drak
      Hello There,
      I did a fresh install following STEP recommandations (FNV not in program files, modding directory neither, I started FNV after installing it).
      I can start the game with all mods from STEP except Step Patch - Conflict Resolution.

      I tryied to pinpoint my problem and as soon as I add the Step patch (then LOOT order dirladada) I get the following error in 
      nvac.log :
      23190643 _ NewVegasAntiCrash FalloutNV.exe
      23190643 _ 17E90000 07050000 nvac.dll
      23190643 i 008BFBC1 0441B60F FalloutNV.exe
      23190643 _ 17AE0000 06020050 nvse_1_4.dll
      23190643 _ 77170000 0A004A64 ntdll.dll
      23190646 a 0072607A 0048A1DF FalloutNV.exe
      23190647 h 181A42EB 8B48088B nvse_stewie_tweaks.dll (100342EB)
      23190647 ^ 0076E223 00000004 FalloutNV.exe
      23190647 h 181A42EE 8B01FF10 nvse_stewie_tweaks.dll (100342EE)
      23190647 ^ 0076E223 00000004 FalloutNV.exe
      23190647 h 181A42F0 FF1068F0 nvse_stewie_tweaks.dll (100342F0)
      23190647 ^ 0076E223 00000004 FalloutNV.exe
      23190647 m 000003EC 219C46E0
      23190647 r 10001432 00000009 d3dx9_38.dll (10001432)
      23190647 ^ 0045CEF5 0000000D FalloutNV.exe
      23190647 h 100034E0 834104FF d3dx9_38.dll (100034E0)
      23190647 ^ 0045CEF5 0000000D FalloutNV.exe
      23190647 h 100034E6 C7010000 d3dx9_38.dll (100034E6)
      23190647 ^ 0045CEF5 0000000D FalloutNV.exe
      23190647 u 00F0B4FA C0000409 FalloutNV.exe
      23190647 ! CRASHSAV E_FAIL_0 FalloutNV.exe
      23190648 q 00F0B4FA C0000409 FalloutNV.exe
      23190648 ! CRASHSAV E_FAIL_0 FalloutNV.exe
       
      I also tryed to use Cobb Crash Logger 
       
      Cobb Crash Logger Version 3.0.0, build 0.
      If this file is empty, then your game didn't crash! Probably!
      Exception C0000409 caught!
      Calltrace: 
      0x00F0B4FA ==> EntryPoint+0xFFFFFFFF in FalloutNV (0x0019F138) 
      0x771F88B4 ==> RtlInterlockedCompareExchange64+0x1B4 in ntdll (0x0019F204) 
      0x771E4EE6 ==> KiUserExceptionDispatcher+0x26 in ntdll (0x0019F208) 
      0x0019F21C ==> ¯\(°_o)/¯ (Corrupt stack or heap?)  (0x0019F20C)
      0x0019F26C ==> ¯\(°_o)/¯ (Corrupt stack or heap?)  (0x0019F21C)
      blablabla
      GAME CRASHED AT INSTRUCTION Base+0x00B0B4FA IN MODULE: C:\Steam\steamapps\common\Fallout New Vegas\FalloutNV.exe
      Please note that this does not automatically mean that that module is responsible. 
      It may have been supplied bad data or program state as the result of an issue in 
      the base game or a different DLL.
       
      Help welcome, I am at a loss..
    • By z929669
      Step Fallout: New Vegas Guide 1.0.0 released!

      Guide Link | Changelog | Feedback & Bug Reports
      Nexus Link
      Many thanks to @Majorman for working on this guide for the past 6 weeks as our official FNV guide Curator!
    • 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.
  • 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.