pdmarsh

Until today, the "NOT SOI" notice that appears on the MFDs would clear after a minute or so. Now it stays on permanently unless the given MFD is the SOI. Is there a setting that will allow the notice to clear after a given time? Thanks, Paul

Thanks for the quick response. I had a feeling it might require the driver change. I'll see how easy or difficult going back and forth is and post about it here. In any case, thank you for taking time to write this application. Skeeter

@ArturDCS -- I'm looking forward to running your application--it looks great. Will any of the changes required to make the switch panel work in DCS affect how it functions in X-Plane (which I use) or FSX? To get the Saitek panels to work in X-Plane, I had to install special drivers. Would I have to change drivers every time I switch applications? Thanks, Skeeter

I found and corrected another bug in this mission. The white zone defenders were visible from the start, and before being activated, and get destroyed too soon. Their ETA was set incorrectly. A new version of the mission was uploaded to the link already posted. Thanks, Skeeter

P.S. to DCS -- I'm hoping you can easily compare my modified mission with the original to spot the changes I made to what I believe to be errors. However, I can take the time to point you to the specific areas of you like. Thanks, Paul (a.k.a. Skeeter)

I hope you won't object, but the following is a copy/paste of my post on Combatsim.com. It was suggested that I post this on the ED forum. Given that the subject mission was included with the Flaming Cliffs 3 package from DCS, I was surprised to find what I believe are quite a few errors in the mission that render it unworkable and, most likely, unwinnable. In at least two cases incorrect units are being activated. In another case, the wrong unit is being tracked for entry into a trigger zone. The condition "FLAG IS MORE" was used when it should have been "FLAG IS TRUE" in another instance. Finally, the CAS2 orbit was set up such that they would never fly through the trigger zone that would allow their activation (or the trigger zone was placed between the wrong waypoints). Finally, the return and nearby bases were set to neutral, which would disallow repair and rearming. This might have been intentional. I suppose that with judicious use of your wingman and available CAS units, this mission could be won without rearming, but maybe not. I certainly could be wrong about some of these things, but in some cases the errors are pretty clear. If you wish, you can download a modified version of this mission with the above changes. I have yet to win this mission, so there might be other things lurking, but I have gone over it fairly thoroughly now. One additional change that I make for myself since I'm still very green is to eliminate the two SAM batteries and give myself at least a fighting chance (that change was not made in the linked version). I hope this helps anyone who might be interested. Also, I'm very open to strategy advice on this one. It seems success is highly dependent upon proper use of your available assets, mainly in terms of when they get activated. Thanks, Skeeter Download link: http://www.poweredmodelairplanes.com/FC3-A-10A-Gory_Gori_Corrected.miz

I seem to be having trouble getting my flight time to log in my pilot log. Sometimes flight time gets logged and other times it doesn't. What steps need to be taken to assure that flight time gets logged? I only have one pilot created and the skill level in my missions is set to "Player," which I have been told it needs to be. Thanks, Paul

Thank you for the help in kicking this loose, EhterealIN. It does appear that there was a breakdown in the ticket process that caused my inquiry to go unnoticed after a time. In any case, I did get a rapid response as soon as the ticket was reactivated. As I feared, the problem is on my side, but that's OK. At least I know. Paul

Hi Ethereal, Did you ever get my PM with the ticket number. I just tried sending another PM and it appears that it did not go. I have no record of the first one either. Thanks, Paul

Hi EtherealIN, I just PM'd the ticket number. Thanks. Paul

P.S. -- The ticked system stops cold after their request for the dxdiag file. Nothing posted there either, although I'm sure I would have received an a-mail notice if they did post something. It appears my ticket was automatically closed and I was never notified. Either way you look at this, I think DCS did a rather poor job of handling my inquiry. I hope this is unique and not a general indication of how this company operates.

@EtherealIN -- I did use the ticket system. They responded via that system for a file. I sent the file as requested. When they never responded, I sent an e-mail with the ticket number in the subject line. I have since been to the ticket system and see that my ticket was closed. This is very strange. They requested information, never reponded with any kind of feedback and closed my ticket. Ticket system or no, this is very unprofessional. I believe that my inquiries were civil and well spaced so as not to be harrassing.

@garengarch -- I certainly have, and those who responded were as helpful as they could be. I appreciated their willingness to offer their time and support, free of charge and at their own expense I might ad. The resolution was not black and white. I therefore attemted to get more concrete information from the source, i.e. the people who actually took my money for a product I assume they would be willing to support themselves when need be.

Perhaps my experience is unique, but I have found DCS tech support to be nonexistent. It took a while for them to respond to an e-mail inquiry, at which point they asked for a file. I sent the file immediately. It has been nearly two months and they have not had the courtesy to contact me or respond to my requests for an update. I tried again today only to find that my message was kicked back. It said their e-mail address was unknown. Hmm. As I said in at least one message to them, I am perfectly willing to accept that the problem is with my hardware or with how I am trying to run the software. All I asked for was either suggestions to get through my issue, or tell me flat out that I was the one that misread the specs and should not have purchased the product. As it stands, I'm out $40 as I own a program I can't use. If it was my mistake, so be it. If their software has a major problem that they can't fix, simply refund my money. Live and learn.