ctannell

Well there's the report about the transient stuff underlying the dam in the 2.0 specific forum. http://forums.eagle.ru/showthread.php?t=154901 I also put a report in the regular A-10C bug section (as per instructions for module specific issues, although I no longer think this is just related to the hog). http://forums.eagle.ru/showthread.php?t=154630 I now expect these are the same issue and perhaps should be merged once a mod takes a look at this.

I'm pretty sure that the glitch gets triggered as you fly under the dam (or just a bit past the dam). If you follow the route in Vegas tour I expect you'll get it. The landing part (which is the more noticeable part by far) is, I suspect anyway, just the glitch returning to normal.

I had the same issue in the Vegas tour. I've posted a bug report with a track in the flight dynamics bug section of the A-10C. http://forums.eagle.ru/showthread.php?t=154018 It's very strange. I needed to go almost full stick forward despite being perfectly trimmed before until I could get the trim reset again. I think noobsbane was onto something. If you look at the trim setting using the control position window (Rt Ctrl + Enter), before flying under the hoover dam the trim setting is about the big diamonds height above neutral. After the hoover dam at the same speeds the trim ended up around the neutral position as if it was compensating for a nose down force. At flare it's as if the nose down force disappears causing the nose to pop up. You can see that after the go-around caused by the attitude change, the trim gets set to the same position as before the hoover dam.

This thread is just the bug report of the original issue brought up in the regular A-10C general discussion. http://forums.eagle.ru/showthread.php?t=154018 As described in that thread, around the time of flare, the aircraft strongly pitches nose up as if the trim is being reset despite the control position window (Rt Ctrl + Enter) showing no change in trim. The issue is reproducible for me in the Las Vegas tour mission. After the go-around caused by the initial problem, the second landing attempt is normal. Edit: Just to add a later observation: I think noobsbane was onto something. If you look at the trim setting using the control position window (Rt Ctrl + Enter), before flying under the hoover dame the trim setting is about the big diamonds height above neutral. After the hoover dam at the same speeds the trim ended up around the neutral position as if it was compensating for a nose down force. At flare it's as if the nose down force disappears causing the nose to pop up. You can see that after the go-around caused by the attitude change, the trim gets set to the same position as before the hoover dam. Trim_bug.zip

I had the same issue tonight with push 2-1. 10-20 minutes in also. Crashed three times in a row. AMD 280X (latest stable drivers) Intel i5 4670K 64 bit windows 7 X-52 hotas TrackIR 5 # -------------- 20151009-223544 -------------- # C0000005 ACCESS_VIOLATION at DDC19680 00:00000000 00000000 00000000 0000:00000000 DDC19680 001CEF80 0000:00000000 ?setShader@DX11Renderer@RenderAPI@@UEAAHPEAUIShader@2@_K@Z()+60 DF4C1E6C 001CF040 0000:00000000 ?GetLoadPriority@NGModel@model@@UEAAMXZ()+254C DF4C1A4D 001CF070 0000:00000000 ?GetLoadPriority@NGModel@model@@UEAAMXZ()+212D E43440FF 001CF0A0 0000:00000000 ?DrawObjects@DXRenderer@Graphics@@UEAAXPEAPEAVRenderObject@2@I@Z()+6F E130DEEA 001CF0E0 0000:00000000 ?DrawZWrited@RenderParserImpl@@QEAAXXZ()+11A E13100EA 001CF120 0000:00000000 ?isEmpty@RenderParserImpl@@QEAA_NXZ()+1B2A E1329C7C 001CF400 0000:00000000 ?Render@SceneManager_Implement@@UEAAXXZ()+BCC 3F457D04 001CF490 0000:00000000 3F45B44E 001CF4F0 0000:00000000 3F471BE4 001CF520 0000:00000000 3F471B34 001CF550 0000:00000000 3F51B4BC 001CFC00 0000:00000000 3F51D365 001CFC40 0000:00000000 76F05A4D 001CFC70 0000:00000000 BaseThreadInitThunk()+D 7713B831 001CFCC0 0000:00000000 RtlUserThreadStart()+21 Logs.zip

I'm still good for the 30th. edit: Ideally at 1900 Z or before, otherwise I might have to duck out early. Conner

Ah, I think I just ran into this issue as well a couple weeks ago. Instead of registering a button press once, it just keeps going and going for a few times. The issue turned out to be a bug between teamspeak and the X-52 software. Don't worry, there's and easy fix. This post should help: http://forums.eagle.ru/showthread.php?t=115747 The short version is this. In teamspeak, go to Settings > Options > Hoykeys On the bottom right there is a pull down menu labelled 'Default', change it to 'Keyboard & Mouse' and press apply. I hope that helps.

Haha, you mean my autopilots skills were number one :). It was good flying with you MAC, that was my first time in a multiplayer game and it was a blast! And as you said, the 5-6 ship formation at the end was truly awesome, while at the same time a bit hard on the nerves! Thanks Linebacker for putting this all together. The effort was greatly appreciated by many of us. On a lighter note, I was in that fireball on the ramp at mission end after parking lol. Imagine my surprise when one minute my head was down in the pit hitting switches and the next I'm up in smoke. I still have no idea what happened. -Conner

Count me in as well. -Conner

Count me in. Cold please.

This game doesn't really stress the GPU as much as the CPU. To make that statement you would have to look at the load of your GPU in something like GPU-Z while running the game and see if it's close to 100%. Depending on your specs, you're probably bottlenecked by your CPU. That's what edge is going to bring to the table for a lot of people. With multicore support we won't need 6 GHz CPUs! Cheers

DCS UH-1H Huey! Merry Christmas!

Something like: C:\<your install area>\DCS\World\Mods\aircrafts\A-10C\Doc

I saw that a few weeks ago as well and tried it in the sim out of curiosity. I can't remember what alt I was at, but the total fuel flow in the single engine case (after proper trim adjustments) was a bit greater than the dual engine case for a given airspeed (max endurance according to the AoA gauge). I think I completely shut the engine down though, I'm not sure if it would be different at idle.

Rearm always gives default loadout I'm trying to rearm mid-mission (campaign, single player missions) using any of the preprogrammed loadouts in the ground crew menu, but when I select some specific loadout the ground crew keeps giving me the default loadout (the one I started the mission with) regardless of what loadout I select. Does anyone know what I might be missing here? Thanks in advance!