lxsapper

I think you missed the point of the discussion.

Thanks Flagrum! I've moved my questions to http://forums.eagle.ru/showthread.php?t=108945&page=2

Ok I hadn't seen this before and opened another thread (http://forums.eagle.ru/showthread.php?p=1872893#post1872893) but I'm now better informed, after reading this and other similar treads. I still have some questions, in the example Leto gives above for Sukhumi the runway designator is derived from the true heading. I know this is not the case for western airfields, it's the magnetic heading that's used. Is this correct for IRL do Eastern contries airfields use the true heading as base since their instruments show true heading by default? Or has DCS placed all it's airfields wrong having referenced as true heading what should have been a magnetic heading?

I've checked SU-25 kneeboard I belive those charts are old. Initialy some Airfields in DCS did not have headings acording to their real world conterparts and it's been corrected but the charts didn't get updated. In anycase all those headings are magnetic and not 'true'. On a further note the SU-25 aligned on the runway shows the correct heading on it's HSI. Is this an issue not afecting FC3 aircraft only DCS level aircraft?

That may be what the chart is telling but it's not true in game. If you use the ruler tool on the Map you can check the lenght and heading of the runway it's in fact 070 (besides runways headings are magnetic and not true, and if Kobuleti was 064 it should be runway 06 not 07). Also zooming on the map (in the mission editor) on top of the ILS it clearly says 111.50 070 as oposed to say Batumi 110.30 126. However I've now checked and it apears this is not a problem with the A-10C, the UH-1H shows the same heading on the backup compass. So I'm confused now.

So I found what I belive is a but in the A-10C. I found this while doing some ILS/TACAN practice aproaches. The problem seems to have it's heading disaligned by about -5.5º to 6º Degrees. I'm posting a few screenshots to ilustrate the problem. I'll also leave a couple of tracks of an ILS aproach flown in the A-10C and another in the SU-25T for comparison. The shots and tracks were made in Kobuleti, but the problem is not specific to this area. When viewing the material keep in mind that kobuleti runway has a heading of 070º, I've done this testing in Batumi where the runway heading is 126º, results where consistent. So this first image is taken in Kobuleti aligned with runway 07 with a mission set with a takeoff start so the airplane is perfectly aligned with the runway, no problems at all but Pause Mode is still active. As soon as I take it off Pause: So we can better see the problem I adjust my HSI course, first to 070 And then to about 064.5 Notice the magnetic compass on the cockpit frame: Because the problem seems to develop after taking off pause I thought to do a ramp start so I could do a full alignement of the aircraft but the problem persisted: as you can see after rampstart I taxied and aligned the aircraft near perfectly on the runway It's very much the same I'm sory for the bottom part on the screens I have a second monitor set up on the bottom to export the MFCDs I should have croped the shots before uploading them. Also I feel like hitting myself for not doing it during the day, but this was an edit for another mission I was fooling around with and I forgot. A10C ILS.trk SU25T ILS.trk

You are probably doing nothing wrong, you just have to learn how to compensate for what's wrong with the HUD symbology right now. Even in that track I was not able to get my BLUs hanging directly over the target area even once, just close enough they could be effective or partially effective. If no IR targets are found there wont be any detonation; in fact with the 97s no detonations occur, only high speed projectiles beeing shot toward the targets. But to answeer you question more specificaly, you are correct the weapons will not fire and the skeets will disarm and fall on the ground. In the game there will be a big concentration of puffs of grey dust where they fall.

Bugged manual! :D

I have both (with FC3), and I like to take the A-10A for a spin. But I think if you are unsure if you should get it. My two cents are that if it was a DCS level aircraft it would probably be worth it, since it is not if you do not load a TGP on your A-10C and refraim from usinf the TAD you will be limited to much of the A-10A mission profile. There are no other significant diferences between the two aircraft apart from some minor diferences of a few stations loading diferences. If the A was a DCS level aircraft you would have some other things like the weapon control panel, Laser guided bombs with the pave penny, wich is not implemented in the C and is something I would really like to try.

Ok I see it now, schroediis correct the AGM-65Ks have narrow FOV in the C but not the A. The AGM-65Ds are the same in both aircraft. I'm not sure but I think it should be reported as a bug.

Found a solution in another tread and was able to further pinpoint the problem I only deleted the files: autoupdate.settings network.cfg network.vault under users/savedgames/DCS/Config That cleared the problem for me.

I'm having the same issue, mission loads, but load screen does not go away. I can see the game on the edges of the screen (about 1 pixel wide) but that danm loading screen is there. This was trying to host, I'll now try as client.

The A-10A does have the narrow FOV - and = keys (next to backspace) are default to change FOV.

China-Hat Forward short with Mav as SOI...

Made this track using both diving and aiming ahead to achive reasonable sucess. A-10A_CBUs97.trk

With current balistic calculations the Weapon cassings land right on target, but the hanging BLUs are way behind. Try some deliveries with the A-10C to see how diferent the information on your HUD. The C puts you in the correct possition to put the BLUs over the target. The A seems to be using balistics for non fragmentation munitions. I think the trick is really to aim ahead. If you just dive you may minimize the error (distance between the target and your hanging BLUs) putting some of the weapon skeets close enough to engage the target but you are still trusting a wrong balistic calculation.

Don't forget every other atack helicopter in the world is a two seater, one guy to fly one to control and employ weaponary. Flying an helicopter and aiming weapons (other than strafing runs) is just a too great work overload.

Steam starts it's sales same time everywhere.

Aim about 300 - 500 meters in front and you should be getting good results. But yeah it needs fixing.

To say someone is wrong about something, isn't rude like impling someone can't read. Not to mention to then go on and giving them Neg. Rep. Thanks by the way.

I missunderstood you, to be talking about the PAC function itself. No need for your level of response.

Wrong!!! Read the 1.2.6 change log. It's on by default now (permanently). The button on the Cockpit frame stays in the off position and has no impact of the function itself.

In case it isn't clear by now. It's in the flight stick. You CAN'T press it with the mouse in the cockpit. It should be assigned to you HOTAS of Joystick or whatever, or just use the keyboard instead.

I can confirm that issue. As I tested it I found another one I'm not sure is related to the new patch since I'm not used to night operations. But the MFCDs are tottaly unreadeable with night vision when set to NT and are actually much more readable in DAY setting, but even then some elements can't be read.

So What about the old buttons labeled FWD MID AFT? had they no funtion as well?