Leg2ion

Hi @Frederf - found it thanks. Just back from a 2 hour navex between bases - as playing with navigation waypoints, flightplans etc to make things clearer in my noggin how to set flight plans/waypoints in the middle of an already established route. Up until your previous post and a bit of googling I didn't realise you could use the easy comms to actually change frequencies by using the F numbers. Previously I would toggle my comms switch, F5 for ATCs then look at the base/frequency I wanted to aim at and then still dial it in manually - so basically had managed to unwittingly develop a 'semi realistic' mode! As far as I can see realistic mode just adds another painful experience of having to refer to another kneepad/map or whatever to get the correct frequency. Sure it will become second nature in due course.

Didn't know there was such a thing. Will investigate and select 'realistic'? Where is that setting? Did post about this about three weeks ago above. Understood the other three points - but nice to get confirmation. Would say completely broken then, as if it transmits on a dialled in and loaded frequency by not moving the preset wheel you're not really pre-setting anything, just dialling in a frequency and loading it to transmit? Although I guess it is proving the load button works.

Ok - set 2 frequencies to 2 channels - UHF radio - hopefully this trk will let you see what I am getting - when I broadcast the selector moves from pre to amn.. Radio.trk

Ah - ok. Will try it out as first mission when next I fire up DCS.

Yep - same issue - 'tis being investigated. Works a little bit better if you use pre-sets at the top of the wheel - so dial it up to 20 and work backwards - but still not brilliant and frequencies still get dropped.

Does say to turn off civ traffic that in the mission brief.

If you haven't already try unplugging them from the PC with DCS open and then plugging them back in again. Had similar whereby DCS 'lost' my stick, in that it wouldn't work in-game, but in the controls option (outside of a mission) all appeared to be OK. Unpluggint/replugging appeared to work.

Not sure if it will help any, but with DCS open try unplugging and then replugging all your controllers from the USB ports. Had a similar issue when introducing some pedals into my controls - in that my stick was dropped. Some of the bindings were missing, others not recognised. Rebooting didn't help, but unplug/replug fixed it.

To be honest, if affected by the nose wheel position - offset to the right - wouldn't/shouldn't the nose pull to the right (shorter turning moment?).

Could be - but I then would expect maximum turn rate to be exaggerated at the higher speed - and not the lower? Unless of course the opposite applies, and the higher speed helps keep it more stable.

No problems! Fairly certain I had no loadout. Basically set a mission up from Tonopah, hot start from runway, pushed throttle fwd to get a decent taxi speed (less than 50), cut throttle, waitied a few seconds then pressed 'W'. Had around a 5 degree yaw to the left - it being exaggerated towards the end of the brake.

? Explain please ? Just don't understand why so many peeps have issues over a persons desire for an alternative auto start that fits their needs? If it makes things more accessible and spreads the user base then why not - as a previous person mentioned you don't have to use it?

That'll be why I didn't use my pedals to brake and just pressed on 'W' - and still veered off...

Apologies if resurrecting something old - seen a few posts regarding the F16 but not the A10C2. Noticed last night on landing I veered to the left as I applied wheels brakes. Not noticed it before as my landings are 'dicey'!!! Thought it may have been 'me' so checked pedal bindings etc - all good. Just lined up quickly on a runway, applied power to get rolling, reduced power and hit 'W' (to eliminate any possible issue with my pedals), and yep - veered to the left. Straightened up, rolling, brakes - to the left, one more time - same. Wind at 0 m/s so shouldn't be any weather vaning. Track attached. Wheel Brake Taxi.trk

Also found another reference to the slideshow in the power settings - not sure if it would make any difference but now set to 'Paused':

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...