EOS 1.2.7

[fitness88]

Strange to see, that from FC2 to FC3 things that were OK before re-appear as bugs and need additional fixes...

 

There is a German expression for it. We call it "verschlimmbessern" ... :music_whistling:

 

I call it FUBAR...:doh:

[fitness88]

Blablabla just a bunch of pessimistic nonsense..

DCS/FC3 is the evolution of Flanker/LockOn/FC and in its best state ever.

I fly daily, for many hours, without any bugs or crashes.

With 1.2.7 list if fixes, it's sure looking to be a great new year in DCS!

 

:pilotfly:

 

I hear ya and I too don't have any crashes...rarely did, I just expected FC3 to pick up from where FC2 left off from a user interface perspective. I suppose I'm not technical enough to appreciate the hard work of subtle code changes that affect flight at 5000 metres with a cross wind of 5 m/per second and turbulence at 3500 metres on a cloudy day in July...wish I could but with all this attention to fine detail, I feel some functionality is being overlooked.

 

Of course there is a lot of good to be said about the sim so I guess I'm speaking for the silent minority or majority...just don't know:huh:

Edited December 14, 2013 by fitness88

[8core]

fictitious EOS

 

hello gentlemen, I think the EOS of Russian DCS planes are running a wrongly

EOS system is achieving detect an aircraft at 150 ~190 miles, real EOS can detect only 45 KM

[sobek]

EOS is still WIP.

[8core]

EOS is still WIP.

inaccurate data causes the DCS/FC3 become just a game

[sobek]

inaccurate data causes the DCS/FC3 become just a game

 

The data is fine, it isn't finished yet.

[8core]

The data is fine, it isn't finished yet.

I hope it is fixed as soon as possible because EOS this totally unrealistic

 

Thanks for listening :smilewink:

[EtherealN]

Please consider that in the simulator, we're not talking about just a "if 45km then detect". Different aircraft will be detected at different rangers, and the same aircraft will have different detection ranges depending on aspect, exhaust etcetera. The simulator needs to account for all of this.

 

And do recall that when you read, on a website or similar, that detection range is "45km", this is full of qualifiers; which aircraft, which aspect, which throttle setting and - even - which atmospheric conditions? So please do consider that it is actually pretty hard to find underlying algorithms that give correct behaviour, especially considering that the REAL performance data is most likely top secret and the numbers that filter out into the open are typically "sanitized".

[8core]

Please consider that in the simulator, we're not talking about just a "if 45km then detect". Different aircraft will be detected at different rangers, and the same aircraft will have different detection ranges depending on aspect, exhaust etcetera. The simulator needs to account for all of this.

 

And do recall that when you read, on a website or similar, that detection range is "45km", this is full of qualifiers; which aircraft, which aspect, which throttle setting and - even - which atmospheric conditions? So please do consider that it is actually pretty hard to find underlying algorithms that give correct behaviour, especially considering that the REAL performance data is most likely top secret and the numbers that filter out into the open are typically "sanitized".

 

in parts I agree with you.

but EOS detect 190 miles, is totally unrealistic.

do not forget that is airplane manufactured in 1960

old technology

[104th_Maverick]

Its not quite 190 miles but it is very over powered.

 

Its a known issue sir that is WIP as Sobek mentioned, you join a long line of Eagle pilots who are waiting for this to be fixed!

 

In the meantime you just have to fly taking this into account and adjust your tactics accordingly, good luck!

[Axion]

They've done great things to get EOS this far in FC3, baby steps my friends, baby steps.;)

[karambiatos]

the fact that you can just detect a target is not as bad as the laser being able to reach and read the speed and heading and altitude at insane ranges.

[8core]

In the meantime you just have to fly taking this into account and adjust their tactics accordingly, good luck!

 

-------------------------------------------------------------------------------------------------

 

is not the kind of answer I like to hear, and this defect has long existed

 

hope you can do your job properly good luck!

[sobek]

Or fly 1.2.6 when you don't want to deal with bugs...

[104th_Maverick]

is not the kind of answer I like to hear

 

 

You think this bothers me?

 

Oh and I'm a volunteer, its not my job to do anything!

[8core]

;1953441']You think this bothers me?

 

Oh and I'm a volunteer, its not my job to do anything!

 

I thought you were the test team

but I was mistaken, thank you for clarify

you volunteered for the post of pointless to do nothing.

Edited December 22, 2013 by 8core

[Nate--IRL--]

I thought you were the test team

but I was mistaken, thank you for clarify

you volunteered for the post of pointless to do nothing.

 

The Test team are all Volunteers.

 

Nate

[104th_Maverick]

you volunteered for the post of pointless to do nothing.

 

You got me... busted!!!

[Vekkinho]

Updated 1.2.7 change log today:

 

"Corrected EOS scan volume, removed gyro-stabilization, and added EOS manual elevation scan control for the Su-27 and Su-33. The EOS on the MiG-29 that does not include an elevation adjustment function."

 

So OLS-27 nad -27K now work as they should which is +/-30 in azimuth and +60°/-15 in elevation?

OLS-29 +/-30 in azimuth and +30/-15 in elevation or do we still simulate OLS-29 for all the platforms?

 

What's with simulating different FOV for OLS systems? Any way of having better detection range with OLS-27K than with OLS-27?

 

I hope some of that gets implemented in the future with AFM DCS-FC updates of these aircraft.

[fitness88]

It seems to me that FC2 had EOS working quite well...why didn't FC3 just keep it going that way and improve where necessary?

[Kuky]

So OLS-27 nad -27K now work as they should which is +/-30 in azimuth and +60°/-15 in elevation?

OLS-29 +/-30 in azimuth and +30/-15 in elevation or do we still simulate OLS-29 for all the platforms?

 

What's with simulating different FOV for OLS systems? Any way of having better detection range with OLS-27K than with OLS-27?

 

I hope some of that gets implemented in the future with AFM DCS-FC updates of these aircraft.

 

Testers version has Su-27 EOS bit more sensitive compared to MiG-29. I just tested both to see at what range I can detect target at 6 o'clock aspect... I tried F-14 as target traveling at 5km altitude 800Km/h... so, without afterburner MiG-29 could detect him at around 24Km and Su-27 at around 40Km range... this is not in 1.2.7 yet though.

[*Rage*]

Nice:)

[Vekkinho]

Testers version has Su-27 EOS bit more sensitive compared to MiG-29. I just tested both to see at what range I can detect target at 6 o'clock aspect... I tried F-14 as target traveling at 5km altitude 800Km/h... so, without afterburner MiG-29 could detect him at around 24Km and Su-27 at around 40Km range... this is not in 1.2.7 yet though.

 

What are the tracking ranges? Can it detect flare decoys?

[fitness88]

EOS works extremely well now in 1.2.7 beta!

Flankers can adjust elevation manually as well as with the nose.

MiGs can only use the nose. But it definitely works great!

 

The Migs in FC2 were able to adjust EOS elevation manually as well as with the nose, now you can only adjust with the nose.

[IvanK]

So in the 1.2.7 Exactly what elevation increment is for each "click" of the elevation button ? .... 1 click up raises the EOS scan volume by how much

 

I note with EOS selected there is a "10" value for the expected target range

Edited December 25, 2013 by IvanK