Ramses823

Come to think of it I have been flying my missions off of a mission template where I basically have a A-10 that I consistently use that way I don't have to set up the ARC-210 comms everytime I build a new mission I'm going to delete the A-10 from the mission template and I'll place another one down and see I'll see if it fixes the issue...

Ok I will post a track the next time it happens...

I actually do. The pitch up issue has been around for a while but it's always been very infrequent to the point to where it isn't a issue but it has always happened very randomly I mean you could do numerous flights and not even have it appear but it seems to be happening more frequently since the update. I pretty much fly the A-10 5 days a week and before the update I almost never ran into it but since the update it has become rather frequent, I'll come out of a overhead break on downwind trimming like crazy to prevent the nose from pitching down then come off the perch and as I reach the threshold I'll cut the power and begin a flair then it's like all the trim I put in suddenly catches up then the nose wants to shoot for the sky and it's go around time, a interesting twist is once you execute a go around everything is fine like I've never went for a go around and then had it happen again...

There seems to be a strange issue what I can only describe as a heavy random drop in trim that has come up since the update and I don't think I will be able to easily come up with a track as it happened during a two hour mission on the NTTR map, so I will try my best to describe exactly what happened. I was on the NTTR map doing a series of 30 degree dive bombs runs with BDU-50s I had 4 X BDU-50 and dropped a single BDU-50 at 30 degrees on each pass.I had no issue whatsoever with the dive bomb passes but once I switched to 30 degree high angle strafe passes the issue came up randomly, so my first few passes no problem then on maby my 6th strafe pass I have the target at my 10 o'clock and as I'm on my base leg just before I roll in I give the jet three clicks of nose down trim which is my normal procedure basically one click of trim for every ten degrees of dive angle so in this case I'm doing 30 degree strafe passes so 3 clicks nose down trim; so I roll in with the sight just short of the target then I let it track up to the target and once the piper is on target I engage the pac and fire at 1.2 slant range then as I begin my 4 G climbing safe escape to 30 degrees I get my nose halfway up and then the nose just stops so I pull all the way back on the stick to continue climbing to prevent myself from hitting the ground, now this is strange behavior because normally pulling all the way back on the stick would result in a serious over G . The maximum speed for the A-10 is 450 KIAS and the fastest I got it in the dive was no more than maby 390 KIAS so I didn't overspeed the aircraft. Also after I recovered from the dive I had to add a considerable amount of nose up trim I also checked to make sure I didn't have any keybind issues I'd say the biggest clue I have at this point is there is a random drop in aircraft trim as I'm coming off target for no reason I don't know maybe it has something to do with the pac also I'm only adding 3 clicks of nose down trim just before I roll in so I'm not adding excessive nose down trim for a 30° wire at this point I've got close to 1000hrs in the A-10 so I've done countless strafe passes and have never experienced this. Unfortunately because it is completely random and when creating a fast mission it doesn't happen I'm unable to produce a track file which is very unfortunate because that makes it very difficult for the developers to narrow down the issue. Hopefully my description has been detailed enough to point in the direction of what may be going on.... as a side note the temperature was 8° C with the winds at 7 knots ground level and turbulence was set to 3...

As far as I know the engine preformance is realistically modeled, you will hear stories of real A-10 pilots saying they wish the airplane had more power. The biggest thing is to use realistic loadouts with the A-10, there are a ton of pictures online with combat loadouts that they use in real life and for new players you have to understand where the aircraft preformance is at its best which is from 15,000ft on down if you try to load the A-10 with 6 Maverics and 6 GBU-12s and fly in at 20,000ft she's going to be a absolute pig.

82 and playing DCS, I'm in my fourties. I want to be like you when I grow up

Honestly ED should add his mod into the base game, his work with the weather effects is top notch. I can look at the real world weather for a particular area and just about create those conditions for my missions...

Thats the post I was referencing. I'm, sure the ED team has their hands full with the new maps and everything but this issue needs a little light shined on it so it can be addressed.

There seems to an issue with the start cycle in colder weather. I have been flying the F-16 for the past few months, but I have been back in the A-10 for the past two weeks or so. I have well over 800 hours in the A-10 so I'm very familiar with the start cycle. now I remember reading in a post at some point someone saying something about the start cycle in the A-10 and cold weather. I was messing with the F-16 at the time, so I didn't pay it much attention however, I just did a mission with the weather at 3.2 C and I motored the left engine then once over 20 percent rpm I brought the left throttle over the hump then set the left start switch back to norm and she started up no problem well I'm waiting for the start cycle light to go out on the caution panel and no dice it stays on. So I try to moter the right engine with the right engine start switch and nothing. So out of frustration after trying some random combination switches and playing with the right throttle I get the right engine up definitely not a by the book start up... So I go back in the mission editor and set the temp to 8 degrees c and jumped back in the pit no problem she started up smooth as silk....

They Just fixed it on Steam you should be good now...

Thanks

I Just finished the integrity check, and it still says it's not Authorized. I'm going to make a support ticket.

Ok I'll try to Verify the integrity of the game files in steam and see what happens.

I double checked and Iraq is the only map that isn't working.

dcs.log Here is the Log from a launch that I just did. I checked my system time, and it is correct. I don't allow my antivirus to scan my drives at all because I know a lot of people have had issues with Antivirus software and DCS. I have a lot of DCS Maps and Iraq is the only one that this is happening with...

I posted this on steam but I'm Posting this on here as well.... After downloading the Iraq map when I try to launch DCS through steam it says "Authorization is valid for 2d 23h and 59m" then right below that it says "the following DLCs are not Authorized and will be disabled Iraq" . Although it says it will be disabled in two days once DCS is launched Iraq doesn't show up at all. I'm at a loss as to what to do.

I'm also experiencing the same issue with the landing gear down as I come in to land the aircraft is very wobbly...

Hey thanks for the update

Thanks you're mod has been a game changer

It just hangs on the loading screen when I try to open the mission editor

Sadly it stopped working for me as well with this update...

I was about to do a report on this myself, good thing that I checked to see if anyone else was having the same issue....

I have noticed since the update if I press TMS right long to switch the radar from RWS to TWS the radar will switch no problem however once I am in TWS if I then try to switch to RWS from TWS by pressing TMS right long the Radar will not switch to RWS but if I press TMS aft then the Radar will switch to RWS from TWS and I also notice Spotlight search won't work in TWS... Radar issue.trk

Hey ED you guys have been doing some great work but you got to get native support for Tobii. Everyone isn't super computer savvy and a update shouldn't be causing issues like this...