Avatar72

Does anyone know how to complete mission ATO-B-P5.4.miz from Chapter 2. Ive played this over and over and cant finish the darn thing and I'm being forced to go back to Phase 4. I've gone through all three recon points and was given the messages saying they were complete. I also destroyed the primary Abram tanks at the front line and when I return I get a result of 15!!. I have no idea what more I'm suppoised to do here.

No big deal. I think I got the feedback I needed to hear. Looks like flying missions are going to be more work than anticipated. So is it recommended that I scan my flight path, move ahead 3 Km. or so and do it again and again...looking for those hard to find AA defences not found on the overhead map? Sounds like a whipping....

Thanks for hijacking my thread.

It seems every nav point is too dangerous from mission to mission. However, travelling outside the waypoints is just as dangerous. There are are unmarked AA batteries or shoulder mounted missle launchers hiding near tree lines. There's just not enough intel on AA placements on the overhead map.

Question about the 1st Oil campaign phase/mission 3. This is more of a strategy question that can apply to many missions. i've read about the success % given out after missions. i'm just trying to determine how to handle obstacles for missions success. So in this mission, I'm supposed to follow a very narrow flight path to destroy a set of high priority targets. along the way, you pass a heavily defended town that includes at least 3 sam launchers and many more AA threats.. Passing by on the way to the main targets is a BAD idea since you will get shot at often. There's some cover along the way, but you will need to pop out from it to destroy main targets. so leaving the SAMs in tact is not a good idea. On the North side of the town are mountains with low clouds and on the other side are some hills (the cover) with even more non mission critical Launchers to the south. I feel like playing smart and taking out as much Air threat targets as i can before flying by the town, but I end up running out of vikhrs (wingman too) before arriving at the main target. so we cant engage the main target from long range and getting in close is not advised due to more AA threats near the objective. Am I to just suck it up, turn back and rearm or should I just be attempting to find long ways around which is high risk. Do i need to be much more subjective in my targets leaving armored units in tact only destroying specialized air threats. Basicaly, whats the best method of getting through a heavily denfended air threat location with enough weapons to destroy your main target(s). There are some ally tanks on my side, but they are highly outnumbered and dont advance to destroy softter target for me should I destroy enemy tanks.

What was wrong with it? I tried it for the first time last night and there was barely anyone on it. So either its just not popular or its real bad.

I was thinking it might be related to night time displays etc. A mix between explosions, continuous fires, night displays, lights Zooming in and out real close to the Shval so I can make out vehicles... I know the other campaigns have the warning that they arent compatible with Vista. Although people have played them in vista, I'm wondering if there are similar elements to those campaigns that exists in the DUSK mission. I would have no idea what they would be. but the Devs or missions editors might know... I tried the missions again last night and completed it. I didnt even fly back home. I just escaped - quit after misson success for fear of the crash again. I still want to know what could have caused it. My FSX random crashing has turned me off to the game and I dont want the same thing happening for BS.

Here is the crash text # -------------- 20090503-212754 -------------- F:\Eagle Dynamics\Ka-50\bin\stable\WorldGeneral.dll # C0000005 ACCESS_VIOLATION at 02324A0B 01:00033A0B # # EAX = 0017F8C8 # EBX = 00000000 # ECX = 7C782740 # EDX = 1CAC0831 # ESI = 7C782740 # EDI = 00000000 # CS:EIP = 0023:02324A0B # SS:ESP = 002B:0017F898 EBP = 0017F8D4 # DS = 002B ES = 002B FS = 0053 GS = 002B # Flags = 00010202 02324A0B 0017F8D4 0001:00033A0B F:\Eagle Dynamics\Ka-50\bin\stable\WorldGeneral.dll Ordinal999()+34A0B 02324A0B 0017F8D4 0001:00033A0B F:\Eagle Dynamics\Ka-50\bin\stable\WorldGeneral.dll Ordinal999()+34A0B 02324EAC 0017F920 0001:00033EAC F:\Eagle Dynamics\Ka-50\bin\stable\WorldGeneral.dll Ordinal999()+34EAC 0232530B 0017F944 0001:0003430B F:\Eagle Dynamics\Ka-50\bin\stable\WorldGeneral.dll Ordinal999()+3530B

I've been going through the first campaign and everything was find until I got to the mission DUSK. The game crash occurs anytime I'm making an assault on thr enemy base. The sun is going down, lots of fires going off at the base and then boom..crash. Its quite random and nothing I do seems to be the triggering point. I have Vista 64 SP1 w/ 4 GB RAM and two 8800 GT Nvidia cards running in SLI. They Vid cards are on v. 7.15.11.7516 I'm also using a Saitek X52 Pro. I read somewhere that a file directout with X52 Pro could be causing the crashes but is removing it a good idea for users of this joystick. The crash file is attached

