Blooze

:thumbup:

Try rebooting your PC and Repair DCS World again.

Repair DCS World, not Update DCS World

Start/All Programs/Eagle Dynamics/Repair DCS World

Try doing a DCS repair from the start menu.

Do you need some practice with the A-10C?

Here's a simple MP coop mission for A-10Cs. It has 4 slots but 2 players can easily complete it. It can be flown as SP as well. Cheers Black Gold_1.2.16.miz

For me the solution was simple. Rather than endure the agonizing process of learning to do something that never will have the potential to simulate the real thing exactly, I just decided to forget about it and engage in the things that I enjoy about this game instead. In spite of what others may think, my self esteem remains intact. :music_whistling:

Be sure that FALL has been selected in the mission editor weather section.

I agree. It seemed pretty obvious to me.

I use the same stick and recommend creating a profile in the Saitek software program. It takes time to learn but it's well worth the effort.

Is this something that needs to be corrected by the user to get full functionality of the mod?

Not to be argumentative but I was referring to the 1.2.15 update. I am not using the beta.

With all due respect to ED I think we have all seen many instances of unintended consequences included in updates in the past and considering that the only change that occurred with my mission was the introduction of an update, I believe this is just one more example.

Here's TAAF: TGP Attitude Advisory Function (TAAF), data entry OSB 20. Using the scratchpad, you may enter the Attitude Advisory value in feet. Valid values range from 0 to 65000. If 0 is entered, TAAF is disabled. The default setting is 10,000 feet. The TAAF warning will be triggered if the aircraft is below the set attitude and its bank angle is greater than 75° with a pitch less than 0°, and/or pitch angle is less than -20°. The warning consists of a “CHECK ATTITUDE” in red reverse video on both MFCDs. The warning is automatically removed when advisory warning conditions no longer exist. The entered value is displayed below the TAAF OSB label.

I just flew a mission that I made in which it used to take at least 2 MK82s to destroy a ship. Now only one will do it, so it seems like confirmation of the OPs question, with this mission at least. Another thing that changed in the same mission is that I have a single explosion triggered to destroy a SA13 near some fuel tanks. It used to just destroy the SA13, now the same explosion takes out 3 of the fuel tanks as well. I had to move it farther away to prevent this from happening again. Things have changed with the last update but you don't ever know just how it will effect a mission until you fly it. There's always a few surprises in store with every update and it seems that one can only expect a mission to remain as intended until the next update arrives. Oh well, at least it gives me something to look forward to. :music_whistling:

Looks like Dubai to me. Thanks! I didn't see it mentioned but FALL needs to be selected as the season in the ME for this mod to show. This mod is a completly retexturing of the caucasus map in a south-east-asian look including: Starway you may want to change this in the description

If you are referring to the paint scheme drop down menu in the ME when you say "list" then in my experience if the aircraft does not appear there it can only mean that the country has not been designated properly in the livery description.lua file but that wouldn't explain why it only happens sometimes and not every time.

It has been a common practice in the past that when there is an update any missions should be brought into the ME and re-saved in the updated ME. If you have not been doing this then it may eliminate this from happening in the future if you do, but that's just a guess.

Well......I'm glad to see I'm not the only senior citizen involved with this monkey business.

Click HERE

??????

To begin with click HERE to see a list of games that TrackIR is supported in. So even though the manual says the distance should be between 2 and 6 feet between the proclip and the camera, that may work for some of these games but IMO is not optimal for DCS aircraft. If the camera is positioned correctly, the proclip has been selected in the software window and the alignment has been properly set up then it should work fine with default settings. If not then IMO something is wrong with the setup. If your camera is 3 feet away from the proclip I doubt that until you get closer no amount of settings tweaking will give you what you are looking for. Try just moving closer to see how it changes the sensitivity and I think you will see what I mean.

I had a friend with a similar problem that used a TV for a monitor. He was able to use one of these to create an extension for the camera without obstructing his view and it worked great.

Here is an image from the manual and it resembles my setup. The greater the distance between the clip and the camera, the faster the view will move making it more difficult to control smooth movement. Shortening that distance will often improve control issues in my experience.