Jump to content
  • 0
Pandore

FCO and NVR3 (supposed) issues

Question

HI there,

 

Reporting some issues that I have with the game, at the Character Creation. I know some of the issues were reported somewhere but can't find something that make it work for me. So, characters have double/triple iris but not with what seems default eyes (Green, Blue, Brown ect., the simple one). I don't know if I have to enable, disable the FCO esm and esp, because it says it on the Nexus page of NVR3 but it didnt change anything ... I'll take photos of all the issues tomorrow I think, but if someone has already an idea ...

 

Plus a question : if I want to add cazys hair at all the races added by FCO, how do I do that ?

 

Thank you kind people :)

Share this post


Link to post
Share on other sites

10 answers to this question

Recommended Posts

  • 0

Probably need the Eyes tag when running the Bashed Patch. Check in Wrye Flash if FCO and NVR3 have the tag and if not then add it manually by right clicking the bottom right box where the tags are listed while that plugin is loaded.

Share this post


Link to post
Share on other sites
  • 0

Hi !
 
 

Probably need the Eyes tag when running the Bashed Patch. Check in Wrye Flash if FCO and NVR3 have the tag and if not then add it manually by right clicking the bottom right box where the tags are listed while that plugin is loaded.

I tried it, but didnt fixed it (first photo) ... I have other problems too :

- when i hit F12 for screenshots (steam), it does that strange thing where all is transparent (see photo 2 and 4) ... About 5 sec later it's gone oO

- Plus, there is strange aura around hair and face character (third photo).

- And another question : is that cubes on the HUD are normal ? Here some photos for you to understand

Edited by Pandore

Share this post


Link to post
Share on other sites
  • 0

If you mean the yellow cube no that's not normal. I'd almost suspect your monitor cause it's in the same place every time.

 

The third photo looks fine to me, but that's very likely cause in taking the shot you turned your ENB off with F12. But I think I know what you mean and if I'm correct it's essentially an Engine fault. It can be fixed by installing the ENB Hair Meshes option in FCO.

Share this post


Link to post
Share on other sites
  • 0

Double iris': NVR3 is clashing with FCO. Open up NVR3 in MO and go to the "Conflicts" tab. Hide any file in the upper box that has the words "FCO" in it. 

 

Transparent/See Through Objects: Disable the Steam Overlay. It is incompatible with ENB and you don't need it anyway. ENB has its own screenshot feature. 

 

"Strange Aura": This is an issue with ENB and the game engine and cannot be completely fixed; even with said ENB Hair Mesh options. What you are seeing is the Mesh's Alpha Channel. 

 

Cube: I am not so sure actually. :\

  • Upvote 1

Share this post


Link to post
Share on other sites
  • 0

Hey i noticied your running a non english version of fnv that may create issues with mods that are made with the english version of the game due to having different formids while i dont know if it could cause the problems you are having it may be something to look into in fnvedit incase if fco or nvr3 are causing the issues

 

here is more information here

 

https://forums.nexusmods.com/index.php?/topic/1588819-non-english-user-running-english-mods-english-creator-making-non-english-translations-read-this/

Edited by slayer80

Share this post


Link to post
Share on other sites
  • 0

I had the double iris thing as well. Deleting NVR3 completely sorted the problem, so it was indeed a conflict with that mod, as Audley said.

Btw, I deleted NVR3 because I like the skins from FCO much better. Personal taste and all that.

Share this post


Link to post
Share on other sites
  • 0

While I really think NVR3 is a good mod, I just plain don't use it due to the vast amount of issues it causes. It conflicts with other mods such as: Type 3 Body, Robert's Male Body, Interior Lighting Overhaul, Spice of Life, and of course mods like FCO. No matter how many proper tags you add, a bashed patch isn't going to fix all of these issues. I hate to say it but this mod will be a bit of a mess until proper compatibility patches are made. :\

Edited by Audley

Share this post


Link to post
Share on other sites
  • 0

If you mean the yellow cube no that's not normal. I'd almost suspect your monitor cause it's in the same place every time.

 

The third photo looks fine to me, but that's very likely cause in taking the shot you turned your ENB off with F12. But I think I know what you mean and if I'm correct it's essentially an Engine fault. It can be fixed by installing the ENB Hair Meshes option in FCO.

Yeah I mean that cube and in some views one blue cube in the top left corner ... It seems that the yellow one replace the cursor and the blue some part of the hub, that's strange .... How do I fix that ? ôo

 

 

Double iris': NVR3 is clashing with FCO. Open up NVR3 in MO and go to the "Conflicts" tab. Hide any file in the upper box that has the words "FCO" in it. 

 

Transparent/See Through Objects: Disable the Steam Overlay. It is incompatible with ENB and you don't need it anyway. ENB has its own screenshot feature. 

 

