shelt

As stated in some earlier replies, the old files previouly posted will not work with the 1.1.0.9 patch. I created a rar which matches the A10C folder hierarchy for those having trouble editing their own. I also added the originals in case you want to go back. These give the option of "Very High" in Visib Range selection VeryHigh.rar

The idea of being restricted with a wireless headset didn't make sense, so I tried this as well. Pretty pleased with the results. I did cut excess wire from the USB cable, not really a problem as it is only a red and black power wire to splice. If you are confident in your hands it is a very simple process. See http://www.sdsquad.com/index.php?topic=2403.0 for more details on how I completed this project and more pictures

I do think labels have a place in the simulation. For those who have just purchased the game, they are great for learning to use the weapons on the A10. I used them extensively until I was up to speed on the "how" to successfully use the weapons rather than having to search for targets, then engage. Just one less frustration in the equation. As people become more comfortable with one stage of the game, it is much easier to move to another stage. I find there is enjoyment in flying with no labels, searching for targets, avoiding enemy threats, and using JFAC to input target coordinates; but at times feel the desire to turn labels on and just blow some stuff up! I do have to admit the full labels are a little much, and prefer to use just the dots at 5000m myself. Just wish there was a way to force all clients to see only dots when labels are on.

Maybe a bluish tint would be better

Just learning to work with the skins, so some flaws I expect. I have had the same thoughts you pointed out, and have toyed with the idea of changing the underside to a blue/grey or white. Thanks for the comments and ideas.

A unique camo pattern http://files.digitalcombatsimulator.com/en/84700/

Another skin, a little more white than I expected :music_whistling: http://files.digitalcombatsimulator.com/en/84672/ Reuploaded the file and now link is working

Sky Blue skin for the A-10C has been completed. Art has been added but can be removed if requested, send me a message for the download link My first skin :thumbup: Thanks to Ranger for the video tutorial! Got a few more waiting for the OK can be found here: http://files.digitalcombatsimulator.com/en/84669/

For some reason I had the impression the "is user" indicates dead (0) or alive (1), must have read in a previous post something along those lines anyways. The "is user" relating to flags makes much more sense now that it has been pointed out

There are several mods released for the game, check the Mods and Apps forum for examples and probably better answers to tools needed http://forums.eagle.ru/forumdisplay.php?f=89 For question #2 see http://forums.eagle.ru/showthread.php?t=41814 and http://en.wiki.eagle.ru/wiki/All_about_land Glad to see you are enjoying the game, it is a great one!

Will give it a try, I was thinking it would require a lua expression for the group being dead. What I see in the ME is just the phrase "is user", but the manual does show it as "is user flag". Just had me a little confused just what "user" was being implied thanks for the replies

So the code in the conditon is?? This is manually enter so what format is it entered? flag5=true?

I am in the process of creating a mission which will use a scout plane to call targets from bullseye. Since I am not using the scout plane as AFAC, I have set the plane to orbit the waypoint but need to set it to a condition of "group dead". As the mission stands now, the scout plane calls bull for the first target group, then blows past the remaining waypoints as no other targets have been activated. I know when using as AFAC it is a simple as checking the "is user" start as 1 and stop as 0. What code needs to be added to the "condition" to cause the scout plane to orbit intil the group is dead. Also, is there a thread which details all the basic commands that can be used as these conditions? The mission is tutorial on inputting the calls from bullseye into the CDU and locating ground targets Thanks

You may be eliminating the targets before you are in their range. There is usually only 1 major threat (which is what is called out by the script) and various support vehicles at each UTM coordinate. The SA-13 and SA-9 range is limited to approx. 5000 to 6500 respectively. It is not difficult to lock and fire a AGM-65D before they would ever launch. I know you get a warning on missile launch. The mission was designed for practice inputting the UTM's and identifying ground targets with TGP and using your munitions.

Good stuff, was wondering how to put the calls to use

Thanks to you for creating them! love them by the way, wouldn't fly without them...well I would, but it makes it more enjoyable :thumbup:

Search and destroy 6 player/multi-player only mission. Speed's ChatIOlibv1 is used to provide enemy coordinates, so please be aware of this. UTM input is required in this mission. Each assigned column must be completely destroyed before next coordinates are provided. This mission uses the DCS A-10C Digital Skins so you will either need to change them in load out or click on the link to download (or else fly an orange A10 with "TEXTURE MISSING" written all over it). Installation of skins procedure for 1.1.0.8 has changed from instructions provided in the download, for more information see this thread http://forums.eagle.ru/showthread.php?t=74763 Situation: Blue Task: Senaki Storm v3.miz

Thanks for this! Have used it in a mission and have enjoyed the features. I really like the fact you can have the vehicle coordinates without having to rely on JFAC or AFAC who sometimes just don't seem to report properly. Also like the ability to call in assistance when SA sites are present. Just wanted to leave a note to let you know your work is appreciated. RTR ;)

A full uninstall and reinstall didn't fix my problems. I had the game installer and patches 1.1.0.6 and 1.1.0.7, and reinstalling these did not stop the freezing on explosion, it duplicated the problem. A download of the install program with the integrated 1.1.0.6 patch, then patching to 1.1.0.7 did fix my problem

Yep, downloaded the exe with 1.1.0.6 integrated, after install tested start up from time from hitting fly to load was 48 seconds. After installing the 1.1.0.7 patch and doing the same test, game now loads in 35 seconds after clicking the fly button so actually is faster on loading. Stuttering no longer an issue either Thanks for the help

First time I have had any complaint on the game as far as graphics. After patch noticed lower fps and video will actually freeze at times (for 2-4 seconds) Loading a mission went from 40 seconds from the time I hit the "fly" button to over 75 seconds. The last "please wait" message takes the longest. I tried a fresh install then tested start times for the same mission with the fresh install, then each patch. Load time was basically the same 40 seconds on fresh install and 1.1.0.6, but almost double on 1.1.0.7. I made sure the video options were the same on each. I have a friend who has almost the same components and he reported better performance since the patch. Not sure why this happened. Official Nvidia Drivers 266.58 System specs in my signature

Thanks for the replies, guess I'll try the zero both ways and hopefully that is what is being omitted.. Not sure if the fix will be included in the next patch. As a host of a server, JTAC will send data and the coordinates can be gotten from the TAD, but I do not think other players in MP get these marks, so they have to rely on the coordinates given. Gets to be a problem if they are missing a digit!

Sometimes JTAC returns coordinates which consists of 2 letters and only 5 digits. When entering into the CDU it returns a error. Is a digit being left off or is a zero supposed to be inserted to complete the 6 digit number. I have seen this on at least one target in every mission where JTAC is used. I have noticed in some of the posts concerning LAT/LONG it was mentioned a zero had to proceed the first digit. Is this a bug or am I not entering this in the right format?