Talvid

ok, after reading the manual, and another thread which I probably should have searched for before starting a new one I found out that with this plane if you press the NWS button you must not let it go until the nosewheel is in the neutral, straight position, otherwise it won't engage again until you have the rudder pedals in the same position as the nose-wheel is in. Whenever I let up on the NWS button (because of laziness) it disengaged and wouldn't engage again until the rudder pedals were in the same position as when I let up the button. Problem solved. Pmiceli I see your solution, the only difficulty with using the wheelbrakes to steer is it doesn't work effectively from a full stop, only when rolling. So the solution is. press the NWS button to engage nosewheel steering only when the rudder pedals are neutral, and only let off the NWS button while the rudder pedals are back at neutral, otherwise you will have to 'catch' the nosewheel by turning the rudder pedals in the direction the jet is turning, and try pressing the NWS button to see if you had it aligned right. This is a nightmare if you are careless enough to let off that button while turning. Whew. I was able to go in to the 4YA server and I taxied around no problem. thanks for the help all.

It's true, because I went in to my F-86 settings and checked the box for realistic nosewheel steering, and now I have the same problem in single-player, how do I steer the Sabre on the ground, I'm holding down the NWS button and I still can't correct the nosewheel.

I can taxi and use nosewheel steering just fine in single player, but in multiplayer I can't get the nosewheel to move reliably. has anyone noticed this same issue?

Mission 12: I couldn't hit the Tanker. Everytime I send 'ready pre-contact' they call out "Enfield 1-1 this is [tanker] with two chicks in tow, but they don't send " cleared contact" and even though I swear I catch the basket it doesn't latch. was anyone able to take on fuel in mission 12.

Museum Relic is very entertaining. I started it first to learn the Sabre and that's proved to be a good starter campaign. The missions are very manageable, and immersive in nature with a charming plot. I'm now looking forward to the Yalu campaign.

and it's undesignate that does that in TWS. Thanks for the info. Sorry for posting in English in the Russian forum.

I apologize, I didn't realize I was in the Russian part of the forum, I thought all languages were in the same forum like the old site. Sorry!

good to know, mapping it now to my TMS left button, thanks

Hello all, When I have a bandit approaching at close range, or I'm engaged in ACM, I like to press SCS right in A/A to turn on AACQ which means Automatic Acquisition mode. Sometimes this gets me locked on to an aerial target that is 30nm or so in the distance, while I'd much rather it get a lock only on the nearest aircraft to me, like the one trying to shoot me down in close proximity. What is a good way to break the lock with the contact far away? Is there a button to press that will cycle targets, or should I back out of AACQ mode and do SCS Up to enter ACM Bore, and then SCS Down to enter ACM Vertical scan mode? What do you do to track bandits in a dogfight?

Does SCS Depress do anything?

Kirrasdad, have there been any improvements since you posted? What is it exactly that isn't working? Is the main screen showing DCS? you might need to update the individual LUAs in your Mods\Airframe\Scripts folder. have you seen my post: https://forums.eagle.ru/forum/english/digital-combat-simulator/dcs-world-2-5/bugs-and-problems-ai/multi-monitor/290864-mfd-hsi-ded-ifei-ufc-etc-screens-on-second-monitor It will explain how to make MFD screens appear inside the cockpit screenspace

I've now used in during squadron missions, it works between the F-16, A-10, F-18 etc. Much thanks to everyone for coaching me on this

Yes, now that you guys explained it to my I get it. I just tested it. My assistant turned on 38X and I 101X and I saw his distance from me very accurately. thanks for helping me understand!

Elevation input is not accepted on my tgt ufc . I tried to enter 4880 ft but the ddi page only showed 0 and the slams hit the ground far short of the pre-planned target

I was online yesterday, Jesto in a hornet was on 20X A/A TR, so was I, and there was innaccurate range info on the HSI. The Tacan 3 alpha code wasn't even there nor a way to set it.

Today's findings on the mission editor: I was able to get distance info on my HSI in both the F16 and F18 using the Tacan to tune in to 16X, 18X, 39X, and 41X. Like you said, Nealius, the bearing info isn't available but I was able to see the nm range to the aircraft. Now I'm curious as to whether it will work in multiplayer