"Strange Aura": This is an issue with ENB and the game engine and cannot be completely fixed; even with said ENB Hair Mesh options. What you are seeing is the Mesh's Alpha Channel. 

 

Cube: I am not so sure actually. :\

For the conflict tab I'm trying that right away, I'll tell you if it works ...

 

I had the double iris thing as well. Deleting NVR3 completely sorted the problem, so it was indeed a conflict with that mod, as Audley said.

Btw, I deleted NVR3 because I like the skins from FCO much better. Personal taste and all that.

 

 

While I really think NVR3 is a good mod, I just plain don't use it due to the vast amount of issues it causes. It conflicts with other mods such as: Type 3 Body, Robert's Male Body, Interior Lighting Overhaul, Spice of Life, and of course mods like FCO. No matter how many proper tags you add, a bashed patch isn't going to fix all of these issues. I hate to say it but this mod will be a bit of a mess until proper compatibility patches are made. :\

I think if I dont get the game to work I'll delete NVR3 too ...

Hey i noticied your running a non english version of fnv that may create issues with mods that are made with the english version of the game due to having different formids while i dont know if it could cause the problems you are having it may be something to look into in fnvedit incase if fco or nvr3 are causing the issues

 

here is more information here

 

https://forums.nexusmods.com/index.php?/topic/1588819-non-english-user-running-english-mods-english-creator-making-non-english-translations-read-this/

I thought of that too, but it seems diffcult to fix ... :(

Share this post


Link to post
Share on other sites
  • 0

So :

 

- The eye glitch has disappeared when I hide the conflicts with FCO, ty Audley !

- Have another problem with eyelashes ... See first photo. Is that ENB ?

- Then more photos of the cube problem ... I really think it's the UI/HUD (other cubes appears when I put the "yellow cube cursor" on something) but I dont know how to fix it ... Is that a language problem ? A font problem ? Maybe the writting of the HUD is not displaying properly but I don't know why ...

 

Please help :( (again)

 

PS : maybe you want me to create another topic on that particular weird problem ?

 

(had to cut pictures because dont have enough upload space ...)

 

PS n°2 : MO said that error thing maybe ... ?

 

DEBUG (23:43:19.0602): remove mod file D:\Steam\SteamApps\common\Fallout New Vegas\Data\Bashed Patch, 0.esp
INFO (23:43:19.0602): deleting D:\Steam\SteamApps\common\Fallout New Vegas\Data\Bashed Patch, 0.esp -> D:\Steam\SteamApps\common\Fallout New Vegas\data\Bashed Patch, 0.esp
DEBUG (23:43:19.0677): using path from previous deletion: D:\Steam\SteamApps\common\Fallout New Vegas\data\Bashed Patch, 0.esp
DEBUG (23:43:19.0677): remove mod file D:\Steam\SteamApps\common\Fallout New Vegas\Data\Bashed Patch, 0.esp.tmp
ERROR (23:43:19.0677): not a mod directory: D:\Steam\SteamApps\common\Fallout New Vegas\data\Bashed Patch, 0.esp
DEBUG (23:43:19.0724): move (ex) D:\Steam\SteamApps\common\Fallout New Vegas\Data\Bashed Patch, 0.esp.tmp to D:\Steam\SteamApps\common\Fallout New Vegas\Data\Bashed Patch, 0.esp - 1 (183)
DEBUG (23:43:19.0724): handle opened with backup semantics: D:\Steam\SteamApps\common\Fallout New Vegas\Data\Bashed Patch, 0.esp
DEBUG (23:43:19.0770): get file attributes: C:\Users\M�lanie\AppData\Local\FalloutNV\plugins.txt -> D:\Steam\SteamApps\common\Fallout New Vegas\Mod Organizer\profiles\Fear and Loathing\plugins.txt: 20
DEBUG (23:43:19.0770): get file attributes: C:\Users\M�lanie\AppData\Local\FalloutNV\plugins.txt -> D:\Steam\SteamApps\common\Fallout New Vegas\Mod Organizer\profiles\Fear and Loathing\plugins.txt: 20
DEBUG (23:43:19.0770): get file attributes: C:\Users\M�lanie\AppData\Local\FalloutNV\plugins.txt -> D:\Steam\SteamApps\common\Fallout New Vegas\Mod Organizer\profiles\Fear and Loathing\plugins.txt: 20
 

 

Edited by Pandore

Share this post


Link to post
Share on other sites
  • 0

I think you may be correct about an issue with your UI.

Probably best to make a UI specific thread so others might have a better of chance of seeing any answers if it is labelled as such.

 

First thing I would check is the DarnUI font section in the [Fonts] section of the INI. Go over that section of the guide again.

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 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.