FaejaVu

Both loaded for me. The "broken" one took a little longer, but still loaded. Does anyone know what the actual issue is yet?

Of course it does. This site only tolerates legitimate versions of the game, which unfortunately inherently involves Steam. Even so, legit or ill-legit, the mods will work regardless simply because the files and folders of both games are obviously identical. So long as you follow the directions of where the files of the mod are supposed to be placed, it should work.

I read somewhere that by opening the console, clicking the old tree, typing "markfordelete", saving, and then reloading that save should fix the problem. Unfortunately I can't say for sure because my sapling isn't even showing up... it's quite honestly driving me nuts. Edit: Just realized I replied in a month old thread.. My apologies. >.<

I would first suggest that you make sure you put all the necessary files in the correct places. If you have the ability to do so, check the .dds texture file for the re-texture to make sure that your problem isn't there. I doubt that is the issue (unless the re-texture also includes a remodel, in which case, you'll have to make sure you've included the mesh that should have come with your re-tex mod.). Other than that, I don't have any "grand" suggestions. :confused:

I may have had a similar problem recently. Due to your lack of description I really can't know for sure though. I'm using CBBE Slim, with some other tweaks. At this point I don't recall what all I have applied since I've been slowly tweaking here and there getting it just how I want. Anyway, earlier today while I was looking at different outfit options I had a really odd "polygon discoloration". I had just equipped and unequipped one of the shrouded armors. After I had removed it, instead of seeing my characters skin, there was a very odd black coloration. I really don't know how to describe what it looked like. In a way, it was reminiscent of a one-piece swimming suit mixed with a stripper/assassin/heroin "flamboyancy". Moving the camera caused it to distort some, and at some angles make it cover my character completely, save for the neck/head. Moving the camera into my character and back out allowed the normal skin texture to be seen for a split second before returning to the black poliginal bizarrity (sp? >.>). My only suggestion is to restart the game. Possibly even merely leaving the area you are at or saving and reloading would cure the issue. Since it's "out of the blue" one should be able to assume that one of the mods is not causing the issue, but of course one never knows with absolute certainty. Hope that helps. :happy:

That was an example since I have seen some resource packs use .esp and .esm files. If you have placed the files of the resource pack in the right locations, it should be a simple matter of finding them within the GECK object window list (Remember you can use the search bar if you know what the object is called so you can find it faster.). If they don't show up, Then right click within the list and click "New". The information to fill out on new file window should be fairly self-explanatory. When it comes to the model, a new window pops up. Click the Edit button and a window will pop up for you to select the mesh you wish to use. I hope that explains it a little better for you.

I'm not sure about keeping them organized when installed. They go where they are supposed to go. The only way I can think of to try organizing it any differently would be to go into GECK and change where it references the files from, which would seem to be way too much work for how little it would likely actually help in the long run. So long as you make sure all the files for the mods are in the correct places everything should run fine unless the mods themselves cause some sort of a conflict with another.

That's rather odd. I would suggest trying to reinstall it again. Though if it claims it is installed, try a search of your computer for FalloutNV.esm. That should fairly quickly track down the folder containing FNV data.

If the only problem is that you're missing the data folder, this problem will be very easily resolved. Right click within the folder that the data folder is supposed to be in, click New > Folder and name it Data. So it should be (if remembering correctly since I am not currently at my own computer to double check) Fallout New Vegas / Data. I hope that gets you up and running again. :happy: Edit: I forgot to mention FOMM not recognizing it being installed. There is an option within FOMM to tell it where your game is installed. Unfortunately as I stated above, I can't tell you exactly where that option is since I am not currently at my home computer. Once it's for sure pointed to the right directory though, it should work just fine.

It should be as simple as placing all the files of QSR into your data folder and checking the box of any .esp/.esm files related to it, as well as any others required for your mod (such as FalloutNV.esm) when opening up GECK. Then all you'll need to do is find the assets in the same list you find all the other game assets. :thumbsup:

Well the first thing I would suggest looking at is your computer specs, just to make sure everything is good enough to run the game. Assuming they are, I can think of two things right off to try to fix the issue. First, verify the game cache (right click FNV in the Steam Library and click Properties, then Local Files, and finally Verify Integrity of Game Cache). I've had times where a freshly installed game didn't run until after I did that. The next option, should the verify cache not work, is to reinstall the game. Sometimes files get corrupted or whatnot, so who knows, it might help. If those don't work then someone with more experience with these issues will have to help you. :sweat:

I am aware that it should not happen. According to the file name, I was using GECK 1.4. I suppose it is possible I accidentally got a FO3 GECK and simply didn't realize it. For all I know there could be another issue besides the GECK version, it just happened to be what fixed it for me. I assure you however, I am using a legit version of the game Edit: *Face-desk* I just checked the the GECK readme for the 1.4 file I have and it's for FO3. Not sure how I managed that, but that might help explain why it wasn't working right.

