hughlb

Just seeking clarification - does the #50 springs come factory installed on the Gunfighter Pro? The manual doesn't state factory installed: "The Gunfighter Pro comes with an additional spring to support the extension: • #50 - extra strong" Just wondering if I have to fit the #50's when it arrives

That sounds like possible connection. However, if is were a timing issue, then it should be occurring in other games, and it's not. It's also worth mentioning there is no stutter when panning the view with keyboard or joystick hats. If it were a general timing issue, I would expect it to be stuttering all the time, not just with TrackIR. Thoughts? EDIT: I ran the Windows Timer Tool and set it to 1ms response time, which matches my monitor, but no difference in DCS. Likewise, I think I've tried before, but I disabled/enabled HPET and Hyperthreading, but no change Also, sorry, I missed your last question - no, there is no return for TrackIR, it'd need to be sent overseas - in addition, my warranty has run out (although I did lodge an initial ticket with NaturalPoint during the warranty period).

Ha, all good, I appreciate your help. I took a break for a few months, the good news is every time I return, there are new things to try. The main frustration is the cost - I could buy a new TrackIR, but it may end up on the growing pile of investments unrelated to the problem ;) I wish my friends liked simming! I'd borrow hardware. I tried deleting all mouse bindings in-game and in the various lua files in the config folder, but nno change. I am currently running TrackIR into a powered PCI-E USB 3.0 card, with nothing else plugged into it, so it should be getting sufficient power. I also tried maximizing the Windows USB power options, but no change. I would dearly love to try another receiver. I've toyed with the idea of purchasing another TrackIR, but yeah, it's still a lot of money. I mean, if Mike at NaturalPoint said "I think your TrackIR might be faulty", I'd happily give it a shot, but there haven't been too many suggestions about a faulty unit. The oddest thing is the behavior of the problem - It's linear, in that, the stuttering is consistent and directly related to the framerate in-game, regardless of graphics settings. It's the sort of thing you would see if your mouse and TrackIR were sending conflicting view inputs, or something similar. Or a monitor refresh rate / TrackIR interaction problem. What I do know, is that TrackIR runs at a native 120hz, and the stuttering is solved in-game, when my framerate is at 120fps. I can't help but believe there is some sort of connection there. EDIT: Okay, this is odd. When I disconnect my mouse from my computer, DCS says my TrackIR has been disconnected and I lose headtracking. Is that normal? Doesn't happen when I unplug my keyboard, just my mouse.

I was hopeful, but unfortunately I'm currently on the latest version of TrackIR software, but with no luck. I have tried the following over the last year: 2 monitors - gsync/non-gsync 2 video cards - 970/1070 2 different 16GB DDR3 kits - 1 1600, 1 2400 2 different SSD's - two different brands and sizes 8 different USB slots - 3.0 and 2.0, front, mobo, pci-e card Tried 2 different OS - 8.1 and 10 Tried a fresh install of OS, and DCS Tried various drivers, firmware etc. Tried different Nvidia and game settings, including vsync, gsync, no sync Clean install of windows and DCS, including formatting all drives, three times now. Bios updated to the latest version Hyperthreading on/off, and various other latency, affinity tweaks (currently at default) No issues with stuttering with DCS, or other 3D applications - stuttering only occurs in conjunction with trackIR/DCS Can anyone think of anything else I can try? Could it be my motherboard? my PSU? CPU? TrackIR hardware? - I've almost bought an entirely new machine to resolve this issue. I can't replicate the problem in other games, it seems native to DCS. I've had tickets with ED and with NaturalPoint, but I think they're at the point where there isn't anything else to try. It's disappointing to throw this much money and time at the problem, and still not know what the cause is, let alone how to fix it.

Saw it in my inbox! That's the email we've been waiting for :) thanks VKB and Rainer!

Yes, if you could detail the testing procedure that'd be great! I am not ruling out that there is a hardware issue with my specific TrackIR device, which is always possible. I noted a couple of people in previous threads that appeared to have the same issue, but again, it might be specific to a certain hardware configuration, or game configuration.

Yes, done probably anything you can think of ;) Even bought a new OS, vid card, memory, ssd, usb pci card, monitor, and peripherals... practically a new computer. I am guessing this problem is common, but not many people are running 120hz-140hz monitors with an uncapped framerate, so they're not seeing the issue. It's incredibly annoying because at 120fps/120hz with gsync, it's so smooth, so you really notice the difference.

Track Clip Pro, on my end.

Excellent, this is the sort of feedback I'm looking for, Sgt_Baker. Thanks also JG14_Smil. Those who are reading this thread for the first time, jump in DCS and test if you can. The more feedback, the better the opportunity to work out what the issue is.

