Chief1942

SFC Tako, Thanks for that video. I suppose I'm one of those dummies that this works for. I tried every recommendation for proper landing parameters posted on these forums, along with reading the P-51D Pilots manual and I was still having a difficult time with the "bounce" (riding the bucking bronco). Using the approach and technique you have provided has helped enormously. Of course I still need a lot of practice, practice, practice, until it becomes second nature.

If the SU-27 IRL has some of the spin anomalies as this representation by ED, then it is a wonder there are any living SU-27 pilots left. The PFM is a great advancement from the previous, but that does not imply that it does not have some questionable "quirks". It is "Beta" for the very reason that it is a work in progress and subject to "fine tuning/corrections". Even a PFM still has to obey the laws of physics.

Definitely not an aeronautic engineer, but since there is no lift to take-off until the energy from the engines/afterburners apply forward motion, then how can the same engines/afterburner forces not have the slightest effect on the aircrafts motion in a flat spin? Whether upright or inverted, the sheer energy produced by full afterburner should have some physics effect. I appreciate the loss of control due to the absence of forward movement (lift) of the airframe, but I agree with Nedum, where is all the energy going?

I had the same issue until I uninstalled the More Visibility v1.2 mod. Might check to see if you have that installed. I understand they are looking for a fix to that mod for the latest update.

I went with the ASUS Z-97A. I'm running two GTX780 in SLI plus it gives you the ability to overclock. Just the basics and no whistles or bells that I wouldn't use. Good price as well.

Okay, consider me slow of mind:music_whistling: It seems my issue was caused by a MOD I had installed (More Visibility v1.2). Do not have any MODS in the Open Beta and hence no issue there. :chair: Sorry for the post.

I have both installs of DCSW (Standard and Open Beta) and I am having a problem with my SU-27 HUD display in the standard DCSW. I have enclosed a screen shot to show the problem. What is giving me fits is that it works fine in the Open Beta install. Even tried copying the FC3 folder from the Open Beta to the standard and still have this problem. I know it is some setting probably and definitely not a bug since it works in the OB. Any thoughts would be appreciated. I did do a DCS Repair and still no joy.:cry:

Most definitely this!! /\

Sad to say my updates come in at about .9MB/s. But then I live in very rural Arizona and I feel fortunate to even have broadband as it exists in our region. But DCS is worth the waits.

Any solution to this issue yet?

Politics and other issues aside, you develop this A-4 Skyhawk and I'll buy it.

ED is aware. "I can usually bring him down easily with between 60-100 hits ..." In my military career I was an airframes mechanic and I would tell you that .50 cal AP/API rounds are VERY destructive when passing through an airframe:cry:. In reality it should not take more than half the rounds it takes you to significantly affect the operation and handling of an airframe such as the FW or the Mustang. It's not as if they are hollow everywhere but the cockpit and engine areas and therefore such a round could pass through without striking anything of significance. I know this issue has been beat to death on the forums :music_whistling:so I suspect ED will address it when they are not swamped working on issues more important to the larger user segments:thumbup:.

I agree with cich, simply install DCSW and it's modules on one SSD and your operating system on the other and forget RAID. I think you'll find the performance admirable compared to platter HD's and as cich said you reduce your chances of a total HD collapse.

Just did a new system build. Went with the i5 4690K Devils canyon in an ASUS MB with 16G memory and two ASUS GTX 780 in SLI. Even though I couldn't get the system to recognize and operate in SLI due to a bad PCIe slot on the MB, DCSW ran great. Usually getting high 80-90 FPS away from congested areas with only a couple of a/c , and in the more "active" areas was getting no less than 40FPS. I am hoping once I get the system running in SLI mode, it will be even better. I think you will be well to choose the i5 4690K as it really does tits up in DCSW. The one caveat is............EDGE. Nothing but speculation as to how that significant change in DCSW will affect us all.

Sorry for the vagueness. In today's litigious environment, one can't be too cautious when singling out a large business.:music_whistling: Thought the reference would be a good "mind puzzle" for some;)

