NPC lips not synced with dialogue.

[screams2jz]

I recently got a new computer, reinstalled my copy of F:NV, and all my mods. Everything is working perfectly. Everything except...

 

In dialogue with quest givers or other NPC's, their mouth stops moving long before the sentence they were speaking is over, and when their lips ARE moving, it is absolutely NOTHING like what they are saying. It almost looks like Steam installed F:NV in another language, but the audio that plays is still English.

Any input? This is supremely annoying.

[GrindedStone]

There's a .ini setting for LoadLipFilesInBackground Something like that. You could try that. Also I would use Fallout, Vegas, or Skyrim configurator to set things in the .ini because it's easy to mess up. In Vegas you have to set it in a possible of 3 different .ini for the lip background an it's possible you would have to do this manually rather than using the configurator. There's the .ini in the games folder named fallout default, then the other two .ini in mydocuments/mygames/vegas. What I usually do is check them to see if the setting was there an if it is just change it. If the setting wasn't there I ignore that one. You could also try lowering some of you settings. Namely the draw distance.

[screams2jz]

I'll give this a try! Thank you. Weill let you know what I come up with.

[m3th0d2008]

I've suddenly the same problem. Never had that before. But I should mention that this is the first time that I play with the latest official patch that forced VSync on everyone. I deactivated it via the .ini files. Maybe that's the cause why the lips move way too fast.

 

*EDIT*

 

Yep, just as I thought. This is caused by deactivating VSync in the .ini files.

 

iPresentInterval=1 (VSync on, lips sync)

iPresentInterval=0 (VSync off, lips going crazy)

 

This really sucks because I did the standard MouseAccel fix but it still felt wonky. I googled abit and found out that they forced VSync on everyone with the most recent patch (the checkbox in the Launcher Options has no effect anymore) so I deactivated VSync in the .ini files and all was good again... except for the lips of madness. Guess I have to live with a bit of wonkiness since the lip desync is unbearable :D

Edited August 9, 2012 by m3th0d2008

[screams2jz]

I've suddenly the same problem. Never had that before. But I should mention that this is the first time that I play with the latest official patch that forced VSync on everyone. I deactivated it via the .ini files. Maybe that's the cause why the lips move way too fast.

 

*EDIT*

 

Yep, just as I thought. This is caused by deactivating VSync in the .ini files.

 

iPresentInterval=1 (VSync on, lips sync)

iPresentInterval=0 (VSync off, lips going crazy)

 

This really sucks because I did the standard MouseAccel fix but it still felt wonky. I googled abit and found out that they forced VSync on everyone with the most recent patch (the checkbox in the Launcher Options has no effect anymore) so I deactivated VSync in the .ini files and all was good again... except for the lips of madness. Guess I have to live with a bit of wonkiness since the lip desync is unbearable :D

 

 

 

Amazing. Confirmed! I tried both settings, and had the exact same results.

 

Well... damn. This makes me a sad panda.

[GrindedStone]

It's not a first person shooter. FO3/FNV has never been better with Vsync off. Your havok physics along with every animation in the game will speed up an slow down depending on load. That's why it was forced. Because if it isn't someone will turn it off thinking it's better. You run into performance limits from picking settings that are too high, then go to disable Vsync to get something back. It's not that kind of game. If the framerate is slow, *ahem* turn down the settings/detail/quality...

[m3th0d2008]

It's not a first person shooter. FO3/FNV has never been better with Vsync off. Your havok physics along with every animation in the game will speed up an slow down depending on load. That's why it was forced. Because if it isn't someone will turn it off thinking it's better. You run into performance limits from picking settings that are too high, then go to disable Vsync to get something back. It's not that kind of game. If the framerate is slow, *ahem* turn down the settings/detail/quality...

 

It's not the framerate that is low, it's the mouse that feels wonky when it's active. I already deactivated the mouse acceleration. It has absolutely nothing to do with my performance since the mouse is wonky even when my fps is maxed at 60fps vsynced to my display's 60hz. Ontop of that, I never had any problems before the update that forced it on everyone.

 

Gamebryo behaving weird again, that's what it is.

[GrindedStone]

Wonky like you fire a weapon an there is a delay? You can lower CPU pre-rendered frames to combat input lag. Idk if that's the cause though. You got any mods running? Autosaving & Quicksaving much? I would say to look at the recent save game file size. If it's 15 to 20 Mb it's suspect for coruption. Then any weird looking saves in there like .bak backup copies, scripted autosaves, and modder forced saves are all suspect to cause issues. Delete em.

 

