Jump to content

Recommended Posts

Posted

Confused

 

So, after reading 30 pages of this thread, my head is abuzz with all the things mentioned, and I can no longer make sense of what has become an incomprehensible mess.

 

Today, I bought a Microsoft LifeCam HD 5000 (great cam btw!) which is listed on FaceTrackNoIR's website as being compatible with their software. I made sure to get the latest firmware and software updates for the cam.

 

I then downloaded the FaceTrackNoIR 1.3 version. Installed it. Downloaded the other updates, and installed them. I also grabbed the 64-bit API for A-10c and followed the directions for it. I go to fire up FaceTrack, and it is a no go. I get the very unfriendly waterfall message, and the subsequent message after, included in attachments.

 

So, I decide to see if the demo from the Seeing Machines site works, but it provided the same unfriendly messages. Supposedly, the FaceTrack program should be working first go, especially with the DCS A-10 API installed, first blush. This is apparently an ugly lie, or I missed something.

 

I decided to start over, and wiped all the previous progress out. I downloaded FaceTrack ver 1.3 and installed that only (with admin rights). Installed fine. However it still provided the previous message.

 

This leads me to believe I'm an idiot, even though I never have this much trouble installing anything. The manual is less than helpful. There is no troubleshooting for this issue on the site. The information I found within the thread I have since lost, and was dealing with things before the API release.

 

So, can somebody give a step-by-step rundown of the current, up-to-date, process? Starting from zero, with nothing but the original camera software installed. Must be for Win 7 64 Bit Home Premium. I'm tired of trying to sort the useful information from all the calcophony of noise.

 

I was hoping to go this route to make my time flying in DCS A-10c better, and more enjoyable, and I've held off doing anything more than lurking on these forums for the last two months. At this time, I'm stuck. My head hurts, and I can hardly tell up from down in all the mess. :helpsmilie:

Waterfall.PNG.4847345ca1050256c1910ec37184a548.PNG

Waterfall2.PNG.43b35d5883b42da0630f1ad046fa1d75.PNG

  • Replies 390
  • Created
  • Last Reply

Top Posters In This Topic

Posted

Hi TraumaBait,

 

I'm sorry to hear that you have spent the last two months trying to get face-tracking to work. :( I wish you would have contacted me earlier.

 

There are a few questions left, even after reading your impressively-sized post: what CPU does your PC have? Have you read the 'known issues' page on the FaceTrackNoIR website?

 