I think I got to that point then. I saw the explosion or rather the smoke but I still had no audio cue that it was time to move in. There were some enemy helos in the area and I still didnt move in. Plus the shaded blue area representing the air defences was still very big so again, I didnt move in until about 10 minutes later after getting impatient...I slowly moved up and then my helicopter blew up... :(

I puchased the game a couple of weeks ago, several days after its release. I purchased it at Frys in Plano, Texas. When I bought it, there were about 25 copies on the shelf. Now, over two weeks later, there are about 8 left. So although they dont fly off the shelf like an "A" title will, it seems to be selling well for a flight sim...I guess... For a first release in a series, if the developers were extremely concerned about the product initial release, maybe they should have stated off with a more popular aircraft. Given the games reviews though, it hopefully wont matter.

So, I'm doing the mission On the Other Side which is the 7-9 or so mission from the first campaign. You fly a LONG ways through moutain and a valley where you need to destroy ground vehicles. However, you need to sit at the Ingress Point and wait for the bombers to take out air defences. Well I sat there for nearly 10 minutes after they said they were going in and they said they hit the targe, but there are no other radio messages telling me its safe to go in..so i sat there..and sat there. Is there some sort of triggered event i'm supposed to wait for here. I finally started to move up a bit saying clear of the air to air range (blue shaded area) and then I just go shot out of the sky. By what I have no idea...This sucks because it took me like 40 mins to get there. After I was destroyed I hit F2 to look around and there were some Hinds going up against Ka-50 and some jets/bombers circling the area. There's no audio que or status as to when to start an attack run. any clues?

So, it isnt necessarily where I sit back and fire missles at enemy AA, Tanks etc.? And even if I should, there is no guarantee its line of site to the target? That all being said, then when you get to the Ingress Point, from there, you may have to inspect the area and perhaps find another place to hover attack? It really is just a final waypoint before the target, but one where you slow down from travel and perhaps start turning on your Laser and Arming weapons etc.?

Ok, I know this is going to sound so Rookie despite my years of playing Flight Sims (20+ years) but can someone tell me what the purpose of an Ingress Point is? How do I use it other than another waypoint to the target? It is where I sit my chopper for attack? If so, then I take it I will need to improvise too because when I sat on an IP, I had no sight to the target. Or is it just a waypoint name you give before a target waypoint that has no strategic value? So, i'm losing my understanding of what it is and is used for. Thanks!

I've been flying Sims off and on for over 20 years and Longbow II was definately the best hands down. I miss Skunk Works software company. Needless to say, I look forward to see what DCS can do with the Apache although it will be a while, and it wont even be the Longbow :( I understand why they didnt do the Apache first, if they did, there'd be a lot less buyers for Ka-50 or any other chopper sim. But I'll say this for sure, I miss those Hellfires missles. I cant stand the Ka-50 missles. Watching a Hellfire shoot up and come straight down on those enemy tanks hard is a sight to behold. Oh BTW, +1 for TRACK IR :thumbup:. Mandatory for WWII sims.

Ok, I've never messed with the Saitek Profiler before and I think I did it. I used the Bands like you suggested and its working. I like the other method better since I can get a neutral setting easier but this method will just take some getting used to. After all this though, I should probably just use the 4 way hat for zoom in and out as it accomplishes the same thing. I shouldn't need it since I'm using Track IR but if Track IR ever goes out like it sometimes does then I'm screwd. Thanks for your help. :thumbup: I learned something today about my $$ joystick :D +1 Rep for ya :)

oh wow. I can see the Jitters in the Saitek Control Panel where you set deadzones for the axis controls. They occur in exactly the same places they do in game.

Ok, my last response was a bit confusing. I actually am using a rotary knob. I just called it the slider and I mis spoke. The rotary knob around the red thumb button is the one I'm using. It was a nice convenient location for a widely used feature. Should I maybe use the slider instead and put a dead zone on it? The rotary causes the jitter too even with a small dead zone for it. It makes sense that it could be the Saitek though so I'm totally with you on that regard.

Heh. I guess I should have made that clear. I am actually using the zoom function. I'm using a Saitek 52 pro myself and I have one of the sliders mapped to a Zoom Axis. To be specific, its the turning slider button wrapped around the red thumb button on the collective.

First I want to say I read a few posts about similar issues but none seem to be similar to my own. Whats happening is when my zoom view is neutral (half way), extreme zoom in or extreme zoom out, everything is fine. But when you are in betwee those extremes, the View is jittering back and forth. its like watching your self zoom in and out real quick within one setting. Its not erraic behavior, its just annoying. I'm familiar with some of the other issue that cause extreme tracking problems and Im not having those. The Track IR track modes look good and are behaving. It doesnt seems to be a TRack Ir issue since there are areas within zooming that are just fine. It feels like its an in game issue. I havent experienced this jitter effect in any other game. When zooming in on controls, the back and forth effect makes clicking on control difficult as you can image.