Steinbauer

Could be... I think I'll just use half the value for now, until they fix it. You're probably right in that they're interperating the external wind from the mission editor as m/sec.

Hello, Is the airspeed correct on the Christen Eagle? I was practicing crosswind landings, and it seemed like the crosswind had more effect than it should. I changed the scenario to a simple headwind of 25 kts, and again it seems too strong. Even sitting still on the runway shows the 25 kt headwind as 60 mph on the airspeed guage. It seems off by about a factor of two. I'm attaching a misison file along with a track file and a pic of the airspeed indicator while sitting still. Also, if I turn the plane 180 deg so the wind is a tail wind, it still registers about 60 mph on the guage. CE2Batumi25KtHeadwind.miz CE2Batumi25KtHeadwind.trk

Ok, Thanks. I will post on that thread!

Here is a pic from the mission editor... they list it as kts.

Hello, Is the airspeed correct on the Christen Eagle? I was practicing crosswind landings, and it seemed like the crosswind had more effect than it should. I changed the scenario to a simple headwind of 25 kts, and again it seems too strong. Even sitting still on the runway shows the 25 kt headwind as 60 mph on the airspeed guage. It seems off by about a factor of two. I'm attaching a misison file along with a track file and a pic of the airspeed indicator while sitting still. Also, if I turn the plane 180 deg so the wind is a tail wind, it still registers about 60 mph on the guage. CE2Persian25KtHeadwindA.trk CE2Persian25KtHeadwindA.miz

Ok, nevermind I guess. Played with this new version for a week, and had the undesignate problem. Now, just after writing the problem report, undesignate works as before. Either you guys are that good, that you fixed it while I was writing this (and somehow had a ghost implement a patch on my machine), or its a "sometimes" bug... like sometimes it behaves and sometimes not. I'll keep my eye on it. Sorry if it turns out to be operator error (won't be the first time).

Howdy. I recently upgraded DCS World from 2.5.4.26552 to 2.5.4.27430 and seem to be having problems with the undesignate button. Before the upgrade, I could could be tracking an aircraft, fire an AIM120 at it, undesignate it, find another target and begin tracking itss through the boresight mode. Now, after firing on first target, undesignate button has no effect (use to stop tracking). Tracking remains on first target till missile impacts target and target crashes into ground. Work around for engaging multiple targets quickly (use to be the undesignate button) is to now shoot, leave A2A mode to A2G mode to drop the radar track, then back to A2A mode. Is it just me, or did something change in how the undesignate button should operate?

I'm an idiot. Thanks for clearing it up. We should delete this thread.

I loaded up the latest Open Beta version (2.5.3.22176) and it seems to have much better radar behavior in the F-18, so I'm fine for now. But I still would like to know what I'm doing wrong that is keeping me from reverting DCS World back to 2.5.3.20601.

Ok, great catch. I blew it. But... I still get same error with what I believe from SkateZilla's thread is the correct version number. 00003.306 INFO : Got reply from www.digitalcombatsimulator.com 00004.198 INFO : Got reply from srv11update.digitalcombatsimulator.com 00004.213 ERROR: Version 2.5.3.20601 is not available. 00015.067 === Log closed. and... 00000.011 STATUS: Checking for updates... 00001.178 INFO : Got reply from www.digitalcombatsimulator.com 00001.621 INFO : Got reply from srv11update.digitalcombatsimulator.com 00001.629 ERROR: Version 2.5.3.20785 is not available. Sorry, it is probably something I'm still doing wrong, but I would like to go back and can't figure out what it is.

I updated to released 2.5.21708 in DCS World. Saw lots of new radar problems on the F-18, want to go back to released 2.5.20601. Read several threads, watched BigNewy's YouTube on cleanup and repair (good, but did not show how to go back). But found a similar thread that showed how to use the DCS_updater function "update" to allow you to go back to a previous version. Tried it as instructed, and it seems to start correctly, but it just gives up and says "Version 2.5.20785 is not available" in a pop-up window. Same for released version 2.5.20601... says its not available. Anybody know how I can go back to 20601 which was working fine for me? Here is a log dump of the updater error... 00000.011 --- Log file: C:\Users\Game\AppData\Local\Temp\DCS\autoupdate_templog.txt 00000.000 === Log opened UTC 2018-09-28 01:18:23 00000.006 INFO : DCS_Updater/2.9.4.76 (Windows NT 10.0.15063; Win64; en-US) 00000.006 INFO : cmdline: "C:\Program Files\Eagle Dynamics\DCS World\bin\DCS_updater.exe" update 2.5.20785 00000.008 STATUS: Initializing... 00000.010 INFO : basedir: C:\Program Files\Eagle Dynamics\DCS World\ 00000.011 INFO : DCS/2.5.3.21708 (x86_64; EN; WORLD,A-10C,POLYCHOPSIM_SA342,SU-27,KA-50,NEVADA_terrain,FA-18C) 00000.011 INFO : branch: 00000.011 STATUS: Checking for updates... 00002.308 INFO : Got reply from www.digitalcombatsimulator.com 00002.910 INFO : Got reply from srv14update.digitalcombatsimulator.com 00002.915 ERROR: Version 2.5.20785 is not available. 00006.278 === Log closed.

Howdy, I apologize if this question is in the wrong thread... first timer. When flying the Ka-50, I can blow up general traffic (cars on the road) in Nevada but not Caucasus. There are lots of other things I use to be able to blow up that don't anymore in Caucasus. Is it just me? Do I have a setting wrong?