facetracknoir / Discussion / PointTracker: More than 99fps [camera settings]

tanta1 - 2013-03-07

Hey,

Atm 99fps is the maximum in the camera settings. Is there a way to bypass this lock?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Stanisław Halik - 2013-03-07

Not without changing the source code.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Stanisław Halik - 2013-03-07

Try modifying .ini, and never visiting the dialog.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

tanta1 - 2013-03-08

I already tried that. Doesn't work.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Stanisław Halik - 2013-03-08

Testing build available.

http://ananke.laggygamerz.com/ftnoir/ftnoir-posix-20130308-12_33_48-52ab8d872fd0b6233dd48370b25512f3f0196378.7z

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Wim Vriend - 2013-03-08

Hi tanta1,

Maybe the max. of 99 is there for a good reason. Why do you want to raise fps so much?
Most web-cams (or their driver) limits fps to a much lower value than 99.

In my opinion, you should not need a higher value. If you have a problem, please tell us what it is and maybe Patrick can help you?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Stanisław Halik - 2013-03-08

I think that PT is very little CPU-intensive, and if user wants to do something maybe a little bit misguided, let'em have it! :-)

If Patrick wanted a particular limit, he'd input a multiply of 30 or 15 I think. It's probably just numberupdown default.

But he can say best, not me.

Last edit: Stanisław Halik 2013-03-08

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

tanta1 - 2013-03-09

@Stanisław
It crashes after some second after clicking start and the positions are "inverted". Here's a screenshot: http://gyazo.com/c49ea04905db682fbc3a021ec8947e53.png?1362831949
I also doublechecked my setting just in case.

@Wim
Response time and more range/play for smoothing is quite important for me. I want to try 170+fps with Cl eye drivers for the PS3Eye camera.

edit: Looks like QtCore4.dll is the problem.

" Problem Event Name: APPCRASH
Application Name: ftnoir.exe
Application Name: 0.0.0.0
Application Timestamp: 5138f565
Fault Module Name: QtGui4.dll
Fault Module Version: 4.8.4.0
Fault Module Timestamp: 50b31e4e
Exception Code: c0000005
Exception Offset: 00192414
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
"

Last edit: tanta1 2013-03-09

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Stanisław Halik - 2013-03-09

Without a backtrace there's little I can do, sorry.

Inverted horizontally or vertically?

New build, maybe it's fixed, maybe not:

EDIT: broken. New build in the morning.

Last edit: Stanisław Halik 2013-03-09

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

tanta1 - 2013-03-09

It's flipped vertically.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Stanisław Halik - 2013-03-10

Thanks. Will fix. Is it flipped on input for tracker or just the video widget?

http://ananke.laggygamerz.com/ftnoir/ftnoir-posix-20130310-07_13_26-666e99b658c75580d56e04f16421dd9d0674abca.7z

New testing build. Guessed right, building Qt took whole night.

Last edit: Stanisław Halik 2013-03-10

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

tanta1 - 2013-03-10

The tracking was fixed but it still crashes either on clicking start or some seconds after clicking start.

Well, thanks for the trouble. Looks like it's purely on my side.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Stanisław Halik - 2013-03-10

I've tested on Linux and it works. What is your CPU, does it have SSE2?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

tanta1 - 2013-03-10

i5 2500k and yes.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Stanisław Halik - 2013-03-10

Could you try with a fresh config?

I assume that you can't be bothered to install Visual Studio in order to get a backtrace?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

tanta1 - 2013-03-10

Fresh config? Unfortunately no.

I tried to get a backtrace without Visual Studio (I pretty much know nothing about stuff like this). Maybe this can help you:

Microsoft (R) Windows Debugger Version 6.2.9200.16384 X86
Copyright (c) Microsoft Corporation. All rights reserved.

