39 réponses à ce sujet

[Machinima]

When I try to call FaceFX I get the following error:

FaceFX Studio was not found, please use configure toolset to specify proper location

I tried to run configure toolset program, but found no way to specify FaceFX location within it.
Does anyone know how to specify the location of FaceFX in the toolset?

[Staalkbh]

I wondering about this myself...

[Machinima]

Hope we find someoen to help us with FaceFx.

Tried FaceFX as standalone tool. The example that is provided does

not work either an FaceFX crashes.

[BryanDerksen]

We've also had reports of the "Generate FaceFX" command simply not showing up in the Tools menu at all. Something's obviously not entirely robust about how FaceFX and the toolset are working together, I'm going to see if I can figure this out.



Just to make sure, since I'm only seeing the reports of bugs and not successess - is FaceFX working for most people who've tried it? It works on our test machines, but we only have a limited number of configurations we can try on those.

[Arkenor Oakshadow]

Are you sure it's not connected to the Keyfile issues that are stopping many of the utilities from working?

Are you definitely using the same version of the toolset as we are? There was talk of some sort of mixup, as not only does our toolset miss keyfiles for utilities, but also we have database entires not matching between the toolset and the game, as described here: http://social.biowar...114380/2#128953

Modifié par Arkenor Oakshadow, 10 novembre 2009 - 05:40 .

[Eizneckam]

It does not show up at all for me. Running Windows 7 64-bit with DA installed from Steam. "Generate VO Local" blows up too, with the following:



E: 12:34:13 - 'Age\\addins\\test\\core\\override -platform Win32 -addin_folder_name test' is an unknown option



Don't tell me that's a space-in-the-path bug... =)

[Eizneckam]

So I went looking around, and... sure enough, HKCU\\\\Software\\\\BioWare\\\\Dragon Age\\\\Toolset\\\\Environment\\\\FaceFXStudioPath was empty. Set it to C:\\\\Program Files (x86)\\\\Steam\\\\steamapps\\\\common\\\\dragon age origins\\\\tools\\\\FaceFX and my FaceFX menu item appears now.

Modifié par Eizneckam, 10 novembre 2009 - 06:47 .

[Eizneckam]

Side note: that backslash escaping bug in the forum is _super_ annoying.

[Machinima]

Tnx, patching the registry entry did work for me as well.

Great to see FaceFX up an running.

[st4rdog]

Nice find Eizneckam. It works.



Here's the step-by-step for anyone clueless:



Start > Run > regedit

[Yoshidingue]

Thanks a lot str4dog, this worked for me and the FaceFX menu now shows properly. Strangely, I had to create the whole Environment key myself, because the toolset didn't create it.

Windows 7 x64 here, if it helps.

[ixobelle]

I also didn't even have the Environment key.

for anyone who doesn't have it, just right click on Toolset > New Key, name it Environment. within that, create a new string as shown above.

p.s. windows vista x64, SP2

p.p.s THANK YOU FOR THE FIX!

Modifié par ixobelle, 11 novembre 2009 - 09:34 .

[KaylaKaze]

Weird. I don't have "Environment" at all in my registry for the DA Toolset

[Smakit]

Vista x64 here as well.



Also never had the menu item, nor the Environment key. Quirky little thing, but props to everyone for their continued work on this stuff - well done.

[Grimmy0nzU]

I tried this fix for the registry but it still will not work for me. Any Ideas?

[Grimmy0nzU]

Nevermind. I reinstalled the toolset and now it seems to work. It managed to add the Environment key the second time. Odd...

[Shar888]

Was going insane before I found this thread. Thanks very much for the work around.

[Ginggis Khan]

Fix helped me too, thanks a lot guys, you rock, Bioware sucks in this case, but generally it rocks. I feel ashamed actually that they have released quite so full of bugs and problems.Toolset. Its like we had to figure out not only how to work with it due to a poor documentation but how to actually MAKE IT WORK. Bad bad Bioware. Boo .

[Blind Bard]

Worked like a charm, cheers fellas!!!

Modifié par Blind Bard, 30 novembre 2009 - 08:29 .

[R3v3r3nD420]

So, I didnt have the "Environment" entry either. After following the suggestion above of re-installing the toolset, I still did not have a registry entry for "Environments". I went ahead and just created the whole "Environments" section from scratch.

Upon loading up the toolset it tells me that the module that its trying to load on startup (the last module that was loaded), my custom mod, is gone. Really?

So its telling me that I cant even reinstall the toolset over itself without losing EVERYTHING I've done??

Please someone tell me there is a way to get my stuff back in the toolset. The mod was still in the works so I dont have a .dazip, and hadnt needed to make a b2b package yet either. Is my stuff gone for good? My 2 weeks of hard work vanished?

Might just be done with the toolset and dao if so....

EDIT: ALL of my mods are missing from the manage modules menu!!! HELP!!!!!!!!

Modifié par R3v3r3nD420, 01 décembre 2009 - 01:29 .

[Looy]

I used this fix and now Face FX is working as I can preview lines, however I still don't get the menu option. Any Advice?

[Looy]

Okay fixed it, I misspelled "Environment"



Anyway, if you click File > Restore Environment it should add the Environment Key to the registry, then you only need to add the FaceFX string instead of everything else.

[Fralboj]

I did everything that's been told on this topic but FaceFX still doesn't show up. I restored environment, and modified with Regedit, but no result... I'm completely stuck with the post-sync now.

Any help please ?

[Syberduh]

Yeah same problem here. Went into regedit but environment was already there and the FaceFXStudioPath was already correct (C:\\Program Files\\Steam\\steamapps\\common\\dragon age origins\\tools\\FaceFX) Could this be another Steam issue?

[Mielieman]

Hmm, I had the missing FaceFX problem too. Nice work on finding the solution. It seems that for some reason the toolset doesn't create the registry entry on any of the 64-bit systems, since it's the x64 Vista and 7 users who have been victimised.



Shouldn't be too hard to fix in the next version though I'd imagine.