derelor

+1

Yes, everyone :) It has to do with the Mods\aircrafts folder being renamed to Mods\aircraft in the latest update: http://forums.eagle.ru/showpost.php?p=2179220&postcount=38

You could try to force update manually: http://forums.eagle.ru/showpost.php?p=2179383&postcount=60

Yes, there is an auto updater. It only checks once a day for new versions, but you can manually force it to check for new updates any time by calling: There are also full installers: Large files that - depending on your internet connection speed - could take long to download, but are useful when you run into problems.

Torrent link is now up: http://www.digitalcombatsimulator.com/en/downloads/world/dcs_world/ (link is at the bottom of the page)

Same here, perfect timing. Thank you, Leatherneck!

Soon :)

FYI, installers are now ready: http://www.digitalcombatsimulator.com/en/downloads/world/dcs_world/ ... http://www.digitalcombatsimulator.com/en/downloads/modules/mig21bis/

I don't use the tool myself, but if the directory is hardcoded, icemaker will probably have to release an update.

Open "Run" or Command Prompt and type (including quotes): "C:\Program Files\Eagle Dynamics\DCS World\bin\DCS_updater.exe" repair Be sure to adapt to your own install directory.

It is now released :cheer3nc:

That explains it. Glad it works now ;)

Correct, I am glad this typo is finally fixed :)

After the update, there should only be a Mods\aircraft folder. What is inside your Mods\aircrafts folder?

No, I think this will never happen - which IMO is good. There is a lot of information which is not yet or not at all intended for the public (NDA). Also, a lot of entries are very technical / hard to understand for normal users. IMO regular users would often not be able to interpret a lot of information in the tickets and jump to wrong conclusions.

The Mods\aircrafts folder was renamed to Mods\aircraft with this update. Your problem seems to be related. Can you try a repair?

While I personally agree with you, I also think for the majority of users a "condensed" changelog is more suitable. For example, the entry "Corrected cockpit and external 3D models." includes ... - ~20 individual errors (for example typos/wrong positions) fixed in the exterior model - Texture DIF File: There was only one set of gun port textures - Wrong Pitot Tube Model - Variable Sight Selector Unit "MILS" label missing - Airspeed Indicator missing caret - Fuel Quantity Gauge Texture Error ("X" missing) - Radio Compass Indicator: Label "VAR E W" missing on the knob - AN/APX-6 IFF Panel Left screw missing - AN/APX-6 IFF Panel Bottom left: screw wrong color (black -> red) - AN/APX-6 IFF Panel Right: Destruct label missing on switch cover - AN/ARN-6 Radio Compass - Tuning knob is actually a crank - AN/ARN-6 Radio Compass - Light switch "HI" and "LO" labels missing - AN/ARN-6 Radio Compass - Function switch: "CONT." position missing - AN/ARN-6 Radio Compass - Screw/light missing between AUTO and COMP labels - AN/ARN-6 Radio Compass - Index marks missing on top of Function switch and Loop L-R switch - AN/ARN-6 Radio Compass - Round "hole" for tuning meter display missing - AN/ARN-6 Radio Compass - LOOP L-R arrow is actually two individual arrows ... and several more fixes - the list is not complete. If all those fixes / tiny details would be listed individually, assembling the changelog would take a lot of care and time. Also the changelog would be of immense size and would confuse some people. On the other hand, it would show the love ED and 3rd-party-developers are putting into their products.

Yes, in the changelog several issues/tickets are grouped into individual entries to make it less technical and more end-user friendly. Also, I noticed that several included improvements are not mentioned in the changelog at all ;)

IIRC, that had to do with an issue where 4 average AI Su-27 won against 4 excellent AI Su-27 in the past. This is now fixed.

You will receive the bugfix soon: http://forums.eagle.ru/showthread.php?p=2178959#post2178959

Exactly my point of view! Well said! :)

Yes, this is known (ticket #26661).

Thank you. Fixed.

Here's an illustration that I made for operation of the Sabre's Landing + Taxi Lights while discussing its function with several people. Maybe someone will find it useful. Update: Attachment fixed. F-86F Landing and Taxi Lights.pdf

+1