From what I can see on the UFC / DED is I can only punch in one Tacan number at a time. I'll see if I can get range info that matches the F10 map distance between blips, to figure it out.

I went back into my mission and tried receiving TACAN 79X for the F-16 and TACAN 81X for the F-18, which I calculated to be 63 MHz higher than the stations I set them to transmit at. Still the TCN symbol on the HSI was just spinning. Maybe it only works in the A-10C.

I heard Mover (C.W. Lemoine) talking about navigation and formation flying in inclement weather. He said that F/A-18s can activate their TACAN and use it to track each other. I tried this in stable, mission editor, and I was able to track a KC-135 tanker with TACAN 65X, but I also set an AI F-16 to activate TACAN 16X as well as an AI F-18 to activate TACAN 18X, and I am only able to get the tanker plane's TACAN up on my HSI/HSD. It would just be a pretty nifty feature to be able to track a flight lead, or wingman with TACAN Air/Air! Thanks already Eagle Dynamics, for an awesome sim, that keeps getting more awesome.

Hello, there are bits and pieces of the solution for how to get MFD and IFEI, DED, UFC windows to show up on your monitor. They are scattered throughout threads, I'm consolidating the info here. Know the name of the [indicator ]window you want to add to your screen and search for it in your DCS directory folder: 1) Find the [indicator]_init.lua in the Mods\aircraft\[airframe]\cockpit\scripts folder 2) right click and select edit that .lua with Notepad++ so as not to corrupt it. Only edit .lua files with Notepad++ which is an app you can download for free 3) under the first dofile... line at the very top, add the line: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") 4) press enter twice to skip to the next line and the next to leave a blank line and add the line: indicator_type = indicator_types.COMMON 5) next if there isn't a line starting with "purposes" add it: purposes = {render_purpose.GENERAL , render_purpose.SCREENSPACE_INSIDE_COCKPIT} (that part after the comma is crucial, here's a hint: erase render_purpose.HUD_ONLY_VIEW from here if you want your alternate F1 HUD only view to not have MFDs on it) 6) add this line if it isn't already there: try_find_assigned_viewport("[indicator name]") make sure that here you replace [indicator name] with the title of the indicator you want to show up on your screen. For example: if I want to add the F-16C Data Entry Display try_find_assigned_viewport("F_16C_DED") <-- make sure whatever is typed inside the quotation marks matches the item for which you enter x,y,height,width in your monitorconfig.lua example: F_16C_DED = { x = 1360, y = 1875, width = 300, height = 135 } <-- in the monitor config.lua if you are trying to add an A-10 screen you might name it A_10C_RWR and make sure your monitorconfig.lua has the line A_10C_RWR = { x = 1360, y = 1875, width = 300, height = 135 } please let me know if this brings good results

is the finished autoexec file supposed to be a .lua?

I ran the clear registry and my X52 started working just fine. It can be found on the Saitek / Logitech support page.

I learned to use JDAMs for loft bombing with pre-planned coordinates. set the mode to auto-loft, 30 degrees, and get up to around 500kts, and pull-up at 5 nm from the target, I hold the flight path marker at the 30 line, and a bomb-fall line with release cue will appear, as well as the words 'in-zone' on the right side of the HUD. It's a press and hold on the pickle and the bomb releases when that cue line meets the FPM.

Hello all, if you have experienced a bug when exporting the F18C_1_DIFF.psd as a .dds to a livery folder in your coremods\f18c folder (the nose and tail sections show up as all black) you can fix this by first exporting the F18C_1_DIFF.psd as a .bmp file and then close your active window, open that F18C_1_DIFF.bmp file in your program again and export it as the .dds file into it's livery folder in your coremods\f18\liveries\f18_hornet file path. It will now show the nose and tail with the livery/skin you designed. I also read at the DCS: Livery Art Group, on Discord, that you can do the thing where you select your main layer, merge all layers, and then right click and select "new from visible" this will make a new layer at the top labeled "new visible" with this selected you can export to .dds into your coremods folder and it will work this saves you a step- skipping the above procedure.

Thanks for your responses I'll look into that