I'm just here to post some more details about FaceAPI crashing.
To the author -> Yes, already tried with the FaceAPI demo, did not work.
What I've found in the Windows event log is that opengl32.dll is causing the FaceAPI to crash. maybe that's a trail ?
That crash happens when FaceAPI demo recognize my face, and then immediatly crashes.
I'm using a logitech c270 and also tried with a generic sony webcam, same results. I also tried downgrading my video drivers (GTX 970), still no luck. Running Windows 10 latest build.
Hope it can help !!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I may have found a temporary solution you can maybe try if you have access to a Windows 8.1 computer. Here is what I said in a different thread...
"... I may have found a possible temporary solution. Now this has not been tested yet inside any simulator/game/program, but it does get rid of the crashing upon recognizing the face. You will want to copy the opengl32.dll from your Windows 8.1 SysWOW64 folder, not the one that is in the System32 folder. Now paste it into the main FaceTrackNoIR directory. Now remember, this has not been thoroughly tested yet, so I'm unsure of any side affects that it may have.."
Scott
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Okay, I need to hear back from you all and anyone else if I could please. What I need to know is...
1) Did this possible temporary fix help? and if so or if not, Which build of Windows 10 are you using? (example answers= Yes, with build 10041)
2) When you installed FaceTrackNoIR, did you right-click and select "Run as administrator"? and, are you running it with "Run this program as an administrator" checked via the Compatibility tab inside the FaceTrackNoIR.exe Properties dialog? (example answers= Yes, No)
More questions may follow later, so keep in touch if you could please.
Scott
Last edit: sf4JC 2015-04-29
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No. Win10 Build 10061 FaceAPI was hanging at initializing. Opengl32(Win8 build 9600) fixed the hanging but as soon as the search starts it causes FaceAPI to crash.
a. Admin Install: Selected Run as Admin & Run per Win8 under Compatibility. b. Run as Admin: Yes
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks again JPJ for your input. I'm hoping to collect enough data so that Wim can get a better idea of what might be causing the problem. Meanwhile, I'm going to see if the "Run this program as an administrator" has any ill affects on my machine, since that may be the only thing different between us besides our build differences (I am still on Windows 10 build 10041).
Scott
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So on W10, faceAPI does not work? That is a pity. But actually I think we were lucky that it did under W8 ...
Unfortunately SeeingMachines does not update or release the demo version any longer. So unless we (or someone smarter) finds a fix, we may need to use other trackers than faceAPI.
Does anyone know if PointTracker works under W10? Or does anyone have a fix for faceAPI...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It actually works on my Windows 10 build 10074, but I do not know why it refuses to work with anyone else so far. I don't want to believe this is an isolated incident, but so far, it looks that way. I can try PointTracker later this weekend if no one else has done so.
Scott
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, my post didn't show up earlier, so I'll try again and hope it doesn't double post. Wim, as far as if the PointTracker tracker working, it does for me in Windows 10 build10074! On a side note, I did not realize a person could use an unmodified (no removed IR filter) webcam to see the IR LED's! It took me totally by surprise when I passed a piece of processed 35mm camera film in front of the webcam. I must have totally missed that back in my FREETrack using days. I thought back then it was mandatory to remove the IR filter from the webcam, which was a pain for me to do. Anyway, PointTracker option works for me!
Scott
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Same issue here... Will try copying OpenGL32.DLL to FaceTrackNoIR folder.
[Edited later]
After copying OpenGL32.DLL and granting execution rights, eventlog reports two diferent crashes, just seconds before FTNOIR crashes:
Nome do aplicativo com falha: conhost.exe, versão: 10.0.10061.0, carimbo de data/hora: 0x5528b7eb
Nome do módulo com falha: ConhostV2.dll, versão: 10.0.10061.0, carimbo de data/hora: 0x5528b837
Last edit: AugustoZ 2015-05-19
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Same issue does not work, I have my old PC in a VMware environment, where i tested and FTNOIR worked (in vmware). My physical win 10 build 10074 does not work if I run the FTnoir_faceAPI_exe.exe it manually it will run, without crashing until I try to restart it or try any of the commands. Meaning it can access my webcam (ps3 eye) successfully. The issue is now that I believe the API just does not want to work on the libraries of win 10.
If someone could tell me what I need I can copy from my win 7 or win 8.1 machine to the run dir of FTNIR and one by one and start to test if I can get it working.
(downloading Dependency walker) to see if I can figure it out on my own.
Last edit: zazzn 2015-05-23
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello guys, just to make sure, I've one question this time. Are you 2 using the opengl32.dll from your Windows 8.1 SysWOW64 folder, and NOT the one that is in the System32 folder?
Scott
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So as my next test, I'm going to create a restore point, copy the opengl32.dll from my win8.1 machine to the actual windows system32 dir and see if she crashes out or works!
So strangely, if you remove all the other files and simply run FTNoIR_FaceAPI_EXE.exe alone, the webcam works and the stats display the FPS ect, however if you press R for restart tracking it will crash out with an access violation showing the usual suspects.
Thanks for trying other possible avenues, zazzn. Maybe it's not worth fighting for if I understood Wim correctly, that Seeing Machines may not update or release it anymore. I'll have to find that post to see for sure.
Scott
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just wanted to chime in and report that I too am running Win10 build 10074 and had this crashing issue. Downloaded a replacement opengl32.dll from the internet and placed in in the program directory and was able to get tracking working...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I had FaceTtrackNoIR working on my laptop with Win 7, then updated to Win 10 ( I don't know which build) on my and it ceased to work.
I "Downloaded an opengl32.dll from the internet " and put it in the directory. Still doesn't work. I am using FaceAPIv3.2.6: Accela Filter Mk2 and FaceTrack 2.0 which worked before. The webcam flashes on and then off.
Trying Point Tracker 1.0 as "Tracker Source" the camera stays on, and a blue and grey image of my head/face appears with a number of 'Xs' which shows movement but itdoes not register on the Yaw Pitch and Roll figures above the picture and does not translate to movement.
I am moderately computer 'savvy' . Anybody got any suggestions ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello guys,
I'm just here to post some more details about FaceAPI crashing.
To the author -> Yes, already tried with the FaceAPI demo, did not work.
What I've found in the Windows event log is that opengl32.dll is causing the FaceAPI to crash. maybe that's a trail ?
That crash happens when FaceAPI demo recognize my face, and then immediatly crashes.
I'm using a logitech c270 and also tried with a generic sony webcam, same results. I also tried downgrading my video drivers (GTX 970), still no luck. Running Windows 10 latest build.
Hope it can help !!
I have this same issue
I may have found a temporary solution you can maybe try if you have access to a Windows 8.1 computer. Here is what I said in a different thread...
"... I may have found a possible temporary solution. Now this has not been tested yet inside any simulator/game/program, but it does get rid of the crashing upon recognizing the face. You will want to copy the opengl32.dll from your Windows 8.1 SysWOW64 folder, not the one that is in the System32 folder. Now paste it into the main FaceTrackNoIR directory. Now remember, this has not been thoroughly tested yet, so I'm unsure of any side affects that it may have.."
Scott
Okay, I need to hear back from you all and anyone else if I could please. What I need to know is...
1) Did this possible temporary fix help? and if so or if not, Which build of Windows 10 are you using? (example answers= Yes, with build 10041)
2) When you installed FaceTrackNoIR, did you right-click and select "Run as administrator"? and, are you running it with "Run this program as an administrator" checked via the Compatibility tab inside the FaceTrackNoIR.exe Properties dialog? (example answers= Yes, No)
More questions may follow later, so keep in touch if you could please.
Scott
Last edit: sf4JC 2015-04-29
Thanks again JPJ for your input. I'm hoping to collect enough data so that Wim can get a better idea of what might be causing the problem. Meanwhile, I'm going to see if the "Run this program as an administrator" has any ill affects on my machine, since that may be the only thing different between us besides our build differences (I am still on Windows 10 build 10041).
Scott
Update: I have updated to Win 10 build 10074(Fresh Install). Same issues persist.
Hi guys (I guess),
So on W10, faceAPI does not work? That is a pity. But actually I think we were lucky that it did under W8 ...
Unfortunately SeeingMachines does not update or release the demo version any longer. So unless we (or someone smarter) finds a fix, we may need to use other trackers than faceAPI.
Does anyone know if PointTracker works under W10? Or does anyone have a fix for faceAPI...
It actually works on my Windows 10 build 10074, but I do not know why it refuses to work with anyone else so far. I don't want to believe this is an isolated incident, but so far, it looks that way. I can try PointTracker later this weekend if no one else has done so.
Scott
Sorry, I forgot to say that my Windows 10 build 10074 was updated from build 10041, and it works on both.
Scott
OK, that's nice to know. So given the right conditions, it can work...
Maybe I can try W10, on a virtual Machine to see if I can reproduce that?
Well, my post didn't show up earlier, so I'll try again and hope it doesn't double post. Wim, as far as if the PointTracker tracker working, it does for me in Windows 10 build 10074! On a side note, I did not realize a person could use an unmodified (no removed IR filter) webcam to see the IR LED's! It took me totally by surprise when I passed a piece of processed 35mm camera film in front of the webcam. I must have totally missed that back in my FREETrack using days. I thought back then it was mandatory to remove the IR filter from the webcam, which was a pain for me to do. Anyway, PointTracker option works for me!
Scott
Same issue here... Will try copying OpenGL32.DLL to FaceTrackNoIR folder.
[Edited later]
After copying OpenGL32.DLL and granting execution rights, eventlog reports two diferent crashes, just seconds before FTNOIR crashes:
Nome do aplicativo com falha: conhost.exe, versão: 10.0.10061.0, carimbo de data/hora: 0x5528b7eb
Nome do módulo com falha: ConhostV2.dll, versão: 10.0.10061.0, carimbo de data/hora: 0x5528b837
Last edit: AugustoZ 2015-05-19
Hello all,
Same issue does not work, I have my old PC in a VMware environment, where i tested and FTNOIR worked (in vmware). My physical win 10 build 10074 does not work if I run the FTnoir_faceAPI_exe.exe it manually it will run, without crashing until I try to restart it or try any of the commands. Meaning it can access my webcam (ps3 eye) successfully. The issue is now that I believe the API just does not want to work on the libraries of win 10.
If someone could tell me what I need I can copy from my win 7 or win 8.1 machine to the run dir of FTNIR and one by one and start to test if I can get it working.
(downloading Dependency walker) to see if I can figure it out on my own.
Last edit: zazzn 2015-05-23
With OPENGL32.DLL form a 8.1 machine it crashes with
Faulting module path: C:\WINDOWS\SYSTEM32\ippmpx-5.3.dll
now.
Hello guys, just to make sure, I've one question this time. Are you 2 using the opengl32.dll from your Windows 8.1 SysWOW64 folder, and NOT the one that is in the System32 folder?
Scott
Yes Copied form sysWOW64 folder.
Here's the results form dependency walker.
Also, here's some more tests that I ran, it seems that FaceTrack is simply starts to fault with more DLL's this time
Faulting module path: C:\WINDOWS\SYSTEM32\ippmpx-5.3.dll
Exception code: : 0xc0000005
so i did the next logicial thing and copied the sysWOW64\ippmpx-5.3.dll from the 8.1 system to the windows 10 and it failed as well with
Exception code: 0xc0000005
Faulting module path: C:\Program Files (x86)\Abbequerque Inc\FaceTrackNoIR\ippmpx-5.3.dll
So as my next test, I'm going to create a restore point, copy the opengl32.dll from my win8.1 machine to the actual windows system32 dir and see if she crashes out or works!
Last edit: zazzn 2015-05-24
So strangely, if you remove all the other files and simply run FTNoIR_FaceAPI_EXE.exe alone, the webcam works and the stats display the FPS ect, however if you press R for restart tracking it will crash out with an access violation showing the usual suspects.
MSVCR80.dll Exception code: 0xc0000005 Fault offset: 0x00390389
Ippmpx-5.3.dll Exception code: 0x40000015 Fault offset: 0x000046b4
OPENGL32.dll Exception code: 0xc0000005 Fault offset: 0x0008d8ef
So it's basically the tracking that is giving the issues.
Thanks for trying other possible avenues, zazzn. Maybe it's not worth fighting for if I understood Wim correctly, that Seeing Machines may not update or release it anymore. I'll have to find that post to see for sure.
Scott
Not sure how long Windows 10 Build 10130 has been out, but again FaceAPI and PointTracker trackers work fine on my machine after the update.
Scott
Just wanted to chime in and report that I too am running Win10 build 10074 and had this crashing issue. Downloaded a replacement opengl32.dll from the internet and placed in in the program directory and was able to get tracking working...
Thanks for the input SuperSirLink, I'm finally glad to hear that someone else has it working, and that I'm not a special case.
Scott
No problem, stumbled on this looking for the solution, hopefully others will find it as well...
I had FaceTtrackNoIR working on my laptop with Win 7, then updated to Win 10 ( I don't know which build) on my and it ceased to work.
I "Downloaded an opengl32.dll from the internet " and put it in the directory. Still doesn't work. I am using FaceAPIv3.2.6: Accela Filter Mk2 and FaceTrack 2.0 which worked before. The webcam flashes on and then off.
Trying Point Tracker 1.0 as "Tracker Source" the camera stays on, and a blue and grey image of my head/face appears with a number of 'Xs' which shows movement but itdoes not register on the Yaw Pitch and Roll figures above the picture and does not translate to movement.
I am moderately computer 'savvy' . Anybody got any suggestions ?