wait with pending attach
Symbol search path is: Invalid
**********
Symbol loading may be unreliable without a symbol search path.
Use .symfix to have the debugger choose a symbol path.
After setting your symbol path, use .reload to refresh symbol locations. **********
Executable search path is:
ModLoad: 00b30000 00b99000 D:\p\FaceTrackNoIR test build\ftnoir.exe
ModLoad: 773d0000 77550000 C:\Windows\SysWOW64\ntdll.dll
ModLoad: 755d0000 756e0000 C:\Windows\syswow64\kernel32.dll
ModLoad: 756e0000 75726000 C:\Windows\syswow64\KERNELBASE.dll
ModLoad: 75f30000 76030000 C:\Windows\syswow64\USER32.dll
ModLoad: 74ff0000 75080000 C:\Windows\syswow64\GDI32.dll
ModLoad: 75880000 7588a000 C:\Windows\syswow64\LPK.dll
ModLoad: 75930000 759cd000 C:\Windows\syswow64\USP10.dll
ModLoad: 75e80000 75f2c000 C:\Windows\syswow64\msvcrt.dll
ModLoad: 759d0000 75a70000 C:\Windows\syswow64\ADVAPI32.dll
ModLoad: 75d60000 75d79000 C:\Windows\SysWOW64\sechost.dll
ModLoad: 75080000 75170000 C:\Windows\syswow64\RPCRT4.dll
ModLoad: 74f30000 74f90000 C:\Windows\syswow64\SspiCli.dll
ModLoad: 74f20000 74f2c000 C:\Windows\syswow64\CRYPTBASE.dll
ModLoad: 6fda0000 6fdaf000 D:\p\FaceTrackNoIR test build\ftnoir-pose-widget.dll
ModLoad: 5e510000 5e7a4000 D:\p\FaceTrackNoIR test build\QtCore4.dll
ModLoad: 75310000 7546c000 C:\Windows\syswow64\ole32.dll
ModLoad: 74f90000 74fc5000 C:\Windows\syswow64\WS2_32.dll
ModLoad: 74fd0000 74fd6000 C:\Windows\syswow64\NSI.dll
ModLoad: 71da0000 71e09000 C:\Windows\system32\MSVCP100.dll
ModLoad: 71ce0000 71d9f000 C:\Windows\system32\MSVCR100.dll
ModLoad: 59a20000 5a27a000 D:\p\FaceTrackNoIR test build\QtGui4.dll
ModLoad: 75730000 757ab000 C:\Windows\syswow64\COMDLG32.dll
ModLoad: 75d00000 75d57000 C:\Windows\syswow64\SHLWAPI.dll
ModLoad: 6bb20000 6bba4000 C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\COMCTL32.dll
ModLoad: 761b0000 76dfa000 C:\Windows\syswow64\SHELL32.dll
ModLoad: 760c0000 7614f000 C:\Windows\syswow64\OLEAUT32.dll
ModLoad: 758d0000 75930000 C:\Windows\syswow64\IMM32.dll
ModLoad: 757b0000 7587c000 C:\Windows\syswow64\MSCTF.dll
ModLoad: 73040000 73072000 C:\Windows\system32\WINMM.dll
ModLoad: 71b30000 71b81000 C:\Windows\system32\WINSPOOL.DRV
ModLoad: 64ec0000 64f8f000 D:\p\FaceTrackNoIR test build\QtOpenGL4.dll
ModLoad: 5d2d0000 5d398000 C:\Windows\system32\OPENGL32.dll
ModLoad: 68de0000 68e02000 C:\Windows\system32\GLU32.dll
ModLoad: 6faa0000 6fb87000 C:\Windows\system32\DDRAW.dll
ModLoad: 6fa90000 6fa96000 C:\Windows\system32\DCIMAN32.dll
ModLoad: 76e30000 76fcd000 C:\Windows\syswow64\SETUPAPI.dll
ModLoad: 752e0000 75307000 C:\Windows\syswow64\CFGMGR32.dll
ModLoad: 75470000 75482000 C:\Windows\syswow64\DEVOBJ.dll
ModLoad: 71370000 71383000 C:\Windows\system32\dwmapi.dll
ModLoad: 67000000 67013000 D:\p\FaceTrackNoIR test build\ftnoir-spline-widget.dll
ModLoad: 64e00000 64e30000 C:\Windows\system32\DINPUT8.dll
ModLoad: 71a60000 71aac000 C:\Windows\system32\apphelp.dll
ModLoad: 719d0000 71a5d000 C:\Windows\AppPatch\AcLayers.dll
ModLoad: 72d80000 72d97000 C:\Windows\system32\USERENV.dll
ModLoad: 72de0000 72deb000 C:\Windows\system32\profapi.dll
ModLoad: 719b0000 719c2000 C:\Windows\system32\MPR.dll
ModLoad: 6f630000 6f848000 C:\Windows\AppPatch\AcGenral.DLL
ModLoad: 71190000 71210000 C:\Windows\system32\UxTheme.dll
ModLoad: 6f620000 6f62f000 C:\Windows\system32\samcli.dll
ModLoad: 71170000 71184000 C:\Windows\system32\MSACM32.dll
ModLoad: 74eb0000 74eb9000 C:\Windows\system32\VERSION.dll
ModLoad: 6f5e0000 6f5e3000 C:\Windows\system32\sfc.dll
ModLoad: 6e370000 6e37d000 C:\Windows\system32\sfc_os.DLL
ModLoad: 75490000 755c7000 C:\Windows\syswow64\urlmon.dll
ModLoad: 75d80000 75e75000 C:\Windows\syswow64\WININET.dll
ModLoad: 75b00000 75cfe000 C:\Windows\syswow64\iertutil.dll
ModLoad: 75170000 7528e000 C:\Windows\syswow64\CRYPT32.dll
ModLoad: 75890000 7589c000 C:\Windows\syswow64\MSASN1.dll
ModLoad: 6e110000 6e369000 C:\Windows\AppPatch\AcXtrnal.DLL
ModLoad: 6e0f0000 6e0f6000 C:\Windows\system32\SHUNIMPL.DLL
ModLoad: 6e0d0000 6e0dd000 C:\Windows\system32\SortServer2003Compat.dll
ModLoad: 73820000 73878000 C:\Program Files (x86)\Common Files\microsoft shared\ink\tiptsf.dll
ModLoad: 74950000 74a70000 C:\Windows\system32\wintab32.dll
ModLoad: 73b60000 73cb5000 C:\Windows\system32\Pen_Tablet.dll
ModLoad: 66cf0000 66d03000 D:\p\FaceTrackNoIR test build\ftnoir-proto-fgfs.dll
ModLoad: 5df30000 5e012000 D:\p\FaceTrackNoIR test build\QtNetwork4.dll
ModLoad: 6fcc0000 6fcce000 D:\p\FaceTrackNoIR test build\ftnoir-proto-freetrack.dll
ModLoad: 66c80000 66c91000 D:\p\FaceTrackNoIR test build\ftnoir-proto-udp.dll
ModLoad: 668f0000 66904000 D:\p\FaceTrackNoIR test build\ftnoir-proto-win32-mouse.dll
ModLoad: 64ea0000 64eb5000 D:\p\FaceTrackNoIR test build\ftnoir-tracker-faceapi.dll
ModLoad: 64e80000 64e98000 D:\p\FaceTrackNoIR test build\ftnoir-tracker-ht.dll
ModLoad: 6fb90000 6fb96000 D:\p\FaceTrackNoIR test build\ftnoir-compat.dll
ModLoad: 64e40000 64e76000 D:\p\FaceTrackNoIR test build\ftnoir-tracker-pt.dll
ModLoad: 5de60000 5df26000 D:\p\FaceTrackNoIR test build\opencv_calib3d244.dll
ModLoad: 5dc60000 5de53000 D:\p\FaceTrackNoIR test build\opencv_core244.dll
ModLoad: 597c0000 59a1d000 D:\p\FaceTrackNoIR test build\opencv_imgproc244.dll
ModLoad: 61b90000 61c0c000 D:\p\FaceTrackNoIR test build\opencv_flann244.dll
ModLoad: 59700000 597b5000 D:\p\FaceTrackNoIR test build\opencv_features2d244.dll
ModLoad: 594f0000 596fa000 D:\p\FaceTrackNoIR test build\opencv_highgui244.dll
ModLoad: 64de0000 64df9000 C:\Windows\system32\AVIFIL32.dll
ModLoad: 5dc30000 5dc51000 C:\Windows\system32\MSVFW32.dll
ModLoad: 64dc0000 64dd3000 C:\Windows\system32\AVICAP32.dll
ModLoad: 5e4f0000 5e503000 D:\p\FaceTrackNoIR test build\ftnoir-tracker-udp.dll
ModLoad: 5dc10000 5dc24000 D:\p\FaceTrackNoIR test build\ftnoir-filter-accela.dll
ModLoad: 5dbf0000 5dc02000 D:\p\FaceTrackNoIR test build\ftnoir-filter-ewma.dll
ModLoad: 6fc40000 6fc47000 C:\Windows\system32\atiglpxx.dll
ModLoad: 55520000 56867000 C:\Windows\system32\atioglxx.dll
ModLoad: 59470000 594e2000 C:\Windows\system32\atiadlxy.dll
ModLoad: 70f10000 71005000 C:\Windows\system32\PROPSYS.dll
ModLoad: 72d70000 72d7d000 C:\Windows\system32\WTSAPI32.dll
ModLoad: 773a0000 773a5000 C:\Windows\syswow64\PSAPI.DLL
ModLoad: 72bc0000 72bdc000 C:\Windows\system32\IPHLPAPI.DLL
ModLoad: 72b90000 72b97000 C:\Windows\system32\WINNSI.DLL
ModLoad: 758a0000 758cd000 C:\Windows\syswow64\WINTRUST.dll
ModLoad: 74490000 7457f000 C:\Windows\system32\aticfx32.dll
ModLoad: 66ff0000 66ffc000 C:\Windows\system32\atigktxx.dll
ModLoad: 76030000 760b3000 C:\Windows\syswow64\CLBCatQ.DLL
ModLoad: 6a830000 6a844000 C:\Windows\SysWOW64\devenum.dll
ModLoad: 72d20000 72d41000 C:\Windows\system32\ntmarta.dll
ModLoad: 75290000 752d5000 C:\Windows\syswow64\WLDAP32.dll
ModLoad: 6e100000 6e10b000 C:\Windows\system32\msdmo.dll
ModLoad: 5dbb0000 5dbe2000 C:\Windows\SysWOW64\qcap.dll
ModLoad: 6a610000 6a787000 C:\Windows\SysWOW64\quartz.dll
ModLoad: 593d0000 59464000 C:\Program Files (x86)\Code Laboratories\CL-Eye Driver\PS3EyeAxFilter.ax
ModLoad: 59350000 593d0000 C:\Windows\SysWOW64\qedit.dll
ModLoad: 71670000 71800000 C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17825_none_72d273598668a06b\gdiplus.dll
ModLoad: 6a500000 6a519000 C:\Windows\system32\atiu9pag.dll
ModLoad: 69a00000 69acc000 C:\Windows\system32\D3DIM700.DLL
ModLoad: 6cf90000 6cf97000 C:\Windows\system32\avrt.DLL
ModLoad: 71bd0000 71bd9000 C:\Windows\system32\HID.DLL
(1910.18f4): Access violation - code c0000005 (!!! second chance !!!) ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Windows\SysWOW64\ntdll.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for D:\p\FaceTrackNoIR test build\QtOpenGL4.dll -
eax=00000000 ebx=0163cae4 ecx=03e3a1c0 edx=005522c0 esi=03e3a218 edi=000000f1
eip=773f15de esp=0163cad0 ebp=0163cfd8 iopl=0 nv up ei pl zr na pe nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000246
ntdll!ZwRaiseException+0x12:
773f15de 83c404 add esp,4

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Stanisław Halik - 2013-03-10

You can't get a backtrace without debug symbols. I'll provide them.

Why does OpenGL fail on your display? Do you have any idea?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Stanisław Halik - 2013-03-10

http://ananke.laggygamerz.com/ftnoir/ftnoir-debug-20130310.7z

Please locate debug symbols when obtaining a backtrace. Thank you for doing this.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Lauri Mela - 2013-03-10

Hi,

The .ini editing for higher fps works. Just remember to lower the delay value in the settings dialog. It is 10 ms by default which limits the max fps to just ~100 fps. I have it at 4 ms and I can use the PS3 Eye camera at over 180 fps.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Patrick Ruoff - 2013-03-11

Hi Lauri,

ok, I guess I clamped the input in the dialog to 99 fps, will be changed to 999 in the next version. However, I do not think that higher framerates than 100 make much sense because of the increased camera noise.
Another way to decrease smoothing and make the tracker more responsive is to decrease the reduction factor of the accela filter. I prefer a value of 10 or 30 over the default 100 for Pointtracker.
The pitch swap is a simple minus sign and will be corrected in the next version.
(although I still think that my angle convention is the right one :-P )

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

SparkMasterB - 2013-09-12

Having >99 FPS would be better than some of you make it out to be. There is less input lag. Smoothing induces an input lag which is unacceptable in many situations. In FT setting it to a solid 100 worked much better than anything lower.

