hughlb

Is anyone recording the Twitch stream? Unfortunately, where I live, it will be streaming at like 4am, so I won't be able to watch it live :( Can't really pull an all-nighter this week with my present workload.

Any word on whether we can purchase an extension with the Gunfighter purchase? Isn't the Gunfighter designed around using an extension (weights etc.)?

It might be worth just waiting it out until 2.5 releases. I have no idea what changes will come, but ED has clearly put a great deal of work into the engine. I'm personally hoping it fixes some trackir stutter problems. A problem like yours is incredibly frustrating, and like you, I've had some issues that I just don't see in other game engines. As a side note, I played the beta of xplane 11 and on absolute minimum settings I'm getting 45fps (I know, I know.. it's beta). However, DCS 2.0 at 120fps, high settings, with Gsync has ruined me for all other flight sims. ;) Hang in there, I'm sure ED will keep working to improve the engine.

To be honest, I'm not familiar with Inno3D as a brand, but it does come with a three year warranty, which is reasonable. I have experience with MSI - I had a 970 from MSI, and I can definitely vouch for Gainward too. Both have been good. But yes, I returned my Gigabyte after three days - wasn't happy with the fan noise or cooling levels.

No, unfortunately. I've tried, K, as well as Alt, Shift, Ctrl K etc.

I'm trying to remove the cockpit entirely so I can use an aircraft as a "camera" - Left Alt + F1, removes the cockpit geo, but it brings up the kneeboard, which can't be removed. Is there a solution to this?

Worse. Founders edition cards are essentially the reference card. Well made, but the reference card. Then your usual suspects come an apply their aftermarket coolers, overclocks etc. With the GTX1070, all the cards offer similar performance, the GLH edition of the Gainward was my pick for the reasons in my previous post. I've learned to trust what I see with videocards - if it's got a small heatsink it wont run as cool, if it's got a blower style fan, it will be louder, if it's got two big fans it will be quieter.

Not a card with theee high speed fans! I can't get my head around why people go for a gigabyte or Asus card. I have had both a gigabyte and gainward gtx1070. The gigabyte was loud and hot, the gainward is faster, cooler, quieter and cheaper. Of course to get all those advantages you have a giant cooler. But unless you were planning to sli at some point, I can't see how that would be an issue.

I have a 1070 and it uses about 4.5gb of vram over Las Vegas. I doubt you will use up all those 8gb of vram. I feel safer with 8, rather than 6 on the 980ti. I had a 970 and it simply didn't have enough vram.

Perhaps December 25th? Roughly two weeks after the Spitfire, and a somewhat fitting day for a gift! ;)

Is it normal for DCS to tell me that TrackIR is disabled when I unplug my mouse? For some reason TrackIR just completely stops working when I unplug my mouse in DCS, however when I quit DCS and enter the TrackIR software, it works perfectly. This also happens when I unplug my game controller - it shuts down TrackIR in DCS. I'm concerned that a TrackIR stutter issue I am having is somehow linked to mouse view in DCS - and now it seems there is a link at least, between the mouse being connected and TrackIR running. Anyone got any ideas or seen this before?

Thanks for your input BitMaster. Unfortunately that thread discusses a problem with general stutter. I would like to clarify, that I don't actually get any stutter with the game itself (or any other game for that matter). The problem that mmtaraval and I are getting is stutter when looking around - as in TrackIR itself is stuttering when panning. When I hold my head still, everything is smooth. When I use the joystick hats to pan around, everything is smooth. It's just looking around with TrackIR, when the framerate is less than 120fps. Any other suggestions? I have contacted ED but I have not heard back from them in some time.

Great update, thanks for your hard work!

So would that mean 1.5, 1.5 beta, 2.0, and Normandy as separate installations? I wonder why Normandy isn't delayed until the 2.5 release. Hard not to be sad about the Hornet and 2.5, but looking at it positively, it will be nice to not have a distraction from the Spit and Viggen. As well as something to look forward to in 2017. :)

I'm pretty sure that facebook post with the new shader images said the new lighting was coming to the Nevada update. Perhaps ED meant with 2.5, I just got the impression it was coming with Nevada, due later this year. Thoughts?

So it was mentioned on the FB page that there would be bloom included in this lighting update - Does this mean we will finally see sun glinting off aircraft in the distance? Might solve a lot of the model visibility issues.

Thanks for getting back to me. How about mouse and keyboard? Are you running Windows 10? Given that our problems are identical, and given the main common thread is Gsync - it still looks like it's a gsync/nvidia compatibility issue. I also only have 1 trackIR application (DCS). So I haven't been able to test the issue in another game. If there is no problem in another game, then it becomes a DCS/Gsync/TrackIR issue. I have taken a ticket out with ED, it might be an idea to do the same.

I will certainly pass it on. Would you be able to answer those above questions as best you can? Right now you are the only person who I can check with. NaturalPoint are trying to source a gsync monitor to check the problem, but until they do, it's on my shoulders.

Hi mmtaraval, good to make contact with you. Like you, I deleted the maxfps=180 line, and I agree, it helped quite a lot. Can we compare hardware/software? I wouldn't mind seeing if we have a common piece of hardware (other than trackIR), that might be causing the issue. What motherboard do you have? What peripherals are you running? Do you have this problem in other trackIR applications?

I have 5 and I'm running the latest software version from NaturalPoint.

Thanks for your suggestions, yes it's been a long process of elimination, but I'm still unclear about where the problem is. I will check out usblogview now, didn't know about that. Hopefully it gives some indication to what might be happening. Good thinking on a possible Asrock usb issue. After trying the usb 2.0/3.0 slots on the back of the case, I now have trackIR running through the inputs at the front of my case. Would a usb pci-e card circumvent any asrock problems? If so, I might try it tomorrow.

You might be right, but I'm running out of things to try. Tried 2 monitors - gsync/non-gsync Tried 2 video cards - 970/1070 Tried 2 different 16GB DDR3 kits - 1 1600, 1 2400 Tried 2 different SSD's - two different brands and sizes Tried 6 different USB slots - 3.0 and 2.0 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. No issues with stuttering with DCS, or other 3D applications - stuttering only occurs in conjunction with trackIR/DCS Any suggestions that I haven't already tried?

I recall reading an earlier post by LN, stating they had learned some things from developing the MiG-21, regarding graphical/cpu performance. Does anyone know where/what they wrote? I still have performance issues in the cockpit of the MiG-21, even with a 1070... I'm hoping the Viggen is a little bit kinder to the system ;)

Thanks guys, yes I've tried different drivers, but had no luck. I'm fairly sure it's a compatibility issue with Gsync/TrackIR/DCS. I found a thread from earlier this year where someone with a gsync monitor described exactly the same issue with TrackIR: https://forums.eagle.ru/showthread.php?t=157406

I agree, that was my reaction too. There have been several instances through the year where it was suggested the 2016 window for EA was still being aimed for, most notably in the last couple of months. Wags was also pretty clear about the objectives they had for the last four months of 2016 - notably, integrating systems and working on the PFM (which could blow out into early 2017, sure). Aside from Chizh's comment, there has been nothing to suggest a year delay for EA. However, there's plenty to suggest an EA period could be a year or more, as has been the case with a lot of modules. To me, that makes Chizh's comment make more sense. I'm definitely looking forward to some clarification.