Gault05

Logged into dcs this morning to find that my FC3 module has been taken out, and has returned the standalone modules in the main menu. The module manager has the '1' number(assuming that fc3 was ready to install) but come to find out its missing from my list of installed modules. Its not even in the modules page either(nor any other mods besides the Harrier). What happened?

On the right side of the HUD of the Su33 is supposed to be another indicator for how much fuel thee is, yet it never functions aside from the main gauge. Is this a bug or does it not work in the real-life 33?

Well, it was a server worth playing over and over! Definitely had fun times killing the SAMs off the coast! But health comes first, so thanks a bunch for a blast.:smilewink:

Could you be more specific about what trouble you're facing? Like what mission? What objective?

The F15 campaign Bear Trap mission against Mozdok airfield is giving me a real struggle to complete this mission. :helpsmilie: The trouble is when the SEAD flight(specifically Colt 7 flight) is making its way to hammer the SA11 site at the airfield. On the way, 4 if not 5 su27s scramble up to kill them off. To top it off, the 2 27s orbiting Beslan aren't easy to kill either, even when I send my 3&4 wingmen to take them out. By the time those 2 are dead, it's either myself, or me&my #2 wingman, which isn't near enough to defend the SEAD Flight. Most of the time, I get killed, or the SEAD+Strike planes die as well. Is there a way to beat the mission without having to either get killed or the SEAD/Strike group killed too?

Does changing the fuel switches on the f15 impact how it uses its fuel in-flight? Even if it has fuel tanks on board? Trying to get a better understanding of how its supposed to work is all.

23 yrs old for this simmer.

The runway lights on the su-27 when switched to the second stage seem to dizzy off to the left side of the nose, and doesn't light all the way down straight. Noticed this when playing the FM campaign.

Vodka Flight on O.C. and my first ever successful crash landing.;)

Alright, heres the deal: While I was watching some yt vids, my pc suddenly shuts down for no good reason. At first, I thought it was the vga cable giving out, so i readjusted it, and started it back up again. After a few more minutes pass, it goes out again. Now Im thinking somethings wrong, because whenever im on dcs it NEVER closes my gaming sessions. My attention then turns to the processor. I used a temp. Monitoring program to keep an eye on the heat it was gathering. Turns out it reaches up to 80C, which given my first time using this was a bit concerning, so after that, I decided to switch out the original fan with the Hyper 212 evo to see if that would ease the temp, and clean and relube my processor. It was only after I put everything in place along with the new fan that the pc would no longer start (meaning that I press the power button, the fans spin split second then stop). All the connectors were in place plugged in tightly, restarted the psu, still the same result. At this point, I called the manufacturer to get the mobo replaced because i thought it might have been a defect. Now i just recieved a new mobo, installed everything again as usual, only to go through the same problem again: no startup. I had my power supply tested as well to see if it was that, but it checked out fine. Did it again and it was working properly. So now im not sure what is the problem anymore. EDIT: For those who are wondering what I used to test the PSU, it was a power supply self tester by.HDE. All the RAM were locked in place, the CPU fan outlet was plugged in its place, and the processor was locked in correctly aligned. Nothing else was bothered with.

Only four months in and already my new fraking rig is giving me the worst week of my life. All I did was switch out my fans and poopf! No power in the midst of the frakin setup. Checked the connectors, tested the power supply TWICE, I even had to get my motherboard replaced and it wont do aanything than shut down on startup. Is there anything to do at this point?:(

The upper cloudscape looks weird after the update on the server.

I would like to point out that I believe it would be more better if we had the ground crew spend less time going through ALL the weapon stations on a nearly or already armed fighter/striker. Just change/rearm the weapons on the desired or empty pylons and wachow! Ready to go!:thumbup:

So I recently ordered a new keyboard which arrived this afternoon. However, after it successfully installed, and I tried to play it for DCS, the keys were off by so much: tabbing out of games, systems not working properly, etc. etc. I'm trying to figure out how to configure the keys properly, but I'm not sure where to go, given that it doesn't have any discs or software needed to complete it. Basically its Plug and Play, without the 'play part. It's a Redragon K503 Harpe gaming board.

So in its "as is" perspective, its an impassable mission?

No, it's the "Fortress Mozdok" campaign. EDIT: The last mission "Davy Jones Locker"(I think.)

So, the last mission isn't all that complicated. You just have to defeat a couple flights of Hornets while a mass strike force goes for the American carrier group. The problem is the strike group. Not all of them deploy their anti-ship payloads, specifically three Su-34s. They just turn around and hightail back to base, leaving only a Ticonderoga and the carrier left. Played it again and again, same results.:huh: Is something gone wrong on this mission to cause it like this?

After about a dozen sorties and frustration ventilation, I believe I've figured out how to beat it: The key to beating it is "stealth". Have your flight follow you through the designated waypoints while flying above the patriot bases. DO NOT use ecm pods while your flying and keep on the course until reaching wp3 or starting at wp4(its why I kept getting killed by the -16s later on). The 16s won't find you as easy as they would if ecms were on. By the time you reach 3 and start at 4, they'll more likely make you out, then send your wingmen after them. You'll have a 16 come at you, so you can either kill him, or go straight for the awacs(w/eagle escorts btw). If lucky, a spare wingman or two might distract the eagles or even kill the awacs for you when they're done with the 16s, completing the mission.

Open Conflict 33's refueling featuring Dong and another pilot whose name I forgot.

On the left side of the HUD in BVR mode, radar on, the range scale indicator shows how far the target is in kilometers. What I'm trying to figure out is what do the bars underneath the numbers indicate? Like how far is it in different ranges like in 100, 50, 25 km?

Where can I re-install the original(unaltered) lua file for the A-10A? Cause there are certain servers within the MP that do "integrity checks" which I guess don't use tampered files on their servers.

Thanks for answering, came out great!

Does this work for standalone mods like the A-10A, Su-27 or is it just FC3?

Does anyone know how to get the AWACS in this mission? It's being a hassle for myself just trying to rush in and getting killed either by the 15's and/or the 16 surprise group.:mad: Only thing I haven't been killed by are the Patriot batteries, and my wingmen aren't much useful either, even with jammers on.

I think I may have finally found out the problem: the VGA screws. I think the reason why it didn't display before, was because the screws were tightened all the way. So I loosened them to see if it made a difference, and it did!:doh: And here I was panicking thinking it was a virus or something!