DmitriKozlowsky

Khasab ILS inaccurate Why is ILS, on A-10C II, so inaccurate, on this field? I may be a little low, but look at localizer and glideslope bars. Highly off. If I wa sin Cat II or Cat III IFR ILS conditions, and relying on ILS, I would crash to the side of the runway.

On ground, with canopy open, any radio can be used to communicate with ground crew.

Cockpit canopy should be open. There may also be intercom option. In RL, at least from watching exercises, A-10 pilots communicate with crew chies via cable, but canopy open. Chocks are pulled , and aircraft rools. Canopy is closed and ejection safety is armed only when aircraft has cleared enclosure roof.

That moment that I realize that I am really really good with A-10CII. As long as noone is shooting at me, and I can see the ground 10 miles in front of me.

Sitting on a lit tarmac at night, the tarmac is lit but aircraft it pitch black silhouethe. Looking at runway at night on approach. Zoom view and runway lights are visible through HUD. Zoom out, and runway lights fade out, leaving me staring into pitch black, on final mile or so from threshhold. Its disorienting and confusing. Almost every vehicle , except SCUD, when viewed through HUD and NVG at night is 100% invisible from 700 meters. Completely lost in noise of NVG. During daytime, vehicles are pixels, totally lost in texture, until 500 meters or closer, when pipper adjustment via flightpath is impossible. Some damn fine camo, but IMHO, the scaling is problematic. I am suspicious sort, and I suspect ED is using dynamic opacity where a 3d object at distance has zero opacity that fades in as distance closes. I'd be doing CCIP in day time, at 5000 feet AGL, nothing, passing through 3500 feet AGL, nothing, 2500 maybe something, can't tell, 1500-1800 a slightly darker pixel, but too late to adjust. Brake off and reattack.

I beg to differ on nightime lighting. In fact, DCS nighttime, is unrealistically pitch black. Granted this is not a realtime ray tracing global illumination setup, but some ambience is needed. I also have a problem with scaling of ground object. From 800 meters away, a truck is pixel or smaller, at normal zoom. The TGP diamond is a major problem for me for strafing. When ground target is a pixel and is lost in noise of ground, and diamond is not drawn inside gun retticle, bringing pipper onto target, when the target is invisible is a problem. I would fly gun piper onto diamond on HUD, and as soon as pipper intersects with diamond, the diamond disappears, and squinting into pipper trying to identify the pixel that is target, and I see NOTHING! Plus the frustrating behavior of TPOD of z-rolling and slewing off target, by itself, at end of roll in. Happens way too often, if I overfly target, I do a 180 to reattack. TGP slews and reaquires target, and as soon as I am wings level, the pod slews away, goes off target in some random direction, some random amount. At night, or small target, reaquistion is impossible in time.

Yep! Thank you. Got that mapped nicely. My personal preference is to have TPOD's default mode being boresight. Right now its auto-slew to waypoint or SPI. I don't know if real A-10C has a FLIR HUD projection, like in Harrier and F-15E, but it would be more usefull then NVG. NVG and A-10CII MFD don't play nice with each other. Even at dimmest, MFD appear too bright in NVG, and having to muck around with NVG brightness, MFD bright/cont, while flying, navigating, and fighting in pitch dark is too much to ask.

Motorcycle insurgent duo team One rides, the passenger rider is armed with RPG or AK

One function, that I miss from old v1 A-10C is snowplowing centering of TPOD. That function that did that v1 of A-10C now toggles it between Laser spor search or autopoint TPOD at sensor point of interest. TO quickly snowplow TPOD, I have to STBY then put it back in AG. Its a hassle, and slew rate of TPOD, even when set to 1 in Special Options is too slow.

2.9.11.4686 MYT F-5E legacy FPS dropped to single digits in all theaters Something broke F-5E

NVG HUD ground targets at night. I see nothing I don't quite get what I am suppoused to look for. I don't see anything. In flight in motion, the pixel or subpixel sized ground targets are totally lost in noise. Whats the trick here?

How would you describe it?

I am having serious trouble locking Mav H onto moving armor. It won't lock, or won't hold it. Is there a new'er trick with all these updates.

Are AI F-5E3 now remastered or legacy?

I know , now, what caused it. Controls for controlling HMQS brighness, are shared with another function. When SOI is HMQS, those other functions become brighness controls.

NATO Mig-15 naming is old British term for discarded butt of smoked cigarrete. Unfourtunately it shares spelling and pronounciation for offnsive pejorative for male LGBT member. I served in US. Army (13A) in 1990's. I am a product of Army's then inclusity and diversity training as ordered by then POTUS Bill Jefferson Clinton.

Uhmmmm........ 'coolie' is pejorative name for China hat. From American Old West term for Chinese labor working on Transcontinental Railroad. Its UNPC nowadays and is consedered offensive R-worded. You are welcome.

You are correct. Slight error on my part. I confused DMS with China Hat. I do have it mapped correctly on my HOTAS. I've been away from A-10CII for some time.

I know DMS switches. However I never had Scorpion go dim and then turn OFF by itself. I still don't know what caused it. DMS down is HMQS as SOI.

HMQS Scorpion overlay inexplicably went dim then off despite being turned ON. Midmission What controls brightness of Scorpion. Becouse I don't have it mapped, and AFAIK , I did not change it knowingly.

Battle damage to canopy not reflected in pit view I was not even aware that I was hit in canopy until after recovery. Neither was I aware that I was hit during engagement.

I simutaneously or within few seconds of each other, receive CLEARED FOR LANDING and GO AROUND RUNWAY OCCUPIED. Even after 10 years with A-10C its still confusing. Why would ATC be like this at Nellis?

Is there HMQS sight alignment as part of start up in A-10CII? I don't recall it on 'old' startup check list.

I do have that file. My DCS went bad in an instant out of the blue.

Damn! Even running DCS_updater.exe genrates the same error. Straight out of the blue.