Aeger

Thanks for the tips. I was able to resolve the issue after selecting "Clear All" for all bindings and rebinding from scratch. I would have thought deleting my config folder would have reset my settings but I guess not! Appreciate the help.

Upon starting a new mission with the C-101CC, the rudder is preset to deflect hard left (whether starting in air or ground). Starting a mission in the air causes an instant spin. Upon touching my rudder pedals (in any direction), the rudder instantly resets. For some reason, disconnecting my Thrustmaster Warthog stick fixes this issue (but obviously I need my stick). Cannot reproduce this issue with any other aircraft (A-10, F5, L-39, etc.) Tried wiping my input configs Tried reinstalling the C-101 module Tried flying with no mappings to my flight stick (makes no difference, the simple detection of the stick seems to trigger this) Tried flying with zero mappings to all axis controls (some signal is still telling the rudder hard left) All axis controls show devices at deadzone DCS ver 2.7.1.7139 Any thoughts or ideas would be appreciated. Thanks!

I've re-enabled VR and full screen mode to see if I can reproduce the issue and I can't :wallbash:

I tried wiping out my options (actually I wiped my profile) and the issue returned. For some reason these "false starts" are not consistent and happen maybe 50% of the time. So far after disabling fullscreen I haven't been able to repro it, however it's odd to me that disabling full screen has no noticeable effect -- I'd assume it'd become windowed, which leaves me to believe something there isn't working? Anyway I've disabled VR as well as I'm not using it. I wish I had more data to provide on this issue.

Same exact issue. I start up DCS, it displays the launcher, then maximizes and goes into a black screen. Happening even after a full reinstall of the game. CPU appears to be doing nothing. It's like the main menu loaded but I can't see it. Version: 2.5.6.47404, Nvidia Drivers 445.87. Attached log. dcs.txt

The Scenery Remove Objects -> Trees no longer works anymore as well.

Took me a lot of troubleshooting back and forth to really understand what's happening. Issue: CCRP in PRS or SGL mode hits targets perfectly. In contrast, bombs released in RPL mode will result in bombs landing extremely short. It seems as if bombs in RPL mode are somehow not pulling elevation data properly from DTSAS. I say this because when I manually enter in my elevation data (switching off of DTS using the data rocker on my UFC) to match what's displayed on my TAD and TGP, the bombs in RPL mode hit perfectly. Version of DCS: 2.5.4.25729 Attached replays as examples. a-10_ccrp_short.trk a-10_ccrp_good.trk a-10_ccrp_good2.trk

I'm still eagerly awaiting an update on this. I still cannot perform a CCRP release in level flight without the massive overshot. Razbam, can you please tell us whether or not this is a known issue? Thanks.

Overshooting with CCRP has been discussed here: https://forums.eagle.ru/showthread.php?t=183010 Appears to be an issue that has already been reported, still hoping for official acknowledgement.

Yeah, I'm definitely not looking for PGM-like accuracy with CCRP (that would be disappointingly unrealistic), but at some point I'd like to see realistic or semi-realistic CEP with MK-82 employment (as opposed to consistently overshooting the target).

I imagine these fixes are probably still pending due to the efforts to get the AV-8B operational (but don't take my word for it).

This is absolutely fantastic... it'll add some great flavor and uniqueness to DCS. I feel like a kid waiting for Christmas all over again...

Great thanks guys, much appreciated!!!

It seems to be, as I cannot bomb otherwise without the bombs overshooting their targets. Basically my point is I cannot employ a payload in the traditional sense of CCRP (at level flight or in a climb) without consistently overshooting my target. I'm just wondering if this is a known issue and/or being looked at. Thanks!

Thanks for the responses guys. Though, my confusion still remains as to why 30 degree dives and 15 degree releases are necessary to hit the target. My understanding of CCRP (albeit basic) is that you should be able to release in level fight and even in positive climb (e.g. even in toss bombing scenarios). https://en.wikipedia.org/wiki/Toss_bombing Isn't the TAS supposed to use radar ranging to determine the slant range to the target and, now that you have distance, using velocity the ballistic computer can calculate the release point (e.g. distance/speed = time, in addition to taking bomb weight/dynamics into account)? I'm almost wondering if the TAS isn't catching the terrain accurately at lower angles of approach, but this is just my guess. Edit: just for fun, a video of an A-10 using CCRP to lob a rocket to the target:

Following the instructions of the manual (designating the target at no greater than 15 degrees and releasing in level flight), my MK-82's are way overshooting their targets. I've tried even placing the CCRP pipper a little short of the target and reducing speed without much improvement... Apparently designating the target with a much steeper dive angle and releasing in a partial dive (10-15) appears to be helping my issue with MK-82's overshooting, but I feel like this is compensation that shouldn't be necessary for CCRP delivery... See attached track for demonstration of the original issue (assuming I'm following procedures correctly). m2000_mk82_2.trk

Thanks for the reply some1. Strange, given that I have full cloud cover (density set to 10). I guess clouds don't obscure moonlight, unless the brightness/color calibration for my monitor is off...

I noticed midnight didn't feel like light midnight, i.e. I could still see as everything if it were daytime. Then I switched the year of my mission from 2012 to 2011... and it finally looked like night time. Able to repro. Quite weird tbh. First two pics are with the year set to 2012, last one is 2011.

When checking to see if GROUP X is "All of group in zone" and GROUP X dies before reaching the zone, this condition immediately becomes TRUE. This should probably be false as the group is dead and therefore didn't make it to the zone. Created and attached a basic mission demonstrating this. Thanks! GroupInZone.miz

Lately I've noticed that the impact timer on my TGP seems off. Ex: after Mav rifle, it counts down and eventually reaches 0, however the impact doesn't occur until 5 seconds later. Additionally, I believe I've seen this go both ways, where the impact happens before the timer is done counting down. Am I missing some data input that would make this more accurate? Thanks!

Sometimes I get all the way up to where JTAC says "Read back correct," but I don't receive any data through my SADL. I expect "Standby Data" as he normal does but he's been frequently skipping that part and going straight to "Report IP INBOUND." In addition, it seems my JTAC has a hard time hearing. He says "Advise when ready for 9-line" and I respond with "Ready to copy remarks" and nothing happens... however if I do it repeatedly I will usually receive an answer and the process will resume. Am I doing something wrong here? Thanks.

Looks like this is potential related to http://forums.eagle.ru/showthread.php?t=151850

Having trouble with getting Mi-24's (armed with S-8KOM) to engage armor (one T-72B in this case). They do an initial attack run but then spend maybe 80-90% of their time performing evasive maneuvers. During some of their attack runs (maybe 25% of the time), they'll fire their rockets into the air (not aimed at the ground). Sometimes I noticed after a few attack runs they'll just give up and fly to the corner of the map without having dispensed all their munitions. I created and attached a mission as an example. Both "Search Then Engage in Zone" and "Engage Group" seem to produce the same results. Thanks. Mi24_Ground_Attack.miz

I believe this issue was fixed and then reintroduced with ver 1.5.2.48162.126 (to the best of my knowledge anyway) http://forums.eagle.ru/showthread.php?t=155338

Thanks for all the input guys. While I've done landings hundreds of times (apparently incorrectly), switching my focus on using speed to control my descent instead of pitch seems to be helping by a wide margin. I'm not feeling that disconnect/awkwardness I had previously with following the ILS glide slope bar. Much appreciated! :thumbup: