c84

PS Attached track mig-15trim.trk

Since last update 1.5.3.52724.74 trim is not working while ForceFeedback is on. (at this moment, only plane in DCS where FFB+Trim works is Mig-21 :() btw i have logitech wingman force 3d

Il-10 for WWII & Korea

Please check the tracks l-39 trim button moves, but stick not. Plane is not being trimmed (show controls indicator) mig-21 trim button moves, AND stick moves too. Plane is being trimmed (show controls indicator)

drop from 60fps to 30 or less Mustang old Lua files helps a bit, but i think there is something else. - Why suddenly thousands of objects while flying over town? btw Seems, ED worked hard to make some ''SmallShit'' (see attachment :-)

Trim does not work while FFB on. It affects only modules made by ED - FC3, L39. Third party modules like a MiG-21 or MiG-15 works fine. Attached 2 tracks, Su-27 - please note neutral stabilizer trim light and MiG-21 Does someone else have a same problem? I tried pretty much everything in settings and nothing helps. btw i have old logitech wingman force 3d - just because there are no new ffb sticks. *edit attached L-39 track su27trim.trk mig21trim.trk L39trim.trk

Same problem here, ASO usually does not work.

Runs reasonable fast. But then, last 20MB downloading already 1 hour - not finished. Stuck at ~967MB out of 985.6MB Peers 148, down 20kb/s

Doing the same. AIM-120 coming? > start descending (about 30 degree) maintain decent speed, beryoza is your friend, when signal near max just pull up hard and AIM-120 surely miss.

From: Matt Wagner ======================= MESSAGE =================================== This is already fixed internally and will be part of DCS World 2. ===================================================================== Thx

Never even been hit by AI controled aicraft gun. Out of curiosity tried TF-51 (i even do not know control this plane - radiators etc) vs excelent AI 2*51+2*109+2*190. Aaand, after 10 minutes of flying zero hits.

1, A, what’s wrong AI fire missiles out of range, always miss. See attached track, this affect almost all BVR missiles. As you can see, AI is unable to kill head on non-manoeuvring, no ECM, no chaffs/flares target. B, Why this happened (speculation, may be wrong) As you know, ED introduced new flight dynamics for missiles which decreased their performance/range few months? ago. But somehow forget decrease ‘’ Range_max = ‘’ values, missiles_data.lua. C, Solution Decrease ‘’ Range_max = ‘’ values to roughly 60 percent. 2, A, what’s wrong AI fire always only one missile and miss (see point1). AI wait until 1st missile hit the ground (cease exist). And only after that fire second missile. Please keep in mind, if AI fire missiles against high flying target it can takes up to couple of minutes until first missile finally crash. So AI is couple of minutes helpless. B. Why this happened (speculation, may be wrong) Some people complain about all-knowing AI. So ED brings this ‘’solution’’. C, Solution Anything else, It is hard to imagine worse solution than current. My temporary – not really fix (I am not able to figure out which file determine this AI behavior), set missile self-destruct after certain time (missiles_data.lua, for example in case of R-27R it is line 1042) PS If you edit missiles_data.lua, you will fail integrity check when goes multiplayer Came back to DCS after long time. Bugs/behavior like this really disappointed. It is not fun if you spend more time trying to figure out bugs than enjoy game. What’s the point of any Single player etc., if AI is totally helpless and you always win? AI AMRAAM.trk AI AMRAAM Tacview-20141218-162047-DCS.txt.zip

sorry, though it somehow fits here and it is not necessary make a new thread

Regarding AI BVR missiles, i submited ticket 2 days ago, so we will see. 1st. complain excelent AI f-15 have a huge problem to kill non-maneuvring, no ECM, no chaffs/flares Mig. tracks attached. This affect almost all BVR missiles. Can be solved if you decrease Range_max = values to roughly 60 percent, missiles_data.lua. Bu if you do that, you fail in integrity check when goes multiplayer 2nd complain AI firing logic. AI always fire only one missile. Lets say this missile miss (sure do, see point1). AI waits until first missile hit the ground -cease exist (Especially missile fired at high altitude needs a lot of time to hit the ground) and only after that fire second. Perhaps i have high expetation, but i would expect something smarter. AI AIM120.trk Tacview-20141213-143911-DCS.txt.zip

Actually i report that few hours ago, so we will see. Sorry for being rude. It is bit annoying, this is not minor bug, but big one - at least for me. It makes any fight against AI poitnless waste of time. You always win if you know this bug. And i am surprised is still here. perhaps i am wrong, but i guess this is what happened: ED introduced new flight dynamics for AA missiles, which decreased performance-range of missiles. But somehow forget change Range_max values (which determine at what max distance AI open fire) in missiles_data.lua. So AI always open fire too early and always miss.