Hi guys, I've had a niggling issue with TrackIR for over a year now - above, and especially below 120fps, TrackIR stutters - not DCS, the framerate is smooth, but looking around looks like 25fps - it's most noticeable between 90-100fps. My theory is that it's a conflict between DCS and the 120hz that TrackIR natively runs at (or it's a TrackIR issue). If I use the hat on my joystick to look around, there is absolutely no stutter. But I need your help to verify this problem. My setup is in my sig, I run a gsync monitor, with both gsync enabled/disabled, at 60, 85, 100, 120, and 144hz. My framerate is unlocked in DCS, and I have TrackIR5 with the latest version of the software installed. If a few of you could run the sim, and simply observe how smooth TrackIR is at framerates from 60-150+, and at different monitor hertz, that would be most helpful. I'm trying to collect some data for Mike at NaturalPoint.

4) Exactly. Flight models in simulations begin and end with accuracy. Accuracy doesn't mean it's easier or harder to fly.

I wouldn't be surprised if it will be updated at one point or another, ED seem to do this. I guess it depends how long they plan to officially support it. I used to think the IL2 Cliffs of Dover models looked amazing, but not anymore. Someone in an earlier post commented on not updating as it will adversely affect performance. Poly count doesn't really have the same impact as shaders and fill rate, so I wouldn't worry about poly count too much :)

Buzz and Sharkbait, have you purchased Nevada? I know the stable version of 1.5 seems the best to have, but it's running an outdated terrain technology. Nevada moved from T3 to T4 terrain (I think I have that naming correct). I get stutters and generally lower frame rates in 1.5, but Nevada is much better. I'd be doing my testing on Nevada if I were you, as the 'great unification' of 2.5 will take you in that direction anyway.

I wouldn't put my money into a CH or Warthog anymore. For a long time, they we the benchmark for affordable enthusiast sticks. But now, VKB, Virpil, BRD have all raised the bar considerably. Sokol has described the limitations of the CH gear. In addition, the CH is not designed to be used as a center-mounted stick. The Warthog is also designed as a side stick, you can mod it to make it a center-mounted stick, but VKB, Virpil and BRD all have sticks that are fundamentally centre-mounted. Also, the Warthog has internals that you would find on an entry level joystick - cheap, poorly made plastic gimbal. You now have three different companies that will give you far more for your money. I've gone with VKB, will let you know what the Gunfighter is like when I get it.

I'm happy to do a ticket too, one of us should at least. I am sure this thread is read by the developers, but a ticket would certainly help.

Is there any update on resolving this bug? There are a number of people suffering the same issue, and I'm sure we are all happy to contribute in any way we can. The problem is severe enough that I'd call the MiG unplayable at this point in time. So please let us know what you need from us.

Yes, happens in all quick missions, and if I just create an aircraft and make it playable in the editor. Happens both cold and dark, and in the air.

This is odd - definitely a problem specifically with the MiG-21. I have deleted/reinstalled license, repaired 2.0a, adjusted the settings - no difference. Every other module is buttery smooth, just the 21 is stuttering wildly. Here's the weird thing - as soon as I hit pause/break, the framerate stabilizes, and looking around is smooth.

Yes, tried repairing and rebooting - I do that generally when patching anyway ;) Tried deleting the 21 and reinstalling just now. Same issue. Does anyone have a gsync monitor or at least an unlocked framerate, who can verify this issue?

I have updated to the latest patches, released today for 1.5b and 2.0a. I am getting an extremely unstable framerate (which appears as constant stutter) in 2.0a with the 21. I'm running a gsync monitor, but this occurs also with gsync disabled. My framerate counter is spiking between 100-140 constantly, regardless of altitude or graphic settings. I have checked 1.5 beta, and this problem is not evident in that version. I have also checked my other modules, including the Viggen, and I can't see any issue with any other module. Thoughts?

Looking forward to the update for 2.0. Thanks for this.

I went from a 970 to a 1070 and saw a lot of benefits. This gen has brought some big gains, but I don't think even a 1080 ti will suffice for VR, ultra wide, 4K gaming. We are a gen or two away from hardware eating those resolutions like they eat 1080p today. I'd get a 1070, put the money you save into a jar, and break that jar in a couple of years. By then, gen two of VR will be out, which should bring its benefits. I know this sounds like always looking forward and never enjoying the moment - but - I remember when I said the same thing about gaming at full HD, and I'm glad I waited a couple of years. Now I have a rig that can run anything at 1080p :)

You do realise a key is a far better deal, right? Any DVD version of a module will need to be patched immediately anyway, so why bother? I sold software in my previous job, and we didn't have a disk version of anything, everything is a digital download now.

Yep, page 8, had the same issue as OP. Delete the regedit entries as discussed on page 8. That gets it working in the Beta. Don't try using in the Alpha or Stable.

I think you'll be chasing a bottleneck around your system if you try to find a weakest link. Realistically your RAM, CPU, GPU all need an upgrade - but then you might as well get a new motherboard and PSU while you're at it. Very quickly it starts looking like a new system ;)