ElGringo

Nobody is denying that Yoyo does a fantastic job. But he is still human and, as such, can still make errors. Telling us that all the evidence we presented to you are worthless because Yoyo is above making errors just makes you lose credibility, from my point of view. You don' t HAVE to prove anything to us, sure... But you still should. Showing some respect to your user base would improve ED' s image.

A dev should not "feel". He has all the means to check the FMs.

Then how do you explain that people were not complaining before 1.5.1? Why this sudden change of perception?

You did not answer my question Sithspawn.

I really don' t get it. People were fine with the FMs before 1.5.1, but they are complaining now. Obviously, something has changed. Shouldn' t this simple logic be enough to warrant a check of the FMs on your side? Do we really need to delve in those long-winded technical arguments?

:thumbup: I think that it is the one thing that keeps DCS from being more popular with the WW2 crowd. That and spotting, but we know they are working on spotting right now.

I opened a new thread in 1.5 bugs and problems section about this issue. I am also thinking that the SFM is the reason behind this AI behaviour. Let' s hope it is possible to make the SFM a little more complex without losing too much frame rate...

It is a well known problem with DCS. Damages to AIs don' t affect their engine performances or flight models. While it not really a problem with modern jets (missiles and 20mm gatling guns are too hard-hitting to notice it), WW2 and Korea era planes suffer from this issue. For example, a P-51 hit by 30 13mm bullets and 3-4 30mm shells will not suffer any loss of performance, and will not disengage combat. AIs only disengage if they are almost destroyed. In this case they will turn nav lights on and RTB. A more detailed management of damages by AI would do a lot to improve realism and immersion when flying solo.

I did a forum search with "AI damage" keywords and found four threads dealing with this issue. Should I create a new one in the "1.5 bugs and problems" section?

Isn' t it a known issue already? You mean devs are not aware of this problem?

Yes Sokol, all the DCS modules need standardisation of the way systems work, especially concerning inputs. It is a mess right now.

Turning way better than it should... Did you read this thread? yZ4XdW4aZ2o

You like it that way Solty? Stop your BS. Everybody knows something changed about it. I got a mission where I fight two of them. in 1.5.0 I could down both of them. Now I can' t even get one. The AI not taking damages into account doesn' t help, either.

Can we expect the Zeke-51 to be fixed sooner or later?

Another problem is AI aircraft still fighting even after suffering extensive damages. Solo is not enjoyable at all ATM because of this. http://forums.eagle.ru/[/img]

Decided to resurrect this thread because there was no answer to those two questions (auto-lean in bf 109 and gun safety lever in Fw 190).

I am guessing the flight models of 2.0alpha might be coming from an older version of DCS than 1.5.x. We will have to wait for the merge to get the improvements from 1.5 in 2.0.

Well, it seems I am not the only one. Providing a way to download update without trouble is up to ED. Would you disagree? EDIT: Downloaded 2.0, now I can't connect to server to get NTTR...NICE!!

Was downloading NTTR... Suddenly it stopped with an error. And it wouldn' t restart the download. Had to uninstall 2.0 and restart download from scratch. Nice update ED. Sad we can not test it...

Same here. I can' t to create a Germany vs USA mission anymore.

-- Flaps {combos = {{key = 'JOY_BTN22'}}, down=device_commands.Flaps0, up=device_commands.Flaps25, cockpit_device_id=devices.FLAPS, value_down=1.0, value_up=1.0, name='Flaps 0 to 25', category='Flight Controls'}, {combos = {{key = 'JOY_BTN23'}}, down=device_commands.Flaps45, up=device_commands.Flaps25, cockpit_device_id=devices.FLAPS, value_down=1.0, value_up=1.0, name='Flaps 45 to 25', category='Flight Controls'}, -- Hydro Booster {down=device_commands.AileronBoosters, up=device_commands.AileronBoosters, cockpit_device_id=devices.MAIN_HYDRO, value_down=1.0, value_up=0.0, name='Aileron Boosters On/Off', category='Flight Controls'},

I also have a textures problem that might be related, colors are off on trees and hangars too. But on my system, the bug is present, irrespective of the chosen graphic settings. Also, this bug is only present when in cockpit view. Outside view is not affected.

First flight in 1.5 beta today. Took the 109 for as quick sortie, and I have to say I am really impressed. Everything is better, not just graphics and performance, but also immersion. I felt the plane floating a bit on finals, and it just was much more intense than in previous versions. Couldn' t explain it better... Nice work ED, I am a believer now. https://www.youtube.com/watch?v=XfuBREMXxts

Isn' t it possible to just add the commands from the old file to the new one while we wait for the LN to release the next patch?

It works for me too Thank you very much