PhoenixBvo

My guess at the cause is gimbal lock in combination with Tholozor's remark that the SPI will follow your TGP if it is still SOI. You describe pointing the nose downward after designating the target. Assuming the target is directly at 12 o'clock this will cause the TGP to rapidly rotate to follow the target. You may hit the gimbal rotation speed limit depending on how close the target is to the longitudinal axis of the TGP. Because the TGP tracks the point it is looking at, it will be tracking another point after the maneuver. And because your SPI is still continuously being defined by the TGP's center of view, IT will also shift. This is not a bug, but in fact an accurate simulation of gimballed optics.

You can simply shout at him as long as the canopy is open ;)

Willie Pete = WP = White Phosphorus => Effects on people

You can ask the crew chief for ground power directly at mission start. After he confirms you can start aligning the INU by enabling the CDU and EGI switches. You still need the APU for engine start, so just continue the normal procedure except that you don't need the APU power generator AND you must ask for ground power disconnect before taxiing. I always have the INU fully aligned by the time I'm ready to flip the EAC on.

Here you go. Add both files to the '...\DCS World\Config\View\ ' directory. Also have a look at PeterP's ideas about the view system: http://forums.eagle.ru/showthread.php?t=96116 He posts a modified view setting with a proper modeling of the human head with neck. It works much better than the default for me. SnapViewsDefault.lua View.lua

Incorrect. From the manual (p. 81): This is actually a laser at an infrared frequency.

Nowhere near! Drag index from Eddie's post: CBU-87/97/103/105 1.17 And the speedbrakes (a.k.a barn doors) have: Speed brakes 20% 10.63 Speed brakes 40% 24.3 Speed brakes 80% 75.9

If you don't want to wait for EGI to align, you can immediately ask for ground power and then start by enabling the CDU and EGI switches. Then just proceed as normal, but don't forget to ask to disconnect ground power before taxiing. This means the EGI starts aligning from the start and by the time you must flip the EAC switch it will be blinking. Most of the tweaks Frogisis is talking about can be done on route to your station. P.S. I know this is not the operational standard procedure, but it works in the sim...:)

Still, do you know how to turn those beacons on? Is it a simple matter of changing BEACON_INACTIVE to BEACON_ACTIVE? I know such a mod would not be very satisfactory, but I'd like to give it a try anyway. From the Devs it would be interesting to hear why they turned these beacons off.

Parallel to EtherealN's suggestion, if you do have mods which only function in the main game folder, use the following method to keep track of changes. Download and install TortoiseHg. This is a distributed revision control system, which sounds more complicated than it is. It directly integrates its interface in the rightclick menu of windows explorer and is very easy to use. Using the rightclick menu create a repository in your DCS World folder. Now add all files you want to keep track of to the repository (using the rightclick context menu). Select the commit option from the rightclick menu. The icons overlaying the tracked files in windows explorer turn green. Whenever the autoupdater has done its thing, you'll see any changes to the tracked files when the respective icon turns red. It also checks any subfolders and shows a red icon on the respective folder. Now you can compare the changes with the original version which is still safely stored in the repository and merge the versions line by line if you wish. After you're done checking the changes, you make another commit and you're ready to go. If you ever want to go back to a previous state of a tracked file, you can do so as all versions are stored incrementally in the repository. This type of tool is actually meant for software development and I use it at work on a daily basis. But for DCS it works like charm as well. You'll find it's quick and easy after you get the hang of it and never have to worry about your mods with the autoupdater anymore.

Right now you can make the JTAC vehicle invisible to the enemy in the ME. That would allow you to at least play the mission until we get infantry JTAC.

Perhaps your question is somewhat unclear. Do you mean to implement additional AI logic? Do you want this to work when you order your wingman to attack using the radio or may it be part of a mission design? I'm sorry, I don't have answers to your question myself, but I'm trying to help you enticing the experts to give you your answer. ;)

I don't disagree with you that there is an effect, but it would be interesting to test how large it is. I see another experiment coming up... ;)