The only other thing that I can suggest at this point is to make sure all the mods/files are in the correct place. Some mods don't extract/install properly due to the creator putting them in extra folders or other similar issues. I've had times where even FOMM doesn't help with those, unfortunately. Edit: "It also says "You have not set a file as an active file. Would you like to continue?" when they're all checked." Why are you trying to open all the files in GECK? Are you trying to make a mod?

Just as a question concerning the mods being off when opening up the data option again. You are clicking the Ok button and not Cancel or the X after checking all the ones you want, right? (I'm not trying to be an ass, just making sure that isn't what is causing them to be unchecked.) If that isn't the cause, I'm not sure why they would be unchecked. I've never had that issue myself. Sorry I can't be of more help on your issue. :confused:

By your description, I would think that the flame texture somehow got replaced. Have you tried reinstalling that DLC to see if that would fix the problem?

I'm sure there is a better answer than the one that I have, but this happened to me before in a mod I was making. I just loaded an earlier save and it worked again. So if you have an earlier save maybe try that but other than that I'm not sure. Sorry I couldn't be more help. I haven't been able to test this mod once yet. I did try an earlier save though. Any earlier and I'd just be starting the game over. Any other ideas? :confused:

Most texture replacer mods I have seen do not have an .esp or .esm file to go with them. Generally they consist of just texture and sometimes mesh files that get put right into your data folder and that's that. .Fomod files are basically just like zip/rar files, only that FOMM unpackages the files and puts them where they belong in the data folder. If the packages are just texture files then you won't see a box to check to turn the mod on. If the textures are not showing up in game like they should be, turn ArchiveInvalidation off, then back on and that should refresh it and the textures should show up as intended in game.

At this point, my mod consists of some simple land tweaks near good springs (consisting of duplicated rocks and a vault gear door), an interior cell with basic layout of my vault/home, and a teleport between the two. I was intending on testing out the layout and seeing what needs tweaked, but it won't show up in game. I can't figure it out. I've done this very thing before (made a door/interior area) and it loaded just fine. The .esp of my mod is in the data folder, the mod is selected in the launcher and FOMM (which is pointing to the correct directory for the game), I have moved from the location where my mod is located to another location and back trying to force it to load with no such luck. I even tried to coc into my mods cell and nothing. I can't figure out where I've gone wrong. :wallbash: Does anyone know how to get around/fix this issue? EDIT: I tried an older version of GECK and tested a new and "mod" (duplicated GSGasStation and renamed) and it worked fine. I tried the exact same thing with the version of GECK I had been working with and had the same issue of it not showing up. Bloody annoying, and I have to restart my work... but at least I seem to have found what was causing my issue...

I had that issue when I tried that mod (actually mine was one boob going straight forward, the other going straight down). What ended up fixing it for me was a clean install and my triple checking that I put all of the files for the mod in the correct places. Unfortunately I never figured out what specifically caused that problem. :confused:

I would like to add necklaces (not chokers) to your list. I'd make something myself, but I lack the know-how of modeling objects like that. I haven't even had any luck getting the programs used to make them set up properly haha. :sweat:

I know of a mod that does what you're asking, though it isn't a suit. Perhaps it will still be what you're looking for? :happy: http://www.newvegasnexus.com/downloads/file.php?id=35115

I took a look around the Nexus for a mod to do as such. Unfortunately I only found one, and so it's probably one you've already found and tried. Here's the link just in case: http://www.newvegasn...e.php?id=42877. You could try requesting such a mod in the Mod Requests section of this forum. I don't imagine it will be too hard to find someone with the modding experience to make this happen. :thumbsup:

I've checked other topics and console commands rarely seems to work. All the characters will tell you is "What do you need?". The quest need to be triggered or else nothing would work. I know there are some console commands relating specifically to quests. Using "setstage 00129d14 1" should theoretically be all one would need to do is set/trigger the quest to the first stage (and perhaps add the MoC to their inventory) and could continue as if nothing happened. Or was that one of the commands mentioned and wouldn't work for fixing this? I looked up the quest itself on a fallout wiki and unfortunately this particular bug was not listed, so that wasn't particularly helpful. My google search didn't turn up any useful information either. Unless there is some mod conflict somewhere somehow, I have no other ideas outside of what I have already suggested to rectify the bug. :sad:

Yeah, those annoyed me too, so I just deleted the files altogether and that solved my issue. :happy:

I use all three of those mods and I've never encountered this issue. :blink: What was the last mod (or set of mods) that you added prior to this showing up? If it was a set, remove them all, test to see if the blue dots appear, and if they don't, start adding the mods back until you do. If it was just one mod, remove it and see if that fixes the issue. Not sure what else to tell you since I haven't had it before.