MavericK96

Hopefully the game will be more optimized than in that Nightfight preview. Framerate looked pretty bad overall. :(

Sounds great, thanks for the continued support! I have no doubt that with some further development and tweaking this could be a great low-cost alternative to TrackIR.

It'd be nice to see this in OA but I doubt it will be there either.

Thanks for the update. :) ---------- Post added at 02:45 AM ---------- Previous post was at 02:10 AM ---------- Looks like it's up again, for the moment at least.

How well does the TrackClip Pro + Freetrack on a webcam work?

Still not working for me...? :confused:

Thanks, I was not sure where to put this thread. :cool: Also, it seems to still be down, which is disconcerting to me because it means the CIT is also down. :(

I tried changing this on a whim (I have nVidia, though) and setting it to -93750 actually seems to have boosted my FPS by a few...I was getting around 46 in Benchmark 1 with either 100000 or -4194304, and with -93750 I'm getting about 49. This could just be a placebo but it's worth a shot. :cool:

Hell, I'll take just about anything from BIS even if it's not free. :D

I've got a fast quad core (see my sig), but I've seen no improvement in the latest betas. Actually, Builds 70100 and 70313 gave me the best performance out of all of them (very low stutter and highest avg framerate) but I still had issues with stability. In terms of AA, it's not needed, but it makes the game look a lot nicer around the edges of objects, because what it does is smooth out the edges so they don't look "jagged", or pixelated. I can run Very High AA with little performance hit so I just leave it on. On another note, I tried setting my Terrain Detail to High instead of Very High, and in the bm_coastalFlight benchmark I was able to run through it several times without an "Out of Memory" error. However, after a few runs I did get the "Receiving..." screen and drastic slowdown in performance (slideshow stuff like I mentioned before), so this helps but is obviously not a fix. It seems apparent, based on the symptoms, that there is a memory leak somewhere in the game. It may be based on terrain rendering, or that could have just been a coincidence since I lowered a setting in general. Also, running at High versus Very High, I saw no performance difference either up or down, so it's apparent my system can handle Very High, but it just causes the memory leak to build and crash the game faster.

What settings/specs are you guys using? I literally saw zero performance increase with the new build... ---------- Post added at 03:59 PM ---------- Previous post was at 03:44 PM ---------- I gave this a shot. It got about halfway through the 2nd run and crashed with an "Out of Memory" error. :( Also, Vsync on takes off about 5 FPS average of my framerate.

Yeah, I'll give it a shot. I recall using Vsync drops performance a fair bit, but I will try it for stability purposes. Thanks for the data.

Yep, I'll definitely test for stability. Thanks for the info. ---------- Post added at 12:53 PM ---------- Previous post was at 12:48 PM ---------- Well, that was quick. I did one run of that BM_coastalFlight test and it didn't even make it through an entire test before CTD with "Out of Memory" error. :( ---------- Post added at 01:08 PM ---------- Previous post was at 12:53 PM ---------- The BM_coastalFlight test is actually a really good repro for the "Out of Memory" error. I ran it twice with exThreads=0 and it crashed both times, in similar places (the first time it was just before the end of the first run, the second time it was just after the end of the first, at the beginning of the second). Oddly enough, using exThreads=3, shortly after the first run I got a "Receiving..." screen, and then later in that same (second) run the game started to slow to a crawl (1 FPS and dropping continuously; slideshow). I alt-tabbed out to the Task Manager, and then went back in game, and the speed picked up for about 2 seconds before starting to slow to a crawl again. Weird issue, I've never seen it happen before and not crash the game.

So does anyone have any performance numbers since the last patch? Or did they only fix the things listed? ---------- Post added at 12:20 PM ---------- Previous post was at 11:57 AM ---------- Just tried it myself. No change in framerate or stutter from 70709. Not sure about stability, yet.

I've been looking into making one of these setups, but I can't find any US dealers who sell the SFH485P IR LEDs. Does anyone know of any? I was going to order from Farnell (a UK company AFAIK) but the minimum order is £20 and I only need about £4 worth of materials. :( Any ideas?

No, all you have to do is download the FaceAPI kit at the site that was linked earlier in the thread: http://www.seeingmachines.com/product/faceapi/downloads/ You have to register, but that is free, and the download is free and does not have a time limit.

I've been messing with this, and one tip I have for people is to put your webcam down below your monitor (if raised) instead of on top. Mine was on top of my 25.5" monitor and it was too high, since there's no zeroing function. It was causing me to look at the ground all the time. I set all the rotational axes (the ones typically used) to about 55 sensitivity, neutral zone to 8-10, and smoothing to 10-15. This seems to provide the best overall experience. However, the jittering is still much to severe to use this regularly. It defeats the purpose of having the look when you can't look to the side and have it be stable.

Nice work. Good to see some hard testing of HT on vs. off. One comment, though, I would resize your pic. They don't like pics larger than 100k posted around here. :cool:

Nice, only $10 more for ArmA2 + OA? I might pick up this one just to have an extra copy of ArmA2. :cool:

Another reason I'd like to see a "calibrate" or "zero" button is that I have to wait for my webcam to initialize before I control settings like zoom, and so if I try to zoom after FaceAPI has already started tracking, it perceives me as being zoomed in on the z-axis all the time. Having a zero function would fix this.

I'd like to see some videos of people using this to see how the stutter/jitter is for them. I've tried messing with the settings a lot but I still can't get it to be playable as the jitter back and forth is just too severe.

Yes, I tried the demo. The tracking seems perfectly fine based on the video preview, like I was saying, but the problem is that it doesn't seem to use the "base" location of my face as the zero value for all axes. If you included a "zero" button that instantly calibrated all values to zero for the current facial position when pressed, I think that would help a lot. Also, as another "for instance" for this problem, when I try to use the zoom (z-axis) feature, my "default" facial position will cause the game to be zoomed in all the way. The same with the leaning function, where if I am not leaning at all in real life, in-game it will have me skewed slightly to the side. Also, I have tried setting the sensitivity from 90 to 200 with no change in jitter. All the sensitivity changes is how much you turn in-game versus how far your head turns. I've tried smoothing as well, but if you turn it above 15 or so you get a very long delay between your head turn and the in-game view change. Setting the neutral-zone higher does also help, though, in terms of staying "locked" in the central view and not going crazy when you're not trying to move your head. Somewhere between around 10 or 15 seems best for me personally.

One problem I'm having is that even if I click "Stop" and "Start" again to calibrate the tracking, it will not "zero" my initial position. For example, in the program it always says the Y axis is at around 10 when I'm looking straight ahead. In game, this apparently translates to me always looking downward by default, and I have to tilt my head at an absurd angle to get it to look up. It isn't calibrating my initial face position when I start the tracking, because it won't start everything at a zero point, but rather some arbitrary points that screw up the in-game view.

I get absolutely no increase with these new drivers using the 70709 beta and exThreads=0. Tried Bench1, Bench2, and the _FPS_6 Cherno bench.

It does, but in my testing it's way, way too jittery to be usable in game. Maybe I'm not setting it up right, but I'm using the default ArmA profile and in the video preview the tracking seems to work fine, but then I get in-game and it's crazy jittery.