kerlix

I've had this happen numerous times. It's actually quite funny to watch. It kept happening so one day I decided to actual look at him and see what was going on. It turns out that he'll just go for a full-thrust takeoff right there on the apron. He'll either slam into a building or go blasting through some trees, tearing himself apart in the process.

I think everyone will be satisfied with what he's putting together. ;) :music_whistling:

I always use the "Sound as if wearing helmet" option. Or something like that. More or less. I find it lowers external sounds quite nicely. And if that fails, close the canopy! Just joking, btw.

Off the top of my head only one thing really stands out. I have no idea what mission it was, so I'm sorry about that. But during the briefing I was told I was going to be leading "Dodge", but once in-mission, I was actually "Enfield". Or possibly the reverse. That was the only thing I noticed that sticks out. The voiceovers were excellent. It brought in an immersion factor that I haven't seen before. I know in one mission once I received the MGRS and the subtitles went away, the coordinates appeared again on the right side and stuck around for a minute. It gave me a chance to write them down. It may have been the first mission where such coordinates were given and that's why. That was basically what prompted me to create my own custom mission cards to keep next to me, because if you miss the call out, you've missed it. Also, in the mission where you have to wait for the (German?) intelligence officer to reach "Sweet Spot", in the briefing it says to contact JTAC to get the coordinates of a roadblock at the beginning of a valley pass. For me at least, no matter how many times I contacted JTAC, I would get an "All clear, free to depart" and it left me to go searching. I didn't pick up on where it was at until I dipped a little lower and started watching tracers leave scorch marks on my nose. After that I was on a mission of vengeance and basically killed everything with a weapon in sight (within the stated ROE and concept). I was never a fan of night missions, especially with a cloud layer because the TGP couldn't see the Hindenburg burning once you're at altitude, in or above the clouds and out of MANPAD range. But looking back, they were fun. Frustrating, but fun. As for MP, I've only played SP. Even though I have thousands of hours and years of sim time, including a few hundred on VATSIM (FSX), the thought of screwing up procedures/military jargon/etc. in front of experienced players makes me hesitant. However, a mission where one player would basically call the shots and call in other CAS and bombers (think SU-25) would be a lot of fun. Have one or two (or more) other players anchor about 10-15 miles out, wait for the lead to spot targets, mark them, and then call the others in for a hell-on-earth bombing run followed by a 2nd flight to swoop in and add to the decimation would be a fun mission to fly. Throw in AAA, MANPADS, etc. and it could get interesting real quick. Anyways, I know that probably doesn't apply to anything in the campaign as of now (save one mission) but maybe something to think about for your future projects. I'm sure you could take that idea and improve on it. I don't doubt you skills. I'm just upset I'm gonna have to wait another 10-12 months for your next campaign haha. Unfortunately, we're in desperate need of more creators like yourself.

I'm currently at the point of completing what I "think" is the final mission. Although I'm not sure. Basically where it's time to get low while in the soup among other things and do some serious damage to the enemy. I forget the mission name at the moment, but baltic_dragon, I hope you know which one I mean. I'm trying not to give away any spoilers to those that haven't reached it yet. If you know which one I'm talking about, you can understand my hesitation haha. It sounds insanely fun, but insanely insane. This campaign has been great from the start. One thing I love (and hate) are those MANPADS or Stingers that come flying up at you, even when at 15-16k ft. I just hope to be looking in the right direction (steep bank, looking down) when that trail comes up. I've been bitten more than once. Or doing something dumb like flying down into a valley to use a gun run or rockets on some troops without realizing there's some AAA on the side of the valley and taking hits from what is probably 300 feet away haha. On that note, it's not related to the campaign, but that scenario did happen to me once and just before I lost control and plowed into the other side of the valley at an incredibly strange orientation (I thought I could bring it back up for a moment) I heard Betty screaming "SPEED-BRAKE, SPEED-BRAKE!" at me. I know I had lost hydraulics on both sides (lucky me.). Did that just mean that my speedbrakes were opening on their own? I'm just curious.

