miaig

Yes, I am on 2.5.4 OB so that explains the ATC problem. Regarding the wingman, I'll try next mission to do that although I think he is supposed to be the instructor :)

Ok, so I did a few more tests and I am at 2290 feet at around 5.5 NM from waypoint 4 (located on the airport) when I am given the "terminate terminate terminate" message. I am way above the glidescope at this point. Even the instructor tells me I am above the glidescope. So it seems that the flag that disables the altitude check does not get triggered for some reason. Another thing is that I am never cleared by ATC to land. I am asking ATC for "Inbound", given a vector, and then I never hear from them again. The only options in the ATC menu are "Abort Inbound" and "Request Azimuth". These options only change the moment I touch down on the runway when I get a "Request takeoff" option. All these are from the practice mission rather than from the mission itself. It is much quicker to just do the practice because of the airstart. Thanks.

Hi Sabre, Just to let you know I managed to go past the mission. I didn't try to see if getting lower below 7 nm works or not (I started descending much closer to the runway than that) because I really wanted to finish the mission. I will try to play again the training mission however and let you know what I find, but it might take a while since I don't have much time lately :( Thanks!

Thanks Sabre, I will try it again soon and let you know.

Hi, I am going though the A10 Basic Training Qualification campaign and I am currently at the BFT09 Practice Instrument Approach and Landing mission. I am given instruction to go to Batumi and enter pattern altitude. If afterwards I am trying to follow the ILS indications I am told to abort the mission because I am too low. I have tried to stay at pattern altitude but if I do I am yelled at because I am above the glide scope. If I try to descend immediately after this, I am told again to abort because I am too low. The way to go past this problem is to wait a bit more after I am being told I am above the glide scope and then try to drop as fast as possible in order to land, which is pretty difficult given the fact that it's night, there is a strong crosswind and not much visibility. It seems to me that the condition that checks if I am at pattern altitude should be terminated much earlier than it is. Another problem that I have seen during the last missions is that my wing man is trying to land in the same time as I am so he crashes into me unless I am constantly watching for him and try to avoid him. Thanks.

Great news everybody, works now :thumbup:

I've just tried my coupon but no joy :huh: Anybody had any luck so far?

I can confirm that choosing "3 screen" or "3 screen + MFCD" will result in a crash. "1 screen" works fine. My desktop resolution is 7680x1600. Bezel correction never worked for me in 1.5 so I haven't tried it. EDIT: Forgot to mention, I have the screens in Nvidia Surround.

Game started crashing after the today's update for me too. Mods, no mods, nothing seem to matter, when the loading bar reaches 100% the game crashes. I've attached my logs. Edit: Reverting to 1.5.1.46722.87 works fine. crash.rar

Thanks for the reply Snacko. So it seems I will be needing two 980 since 8000x1600 is roughly double the number the pixels than 5760x1080. I was hoping one will be enough :(

Hi Snacko, How is the new 980? What framerates do you get and what's the current bottleneck now, the cpu, the gpu, or the gpu ram size? I am asking these questions because I have 3 2560x1600 monitors and a 660ti. My current resolution is 4010x800 and I was wondering if a single 980 would be enough to run DCS full resolution. Thanks

Hello, I've created an Android app to display the bf109 and fw190 instruments on a tablet. The app works for IL2-Clod as well (for the bf109). It is based on Leon's Portman P51 instruments app (see this thread: http://forums.eagle.ru/showthread.php?t=97890) You can get the app here: https://play.google.com/store/apps/details?id=com.mihaig.bf109 Enjoy and let me know if you have problems.

In my case this was happening because the airplane was becoming airborne while I was still holding the stick back. It was very puzzling because when the wing was dropping, It looked to me as the plane was still on the ground, but it was not. I started lifting the tail much faster and the wing didn't drop anymore.

Thanks Teo, I'll try it out.

Hi, Is there a way to determine which aircraft is the player using without using the two functions LoGetObjectById and LoGetPlayerPlaneId? The reason for asking this is that according with this post: http://forums.eagle.ru/showthread.php?t=14323 LoGetObjectById does not work if EnableExportScript is set to false. Thanks !

Thanks for the tip Zaelu, I'll try it out.

Thanks for the answer David. It's the Allow360rotation=false line that needs to be removed.

It's not a limitation of TrackIR, it's each specific airplane that does that (Huey doesn't have that for example). It is controlled from somewhere in Views.lua, under ViewSettings, Cockpit.

I thought about that but the pitot heat was on (the mission starts in the air with the pitot heat already on)

Hmm, I'll try to make a recording if it happens again.

Hi, I'm using TrackIr and whenever I am looking left or right the maximum head movement is 180 degrees, which is fine. When looking up however, the movement is limited to 90 degrees. I presume this is done in order to be realistic, but I find it annoying because when I get my lift vector on somebody and I look up, the moment they pass my wingline I end up losing them because of this limitation. Does anybody know where in the lua files can I change this to make it 180 degrees?

Hi, I was playing the Dora campaign and I noticed that if I get into a stall followed by a spin, by the time I recover from spinning (so nose still pointing down, but not spinning anymore) the speed indicates 0. Initially I thought maybe it's 800km/h not 0, but the strange thing is that when I pull the nose back up to get into a level attitude the speed indicator stays at 0 for a while and then it starts _increasing_ up till about 300-400 and that doesn't make any sense. Anyone knows why does this happen? It happened to me at least twice during the campaign (the dog fighting missions) but I didn't try to replicate it.

If you want to make this mission easier, wait until the trucks are on the bridge or they just finished crossing it (they will stop because the road finishes as well). There will be only one stationary aaa firing at you if you do that, the one that's close to the bridge. You don't have to kill any aaa if let them reach that point. Other than that, just swerve, try to make yourself unpredictable.

I like that checklist :)

Yes, I do switch between the tanks but I was wondering if it's realistic or is made like that just to force you to land quicker.