EOS 1.2.7

There is plenty enough angle to see -15 degrees.

 

Actually...

Cone tip and probe by being leading egde of the fuselage get very hot so usually radiate heat and interefere (clutter) the sensor. Close to it's negative gimabals EOS is very buggy.

Perhaps that's the reason for this FC3 limitation...

On the other hand Russian jets get a lot of limitations lately that really degrade them to their 1982 modus operandi instead of upgrading whole lot of it on our way to DCS:Su-27SM or DCS:MiG-35...

From LOMAC 1.02 to FC3 the only upgrade is a functional gun pipper...

It cannot be -30 - there is no possibility to look down from KOLS position. It tells, that HUD is scaled to represent -30. It does not mean the target can appear in the lowest part of it. On another page of that manual the track zone is set +30 -15 and is drawn asymmetrical.

It makes sense the scaled representation of the HUD in lock mode. Thanks.

Maybe this two pics are the ones you are talking about. The first shows +30º -15º on elevation as you said.

Do you have documentation of su-27's EOS?

The Su-27SK manual is public on internet.

My knowledge about Su-27 EOS come through that manual.

Basically the SU-27 EOS has this characteristics:

Scan FOV of 60º in azimut and 10º in elevation in wide mode, with a 5 seconds refresh period.

Scan FOV of 20º in azimut and 5º in elevation in narrow mode, with 1 second refresh period.

The basic scan pattern is + - 60º in azimut and - 15º + 60º in elevation

Great info Esac..

But yet, public information that ED choose to ignore, they know best?

But yet, public information that ED choose to ignore, they know best?

We don't ignore. We just had possibility to model one control type. Later they will be separated.

ED has all that information.

ED isn't interested in increasing the complexity of old code, since new code requires their attention.

Edit: Frogfoot said it nicer.

But yet, public information that ED choose to ignore, they know best?

I don´t think they ignored the information. My guess is when you model at FC level ED must take some decisions about what could be included and what can´t be, and also the level of fidelity.

About EOS they take the decision to model OLS-29, not OLS-27, and to the maximum level of fidelity FC stands. And sadly, not all features could be implemented at this simulation level.

Maybe in the future with a DCS level module for Flanker or Fulcrum.

Edit: Fast replies..... XDDDD no more guess

We don't ignore. We just had possibility to model one control type. Later they will be separated.

So flankerphiles will wait patiently....

Better to under model the Flanker than over model MiG.

FC2 had the ability to scan up and down manually.

And gyro stabilization was not present, actually, only for Radar but not EOS in FC2.

 

Gyro stabilization was present for EOS in FC2 and the HUD only saw +/-5 degrees, the elevation slew allowed +30/-15.

In FC2 when flying level with a contact on the nose at co-altitude if you pitched the nose up or down the contact would remain in the same spot on the HUD because the gyro was in effect, it would only move when your altitude drastically changed. You could not fly up underneath a target point your nose at it and find it on EOS because of the gyro stabilization.

The Su-27SK manual is public on internet.

 

My knowledge about Su-27 EOS come through that manual.

 

Basically the SU-27 EOS has this characteristics:

 

Scan FOV of 60º in azimut and 10º in elevation in wide mode, with a 5 seconds refresh period.

Scan FOV of 20º in azimut and 5º in elevation in narrow mode, with 1 second refresh period.

 

The basic scan pattern is + - 60º in azimut and - 15º + 60º in elevation

 

Alright, so I assume the dashed area in the picture above represents what is hidden by the aircraft nose. Then it means you can't see anything below say -10 degrees unless you maneuver to do so. What the HUD displays does not represent possible real scan angles.

Now we just need to put up with the +15 limited vertical scan as it goes higher in RL. A slight nose up should normally do the trick by the time we get a more accurate EOS implementation.

In 1.2.7 the EOS isn´t gyro stabilized so, you can move your nose up and down freely.

Will the EOS in vertical CAC and HMD modes still have the current vertical gimbals limits or will that be changed as well?

i supossed it would be the same. No reason to change something is correct right now.

Vertical Scan Mode Close Combat. EOS ONLY. HUD only shows + - 12º FOV. Complete Size +16º -14º ( 4º wide )

Vertical Scan Mode Colse Combat. Radar ON. +37º -13º (6º wide)

CAC mode ( OPT ). 3.36º wide lock zone.

HELMET - RADAR - EOS - Longitudinal Missiles Aiming Mode. Helmet + - 60º azimut / +60º -15º elevation.

The Su-27SK manual is public on internet.

Thanks Esac! ;)

Do you have a link?

Also the Fulcrum manual is pubblic?

In russian:

Su-27SK

In spanish ( expanded and improved by me)

Spanish Right clic and save

In russian Mig-29A Flight Manual

Mig-29A Flight Manual

Combat Manual.

Combat manual

In spanish

Spanish Flight Manual Right clic and save

Spanish Combat Manual Right clic and save

I believe I read somewhere the range for VS was 15km. Is that in the manual? Currently in game it is 10km.

The Mig-29A Manual talks about 450 mts min to 10 Km max in the page 16.

That's what I was saying. -10° is blackened by the nosecone.

There's a OLS-27 / OLS-29 difference IRL but I'm not sure if there's any in FC.

Fast response ¡¡

Well done ED.

Brilliant news, thank you!!!