Shaman

I also do not understand, just after I spawn FOV is set to something more zoomed out then default. What I do, I move my zoom axis slider just a notch near center how it remained before launch, and it snatches back to center where deadzone is.

All good for me in A-10C with mod and 1.2.8. I have moved default view point. Do you want my user LUA files to try?

Sure thing, thanks for helping too, ..campaign mission #1, F-15C... and it was just familiarization flight, there was like nothing going on to kill these frames below my normal average - at least from players perspective.

Yep, awful. By the time I RTB,it dropped to 10-15, I had to fight terrible frame rate on approach and landing. Things deteriorated with time... I usually fly at 40-60, WTF?! (where's that frame)

Issue confirmed for 1.2.8 DCSW. SA-SIM.com JWGCI event http://sa-sim.com/?p=7384 has been postponed after two attempts to host event on <51>SERVER for 30 clients. Desyncs were so severe we couldn't continue and worst we have seen so far in years. Multiplayer for DCSW 1.2.8 is broken, there is no way to continue competitive flying at this stage.

I have similar, it is good enough! I have been flying on it for like 3 years; Get ACESII replica if you can afford it.

Correct ratio for 1920:1080 is 16:9

Distorted cockpits? Check your monitor's aspect ratio in settings. There is new bug in 1.2.8 and somehow DCS changes monitor aspect ratio on own will.

SAT X/Y 100 CURVE 0 DZ 0 my case for all AFM/PFM planes

what we lack there of is professional damage, wear and tear model :)

You are spot on on this one, GG :) ATC is required to land (by procedure) Finished my training in VRS already ;) Bring me on DCS SuperBug!

are you all talking megabits (mb/s) or MegaBytes (MB/s) per second? big diffrence 8-p I am around 0.6-0.7MB/s on phonelines ADSL.

This is why I am looking forward to change the default behavior. Second reason is because I have multi screen setup with panels and ts3 on secondary displays and DCS rendering in full res border less window filling primary display. ED?

Wow, there you have it. Track Clip Pro performance is deteriorating when head down and turned left or right. It starts to jitter I know. I have used Clip Pro for years and recently switched totally to hat. My squad mates confirmed the same, that basic hat clip tracks better (performance wise) at head down moments. I also noticed difference and reported back to them this observation a week ago. Now with mod neck (cam arm length) is increased so jitter must be generating more in space camera travel than before, and this is what I believe you have observed. Try also to battle this by increasing Smoothing in TIR to like 40-50. Jump in the hat too, ClipPro will fall apart anyway and its cheap IR lights are life limited and die after like 6y of moderate flying.

B So what do I have to do, look at lights panel then decrease FOV? And what shall I get, jitters when tracking at max zoom in this tracking corner? I have might not notice this before because I zoom in only on HUD during guns or when I try to spot something truly far outside windows. Can you show screenshot of your TIR dots when you are in this far corner, are you sure all are still well traced(?), this is common TIR problem I had to fix separately from anything. Changing position of TIR receiver (much higher and angled pitch down) as well moving my cap more on my forehead fixed these issues. Sometimes it takes just an inch higher to get real difference and just a bit more hat on your forehead. I don't think there is much you can do here beside increase tracking performance in your pit but I may as well be wrong. Good thing is within two years we will fly in VR Googles:)

Polaris1, why such unconstructive statement? I do not break anything here on my end, you must have some other issue then. Can you please elaborate what is going on with your ZOOM (FOV??)?

Something gone wrong, can you also please report which airplane you're using? Regarding moving it back/forward/higher/lower, it is explained in first post (click spoiler buttons) or your game manual or controls section for cockpit view. Also confirm sure you are using 1.2.7 DCS World without interfering mods, and not using beta 1.2.8 or legacy versions.

I <3 Tapatalk!

Can someone make a comparison screenshot, ATI vs NVIDIA smoke effects for current ver DCS P-51D? ATI users in my squadron are reporting that engine smoke is clearly opaque and visible at unrealistic distances (+40miles with a little zoom in) while I fly on NVIDIA and have none of these troubles. Maybe rendered has something to do with this too?

That's new to me what you just did. All right will try, but back when I was wondering how to fix that I could not get my good result with Sat-X other then 100 with reduced Sat-Y! I just wish ED fixed TIR support out of the box, I even filled bug report back in DCS, but no true fix from ED since forever.

Polaris1 and _Dredd, please double check what you have done, saturation fix shall be applied only to Saturation-Y value from 100 to selected value within that AXIS TUNE dialogue for TRACKIR_YAW..PITCH..ROLL, do not touch Saturation-X value (leave at 100) in any of the three.

Not the panel'ed one, due to features in my pit I went with 3DConnexion for Notebooks, it had necessary size to fix it where I need it most. Cheap solution too!

I have been convinced since DCS A-10C release to get rid of keyboard from my pit, I only use miniature bluetooth keyboard (pocket size) for typing IP address or rarely chat text message that is incorporated into the pit. Everything else is HOTAS + MFD bezels, two touchscreens with panels, and special keypads for radio control and sim functions control. Even mouse has been eliminated in favor of mini track-ball stuck to my throttle. For controling views I have 3DConnexion controller next to throttle. Everything AI/radio related and additional functions within sim are voice controlled. I am totally RIFT ready! Should I get DK2 or resolution still to low to read HUD, displays and analogue instruments, for 960px wide @ 100deg FOV I find it most likely so?

Saturation fix is true for roll too, but it's not TRACKIR_X responsible for roll, that one is for translation, but TRACKIR_ROLL instead.

Happy this helps, I have edited post above, but since you're already set:thumbup: