Leg2ion

With all due respect - because it is a 'game'...a realistic one but....! Understand some wish for the sense of realism - but far too many serious people commenting and jumping down the throat of someone who wishes for an easier life.... Gonna bin starting in the air as well?

Where did you get your magvar from? Currently operating out of Kobuleti and havn't had any problems with setting 70o and lining up. Try either only using TACAN or ILS separately to see what each does independent of the other. As far as I know TACAN gives you a range and bearing to aim for, whereas ILS should (if it is working) give you a beam to drive down. So for instance you can go point to point between TACANs, and it doesn't matter from what angle/height you approach the transmitters, whereas for ILS you need to be within range and pointed roughly in the right direction to get a steer. Try setting up a simple NAVEX flight using TACAN transmitters to navigate between. You can just fly 'point to point' between them, or, as you tune into each transmitter also set a course/heading of the runway it is linked to, then you can manoeuvre so you approach the TACAN on the desired course/heading - overflying the TACAN parallel (or close) to the runway heading. Once in the 'ballpark' I tend to knock out TACAN, rely solely on ILS and set both course/heading to the runway approach. Technically heading could change dependent on wind etc to maintain correct course.

Glad to be of help @Toad McFrog! After a bit more research and digging I have noticed that the Dragon Center overclocks your graphics card (assuming you have MSI GPU?) and also gives the option of 'Ultimate' power settings which it had defaulted to over the stock 'High' settings. Also have a feeling it overclocks the CPU as it also installs a Ryzen SDK - but couldn't see any noticeable differences. The biggest difference on High/Ultimate appears to be that it defaults your minimum and maximum processor power to 100%. As a test completely wiped my drives - re-installed Windows and DCS (extreme but new build so not a lot installed), then selected advanced power options to High without using DC - same effect - no jitter/stutter. When turned back to balanced - stutters. Thing I am now trying to reduce is the shimmering buildings. I can completely eliminate it if I have both X2 MSAA and X2 SSAA selected inside DCS - any deviation from this and I get shimmer. It appears any changes made in Nvidia Control Panel have no tangible affect.

Also noticed the UHF panel - despite being able to set pre-sets - will flick from 'pre-set' to 'man' when transmitting - and remain there - so if you don't notice it and roll the wheel you don't actually change the frequency. Not sure of this is how it is supposed to work? Is the idea you would set 'pre', dial in and load all your frequencies, then to operate select 'pre', dial up a pre-set then reselect to 'man', then if you wished to re-select a different pre-set change back to 'pre', dial it up, then flick back to 'man' to use?

I think they are auto downloaded once 'validated' by Steam, but not 100%. Have always kept clear of Steam for DCS as I think the DCS standalone offers better value during its sales etc. Re - your trim - don't forget to also set up/map a trim null/centralise, as an easy way to re-centre it. Another tip is to drop ordnance of opposite wings - mission dependent of course. Try setting up a free flight mission with a couple of tanks as targets - and go out heavy - then use - say - all the mavericks off one station to see how it affects trim.

East/West Germany.

And hopefully this is a track of flying in the Persian Gulf - dialling in to Abu Dhabi International on 119.20 VHF AM, and transmitting to Batumi along with a reply from Batumi. Abu Dhabi - Batumi.trk

As I am learning! So - defaulted/reset all DCS settings, and went into the OT settings. Wow - what a difference - a horrible difference!!! Very jerky/laggy. So - nulled everything, left OT on its defaults - set my original curves in DCS - smooth.

Had similar after I recently introduced some pedals into the mix. Throttle worked - stick didn't - even if I rebooted. Loaded up DCS, and unplugged the stick from the USB port, then plugged it back in. All is now well...

Got it thanks! Already set to 'Picture'. Also playing around with various settings, and unless I have both MSAA and SSAA selected (in game - 2x and 2x respectively) I get 'shimmer' - predominantly on buildings. If I turn either one off it is noticeable - and even if I reduce SSAA to 1.5x it starts to creep in. Current NVCP settings are all on default except the Power Management mode.

When you say turn off the slideshow - how?

Hopefully the attached works? Set a free flight mission in the Caucasus in A10C II. Initially set the following: VHF AM Channel 1 - Batumi - 131. VHF AM Channel 2 - Kobuleti - 133 VHF AM Channel 3 - Kutaisi - 134 VHF AM Channel 4 - Senaki - 132 Function selector back to Pre. No Frequencies held on any preset channels 1-4. Dialled the preset wheel up to 20. VHF AM Channel 20 - Batumi - 131. VHF AM Channel 19 - Senaki - 132 VHF AM Channel 18 - Kobuleti - 133 VHF AM Channel 17 - Kutaisi - 134 Channel 20 didn't hold - the other 3 did. If actually broadcasting the function selector moves back from pre to man. 2nd track - went mid range - using channels 11-14. VHF AM Channel 11 - Batumi - 131 VHF AM Channel 12 - Senaki - 132 VHF AM Channel 13 - Kobuleti - 133 VHF AM Channel 14 - Kutaisi - 134 All loaded, left on 14 - Kutaisi verified, 13 - Kobuleti verified, 12 - Senaki dropped. 11 - Batumi verified. Reloaded Senaki to 12 - verified. Selected 14 - Senaki shown and not Kutaisi. Similar experience on VHF FM. Radios2.trk Radios.trk

Thanks @Rudel_chw. Understand individuals settings are, well, individual, and would fully expect to 'tweak' - but curious to see others input settings to see how things are affected. The curves created in DCS seem ideal, so (as an example) yaw movement can be tuned so angular movement is fairly slow moving across the instrument panel, but then increases as you move towards looking at the edge of the monitor - hence trying to figure out how this is recreated using Opentrack. I am guessing whereas OT has the centre position bottom left of the graph, DCS has its central position in the centre of the graphic - so thinking if I replicate the movement I see in DCS into something similar in OT, then reset the DCS curves I should get roughly the same movement.

Apologies - will look into recording a track and posting it shortly!

Oh my! Not sure how that translates into the curves seen above - what differentiates between looking down slowly and looking up quicker?

Hi @MAXsenna - many thanks for that - as a test will 'default' the in game settings and have a ganders at yours and see how it compares. @Hiob - completely agree - I would rather set the pre-game software and leave DCS all alone - but just seemed easier to tune DCS. Next question - but what does the asymmetric tracking do compared with the top graph curve - are they just different views of the same thing?

OK - so stopped faffing with the OpenTrack curves. Reset them all back to default, re-calibrated the Delanclip and adjusted the curves in the axis tuning settings in DCS. Things seem to be ok(ish) - just need to fine tune/tweak it now, and re-learn how to land with tracking active!!!

Thanks for that @MAXsenna. So far tuned 'Yaw' - what I have noticed is that at max 'look back' the image flickers in game - as if I'm on the edge of what I can view - so not sure how to stop that happening?

Hi All - after some advice/assistance if possible? Complete novice/newbie with headtracking - and have just purchased DelanClip (awesome turnaround by the way - ordered Wednesday night - received Saturday morning) and have set the camera up and installed OpenTrack. Am now following this guide (A complete guide to set up Head-tracking (Opentrack) - Hardware, Software and Controllers - IL-2 Sturmovik Forum) to calibrate and set curves etc, but also notice you can set curves within DCS. Question is - what is the better way to set up for DCS, set the curves in OpenTrack, curves in DCS or a combination of both?

Just been 'back in' for an hour or so. Set up a simple navex in the Caucasus between 4 airbases, frequencies of 131, 133, 134 and 132 (to make it easy). Tried setting them in Pre-set slots 1-4 - no joy. Rolled the wheel up to pre-set slot 20, and worked backwards. Worked 'a little bit better' but still 1, sometimes 2 stations would be dropped. So had 131 set to 17, 133 set to 18, 134 set to 19 and 132 at 20. Mixed results, would select to transmit on 20, then move to select to transmit on 19 and transmit to same airfield as 20. What I did notice, if I did actually send a message then the function selector moves back from 'pre' to 'main', so in order to reselect another pre-set frequency would have to change function again back to 'pre'. Process that appears to work is set function to main, set pre-set, set frequency, load, change pre-set, set frequency, load and so on. Once all frequencies are in set function to pre. And hope it keeps all the pre-sets - more often than not dropping them. UHF appears a lot simpler. Set to Preload, dial in frequency and preset channel. Press load and repeat. Done...

Something I'll have to figure out how to do once asked. Maybe waiting (ignoring it) for the Arc210 upgrade - which I think is replacing the Arc186?

Apologies if reporting a previously acknowledged issue - but couldn't find anything recent on this? Currently cannot use VHF AM or FM presets. From what I gather the (same for VHF AM and FM) process is - Function Selector dial to 'Man', pre-set wheel to '1', dial in frequency, press load; dial in new frequency, pre-set wheel to '2' and so on. Then set Function Selector to 'Pre' and should be able to use the pre-set wheel to select the different 'loaded' frequencies. I work through the frequencies - verifying contact with each station as I dial them in and load them, then when I switch to pre-load it appears to drop all frequencies. Occasionally it might hold onto the latest frequency dialled in, or if I de-select AM then re-select it re-enables comms with Nellis. Am on the Nevada test range, and am trying to pre-set Tanopah, Creech, Groom Lake and Nellis. As an aside was in the Persian Gulf map - dialled in the frequency for Abu Dhabi, detailed inbound and received a reply from Batumi? UHF presets are working fine.

Hi @RavenLeader. People here are awesome at responding and providing help - as you are finding out. I have just built my own PC, after some input from here and elsewhere, as last time I built one was around 8 years ago so had completely lost touch with current standards. To be honest building a PC is not that difficult, and there is plenty of subject matter via google etc. Normally take me around an evening (and a bottle of red!). What it does do is give you a good understanding of how it all goes together - so if things do go wrong you know how it was built. My build was: AMD 5600X Asus X570-f Rog Strix Motherboard 32 GB DDR4 Ram (2 x 16gb) 500GB m2 NVMe boot drive - Windows/Office etc 2TB m2 SSD 'Games' Drive 2TB SSD for photos/editing etc. DVD-RW Optical Drive MSI 3070 GPU 850w Modular PSU BeQuiet 600 Pure Case Always used to use Scan - and have never had problems with them, though for this build went with CCL as their component prices were slightly lower. After doing some research have also just purchased headtracking - and went with the DelanClip due to decent pricing and availability.

Cheers @Frederf. Makes perfect sense. I was starting to think it was pointless trying to put the 'thread through the eye of the needle' when the result was spreadable chaos back out the other side, but couldn't find anything in the manuals - only quite generic references to CR.