opentrack 2023.1.0

[sthalik]

Compatibility

This release build is only available as a 64-bit executable. This is because the SDK for the new tracker tracker/beam is temporarily only available as an amd64 binary.

Only CPUs supporting AVX will be able to run it. Please provide feedback on compatibiltiy and performance compared to older releases.

Changes

• fix crash on startup with very long environment PATH (issue OpenTrack Crash on Startup #1661, reported by @wfurney13).
• video/opencv: apply bugfixes for Windows 11 and enable Media Foundation input.
• tracker/pt: improved color keying for overexposed pixels (issue Improved chroma key for point tracker #1665, by @tombrazier).
• tracker/eyeware-beam now has a 32-bit version (by @eyedav).
• tracker/aruco: enable 1080p resolution.
• filter/nm: new 'Natural Movement' filter (issue "Natural Movement" Filter #1666, by @tombrazier).
• proto/simconnect: fix high CPU usage on FSX (issue Efficient wait in SimConnect thread #1670, by @tombrazier).
• filter/hamilton, filter/ewma: minor fixes (by @tombrazier, issues Faster settle time for EWMA #1671 and Hamilton documentation and minor fixes #1667).
• proto/vjoystick: link to the fork with a working Windows 11 driver version (issue Joystick emulation config popup link to vjoystick (sp?) gives a 404 error + confusion about the different versions out there #1700, reported by @ackalker)

---

This discussion was created from the release opentrack 2023.1.0.

[Ramillax]

Flagged for "Malicious.moderate.ml.score" Trojan

[SeTSmith]

I have double checked with Eset Internet Security and it does not found anything wrong with the installer or the portable.

[Ramillax]

Oh, weird. I used VirusTotal. I know it does not contain the virus. It was for you to know that it was flagged for that trojan. Thanks for the email though. El lun, 27 mar 2023 a la(s) 17:52, SeTSmith ***@***.***) escribió:

…

I doble check with Eset Internet Security and it does not found anything wrong with the installer or the portable. — Reply to this email directly, view it on GitHub <#1630 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6XYPZPSPUKY6T4S223YWJ3W6H4X5ANCNFSM6AAAAAAWCHCEDA> . You are receiving this because you commented.Message ID: ***@***.***>

[dvgportor]

PS3 eye driver is not longer working after latest windows 11 update

[sthalik]

Is this the open driver? Did you try it with both libusbK and libusb-win32?

[dvgportor]

its working now, thanks

[WF000]

Original ps3 driver, not libusb one.
Very slow/jitter PT performance on win10 , camera fps 10 - 60 varying when tracking movement.
Lots of "packet data" (error?) messages in cmd window. , could say it is unusable in this release.

[WF000]

OK, Thank you. - btw, It is a long shot, but Is it possible that in 64bit environment 32bit CL driver is not seen/registered in win (regsvr) ?
That could explain not recognizable PS3-eye to windows 10 apps layer, camera privacy., eg skype etc.

One other thing,
In 22.3.2, CL-driver seems kind of forced - it is selectable without PS3-eye e
ven being physically present (disconnected from usb) .. see.

22.3.2 - Same but with camera connected to usb. Both drivers available.

23.1 - With camera connected , CL missing - so is it possible that CL 32bit is not
working in 64bit opentrack ? Just a hunch.

[sthalik]

but Is it possible that in 64bit environment 32bit CL driver is not seen/registered in win (regsvr) ?

There's no 64-bit filter (i.e. the .ax file) for CL-Eye.

[WF000]

A-ha. That fits. So its a bummer. Can't be helped then else then someone creates 64 filter.

I've had similar problem with Creative Asio64 , long ago, bugged driver setup didn't register 64 bit dll when installed, so had to do manually. , simple enough, regsvr asio64.dll .. working.
BUT, there I already had 64 bit library, now we don't have . and very probably never will have with CL.

I'm still using CL because it has support for microphone, universal libusb can't enable microphone whatever I try...
Will have to decide in the end, 64bit or Microphone.
Cheers

[sthalik]

Try this build. https://ananke.misaki.pl/opentrack/opentrack-test-20230413_01.7z

[WF000]

It is working fine, performance wise. just from test picture.
It is 32bit., no sub-process and all that.

[whippingstar]

Not seeing the option to select neuralnet as my tracker input with the new release.

[whippingstar]

I'm seeing neuralnet now. Closed/reopened and it was there.

[crashyboi]

OpenTrack is unable to open, even with AVX activated
(Image translated in spanish: The program couldn't start correctly (0xc0000142). Click on Accept to close it.)

[sthalik]

Use Dependency Walker.

[crashyboi]

wasn't able to see anything there

[GO63-samara]

Maybe the problem is that:
This release build is only available as a 64-bit executable

[crashyboi]

Which doesn't make sense considering my system is a Windows 10 64-bit system

[crashyboi]

really this is weird. my pc has AVX enabled, it complies with the other requirements, idk why it doesnt work
2022.3.2 does work, so probably a compatibility issue

[haver13]

Greetings!

If I use newer open track than 2.3.13 the Z axis and sometimes the Y axis is going forward-backwards a little bit.
I see the newer opentrack much better but this little jittering make me nuts.

Any help, please? :(