The forum has been set to read-only mode. For community discussion and questions, head over to our Discord: https://discord.taleoftwowastelands.com

Missing Meshes2.bsa?

General help and technical troubleshooting. Ask for help here if you can't find an answer in the FAQ.
Post Reply
SupremeDream
Posts: 2
Joined: Fri Jul 15, 2022 11:09 pm

Missing Meshes2.bsa?

Post by SupremeDream » Fri Jul 15, 2022 11:29 pm

Hey, I am probably being really stupid here but I don't know. I may figure it out myself I'm not sure.
I have just newly started playing TTW, and all was fine until I left Vault 101.
Across the entire capital wasteland, there are exclamation marks scattered across the distance.

I did some research and many forums pointed that it could be an issue with archive invalidation, mostly the "Meshes2.bsa" archive not being ticked under the Archive tab or MO2.
I looked at the Archive list and low and behold the list doesn't even contain the Meshes2.bsa.

I'm assuming TTW gets all the archives and data from both origins which are Fallout 3 and Fallout New Vegas directories during installation.
Assuming that, I thought maybe there should be a Fallout - Meshes2.bsa archive in one of the fallouts, but there isn't. Neither directory has the Meshes2.bsa.

Before installing TTW, I had been playing Fallout 3 and New Vegas vanilla (modded, but vanilla as in not TTW) and there had been no issues at all.

Is there any way I can acquire the Meshes2.bsa archive, or am I just going to have to reinstall TTW and hope that I will get this Meshes2.bsa archive?
Here is my archive list:
Image

SupremeDream
Posts: 2
Joined: Fri Jul 15, 2022 11:09 pm

Re: Missing Meshes2.bsa?

Post by SupremeDream » Sat Jul 16, 2022 12:34 am

UPDATE!!!
Turns out I was in fact stupid.

Not sure if this was the issue(?) but it's fixed either way.

I have both the GOG and Steam versions of FNV and FO3. The GOG versions have all the DLC's while the Steam version does not.

Anyway, during the TTW installation process I used the GOG versions of the games.
But previously for the TTW portable instance, it was pointing to the Steam version of the game, rather than it being the GOG version of the game.

You're probably going to cringe, but the Steam version of the game was within the Program Files directory.

I think the issue could have been caused from mixing and matching. TTW was built from the GOG versions of the games, but I used an instance pointing to the Steam version of the game.
Either way, it's fixed! (I think, I have not fully tested)

Post Reply