The waterfall-error is caused by the IPP-runtime library. For some CPU's, the installer makes a mistake and installs the wrong DLL's. What you should do (it's also on the known-issues page):

 

  1. un-install the IPP-runtime, via Control Panel/Software;
  2. install the faceAPI demo;
  3. try the faceAPI demo: it should work now;
  4. try FaceTrackNoIR: if the demo works FaceTrackNoIR also should.

There is an important difference between the demo and FaceTrackNoIR: the demo uses a newer version of faceAPI. For i5 and i7 CPU's, update 1.6 (under construction) of FaceTrackNoIR fixes this.

 

Hope this helps to relieve your headache... :music_whistling:

Posted (edited)

Thanks for the clearing up. It hasn't been 2 months, but more like half a day. I've been flying in DCS A-10 for about 2 months. Big difference. I'll take a shot at your suggestion, and let you know how it goes. :)

 

Running an Intel i5 dual core, and yes I checked the known issues. Didn't help me much.

Edited by TraumaBait
Posted

On a seperate note I assume others experience this too... The facetracking API seems to respond to changes in facial movement like eyebrows, where as we are only really interested in head motion. I suspect this added motion or sensitivity increases the amount unwanted movement in game is it perhaps possible to switch it off or simply not utilise this feature of the API?

Posted
On a seperate note I assume others experience this too... The facetracking API seems to respond to changes in facial movement like eyebrows, where as we are only really interested in head motion. I suspect this added motion or sensitivity increases the amount unwanted movement in game is it perhaps possible to switch it off or simply not utilise this feature of the API?

faceAPI uses a set of 'facial-landmarks' to calculate that rotations and translations. The non-commercial version used is a 'basic' version, options like lip- and eyebrow-tracking are actually disabled.

 

So I'm afraid it's not possible to prevent the response, by deactivating things... :cry:

Posted

Good News Bad News

 

So, good news, bad news.

 

The face tracking software works, and tracks. However I am now having problems with DCS A-10c.

 

The program loads fine, into the main screen. It however immediately crashes whenever I try to go fly, like say in Instant Action. If I try to go to options, it hangs on the loading screen, and will not go to the options screen.

Posted

are you running both facetracknoir and dcs a10c as an administrator? That fixed the crashes for me

System:

i7 920 @3.8ghz; GTX 560ti 448; 6gb DDR3 1600 ram; 750gb HDD; 750w PSU; Win7 64bit; x52 Pro; TrackIR 5

Posted

Ok, that straightened out my crashing Username455. Still hasn't straightened out the problem with A-10C hanging when I try to go to the option screen.

 

Anybody know the fix for that?

Posted (edited)

Hey TraumaBait. I've had all the same issues you've had including the problems with A-10C after getting face tracking working. The problem was with the "headtraker" folder I was supposed to add to the bin directory. I placed the files in it, but not the headtracker folder itself. After placing the files & headtracker folder into the bin directory and loaded the A-10C.ini file in facetrackernoir, everything started working just fine.

 

I'm going to create a new thread with my steps A, B, C ;) (done)

Edited by miahallen
Posted

Hay traumabait, how did you get it to work, I seem to be living in your past.

 

Waterfall...

Installed demo can see my facetrack in it.

 

Run FTNOIR and press stat and get a

 

failed to initialise APIScope: unspecified error.

 

Ive unistalled reinstalled and got very very drunk. The wife woke me asleep in my cockpit at 12pm last night after numerous beers to calm the temper!!

Posted (edited)

I skimmed the pages, barely anything on FC2.. why? if I do what most of you did for A10 will it work in FC2? I have win 64, installed FacetrackNoIR and updated to 1.50 and it tracks my face but I dont know how to implement it in game, so what do I need to do now?

do I get TrackIRfixer? or do I get the virtual joystick or Eagle Dynamics API interface DLL 64?

 

 

help me...

Edited by ma21212
  • 2 weeks later...
Posted
I skimmed the pages, barely anything on FC2.. why? if I do what most of you did for A10 will it work in FC2? I have win 64, installed FacetrackNoIR and updated to 1.50 and it tracks my face but I dont know how to implement it in game, so what do I need to do now?

do I get TrackIRfixer? or do I get the virtual joystick or Eagle Dynamics API interface DLL 64?

 

 

help me...

 

I am in the same boat. I have tried the various options in other threads but have been unable to get any movement in game.

 

Don't suppose you have found a solution in the mean time chap?

  • 1 month later...
Posted

FacetrackNoIR version 1.6 is out:

direct dl:

http://sourceforge.net/projects/facetracknoir/files/FaceTrackNoIR_Release_V160.zip/download

WebPage:

http://facetracknoir.sourceforge.net/information_links/download.htm

 

Update 6 has been released as beta and can be downloaded here. Actually, we have chosen to release this version as a full-version. Users with new CPU's (like i5 and i7) should not experience 'IPP-errors' any more, when this full installer is used.

Gigabyte Z490 Gaming X | i5 10600K@4700 | 32 Gb DDR4 @ 3200Mhz | Gigabyte Aorus GeForce GTX 1080 Ti 11G |

MONITOR IIYAMA 24,5" LED LCD @ 1920 x 1080 | Windows 11

 | Saitek X-55 Rhino | TrackIR 5 Pro

Posted
I am in the same boat. I have tried the various options in other threads but have been unable to get any movement in game.

 

Don't suppose you have found a solution in the mean time chap?

 

Eagle Dynamics Headtracker 64 and then you use "FreeTrack" in FNIR.

My DCS stream

[sIGPIC][/sIGPIC]

Past broadcasts, Highlights

Currently too much to do... But watch and (maybe) learn something :)

  • 3 weeks later...
Posted

Sorry for my English, I write with a dictionary, but I think in general you will understand me.

This is -

Eagle Dynamics Headtracker 64 and then you use "FreeTrack" in FNIR.
in LockOn2 and BS is not working.

We have: FaceTrackNoIR_Release_V160 + FaceTrackingAPI + ED_API.,

system:

1.WindowsXP x64, AMD Phenom 8450 Triple 2.11GHz

2.Windows7 x64, i5

none of these systems with FaceTrackNoIR LockOn2 and BS is not working.

In DCS A-10 - works.

Question: how to bind to FaceTrackNoIR LockOn2 and BS in the above systems?

thank you

  • 3 weeks later...
Posted (edited)

Using a Philips SPC 900NC and v1.6 of FTNIR, I can't get the cam to initiate. I hit start, the cam's light blinks, and nothing happens. Anyone experience this?

Edited by neoshi
Posted (edited)

so there's no way to get this working in FC2?

 

i guess track ir fixer works with FC2? i'll try it out when my ps3 cam arrives.

Edited by SilverOne