I mentioned in another post concerning this campaign that it "forced" me to learn things that I had never really used before. Even something as basic as Bullseye Offsets. When I got my first MGRS coordinates, my brain basically stuttered for about 20 seconds. I ended up quitting the mission and actually watching that exact video on YT. It turns out that after you enter the MGRS coordinates more than twice, it becomes 2nd nature. I created a document in Word that basically has spaces for me to fill out into on 6 different flights (Name/Type), along with their frequencies. Then a section for 3 JTAC coordinates so I could right them down as I was receiving them. And finally a small section for weather, mission concept and ROE. I converted it to PDF (because I think it looks nicer. It might just be my imagination.) and then printed out a bunch of copies. Between that video and the sheets I made, it made everything a lot easier. And learning how to input MGRS and LAT/LON coordinates may seem daunting at first, but it actually isn't as bad as it seems. I think as you progress, you'll find this campaign makes you a much better A-10 pilot. In a lot of ways. Too numerous to mention here without going even further off topic.

I'm having trouble on "Scramble!" right now. I'm not sure if I'm NOT supposed to wait for the INS to align itself. I've been waiting the full 4 minutes and the second I start rolling, I take a mortar shell. I guess I'll try it without alignment since there aren't any waypoints anyways. But without it, I won't have EAC. Which will make the guns (only) runs interesting.

I'm still working with Win7 if it helps at all. I'll try other suggestions this afternoon and see how it goes. Half day at work today, so the other half will most likely be filled with the A-10C.

Ha, I try to minimize the changes made to the default loadout and keep it realistic without just going crazy with 6 Mav's, 6 LGB's, and a CLU-103 with 50% fuel just to get off the ground in time. Thanks for the quick response. Also, excellent campaign. It's challenging and incredibly fun. It's also forced me to learn how to do things I've never done before, like entering coordinates, bulleye offsets, etc. I think it's great.

I've never done a MP mission before. I just feel inadequate in the terminology department. Although I've flown online many, many times within FSX I just feel the military aspect of it would leave me looking stupid and not so fun to sim with. So I guess I'd prefer a high quality SP campaign over anything at this point.

I had noticed that there were still enemy in the compound as Bravo was entering. To my horror, my wingman decided that was the perfect time to unleash a Mk-82. I watched in horror as he took out the remaining enemy, as well as about 10 friendlies. I feared he ruined the mission for me, but to my pleasant surprise, nothing was mentioned of it.

Frustratingly, I managed to destroy everything "needed" up to a certain point and was then instructed to contact JTAC. Unfortunately, I was stupid and about 40 minutes beforehand, bound one of my TrackIR keys to F10, which is (of course) the button to contact JTAC. Haha. I couldn't believe it. My own fault though. My technique was to dip below the clouds, figure out where the SAM-9 was, make a mental note, climb back above the soup and then slew the MAV to that area. I got lucky and managed to take out the SAM, as well as some MANPADS. I rifled off a few Mav's in quick succession to try to improve my odds. Also, baltic_dragon, I know during the briefings there are "loadout restrictions". What are the penalties for deviating from the predefined loadout? (Besides feeling like a cheater in the pit of my soul) Nothing major, just swapping one thing out for another in most cases.

My driver is up to date. I just installed a GTX970 and got the latest from NVidia's website. But I'll def try having another window open underneath. I've noticed that it minimizes my TrackIR program to the task bar when DCS starts. And when I hit Alt-Tab, I can briefly see a "flash" of the Windows Start button appear. As if it's trying, but it never lets me actually transition. I'll report back after I try it with a browser page open later this afternoon.

How did you solve this? I'm experiencing the same thing. I have the latest 1.5 version. Occurring in A-10C.

