doveman

Don't you miss the extended side views you had with your 4-screen setup, as shown in your photo here http://forums.eagle.ru/showthread.php?p=1677969 ?

It depends on the TV. I've just bought a Panasonic 50" Plasma and checked before I bought it that it had low latency.

OK, it seems that pressing Esc starts the mission just the same as clicking Fly, so that's one problem solved.

I was interested to read this "Looks like Saitek switched to the same Melexis tri-axial Hall sensor that TM became so enamored with in the HOTAS Warthog and T.16000-M. The PCB position underneath the gimbal and what appears to be a small magnet at the bottom of the stick post with no signs of sensors beside the gimbal assembly suggest that. Fortunately, it's a good sensor. Unfortunately, it makes gimbal mods much more difficult as opposed to the X-52's use of individual Hall sensors for each axis (just ask Okona about his efforts to gimbal-mod the Warthog), and believe it or not, I've seen pics of a Baur BRD-modded X-52 before, which would singlehandedly turn a cheap stick into one of the better sticks money can buy." I'm wondering if anyone knows about this Baur BRD mod, as I could get a X52 Pro s/h a lot cheaper than the X55, so depending on how complicated and expensive this mod would be, it might be worth me doing that instead?

STEM seems to use a big hand-held controller, a bit like Razer Hydra, so that's not going to be very practical. PrioVR might work but the cheapest option appears to be an 8-sensor upper body suit and I'm not really looking to pay for that when I really only need one sensor on one hand.

Yeah, I'm getting there with my VAC profile for the KA-50. Not quite perfect yet but it sure makes a great substitute for physical switches. I can imagine if I was playing with the Rift though, I'd be itching to reach out and flick those virtual switches :)

OK, please post in the other topic if you prefer to keep this one focused on the Huey module and not general object count issues. I'm subscribed to this one anyway, so I'll see if you post any further observations here as well.

No worries, thanks for trying. I think that this version has Accela Mk4 and maybe the older version had Mk3 or Mk2 but it's supposed to be better! Maybe the best thing to do is report your problems to the author here http://sourceforge.net/p/facetracknoir/discussion/1150909/thread/8771c92d/?page=2 and he might be able to help you fix it, or he can fix the software if you've identified a bug.

The more pictures of the X-55 I see, the more cheap and plasticky it looks to me. Sure, it's considerably cheaper than the Hog but it's still expensive enough to annoy me if everytime I use it, it feels cheap. I'll really need to see both in person though before I can make a proper decision about whether it's good enough or whether I think the difference is worth investing in the Hog, which isn't without it's own problems.

Isn't there anything already available that could be used in DCSW to detect hand position, to allow us to virtually flip in-cockpit switches? Could the Leap Motion be used for this? https://www.leapmotion.com/product Or maybe the Kinect? I think this would greatly enhance the virtual experience, even with a monitor but certainly with something like the Rift.

From what I could tell from my testing, the Obj. counter didn't necessarily affect FPS (could have about the same Obj. but much different FPS) and the Render Main counter didn't seem to correlate with the FPS either. It seemed to be the Scene Objects counter that was the main reason for low FPS. I can see from your screenshots that in the Huey one, this is over double what it is in the Hind one. The Render Main is about double as well but as I say, that didn't seem to be connected to the low FPS. Perhaps there's a way to setup a scene with low Render Main but high Scene Objects to verify this.

Sorry, I forgot to paste the link. I'm using the 16 February 2.2 build from here http://ts3.cosaofficial.pl/opentrack/ It actually still shows 2.0rc1 in the window so ignore that. I don't think loading/saving the file I posted in your 2.0.3b will work as I'm sure that version won't recognise the re-titled and amended sections from the later version.

I doubt it's that common as I get motion sickness really easily and can't play a lot of games because of it and I've never had any problems using headtracking with DCS World or ArmA. I'm worried I might not be able to use the Rift though, so will need to thoroughly try it out before buying one.

I've posted some screenshots and observations regarding object count and fps with the KA-50 that you might find interesting as well. http://forums.eagle.ru/showpost.php?p=1996080&postcount=114

