nemises

Modern plane?..the A10?? ;) Avionics are pretty new, but the fuel / hydrolihs / electrics is allll 1960's tech afaik

Hi JS, which training mission? Thanks

why would you put A10s and a WWII figher in the same mission?.. however, if it was WWII figher vs WWII figher in DCS environement (Crimea or Nevada or wherever), sign me up!....especially if it is the first of a new line of classic Addons. Ultimately, ED gives us the tools, but WE create the scenario in the mission editor..

Can you grab a screenshot + co-ordinates, or even better a short track ?

hmm...pretty sure you get get lat/long from anything you target in the shark...you can then just pass on the l/l to the A10 vocally *sniped* good answer Chromium

I don't think so...both call DCS.exe

+/- 128k per client both ways (64k is probably fine) There are some very informative threads / posts around from server admins with exact figures and current setups.. Look for posts by Polecat, I know he's posted the 104th dedicated server setup on several occasions (including bandwidth used) Luck!

yes

the blade tips falling off is caused by top top rotor intersecting with the bottom rotor. At increased speed, the flex (or flap) of the blades becomes dangerous, hence why there is a speed warning.

depends on the mission design. The mission designer can attribute any trigger to add or subtract "points"..so he/she might design it to only be 80% , with the final 20% triggered when you land at base(for eg) In the case of a campaign mission, if you are above 50% you can quit without penalty...so if you check the mission score, and it is at 100% , you can safely quit if you choose.

Just be a little weary, there has been some (anecdotal) evidence that some of the longer campaign missions crashing at about an hour of flight time (or there abouts) if the mission is modified to Start from Ramp. I'm not saying this will necessarily happen, but if you suddenly start getting in game crashes in the campaign missions, this may be why . I say it's anecdotal because it happens to me and at least one other user BUT not to many others. There may be many other factors involved also (specific hardware configuration etc..)...but just something to look out for if it happens to you.

HAppy Birthday Paul!

looks amazing though....really really immersive!

yes, low light = no contrast for the Shkval to differentiate and make a lock..Shkcal is day time only (not sure wt what time it is too dark, but sometime around sunset, or "dusk" as it's called soemtimes ;)) You can still Launch vikhrs without a Shkval lock though (though if the target it moving it's hard)...you may need to select "manual" launch mode and make sure the parameters are met manually. *edit* sniped

hehe...just to be clear, I only know a TINY amount more than everyone in general, just enough to know lots is happening without being privy to details, so sorry, no happy endings for me! (Heya Mick! :)

lots going on , but none of which can be discussed...sorry.

(the kind of lord under an NDA :P)

Hi Lonefox, You should loiter at the IP (or before) until you have a good picture of the target. Use the FAC's also, they are there to designate the targets for you so you don't haveto be as heads-down. Don't be in a rush... as far as I know there are no TOT dependencies..... the flight plans are usually laid out to ingress / egress safely through clear corridors so stick to them UNTIL you hit the IP, but from the IP and beyond, they are more indicative (unless the target area is pre-briefed). Say for eg, in Georgian hammer 1-1-0 (assuming that's the campaign you are talking about), take off and fly the plan to your IP (or even stay south of the IP)...set up a holding pattern and orbit while you contact the JTAC/FAC , (hint , use ALT autopilot whilst in a 45deg bank or so)...once you have a target, scan the target area with the TGP to get a picture of the layout of the target(s). Depending on the weapon's you will use and the likely threats in the area, plan your ingress...perhaps set a few mark points and use those as an impromptu flight plan for your attack. Once you have a plan, and youre set up (Maverick's are powered up/cooled , DSMS profiles are set etc), THEN roll in for your attack. ...it's unlike , say for eg in Falcon4:AF , where you have to be over a target at a certain time and sometimes the pilot workload is too heavy to get your targets and weapons set up...this is more dynamic. Unless there is a briefed time limit , or something bad is about to happen (such as the Tanks you are supposed to be protecting are about to get jumped by new group of T72's) , then you usually have plenty of time to assess the situation from long range with your TGP before rolling in guns blazing

I'm happy with X52, though the Slider axis is useless...otherwise, stick accuracy and buttons seems fine. Need to do quite a lot of "shift" button (I assign mine to the pinkie button) work to get all the HOTAS functions on there, but...well...if price is an issue, I rekon X52 is the way to go. Same goes for the Saitek pedals.. ..TrackIr is vital..

most of the servers , if not passworded, you would be more than welcome on. Many servers will have a Teamspeak server associated (details are usually in the message of the day on join). I'd say jump into a servers lobby, join the teamspeak, and just start chatting to people / askking whats going on. Before you know it, you'll be teamed up with a group of folks hitting an objective and loving every moment of it. Don't worry too too much about proper brevity etc.. you can pick that up as you go along if you don't already know it....just don't blather on about random outside-of-game stuff and you should be fine. ....most servers have a policy of no politics tho ;)..its better for everyone

sure, bullseye is easy in the KA50.. As above, designate a steerpoint as Bullseye (arbitrary, as long as everyone is using the same point). Either your Abris or the PVI to that point, and hey presto... Instant bearing and range info that can very easily (in the case of the PVI) be converted into bullseye co-ords (clue, use the ADI / reciprocal of heading bug + range reading) also, search for Aero's "Bullseye" tutorial on youtube...its for FC2/LOCKON, but is exactly the same in DCS (except for teh names of the instruments involved) never mind, I did it for you :):

standoff range for sure if it can shoot back

I believe it would be redoing the geometry (or at least re-working the old geometry)... more detail would be required to be able to draw shadows across large faces without strange warping. New Shaders as well. the new format (.edm) may not be directly comparable to the old .lom with the toolset (used to be 3dsMax plugins, not sure what tools are used to generate a .edm), which would mean remodeling, re mapping and re-testing. So, a fair bit of work..who knows though, it could happen in theory one day?

if you had another joystick, or analogue controller around you could use that as an Axis for rudders? ...if you removed the spring from a cheapo joystick you could set up soemthing nice with a bit of glue and a piece of wood :)

sounds a bit worrying...good luck!