Actually, the variable airspeed (CAS or TAS) was not kept constant at all. Sharpe states he launched at between 225-275 kts (CAS presumably). But I think airspeed is going to be a minor factor in overall energy as the missile quickly accelerates to a max speed mostly governed by drag which depends on the air density which in turn depends on altitude. So higher launch altitude means less drag and more potential energy from the altitude. Those are the major factors. Keeping TAS/GS equal through all tests would also be very tedious.

Hi Tyger, I wanted to post this on the 74th in the thread you linked to, but it said I wasn't granted "special access" :-(... So I did a little curve fitting using Sharpe's data and came up with the following figure: You may use the equation to find the range at each desired altitude. Of course, this is only an estimate and only valid in the current DCS version, but still it might be useful.

Beste Zlorax, you don't have to buy anything new. Your purchase of the A-10C simulation remains valid for the newest version. Just do the following: 1. Uninstall everything including the C:\Users\{username}\Saved Games\DCS directory. 2. Install DCS World (download it here) 3. Install the A-10C module (and perhaps others you bought) (download here) 4. Play The activation remains active when uninstalling, so you don't have to reactivate provided your computer remains the same. Veel succes!

I can confirm wingmen have problems following orders sometimes. For me the problem has always existed to some extend and I can't really tell whether it has become worse since 1.2.2. This is mainly due to the randomness of the problem. In very similar situations my wingman may or may not execute the order and I have yet to find a pattern. I suspect that this is an important reason why the problem hasn't been fixed yet. You can safely assume that ED is aware of it, but they may have a hard time to pin the causes down.

http://forums.eagle.ru/showpost.php?p=1621017&postcount=10

Thanks for posting! But could you explain the differences with the A-10A manual for the same items? I mean, I know you have access to the correct info, but I don't really understand: e.g. the GBU-12 has drag index 0.51 in both tables whereas the GBU-10 has 1.46 in your list and 0.71 in the A-10A manual...

You'll find the procedure for range using drag index in section 4 of the T.O. 1A-10A-1-1 (the dash one) included in this pdf: A-10A Flight Manual. It starts on page 479 of that pdf. Thanks for uploading Eddie :)

Wingman management has had its problems for as long as DCS is around. (And probably before that in lockon as well, can't really remember) The problem is probably more complex than we can imagine. The devs have improved it over time though (in Black Shark before A-10, the wingmen were almost useless as weapon platforms, only as recon/ cannon fodder). To me it seems to help to really put your SPI on the intended target before calling your wingman in. Most of the time he does the job, although he may take a long time to set up an attack especially in mountainous terrain. When he doesn't attack order him back to the IP (get some distance from the target) before trying again. So yes, I can confirm your problem from my experience. But it has always existed...

lmgtfy.com

1.1.1.1 didn't have the auto-updater yet. The safest way to get 1.2.2 is to uninstall everything DCS on your machine including the C:\Users\{username}\Saved Games\DCS directory. You don't have to deactivate. Then DL and install the latest world and after that the modules you own. I actually backed up the old installation under another name. I maintain a list of changes to .lua files I've made and integrate those in the new version manually. You'll have to be careful though as there may be compatibility issues. Always backup the originals AND the changes you made yourself in separate files. The auto-updater will otherwise overwrite all your work when you hit the "apply update" button. For more convenience people who know their way with .lua editing should consider using Tortoise Hg. It's a distributed revision control system which exactly fits the needs of this problem. Short howto: 1. install Tortoise Hg 2. Create a repository in your DCS World and C:\Users\{username}\Saved Games\DCS directories. 3. Now use the context menu to add all files you changed to the repositories. 4. Commit your changes and add a useful comment. Each time something changes you'll see the icons change. Compare changes and merge using the tortoise tool. Then commit. You can never loose your mods to the auto-updater anymore and you have a very easy way to check for changes to the relevant files and to manage those changes. If a bug pops up, let the auto-updater repair your installation and merge your mods one by one to find and resolve.

OK, then tell us where. Maybe the manual contradicts itself... EDIT: Actually that is not a contradiction: my quote says "If available runway does not require maximum braking" you may use aerobraking. But you said: And that statement appears not to be in the manual. On the contrary: it actually recommends it if you have enough runway available.

I had no problem running the new version. But if you made any modifications to lua files, they will all be reverted when you apply the update, so make sure you have backed up any changes you might want to keep!