[-]SilverOne[-] [- Best Regards

[sIGPIC][/sIGPIC]

Posted

I just installed FaceTrackNoir v1.60. When I launch the program it seems to run fine. But when I press 'Start' in the 'Tracker Source' box no webcam image is displayed. I just see the green X,Y,Z etc. numbers appear and they are all stuck on 0.0.

 

I have BisonCam, NB Pro on Windows 7 x64 bit operating system.

 

To the right of the X,Y,Z box it says BisonCam, NB Pro so I'm guessing it's detected the camera.

 

Any suggestions?

Valve Index | RTX 4080 (Mobile) | i9-14900HX @ 2.20 GHz | 32GB RAM

Posted (edited)

After fiddling with this thing for hours, i finally have it setup up just perfect.

 

Alright, so after carefully conducted research, i came to the conclusion that the best camera out there for this kind of stuff is the PS3 eye camera. So i bought it. Surprisingly it's actually one of the cheapest alternatives out there, costing me 15 bucks from ebay shipped, in other words, mere 10% of the whole price of a track ir 5.

 

It's capable of some impressive 120fps, however, you'll only get up to 60fps on your pc, but don't worry, that's actually allot more than what you seem to need.

 

As an extra, it comes with a 4 microphone array system.

 

So, as expected, it's not exactly plug to play but isn't that hard either, all you gotta do is go here and download the Cl Eye Platform Driver. After that, just install it and connect it to your pc.

 

In order to enable 60fps, you must create a cleye.config file inside the main facetracknoir folder and insert the following code inside, just copy paste it.

 

you can also get the file here : https://rapidshare.com/files/1967866694/facetracknoir.zip

 

<?xml version="1.0" encoding="UTF-8"?>
<cleye>
<item name="mode" value="advanced" />
</cleye>

 

you can use a simple text editor such as notepad, when saving, make sure to select "Save as Type: All files" below the file name, and that the name ends in .config

 

So now it's time to install facetracknoir for FC2:

 

to do this, go to the developers website here, click downloads, and download the V30, the v150 update, and v160 full version.

 

The v130 is type installer so you'll wanna install this one first, then drag the v150 update files to the installation folder.

 

After this is done, you'll wanna rename the installation folder to anything else except the original name. it should be inside here: C:Program Files (x86)Abbequerque Inc

 

Install v160, and replace NPCclient.dll, and trackIR.exe from the OLD 1.5 version, into the 1.6 version, overwriting them, but FIRST MAKE A COPY OF THE ORIGINAL FILES ^^

 

The reason why we're doing this is because version 1.6 is much more stable (less wobbly) than 1.5. And of course, it won't work without those specific files.

 

Alternatively you may install only the v1.6 version and get the necessary files from here: https://rapidshare.com/files/1967866694/facetracknoir.zip

i've included my own config, but take a look at the camera settings under "tracker source" on settings.

 

 

 

Next you'll wanna download track ir fixer, you can get it here, however for compatibilities purposes, or in other words for it to work, you'll wanna download the older version TrackIRFixer v1.2.0.18 instead, now, grab this file and place it in /lockon/bin/x86/stable, open with administrator rights and run it. If it gives you a success message followed by an error, don't worry, it worked. Sorry for being stretchy on details but i did this 3 days ago.

 

 

 

You'll also need TIRviews.dll, this a proprietary file from track irs developers. You'll wanna go to their website and download the trackir5 driver, install it, and find the TIRviews.dll on the trackir installation folder, drag this file into the main facetracknoir folder.

 

 

 

Alright so it's time to open up facetrackn ir and configure it. When you open facetracknoir it immeadetely starts working so on tracker source you'll wanna hit "STOP". Next go to GAME PROTOCOL, and choose fake trackir, then open the little setting boxes below and enable TIRVIEWS.

 

 

Punch START on facetracknoir, open up the game, go to options, control, AXIS(where you setup your joystick x and y axis), make sure track ir is showing up there. it has its own column , like a joystick.

 

if it shows up, congratulations, it's working!

 

You'll wanna consult the developers website for the manual, this will help you understand and fine tune your facetracknoir. you can do it here.

 

Others have posted their settings, i'll post mine, you may get different results based on lighting and your setup itself.

screenshot003gz.jpg

 

 

I came to the conclusion that the wobbling won't really go away unless you set really high smoothness , which creates enormous lag. Here's a more responsive setup i'm currently using, you should probably only try running this on v1.6, lag is barely noticeable. You can probably even lower the VMIN value a little bit more. Please keep in mind this will depend on your camera, your face, the lightning around the room.. etc

 

you can get this configuration from here, don't forget to take a look at the camera settings under "Tracker Source": https://rapidshare.com/files/1967866694/facetracknoir.zip

 

screenshot009wx.jpg

 

screenshot002vv.jpg

 

screenshot001wa.jpg

 

 

Both Smoothing and EWMA MIN are very sensitive and should be carefully fine tuned, they make your vision allot smoother at the cost of outstanding delay. The other two options aren't as sensitive, at least with my ps3eye. As a dogfighter (that's how i roll) i kinda need complete vision of the cockpit so this might be a little too much sensitive for you :D, however, my setup allows for really small reaction times, providing you with a near free lag experience. Anyway use my values as a guide, but eventually you might want to make your own. Also, after adjusting camera settings, such as brightness and RGB values, it seems to be more precise. You can do this from the "tracker source" tab under settings

 