OK, I compared your file and a fresh file created with the version of OT I have and it seems a lot of sections have changed title ( [PointTracker] is now [tracker-pt] ) or been merged ( [PointTrackerDialog] is now part of [tracker-pt] ) or removed. I've done my best to copy your settings into the new format but some things didn't translate exactly (e.g. the Accela MK4 section doesn't have any axis settings), so perhaps you could try loading the attached file into the latest version of OT and tweak it to match your previous settings where necessary and re-upload it for me? Note, this one has my PointTracker/clip settings under [tracker-pt] , as that section has changed too much to easily copy your settings across, so you'll need to enter your settings again with the latest version. OT DCS.txt

txmtb, I can't seem to load your profile in OT, it just results in everything being blank/set to defaults. Are you maybe using an older version? I'm using the latest v2.2 build from 16 January from here http://ts3.cosaofficial.pl/opentrack/

Thanks txmtb, that's really great of you to share your profile :) I'll give it a go and see how I get on. I think I just need to copy and paste my existing [PointTracker] and [PointTrackerDialog] sections over yours (or most of them anyway, there might be one or two lines I'd should leave as you've got them) and it should work.

Indeed. Sorry, should have posted a link and explained a bit more myself, rather than assuming everyone had already heard of it :doh:

Your link is broken llama, here's a working one for anyone looking for the app https://play.google.com/store/apps/details?id=com.portman.panel.uh1h

What I don't really understand (maybe because it's impossible), is how I might be able to get a wider view on a single monitor. With 3 monitors, I guess you use a higher resolution, with the normal 1920x1080 mapped to the central monitor and the rest mapped to the side monitors, so to achieve the same sort of thing with a single monitor, I guess I'd have to use the central third of the screen, 640x360, for the normal view and then 640x360 for the extended left view and the same for the right, which doesn't sound like it would work. Even if it would, my 50" TV is actually only 1280x720 (acutally 1024x768 but it uses square pixels apparently to resolves 1280x720) and whilst it accepts 1920x1080 to produce a picture where everything is smaller, it's obviously not able to display all the pixels and must be skipping the ones in between the actual pixels, so everything's a bit less sharp and it's better to run games at 1280x720 (even if it was 1080P it would be a struggle to read everything in text heavy games from my normal seating position) but probably that's not good enough to be able to spot things clearly in DCS World. I was aware of this limitation when I bought the TV recently but I really wanted a Plasma rather than a LCD as they look so much better for TV/Movies and I also wanted a Panasonic as they make the best Plasmas (or do until March when they're stopping production anyway) and I couldn't afford the extra for a 1080P model and from my normal viewing distance, I wouldn't be able to appreciate the extra detail anyway. Obviously if I built a cockpit I'd be sitting much nearer and would be able to but I don't know if/when I'll be able to do that, so I couldn't really factor that into my purchasing decision and I was mindful that I might want to spend money on the Rift or similar in the near future anyway.

Just wondering if anyone's got a good Opentrack profile(s) for KA-50, A-10C, UH-1H and SU-25T (maybe one profile works fine for all of them)? I've finally got my IR clip working well with my PS3 Eye after removing the IR filter and am just starting with Opentrack and don't really understand what half the settings do!

I did some more testing the other day and noticed that the Obj. you refer to can be about the same with two different views but still the FPS can be a lot lower with one, and the Scene object counter seems to increase a lot when this happens. So it seems Obj. doesn't correlate that accurately with the other counters and it is these other counters that are more important to refer to when seeing low FPS. Obj: 658, Render Main: 30.5, Scene Objects: 23.1, FPS: 24.1 Obj: 623, Render Main: 32.2, Scene Objects: 25.2, FPS: 21.5 Obj: 413, Render Main: 29.4, Scene Objects: 24.5, FPS: 23.6 Obj: 434, Render Main: 26.6, Scene Objects: 18.1, FPS: 25.7 Obj: 492, Render Main: 254.1, Scene Objects: 13.6, FPS: 39.8 (DCS FPS counter: 2.03(72.68)) (this would seem to rule out Render Main as having much effect on the FPS, unless we ignore the MSI overlay and only look at the DCS FPS counter) Obj: 328, Render Main: 9.9, Scene Objects: 5.5, FPS: 40.1 (DCS FPS counter: 69.93(72.68)) Obj: 195, Render Main: 6, Scene Objects: 2.4, FPS: 64.9 (DCS FPS counter: 104.59(103.14)) Obj: 322, Render Main: 9.5, Scene Objects: 6.2, FPS: 93.0 (DCS FPS counter: 71.66(68.91)) (this is a bit confusing, as everything is higher than the previous screenshot but so if the FPS)

Not anymore, as you can see from these screenshots I made :) http://forums.eagle.ru/showpost.php?p=1962162&postcount=51

You need to get the latest MSI AB beta 3.0.0 beta 18 (which comes with Rivatuner Statistics Server (RTSS) v6.0.0 which is the bit that actually shows the OSD), as it was only recently made 64-bit compatible. I use it fine with DCS World now. http://www.guru3d.com/files_details/msi_afterburner_beta_download.html RadeonPro has always been 64-bit compatible though, so you should be able to use it's OSD tab to show some GPU stats. I find that RadeonPro and MSI AB/RTSS tend to conflict with each other though, so either set your DCSW RP profile to "Disable API Monitoring" and "Disable Auto-Detection" or set your DCSW profile in RTSS to "Application Detection Level: None" and the global "Show On-Screen Display: Off".

I'm looking at the X-55 and Warthog but it's a shame neither have FFB and now you say the mini stick on the WH is crap and I hate paying loads of money for something that has issues. So I'm considering buying a MS FFB2 and X52 Pro cheap off e-bay and combining them like this http://simhq.com/forum/ubbthreads.php/topics/3733703/Re_X52_MS_FFB2_Hybrid#Post3733703 so that I have a FFB stick with a decent amount of buttons/hats on it, along with the X52 Pro throttle. I have the A-10C, UH-1H and KA-50 modules but I'm focused more on the helos at the moment and everyone says you really need a FFB stick for them, so it's a shame no-one is making a decent FFB HOTAS at the moment. The only thing I'm not sure about my combo is whether the pots will be good enough or if it will be possible to replace them with hall sensors to make it more accurate, as precision and sensitivity is probably even more important than FFB for balancing the helos. I wouldn't have a clue how to do this myself though, so unless someone's already done it and written a guide I'll have to make my purchasing decisions on the basis that this isn't possible (or at least I'm never going to do it), so if the Sidewinder/X52 combo isn't going to be accurate enough without hall sensors, I should probably forget about it and go back to choosing between the X55 and WH.