apoll

Tks Harker. Yes, got the 2 as wingman. And reading the phrase list, air defence is a phrase. Could also be aaa or sam. It seems to recognise it correctly, but always, says awaiting further input like it is waiting for further information. Not sure what is wrong. But not useful in current state if wingman won't recognise attack phrases.

Hi. After some advice. I am new to Viacom and I have the pro version. Having trouble with the attack commands: my wingman is not attacking when I say 1, engage air defence targets. When I check in the Voice Attack panel out of the game, it keeps saying: 'Awaiting further input". Not sure what's going on. If I say "1, join up", no problems. But attack commands are always: "Awaiting further input". Can someone help? Thanks. apoll

Sorry for a noob question, but I have the new TM F18 controller on a warthog base. I see it has native integration with the DCS F18 module which I also have. My question is this: does that mean, after I've set up the axes, that the right switch controls will automatically be mapped to the stick according to F18 Sim in the settings? Like what happened with the a10c native mapping to the warthog: the correct button strokes were automatically loaded to the Warthog. Is this the same for the F18 stick when I'm using the F18 module? Or do I have individually map each function to the right button on the stick? Grateful advice and if it IS natively and automatically integrated to the F18 sticks, do I have to do anything other than select F18 Sim in the controller options? Just a bit confused. Thank you. apoll

Wags and ED staff, just wanted to say I thought the update was great: really adds to the immersion and I also see, for me at least, performance is at least on par, if not better after the update. Good job: Infind myself being distracted by the scenery now and has resulted in at least one shoot down, :) Apoll

Thanks RightStuff. Much appreciated. apoll

Just to let you know I managed to get it working. New Output file, new init files and Played around getting the outputs in the correct position. BTW, does anyone have a view on what is the best way to find the correct viewport position WITHOUT having to do it by laborious stop/start, trial and error? Thank you. Apoll

Hello. Coming back to DCS A10C after a long break. Now trying to set up Loz's A10C Helios profile. I'm sure his instructions/files are far out of date for DCS World 2 Alpha Nevada. If I follow his instructions, including using the provided init files and such, will it still work? If not, what Export file should I use and what Init files should I use? Anyone got Loz's profile working for Nevada now? Grateful advice here. Thanks. apoll

F-86

Try Capt Zeen's export lua on his website. I think that was the one. Let me know if still o good and I'll try hard to find the exact one. Apoll http://forums.eagle.ru/showthread.php?t=148534&highlight=export+lua

Ah. Stand by...I'll find it again. apoll

Ok. Thanks v much, Cowboy10uk. Appreciate it. Apoll

Hello. Setting up Cap Loz's Helios profile for DCS A10c. Got the guages working via an export lua someone kindly posted here. Now, want to get the view ports up and running. The monitor config lua I can muck around with, but I've always been confused over what init luas to use. This is important, I think, to match the names of the view ports in the monitor config lua with those in the instruments' games folder. 1) Can I ask what init files people are using? Would someone be kind enough to post an example init lua they have working in Helios in DCS 2? Or point me to where I can get the right init luas for the various instruments (clock, etc)? 2) What is the current naming convention with DCS 2 of the viewports in the monitor config lua that matches the init files? Would someone be kind to flash up their working monitor config lua? Thanks in advance. Apoll

Sure SithSpawn...I get it. And the efforts are appreciated. Just needed to chase out this issue for me, since it is no fun to be crap at flying in a sim you really like. I've done that...and elicited a wide variety of responses, and gleaned some info which I've used to get better. I'm still pretty bad at it...but at least I am trying to really be lighter on the joystick, and sure enough, I was pulling too hard. Comes from all that time on Falcon 4 with its AoA limiter; in that sim, it stopped you from over pulling...in DCS, YOU are the AoA limiter. That's what I've learned... So I'm happy to keep plugging along while the devs refine the flight model. Thanks. Apoll

Well...that started quite a useful discussion, with a whole range of responses, from "We bloody know better than you...so suck it up!" attitude from some of the ED testers...(Hey Viper...just because some of us aren't jet jockeys doesn't mean we have not learnt to fly for real...and know what a nicely turning aircraft feels like...), to really helpful, genuine suggestions for newbys from other testers (thanks Tharos for putting your specs and method where your mouth was...really helped...), to perplexed musings from simmers like myself. Sigh. What I did was take seriously comments about being ham fisted, read a really useful articles from SimHQ archives about how less is more when it comes to DCS modelling of joystick behaviour, and watched a lot of tutorials...and then I just jumped in a flew the sim lots. I turned, turned..and then turned some more. At all different altitudes and speeds...and all the while tried NOT to pull the stick too far back. And...I got better at it!! It still shakes and rattles like an old sow, but it is begrudgingly starting to turn tightly....IF (and note this well fellow simmers having my sort of issue...), you stay around corner speed (I reckon for me that is between 350-400kts)...IF I do not just pull it back into my stomach...and IF I keep an eye on the bandit properly. One of the hardest things to do is to keep your eye on the bandit as he flashed past, and NOT over pull the stick...or over climb on the turn. That's really hard to do...but when I can turn reliably at corner...in a flat plane...and still keep my eyes away from the cockpit visual cues and locked on what the bandit is doing, I reckon I will be a competent pilot of sorts. Can't do it yet...but I'm getting better with practise. The next thing to implement is Tacview...and watch every practice mission afterwards to see what I'm doing wrong...repeatedly...self assess. That's what I've discovered and dong to help myself from all these suggestions. It's still crap above 25k, and I have real issues with the Aim-120 effectiveness (they just don't hit reliably....fired off 4 the other night and STILL the Mig shrugged them off...one after another... Another fun us soon I reckon...c'mon you gun ED testers...the Aim-120 IS porked at the present, isn't it?? Ok..ok..another discussion...)...BUT she is responding...and a lighter touch sure helps. Thanks all who posted sincerely to help. Much appreciated.... Apoll

GGTharos, thanks for posting your detail. I won't bang in about high altitude stuff; as you say, clearly an issue but hopefully being worked on. I'm going to try your approach and speeds etc to practise; see how I go. If you were of a mind, and something that would really help, is for you to post a short vid of you taking on a Flanker/mig from the cockpit perspective at mid altitude level...so I can see your turns and what you do snd the AoA angles involved. I took on a Mig 23 the other day with only guns and to my shame, I just could not turn enough to get on his tail without the aircraft stalling snd shaking. I must be very ham fisted! One thing: what curves are you using on your joystick? I'm using 30 with no deadlines. Sound ok? Apoll