If you have a bunch of unused .esm an .esp in the data folder it will certianly go wonky. Delete that an any other useless junk. Then you could take your two .ini files in My documents/my games/vegas then move them somewhere else for safe keeping. Then use the launcher to auto generate a set of default autodetect .ini Although editing the falloutdefault in the games directory would prolly mess that up. So hey take that one an put it with the others, then use Steam to rebuild the game cache, then launcher, which will generate new vanilla .ini

 

After that go to the start menu an search "add or remove programs" look in the list for Visual C+ See if you have any. Normally I have bunches of them. I get them from games and applications or microsoft. Steam say to install both the 32 an 64 bit versions on 64 bit machines. Then in the past crashing issues have been resolved by un-installing these, an trying it. Or re-installing them afterwards...

 

Prolly last I'd wag the finger at merged/bashed patch creation an the possible cleaning of the mods with FO3/FNV edit which would resolve a great deal of issues. The more mods you have the more issues would be resolved. It's pretty simple to clean just lots of clicking. Merged patch an bashed patch are kind of the same thing in different flavors. If you don't know a lot about how the game works then bashed patch an BOSS is better for you. Though this is only because it's a bit more automated. When it boils down to it using the other method is just putting in some work.

 

Bashed is part of Wyre bash. You select a few settings then it generates a bashed patch an also merges any of the little stupid mods into the bashed patch an deactivates the mod. As a way to allow more mods to be used. Like saving space. The bashed part takes all the list type data in race, loot, leveled lists, inventories all of which many modders all change the same thing. So the bashed patch merges them all together so everything is used, not just which ever mod loaded last. Merge patch does the same thing. You can figure out bashed patch on your own it's that easy.

 

Merge patch you load up the whole load order. When it finishes you click one of the mods in the left window. Hit Ctrl A to select all, then right click that an create merge patch. Save it. You can also edit the merge patch to smooth out those areas. Then when you change the load order you generate another one. Same with Bashed.

 

Cleaning in a nuthouse

 

These are pretty basic operations one performs with FO3/FNV edit. You can't clean the Fallout.esm or the DLC's. Also FWE can't be cleaned, but yet it's insanely dirty. That means that even under perfect conditions anyone using FWE is going to have crashes. It may not be many crashes, but it will have them. It depends on the amount of the game that is dirty. As a modder often I change one tiny thing, then load a save game an it has a seemingly dirty caused random crash.

 

Load up the whole load order. Apply a filter with only the conflict inherited by parent box. Remember to skip the DLC an FWE. Start at the top an right click each mod an pick remove identical to master records, then set delete to disabled. Do these two operations on each mod top to bottom. Remove the filter, go back up to the top. Skip the DLC an FWE. Right click each mod an pick clean masters, then right click again an sort masters on all the mods bottom to top.

 

Now look at how many of these mods are in dark bold type. That means they have been modified, or that something was wrong with them. "dirty" Hit Ctrl S to save it. Then if you wanted to you could create a copy of all your FWE esm an esp, put that in a folder somewhere else. Then attempt to clean FWE as described above to see if it works or if you get an error. Then you could experiment an see if just not cleaning the one that causes the error, but clean the rest.

[m3th0d2008]

The wonkyness happens already in the MainMenu. Doesn't matter if I deactivate all the mods or not.

 

It acts a little slower, feels unprecise. Quite the same as it does with activated MouseAccell but way, way more subtle. With VSync off it's absolutely precise.

[screams2jz]

The wonkyness happens already in the MainMenu. Doesn't matter if I deactivate all the mods or not.

 

It acts a little slower, feels unprecise. Quite the same as it does with activated MouseAccell but way, way more subtle. With VSync off it's absolutely precise.

 

 

That's precisely the problem. The mouse movement feels like it's moving through thick jelly. (If that makes any sense.)

The exact reason I turned Vsync off.

 

 

After this (I was OP) I turned it on, and it fixed the issue. Just had to deal. Makes aiming precisely a pain in the ass, but hey. The lip thing was just getting on my nerves too much.

 

 

Also,

Added a neat screenie that became my desktop as thanks for all the help. Was one of the more memorable characters in OWB for me.

Edited August 11, 2012 by screams2jz