I think we all appreciate that the flight sim community is a fairly small group of enthusiasts and therefore it is very valuable to have feedback based on other fellow simmers experiences not only with hardware issues but with all aspects of our sim enjoyment. That's where I have to give credit to ED. They and their affiliates are pretty much up front and make every effort to right any perceived wrong. This problem I am having currently will also pass. But I plan on being a "simmer" until I croak.

If this post violates the rules then I apologize and will not take offense if the moderators remove it. As I decided to build a new system, primarily for DCS and it's many great modules, I jumped the shark regarding EDGE:music_whistling:. I decided on an Intel system based on much of what I have read on these forums. Intel i5 4690K Devil's Canyon in an ASUS Z97-A MB, along with a Corsair AX1200i PSU, Corsair H100i CPU Liquid Cooler, 16 MB memory, and two ASUS GTX780 CU2 OC graphics cards running in SLI mode. Got almost all of it from one place (that recent chicken business). Got it all put together and it seemed everything was working fine, even after reactivating my DCSW install and modules. Right up until I went into NVIDIA Control panel to place the two bridge connected graphics cards into SLI mode. It only indicated one card. Revisited the MB manual to make sure I had them in the right PCIe X16 slots. Long story short, after much trouble shooting and moving the cards back and forth between the available PCIe slots, I came to the conclusion that the one necessary slot was DOA. Since I was still within the 30 day RMA period of the outfit I purchased almost every item from, I requested an RMA and sent the MB back. Upon doing so I posted a review on their website regarding that particular MB. While reading many of the other reviews I noticed that the outfit frequently found other defects in the MB's that were RMA'd other than the specific issue the customer had with the MB and returned it for. Most frequently, damaged pins in the Intel LGA-1150 cpu socket. I had zip problems with the CPU and I find it difficult to believe I/others damaged the socket by simply opening the lever and lifting out the cpu itself. But that is what they (the recent chicken) outfit claimed when they examined mine and others returned MB's to them for other defects. I smell a rat or at least have identified a modus operandi of this outfit. In their email to me that they were returning the faulty MB to me due to damaged pins in the cpu socket without so much as a mention of the faulty PCIe X16 :(socket pretty much throws up a bunch of red flags:mad:. They have basically referred me to the MB manufacturer. How that plays out is yet to be seen. But I know many are putting together new systems in preparation for the release of EDGE and may be inclined to patronize the business from which I got almost all of my parts. I simply would caution everyone to read each "review" of the various parts they may want to purchase from this outfit and make yourselves aware of the issues many such as myself have had with their "customer service". That's my 2 cents. Your mileage may vary.

Yup! I sense a "clean glass" Mod is probably in the works as we speak.

The radar controlled sight is designed to frustrate you and drive you to use the fixed sight and learn off angle/lead shooting skills.;) And since the update, I am getting better and better with each flight against that rascally Mig-15bis.:thumbup:

I also use iFoxRomeo's approach. Otherwise the radio is inop. I'm okay until it is fixed if I can just remember to use the present"fix":joystick:.

Heck, I was hoping this was a trick and they were going to slide EDGE in on us while we were twiddling out thumbs. Patience! I must have patience.

Natural Point has a monopoly in head tracking just as ED has a monoply in hardcore flight Sims. NOT! There are alternatives to those who find fault with either product and they are free to purchase what they want. You get what you pay for!I agree that the TrackIR is relatively expensive for what it is, but then the market for that product is VERY limited and therefore new product development is very risky in this ever changing world. We who are familiar with TrackIR sometime think the whole world is into it. They are not. Just those of us who enjoy a genre' that screams for headtracking.

I stand humbly corrected.:mad: Was not aware of the "evolution" designations. My bad.:doh:

Cobra, You guys rock. Won't be easy waiting foer these fixes, but like the wait for the module itself, well worth it!

Are we into a semantics debate here?:music_whistling: If so, we'll refer to the final release as Gamma. How's that work for ya?