you will also need to create a keyboard shortcut key to center the camera, to do this just hit options and select keyboard shortcuts. Basically this resets everything to zero , so you're basically saying "this is how i look centered in all axis" or , looking forward.

 

Also, keep in mind, when staring , say slightly to the right, it'll still wooble a bit, or should i say move around. it's slightly annoying, but for the price i really can't complain. and it really isn't that bad, this is also why i set up the deadzones.

 

 

 

 

You've probably noticed that each time you load up the sim and enter your pit you're too "zoomed in". You've probably been "zooming out" the whole time. Well, sorry to disappoint but, this won't work anymore. You can probably move your head forward a bit and calibrate that as "standart" or "all axis 0s" and then move it back. This might sound like a great idea at first, until you notice this very slight constant zoom in and out.

 

Thus In order to fix this, we must make that "standard" view a little more zoomed out, to do this you'll have to edit the view.lua file. Don't worry, i promise it'll be simple and not scary. Don't forget to make a backup of the file first!

 

you can find this file at: LockOn Flaming Cliffs 2ConfigView, open view.lua with notepad.

 

In line 145, or, around half way in the file, you'll find the folowing:

If you can't find it, just copy some random text from here and go to "edit - find" or use CTRL F.

-- Camera view angle limits {view angle min, view angle max}.
CameraViewAngleLimits = {}
CameraViewAngleLimits[PlaneIndex.iSu_27] = {30.0, [color="Red"]175.0[/color]}
CameraViewAngleLimits[PlaneIndex.iSu_33] = {30.0, 117.0}
CameraViewAngleLimits[PlaneIndex.iSu_25] = {30.0, 117.0}
CameraViewAngleLimits[PlaneIndex.iSu_39] = {30.0, 121.0}
CameraViewAngleLimits[PlaneIndex.iMiG_29] = {30.0, 112.0}
CameraViewAngleLimits[PlaneIndex.iMiG_29K] = {30.0, 112.0}
CameraViewAngleLimits[PlaneIndex.iA_10] = {30.0, 97.0}
CameraViewAngleLimits[PlaneIndex.iF_15] = {30.0, 110.0}
CameraViewAngleLimits[PlaneIndex.iKA_50] = {30.0, 115.0}

 

Depending on the plane, ion my case the Su-27, you'll wanna change the View angle max, the second variable in the line, i marked it in red for you. I personally like 175, but i didn't really fiddle with it. After you've made your changes just save the file. If anything goes wrong, just restore the backup you made.

This wobble, or movement, isn't noticeable when you're zooming in or out, but when you're still it's very frustrating; takes the "feel" away from your aircraft.

 

 

 

 

here's a video for your viewing pleasure, recorded with the smoother setup. Sorry for the shakiness, i was holding my iphone:

 

 

and also Here's my setup, by the way, my x52pro is usually placed where the keyboard and trackpad are:

 

img0023zw.jpg

 

in my experience, the camera works best below the monitor, i keep it close to myself and take advantage of the ps3 eye microphone.

 

 

i hope this small post helps you, i wanna thank the original poster RipKirby, janisx(from sourceforge.net) who apparently dedicated 10 days of his life to get this working. you can see his much shorter instructions here, and most importantly, the developers who put so much time and effort into the development of facetracknoir; you should probably consider making a small donation to them.

 

If for any reason i have missed some steps please let me know! And if this helped you please rate me + on the lower left on this topic [+- button]

Edited by SilverOne
  • Like 2

[-]SilverOne[-] [- Best Regards

[sIGPIC][/sIGPIC]

Posted

Awesome post SilverOne. These are the kind of step-by-step guides we need.

 

Is anyone using FaceTrackNoir v1.6 with BS2? The software is tracking, and in BS2 control options it is showing a headtracker. But I'm getting no response when in game.

Valve Index | RTX 4080 (Mobile) | i9-14900HX @ 2.20 GHz | 32GB RAM

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...