I'm also on Hammerfall part 3 and I just can't seem to take out the SA-9 before being cut to shreds by either a SAM or the AAA. My TGP is completely unable to see through the cloud cover at altitude as suggested in the briefing ("Scope out enemy positions"). As the SA-9 is an IR launcher, my jammer has no effect. I'm about to start my 4th try on this and it's just getting frustrating having to go through startup, the flight there, just to get lit up and brought down before I have a chance to target and engage out of range. The problem is I have to drop before the cloud cover dangerously close to be able to spot and target the Air Defenses. My wingmen immediately go defensive as well and usually go down within 30 seconds of myself Any help please?

One thing I've noticed is that I can hear my wingmen, as well as Overlord, but or some reason I can't hear any other radio communication. For example, in one mission we're supposed to check in with friendly checkpoints as we overfly them. I can hear myself making the calls to them, but not their response. Then I can hear myself acknowledge whatever it is they said. I'm using a headset (non-USB). One plug for audio, one plug for the mic on my headset.

:thumbup::megalol::lol::D

It took a while, but I flew the first mission of the Georgian Hammer campaign last night in 1.5 and everything appears to be working just fine. On a side note, I remember that the campaign had become broken at some point in 1.2. Somebody created/fixed the campaign and made it available for download. How is the campaign in 1.5? Still sort of "broken", or more or less properly done and ready to go?

Is that technically the correct procedure? I'm assuming it is. I'm just usually anxious to get in the air so I start aligning once I'm on APU power. Then I light the fires, shut down the APU and usually only have 90 seconds to 2 minutes remaining on the alignment. Is there anything wrong with doing it that way? I fly with sim avionics/etc and never noticed any adverse effects.

This helps tremendously. Exporting to an HTML file will be fantastic. There's no way I'd be able to assign everything from memory. I'll also be doing just one module to begin (A-10C). I'll try this after work today and hopefully I'll be up and running before bedtime. I'm really looking forward to see how the new graphics engine performs. Thank you again for all your help.

I guess my main issue is I don't know how the process works. Do I just get 1.5, then go into the controls and assign each item one by one? I believe the lua file originally handled that for me in 1.2. And then the .pro file was for the Saitek software. Which I'm guessing I won't need to "activate" anymore? Or do I need to create both? Assign everything in-game, then go into the Saitek software and assign everything in there as well? If possible, could you just give a brief explanation of what you did? I think I just need a sort of guideline/starting point to get the ball rolling for me. By the way, thank you for the quick response. I really appreciate it.

I'm sorry if this is buried in the forums somewhere. I've been holding off on upgrading to DCSW 1.5 until it releases in a (for the most part) stable version, which as I understand is supposed to be before the end of December 2015. My main question is what do I need to do to get my A-10C X-52 (not Pro) profile into 1.5? I know when I d/l'ed the profile for 1.2, it contained a .pro (I think that was the extension. If not, then something similar) and a .lua file that had to be unzipped and placed into specific locations. Is there a way to import this profile into 1.5? I have no idea how to create a lua file and I'd like to keep the same button assignments on my stick and throttle. If it is just a matter of putting the lua file into a different spot and then manually going into the game and assigning each button one by one, I guess I can do that. I think it might take a good length of time. I was just hoping that there would be an easier way of preserving/transferring things over so I don't have to relearn how to fly the A-10C. And along the same lines, would I need to change anything with regards to the Saitek profile that I load up before starting DCSW? Please let me know if you need clarification on anything. I'm just confused to be completely honest and have no idea how to get my X-52 working in 1.5.

Left console. It's marked in yellow.

I actually had this happen to me yesterday, only it was in a single player campaign, offline. I was using the Georgian Hammer (Fixed) that can be found in the User Files section of downloads. It was odd. I was struck by a SA-19 (I think) at around 7-8k feet. Every light bulb in the cockpit lit up. It was like Christmas - a really bad Christmas. I immediately punched out. I proceeded to watch (from 1st person view), while also watching the altitude at the bottom of the screen, as I helplessly fell all the way to the ground. I know for a fact I descended about 6800 ft from punch out to ground impact. I also had an issue where it wouldn't let me switch to external view. First time anything like that has ever happened. It was......interesting. Edit: This was not using the Beta.