TheCourierModder

In my case, Camo Options came alphabetically before Main File, and Styles came alphabetically after Main File. This is why I think the Camo Textures were being overwritten by the Main File folder and then the meshes of the Main File folder were successfully wing overwritten by the Styles folder.

I have had a mini breakthrough, though I don't know if my hypothesis is correct. I renamed the folders of the mod with numbers in front of their title, corresponding to the order the FOMOD has the user install them. Ex. "1 Main File," "2 Style," "Choose Texture," etc. I then re saved the FOMOD, tested it, and it worked! I didn't change any file paths, just renamed the folders with numbers in the order the FOMOD should install them. For example, in my initial FOMOD that wasn't working, the texture folder was called "Camo Options," the second folder was called "Main File," and the third folder was called, "Styles." When the FOMOD installed, the main file would be installed first, then you choose a style that overwrites the main file, then you choose a camouflage texture that overwrites the main file. The problem was that meshes in the style folder were overwriting correctly, but texture files from the Camo Options folder weren't overwriting. My hypothesis is that the FOMOD was installing the files not in order that the FOMOD installer had you choose them. But alphanumerically based on the folder names.

Also, I have noticed that with Vortex, when installing this FOMOD it can install meshes, then later overwrite them successfully with other mesh options, but it won't do the same thing for textures, as we have seen with my mod. Bizarre.

Hmm that sounds like a good idea. Yeah the main file installs both brown and desert jacket .dds files, and then the optional camo page is supposed to overwrite the desert jacket file (which is why they all have the same name). I will do as you suggest and move separate the desert jacket texture file from the main file and add it to the optional files, and then the FOMOD should theoretically only install one of those options. This issue doesn't affect Mod Organizer 2 for some reason, as it installs the overwriting texture files correctly. Why would this only happen with Vortex?

Hello, I was wondering if anyone had any suggestions here for a specific issue I am having with installing a FOMOD via Vortex. I have consolidated my recent mod for Fallout New Vegas, The Courier, into a FOMOD using the latest available FOMOD Creation Tool and following the "How to create mod installers" guide on Nexus. The FOMOD works perfectly with Mod Organizer 2, which is what I've been using, but I've had a few reports from users that the mod is not installing correctly through Vortex and NMM. Today I installed Vortex, linked it to New Vegas, installed the mod, and tested it out myself. The FOMOD opens correctly and appears to work initially. After it is completed and the mod is installed, I checked the mod's file manager and tested in-game, and saw that part of the FOMOD did not install correctly. The specific issue in question is one panel of the FOMOD where users can choose from a variety of optional camouflage textures to overwrite the mod's base jacket camouflage texture. After installing via the FOMOD, the optional textures do not show, instead leaving the mod's vanilla base texture intact. I initially thought this was a user error or mistake during installation on the user's parts, but now I can confirm that the FOMOD I created is not installing correctly on Vortex. However it works just fine with MO2 which is confusing. I am at a loss as to if this is a Vortex issue, a FOMOD issue, or some other mistake on my part. Any help would be appreciated. =) - dasmart88

Success! ' "

Ok, I turned off "smart punctuation" in my iPhone settings let's see if this worked.

That might be the problem then. Iâve really only noticed it when typing in my iPhone. It happens with the apostrophe and quotation marks from my experience.

Does anyone know how to fix this? Whenever I type a word with an apostrophe, it gets changed to an âaâ with a chevron over it. Like this: Letâs go! Itâs ok. Heâs over there. Why does this happen to me? My region settings are all North America.

Hi everyone, dasmart88 here. So sorry I never posted a follow-up. I ended up rebuilding the outfits, with some necessary changes, in Blender, which somehow magically solved the crashing. The downside, is that there were some changes I had to make to the armor that for some reason no longer worked (like the boot knife). I was in a rush to solve the problem and didnât get to work on it more after the fact so I never found out what the real issue was. Thank you JohnGrimm for posting a solution. Iâll have to dig up my old bugged models and see if I can recreate the problem and try out your solution.

I recently created an armor mod using vanilla mesh mashups. The problem is, with several of the armor pieces, the game will immediately CTD if I take damage while in 3rd person. If tgm god mode is enabled, it does not crash. To create the armor pieces, I used Outfit Studio to import what I wanted and deleted vertices and moved them to make them look just right. Then I applied the meshes as new armor pieces In Creation Kit, loaded up the mod, then played without issue. I even tested to make sure the animations all worked fine. But several of the armor pieces are causing this weird CTD if any damage is taken while in 3rd person. I tried rebuilding those meshes but the result is the same. One of the weird ones is a right armor piece. The vanilla mesh is armor that goes from the wrist up to the shoulder. It works normally in-game. I removed the shoulder piece and it still worked fine. As soon as removed the rest of the mesh, leaving the forearm piece I wanted, it would again CTD on taking damage.