Aeger

Sorry, talking about the actual horizontal steering bar. Thanks.

I've been trying to abide more closely to the ILS glide slope in low visibility landings, but one thing that seems to raise my eyebrow is how the glide slope bar skyrockets after passing the middle marker beacon (on a gradual descension). My question is, is this a realistic characteristic of the ILS system or an improper modeling in DCS? In most of the ILS landing tutorials and flight (commercial) recordings I've seen so far, it seems the pilots can take a smooth gradual decent and ride the glide slope all the way to touch down. Of course if I try to do so in DCS, I'll greatly overshoot the runway due to glide slope instructions to pitch up. Any input appreciated!

@OP Nice to see that this is modeled in the game. JDAM specifications say CEP (circular error probable) of 13 meters but ends up being about 7 meters in practical application. What you're observing sounds normal. For poor weather conditions or obstructions, JDAM's are probably your best bet. Otherwise I'd follow Vitormouraa's advice and go with the LGB's instead. Cheers!

Many thanks for the effort that went into arranging this, creating the recording and notes, and to Olie for volunteering his time to answer our questions!

Yes! Please add me to that list!

YES!! This response made my day! I knew my faith wasn't misplaced! :pilotfly:

Not sure why this is in the Wishlist category... the FLIR is frequently unusable (broken) in many situations. As far as a simulator is concerned, this isn't being simulated very well. While I'm sure people are busy, a "We recognize there's a problem" comment from a dev would go along way.

I have a feeling their plate is really full right now (1.5, 2.0, F-18?) and perhaps they're on vacation. But yeah, critical problem for a critical component of the A-10C module... Someone please acknowledge :cry:

Can we get some official response? Maybe a bug tracking number?

Another example to illustrate the problem... I created a mission and added friendly APC's out in the open, used the world labels to find them on my HUD, and slewed the TGP over a label in order to find one (otherwise, I wouldn't have been able to spot it). Judging by the TGP picture, can you say you would have spotted it? Clearly something isn't working right :( Edit: Good FLIR example (non-violent): [ame] [/ame]

After spending some time with this issue I found if I try playing the game with my TM flight stick disconnected, I can start engines fine. For the sake of pinpointing the problem, can you guys try it as well? Just curious if it's only me or if this indicates some kind of general hardware conflict happening in game.

@OP: Having the same problems... really struggling to differentiate tanks/vehicles from surrounding objects. Attached a picture of a BTR-90 targeted. Thermal signature looks exactly the same as the trees and ground... almost as if I'm just viewing the same image but only in black and white.

Terrific, thanks BimC, that's what I was looking for. Cheers!

Is there a way for me to specifically turn this down without turning down the general volume? The radio volume seems disproportionately loud compared to everything else (communication with ATC hurts my ears tbh). Tried turning down helmet volume to no avail. Oddly enough, I set this volume to 0 and I didn't notice it impacting anything... Using 1.5 currently. Edit: Update Correction, the helmet volume does adjust the radio volume, however the client needs to be restarted for adjustments to take effect.

I've got a thread reporting this issue: http://forums.eagle.ru/showthread.php?t=155338

Hi kk0425, I described this problem in thread http://forums.eagle.ru/showthread.php?t=155338. Edit: I'll try to get a video posted of the issue...

Yep have been doing that. Somehow while hitting TMS up I ended up locking an infrared signature to the left of the tank (the house). Doing that too, just having difficulty verifying that my Mav locked the right target. Maybe I need to get in closer to ensure a successful hit... I think I released from about 6 miles out.

The other day I identified a tank using my TGP (high zoom level) and set it as SPI, slaved my sensors to it, zoomed in with my Maverick (AGM-65D), locked and rifled. Maverick instead flew past the target and struck a house 50ft away... (that house needed a remodel anyway). My question is, is it safe to use these with neutral or friendly elements in the region? How do I determine which little black dot my Maverick has locked? Sometimes they're impossible to see on my MFCD let alone identify... In the past I've tried to lock onto the lead vehicle in a convoy only to hit the ones in the rear. If I just had a missile which could follow laser guidance... then those poor people could have been saved :cry:

- Illumination for buttons on NMSP removed (I can no longer see which one is selected at night) - Detection for initial throttle position broken. Previously, I would have to set my throttles to the start position, then back down to stop, and then start again to start up engines. I was able to get around this issue by selecting "Synchronize Cockpit Controls with HOTAS at Mission Start" under misc options. However, this feature no longer appears to be working and I'm back to the awkward start, stop, start again to try to initiate engine start... (using Thrustmaster Warthog throttle)

Having the exact same issue. ATI 5870 HD, 8 GB memory, Win10. Edit: using DCS 1.5

Try this: Go to Options -> Misc -> Enable "Synchronize Cockpit Controls with HOTAS at Mission Start" Also make sure you don't have any other throttles/sticks connected other than the ones you use for DCS world.

I was having serious issues this morning trying to do a cold start of my A-10C. What really hit me as odd is that this seemed to pop up out of nowhere after starting up successfully hundreds of times prior. I noticed as I moved my TM Warthog throttle off the stop position and forward, that the in-game throttle didn't budge at all. Same issue with both right and left throttles. At first I thought my throttles were broken, however they were working completely fine when starting in the air. Long story short... I enabled the "Synchronize Cockpit Controls with HOTAS at Mission Start" feature in options and it fixed my issue.

Wow, thanks guys for the feedback and wealth of information. Much appreciated. Good community here. Johnny your comment below was spot on. As soon as I set my heading to 301, the localizer bar snapped right into place and aligned with the runway. I'm glad this is resolved, but at the same time somewhat sad that it isn't properly modeled :cry: Hopefully this will get addressed at some point. Cheers all.

Experiencing problems trying to land at Lochini-Tbilisi using ILS... I've confirmed that I have the right ILS frequency (108.90 for runway 31), that my ILS is powered and set on my NMSP, however I cannot get my localizer bar to point me in the direction of the runway, it always seems to be pointing off to the side (which guides me off the path of the runway). The glideslope seems absolutely fine though... Any ideas? Thanks! Attached screenshot as example.

Attached a track as an example. After my first failure, I tried taking over control of my replay and tried different attack methods without success (reducing air speed, pointing the nose upward, etc.). Feels like something is broken... but maybe I'm just something? Vikhr Failure.trk