Jump to content

Non-Windows FNV Gameplay


Recommended Posts

Posted

Just a FYI,  having browsed the forums for answers for lots of different issues and tweaks, I notice that LOOT or BOSS or FNVEdit or other applications/utilities tend to be the answer for problems.

 

Sadly, none of these applications will run in a Virtual machine environment that supports Fallout New Vegas. It appears that the microsoft .Net libraries required for these to work and the ones for Fallout New Vegas to work are incompatible.

 

While another virtual machine can be made the will run them, (it actually ends up needing three separate ones, one for FNV, another for FNVEdit, and one for BOSS/LOOT), because it is a separate virtual machine, it will not allow any editing of the ESMs or ESP files or making any fixes to load order.

 

I know this is not a developer forum, but something to consider as a good practice when writing code for things like FNVEdit, FOMM, BOSS/LOOT, etc.

 

Do not rely on the .NET runtime. Package all file required for your application in their own directory. Windows will then run the different .dlls required for each application in a different memory space, using the directory specified for the application build. This way the core operating system directories are not affected, yet the versions of the required files are there to support the application. Just something I learned over the years when having to write code for multiple operating systems and versions of windows.  

 

A master listing of a load order that does allow the different plug-ins for Sexout to work might be a nice thing to have, so instead of relying on the user to "fix" the load order with BOSS or LOOT, that might not run on their installation, they can be referred to a sticky with that "recommended" load order.

 

While the fomod format is great, sadly for some reason the version of .7z in FOMM seems to only uncompress about 60 percent of the mods. It might be that they are in a different format compression format. Most compression programs can sort it out, such as Betterzip, Archive manager, etc. Listing what compression format used for a fomod posted would be helpful, I have discovered that the ones that fail and crash FOMM, sometimes if I change the compression default, they work. I think, have not investigated but it appears to be a issue with the .7z code that causes this.

 

Just some suggestions.

 

fssntuff

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...