Try going into a game like arma or IL2, set your tracking framerate to 30. Look around. Then 60, then 90. Tell me which one is more responsive with less lag. By editing my config I'm able to keep the frame rate pegged at 100 (when setting it to 95-99 it drops down to 80, every other setting has not been constant, like 90 constantly changes between 85 and 95). 100 is much more responsive and stable than anything else I've managed.

I'm eagerly anticipating the next major patch if the >99 limitation is possible.

Last edit: SparkMasterB 2013-09-12

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Patrick Ruoff - 2013-09-13

Hi again,
I removed the limit in the new version 1.1, but I'm not sure if you will really get a higher framerate, because FTNoIR imho only polls the tracker at 100 fps.
Please tell me what fps you see in the status region when you select more than 100 fps.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

DCTH - 2013-12-11

Hi!
I now have a PS3 eye cam for it. First experience of trying to set it to 100 ended in a bluescreen -.-
Tracking was active though and i only typed in the 1 i think before it BSOD.

Seems you shouldn't do it on the fly. (Will test a bit more)

Edit: Second test altering just the fps to 100 gave no bsod (good). But since the resolution was still on 640x480, the camera froze.

Maybe just allow supported resolution-fps-combinations? (here is a list i think: http://nuigroup.com/forums/viewthread/3263/ )

Edit2:
Tried 320x240@150fps ... was able to type it in, but camera-status always says "99 fps".

Then another bsod when trying to set it to something else on the fly (DON'T DO IT!)

Problemsignatur:
Problemereignisname: BlueScreen
Betriebsystemversion: 6.1.7601.2.1.0.256.48
Gebietsschema-ID: 1031

Zusatzinformationen zum Problem:
BCCode: 10d
BCP1: 000000000000000A
BCP2: FFFFF8800B47F770
BCP3: 0000000000000000
BCP4: FFFFFA800744A010
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Dateien, die bei der Beschreibung des Problems hilfreich sind:
C:\Windows\Minidump\121113-7269-01.dmp
C:\temp\WER-17986-0.sysdata.xml

Last edit: DCTH 2013-12-11

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Stanisław Halik - 2013-12-11

Actually, up to 120 fps should work by all means on Windows, even. In 320x240, that is.

Higher fps is a gimmick, though, unless you shake your head really violently. Has to do with exposure.

Try updating your CL-eye driver, perhaps?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

DCTH - 2013-12-11

I just downloaded the cl-eye driver, so i thik i have the newest.

Lower resolution is quite bad for me anyway, because the tracking gets worse at fast movement.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

More than 99fps [camera settings]

Headtracking program that makes gaming more fun.

Forums

Help

More than 99fps [camera settings]

More than 99fps [camera settings]

Headtracking program that makes gaming more fun.

Forums

Help

More than 99fps [camera settings] document.SUBSCRIPTION_OPTIONS = { "thing": "topic", "subscribed": false, "url": "subscribe", "icon": { "css": "fa fa-envelope-o" } };

More than 99fps [camera settings]