theobeau

The cleaner look is appreciated...Will have a look around to check out the rest of the upgrade.

An interesting post that does a large way in explaining the difficulties and challenges in running and paying for the Nexus service. I can see the logic in incentivising but not forcing users to turn off ad blocking software. Finally, have you considered other ways of encouraging the non modding user (whom I presume make up a large majority of Nexus users) to endorse mods? While it may be difficult to implement fairly (the Steam example being an excellent one) a running tab of user endorsements or having it count to something minor status related may be worth considering.

Great article about crowd sourced funding and the potential it has in re-invigorating PC gaming. Also hope your article helps Sui Generis in its final push to reach what looks like a fund raising goal that is going to be just a little too much though I really hope I an wrong!

As a player who likes his cRPGs but is totally inept at creating custom content, Nexus' series of sites is a godsend. However, this post and several others that Dark0ne has posted has made it clear how much thought and effort has gone into supporting and updating the infrastructure of Nexus. The move towards greater transparency is much appreciated.

Hello there, Thank you for the detailed discussion on the philosophy behind Nexus. While corporate and financial metrics are obviously important, it is heartening to see that what drives Nexus is a sense of whether the game and Nexus match each other and what each party can bring to the relationship. As an aside, I'm pleased to see that cRPGs still play such a prominent role in Nexus. The news that Nexus is supporting Obsidian's Project Eternity was a small but definite part of my decision to back their Kickstarter campaign. It will be interesting to see what comes of that one! Cheers.

@bjd955, If you still haven't solved the problem, try the mod mentioned earlier in this thread. http://newvegas.nexusmods.com/mods/43813 Worked much better for me than fiddling around with slave collars and trying to work out which mods use them as bases, which seemed to be an underlying reason for the error. I hope this helps you.

Quick update and for those searching for similar threads in the future: Jim_UK's suggestion was sound and also was the solution as listed on the Steam forums: Installed a clean version of Steam, Did an initial load up of steam on the new machine Moved the contents of \steamapps from the old to new machine. Made sure that FNV loaded via steam (for some reason Steam decided to re-DL all the master ESM files from FNV and all the DLCs; all 9GB of them! Saved the old FOMM load lists, FNV Configurator profiles, copies of the three FNV *ini files, transferred their contents to the new computer, Tweaked the FNV Configurator profile for the newer PC's improved GPU Crossed my fingers Ran FOMM Much to my relief it then proceeded to run my game as per the old machine through quicker and with improved graphics. Hopefully this thread might be of use to someone in the future who has the same problem. Cheers!

@Jim_UK, I started this thread after not being able to find much info on transferring the game to a new PC on this forum but your comments are reassuring. I'll try instead to move the game as a whole to the new PC rather than the piecemeal method earlier.

After good service of almost 4 years, my Windows XP Quad Core machine is giving up the ghost. That and ME3 have led me to get a new wizz- bang machine with Win 7, SSD, i7 CPU, fancy GPU. The only game I want to transfer to the new machine in the current operational state is FNV as I'm keen to see how pretty it can look with GPU settings turned up to high and as I was in the middle of playing around with a new Courier. I use the unofficially patched FOMM (v0.13.21) to load some 144 mods, mostly direct from Nexus but about 20% have been tweaked with FNVPlugin. I also use FNV Configurator to tweak the game. I was planning to try the the following approach: 1) Back up onto a USB drive from the old computer the the save games and all the contents of the \data folder (esps, meshes, textures, etc....); from FOMM back-up the load order; back-up my preferred FNVConfigurator settings and backup the following ini files fallout, fallout_Default, falloutPrefs from both the steam\etc... folder and the my games\falloutNV folder 2) install (retail in my case) FNV and Steam and then re-DL all purchased DLCs 3) run the new vanilla game once (I think I need to do this to allow steam to re-validate the game) 4) install FNV configutator and re-install preferred settings (after adjusting for new GPU!) 5) transfer in their entirety all old saves and the contents of the \data folder to the new computer to their appropriate locations 6) re-install FOMM, patch it to v 0.13.21 and reload the old load order of esms and esps 7) check that the new ini files so that archive invalidation is turned back on 8) Cross my fingers, run the game via FOMM and play with old saves and mods intact! My question to this forum is to ask for advice and comments about whether this approach is the right one to take and to ask for the experiences and advice from forum members who have successfully transferred their game to the new machines. Any advice offered much appreciated

Hi Daveyofdownunder, For some reason it keeps on resetting every so often. I now make it a habit of making sure auto download is turned off everytime I reboot the machine and restart steam. Something that I've done is to keep a backup of the main BSA and ESM files; there are times that something happens, the files get chewed up and disappear which happened to me when I had problems with the GECK. You can fairly easily work out which file is missing and it is far easier to paste back in your copy of the original that have Steam waste bandwidth and time. Hope this saves you some pain. Cheers!

Hi AzureDrak, I deleted a few mods to bring the total number of active to below 140 and it worked quite smoothly for a day. No texture problems in Goodsprings and around the Mojave. However, I foolishly decided to have a go a making a custom race and installed GECK for the first time; needless to say something stuffed up though it was my fault rather than anything else. I hope the thread offers something use. Cheers!

@AzureDark, I've done a bit of searching to see if others have had the issue. It has been reported before and may have something to do with the number of active mods. When I checked, I found I have over 150 mods installed and active. There is a detailed Beth forums thread that outlines the issue. Hope this helps. Cheers! http://forums.bethsoft.com/index.php?/topic/1223160-some-weird-issues-too-many-mods/page__view__findpost__p__18391001

@Rainmaker91, I think I am experiencing a similar error to yourself; after starting the game, the esc menu may not work, textures don't load up or change colour; large red ! appear instead of items. I've done a bit of research and it may have to do with the number of mods running via FOMM. I may not be explaining it well but there is a link to a beth forum thread that outlines the issue well. http://forums.bethsoft.com/index.php?/topic/1223160-some-weird-issues-too-many-mods/page__view__findpost__p__18391001 Cheers!

@Daveyofdownunder, Good to hear that you are at least saving bandwidth. Best wishes

@ Daveyofdownunder, Hope the instructions switched off the Gbs of downloads replacing the BSA and ESM files. Cheers!