AeriaGloria

You might be surprised how the avionics and HUD for the FC3 model are completely wrong. But yes I agree, with this RSBN correction nav system modeled, you could basically copy and paste the basic functionality to Su-25, Su-27, etc ER is in the trailer and many pre release photos

Oh no please buy it! We need to tell them that there is demand for red modules! MiG-29 “A” should still be a worthy fast attack jet especially if there is access to RSBN correction on many maps. Set you waypoints to IP and target, we can carry S-8 or S-24 with it which is very powerful or bombs. And you can do wind/moving target correction by designating the target first then aiming after 2 seconds!!! That should give us some versatility we don’t have in FC3 to make those rocket and cannon runs extra accurate!!!!

I would be very interested if there are any sources you have access too that give gun accuracy. The aircraft weapon manual described here gives much smaller values then the DCS MiG-15 of 12 mil dispersion for 1 km for 23mm and and 8.3/6.7 mil for 1 km for the HE/AP 37mm rounds, both for 100% circle or MOA. Along with different tracer burn times and ammo mixes. If the link for it does not work I can help. I look forward to a 37mm that is properly accurate and a 23mm that is properly spray and pray, though I do understand if the slightly longer barrel of the MiG-17 NR-23 makes a small improvement in its accuracy.

Which part? The S-21, S-24, or both? Какая часть? S-21, S-24 или обе?

Radar and KOLS range is very close right now. The biggest issue is their interaction and the way the systems operate.

Yes I never use it either, but sometimes it seems there is some ghost input putting it on! It seems OP’s problem was solved. Are you turning on your route channel within the Doppler limits of +/-7 degrees pitch or 30 degrees roll? 50-300 kmh? Usually you can’t use it above 260-289 kmh becuase you need such a negative pitch angle it disables the Doppler

The “F” key toggles the Collective brake. The collective brake will disable the altitude hold. It has been a bug occasionally that the collective brake seems to accidentally be on sometimes and prevent use of the altitude hold.

Hello, I have encountered two things I see repeated in a few places that would be very fun for the module! Most common, I see late MiG-17F fighter bomber squadrons being modified to fire S-24 and needing to stiffen the rear shock absorbers to increase ground clearance. This would be a very fun weapon for such a small and spunky aircraft! Two, I found a mention that S-21 was designed with MiG-17F in mind, and that the sight would program the fuse to detonate at the range the sight was at to, making it an extremely potent anti bomber/large aircraft weapon. Saying the weapon could explode 15m from a bomber and still be expected to mission kill it.

Have you pressed “F”?

The hover button is very finicky! 1. It will try to stabilize you over a particular spot, so you need to only turn it on once you are already in a hover! 2. Just like route mode, since it uses Doppler, it is turned off as soon as you exceed Doppler limits (7 degrees pitch or 30 degrees roll). Now, normally you hover at 3.5 degrees nose up. So what happens if you have any forward speed and press hover button? The hover mode commands nose up to get you to go back to the spot you turned it on over, you exceed the 7 degrees pitch Doppler limit, and it turns off. Add things like tail winds, needing to back up, and it might turn off a lot, so you might need to keep turning it back on! And just like route mode, if it turns off on its own, its last command is “saved” in the autopilot and will interfere with you. So when you are actually done with it you NEED to press the “OFF” button or it will keep messing you up for the rest of your flight. Sometimes it can be a nice crutch to turn on the hover mode before takeoff and have it help you takeoff straight, then turn it off as you start building speed!

Hello Chops, I made a guide for the autopilot, in there there is a chapter where I go through every single special options settings, it might be able to help, if not I can answer any questions https://drive.google.com/file/d/157HdRauUQO8rUJypKMnWrOktTjWqyMBE/view?usp=drivesdk Here is what I would recommend based off your screenshot 1. Turn “Pedal auto move” off, this gives heading hold more authority by trimming your pedals, but often causes control issues especially when heading hold is accidentally activated and you lose overall authority from pedals being trimmed. The normal 18% authority is usually plenty for heading hold to get you from point A to point B 2. Turn “Microswitch logic” either to “disable by return pedals to center” or “automatic off.” But really, what I honestly recommend after all my years is to go “automatic off” and bind “microswitch toggle,” and use this as your “heading hold” button. Just when you start up, turn on your auto pilot, also press your “microswitch toggle,” this will put the put the yaw autopilot into a mode that is helping you fly smooth but not holding heading. Then when you want to activate heading hold just press microswitch toggle and once again to turn it off. Know how each autopilot channel has a dial? If you are having trouble conforming if your heading hold is active or not, move the dial and if it moves the needle in the window above it then heading hold is active! Or if you have R control + enter window open, and if the left most AP window is fighting your turn, then you know heading hold is on. You can do the same thing without R control + enter display by looking at the same AP windows by your left knee. To be honest though, I almost always fly heading hold with microswitch pressed (heading hold off), becuase if you want to fly from point A to B hands off you know what’s even better? Route mode! On top of autopilot panel you have buttons route mode, hover button, etc. Route mode will only work when Doppler is active (it has pitch limits of +/-7 degrees and roll limits of +/-30 degrees), but becuase it uses Doppler that means it corrects for wind! It’s a little more work then heading hold, you have to set your heading with a dial to the left of the autopilot panel. But it will compensate for wind PERFECTLY! Just make sure when you’re done using it to press the “OFF” button next to it, becuase even if it turns off automatically from exceeding Doppler limits it’s last inputs will be “saved” in the autopilot and mess you up. If you instead choose the “disable microswitch by moving pedals to center,” I would recommend to only turn on Yaw AP when you want heading hold and turn it off when you’re done! Becuase if you leave it on in this mode it can accidentally turn on or off at the wrong time and interfere. Let me know if there’s anything else you want to know!

Jojojung is correct, I believe you are mixing up two different types of “dampeners” Zero_Crash Yes. There is the “SDV-500-OA” which is a literal hydraulic dampener, it is not advanced or smart in any way but only slowing down any movement of the pedals from center to full to 3 seconds and being able to be filled by the autopilot to move the pedals on their own if your settings are set that way. And yes it’s turned off with the red guard. But if you turn Yaw AP on and press microswitch there is still a dampening/stabilization function in the autopilot that is completely separate. This function works off not fighting yaw rate, but changes in yaw rate. So if I turn left, it will “dampen/fight/stabilize” the initial turn to the left, but as the turn to the left stabilizes it will go back to neutral. You can see this work in the simulator by using R control + enter and looking at the yaw window with yaw autopilot on and microswitch pressed. It will move the channel 20% for every deg/s/s of acceleration, just like how the channel moves 20% for every deg/s of acceleration in normal heading hold. Becuase of confusion of these two “dampeners,” I have tried to shy away from calling it such and say “stabilization” mode, which some real life sources say as well. This “stabilization” law that is active with Yaw AP while microswitch is pressed was added after Dutch roll issues reared their ugly head, , so it was meant to make that and all high speed flight much smoother In addition, the Trim hat is connected to the Mi-24 AP! When you press and release trim 2 things happen, it not only resets the deflection of the attitude holds, but there is a second autopilot law that it inherits from Mi-8: the autopilot will deflect the attitude holds in the same direction the stick moves to not fight the pilot and reduce the need for re trimming! You can see this on the ground, move the cyclic with R control + enter and you will see the autopilot channels follow your cyclic! This is why having autopilot on can actually INCREASE your control authority to an extent! However, to do this, it needs to know where “center” is. Oh Mi-8, it just took wherever your stick was when you turned it on, same as for attitude holds. So for Mi-24, your trim is resetting the attitude hold and where “center” is, so if you’re cyclic was previously commanding any autopilot deflection it goes away after pressing trim. When you press hat trim, it is also telling the autopilot to move this “center” but NOT moving the attitude holds. So it’s a sort of half measure and why of course in the end nothing can replace re trimming. You can see all this work on the ground. Move your cyclic right, you will see roll autopilot deflect right. Hold it there. Hold right hat trim, you will see the roll autopilot steadily go back to center as your “center” is moving right.

Dogon is just the MPRF mode every MiG-29 has. You are referring to “SP” or “Free Space” mode where targets where plotted by azimuth-velocity, and was supposedly so disliked by Soviet MiG-29 crews it was removed after 2-3 batches, thus you won’t see any pictures with it really.

What evidence is there of that? All I know is that both 9.12 and 9.12A use Parol-2D. 9.12B is using more similar to Kremnij-2M of MiG-21/23 with 8BK code selector. In addition, differences between 9.12 and 9.12A are that 9.12A is using N-019E and export version of KOLS, though both are supposed to have identical performance to their domestic counterparts. In addition the 9.12A is missing Cipher 4-15 on its Datalink panel, which means it cannot connect to any Beryuza datalink ground stations, thus limiting them to Lazur/Vozduch-1M.

It seemed to me that Flappie just labeled in an easy to misunderstand way, and really meant diameter even though the mark is only for radius on the picture. Likely because they measured radius then doubled it to get the correct measurement.

Ah, makes sense! So it is diameter!

Interesting! That does explain why Petro can acquire so much despite using narrow, I had no idea it was using 7.33/22 degrees as a radius and not diameter. The manual does warn of the sight being blocked in a left hand turn while looking left, so if it was half that I guess it wouldn’t be so true. The sources we have don’t indicate if this number is radius or diameter at all

I mean we know for a fact the narrow FOV is 7.33 degrees and the wide 22. Shouldn’t be hard to verify those.

Yes it did. But not 9.12A. I know we both wish it was a domestic model Anyways That is what Cipher #4-15 is for (Beryuza). 1-3 is for Lazur-M. These pictures are for 9.12A and 9.13 but should also apply to 9.12 and 9.12A The Cipher number correlates to number of groups/fighters that can be sent at once to one target, so 3x per target is Lazur limit and Beryuza 12. One graph here shows 13 for Cipher of Lazur-M, but I think it’s mistranslation of 1-3. Im sure this is why if you look at pictures of domestic 9.12/9.13, they often have their cipher knob at 4, becuase they using the more advanced Beryuza system. For some reason they must not have wanted to export Beryuza, or knew that customers wouldn’t have the required ground stations. A lot of 9.12 I’ve seen seem to have the Cipher knob at 4 so that they are in “Beryuza” mode.

The knobs are mechanically connected to the movement of the reticule, so if CCIP causes the reticule to move, the knobs will also move. Only in manual mode the serves that move them are disconnected. Option A 1. Turn switch from ASYNC to SYNC 2. Put pipper on moving target 3. After 2-3 seconds, pipper will lag 4. Re align pipper with target, and its motion will be compensated Option B (my preference) 1. Turn switch from ASYNC to SYNC 2. Follow target with some lead. If moving left to right put them on left side of side. If moving down to up put them on bottom of sight. 3. Sight will begin to lag, but since you were already leading the target slightly this will mean a smaller correction is needed to “re align the pipper with target.” If you have flown a gyro sight in something like MiG-15/19/21, it is same logic, completely based on distance and angular movement. So since Option B requires less maneuvering to re align pipper after it begins to lag, it not only allows faster targeting because less movement is necessary but because the increased turn rate to re align the pipper with target won’t cause such a large difference for the pipper. I have been using the function to lead low flying helicopters, and it works very well! Just need to be aware that since more distance equals more correction needed, the pipper will be extremely jumpy at the max 3-3.5 km range of the sight. Once you get closer, it will both jump less and take less time to “settle,” just like how a gyro sight in a MiG-15/19/21 will jump less and settle faster at close range rather then long.

I wouldn’t say biggest, but it’s definitely a big impact on “feel!” They are lucky they are choosing something with only Lazur-M, Su-27 has Lazur-M, Beryuza, Raduga, 2 SPK protocols lol.

I mean. I know I was personally very surprised when I learned that there is no symbol placed over a target (except for the gimbal indicator and placing your nose on them like a MiG-21), and no target altitude/speed shown without datalink. If datalink is truly early access, and there isn’t say, an up to date EWR on that person or you are surprised, you might have to play it safe because it’ll be harder to tell who you have locked up and their current performance. It will take some skill!

So. Trying to make a list of what to expect, would appreciate if anyone can come up with stuff I can’t! No target marker, diamond now shows radar antenna deflection on 70 by 45 degrees HUD scale 2. Circle now shows IRST target deviation and intercept trajectory in radar mode 3. Right HUD border and elevation/HUD carats are only on IPV/HDD 4. No display of mode 5. No display of PRF except commanded PRF for Lazur GCI 6. No display of Target speed except by datalink 7. No display of Target height except by datalink 8. Barometric altitude in 100s of meters instead of 10s 9. Radar altimeter only in 10s of meters rather then every meter 10. Missiles will only show ready after preparation time, which will happen early if you lock before being in missile range but if you lock within missile range will take 4 seconds 11. TDC box size will change depending on mode 12. Range scale will change only depending on 3 the PRF settings and locked target range and cannot be changed 13. Navigation circle shows where to point nose rather then bank 14. Double deflection gun mode available (described in manual as targeting invisible target, activated or de activated by pressing Ku-31 slew/laser activation button) 15. No heading tape with locked target 16. No target aspect shown with IRST lock, and limited laser range and limited opportunities for radar ranging What is one advantage we will get other then getting an interception cue at the price of no target marker? IPV/HDD will show radar bar being scanned, Seeing what bar is being scanned when you get a radar contact might help tell you their elevation Likely we will get the “r” symbol which according to our delta H knob postion, It’ll have us fly under or over the target by the set altitude and then zoom to equal altitude right before missile range. Might help if you want to do low altitude approach then zoom to target Ranging to jamming targets by turning side to side with 30 degree bank as radar gimbal limit diamond slides from one wing of artificial horizon silhouette to the other Being able to mess with IRST gain Better radar dynamics, including zero closure filter, hopefully false targets, instead of needing any look up angle to get notch removed it will be 5 degree minimum. Hopefully MPRF/ZPS is more aspect agnostic compared to FC3 where it has half the range in front aspect as it does rear. IRST will only have 30 degrees azimuth and pitch angle, instead of 60 Also you won’t have delta H +/-1 as many times as you want but 1/2/4/6/8/10 Expect longer IRST and radar lock times, minimum 2 seconds for radar and 1.5 seconds for IRST Gimbal limits of radar will be +56/-38, rather then +/-60, and HUD diamond will show vertical deviation of gimbal on +/-45 degree scale rather then 60 degeee scale it is in FC3 Eventual datalink. Depending on how it’s implemented it might only show closest target or the target that will meet you first with a 4.5s update rate, and give you commands like afterburner if you’re slow, tell you how much to climb, and turn on radar when within range and automatically gate the target. You could also use IRST though you will have to manually lock the target. You won’t be able to change target. Target directions will be shown horizontally with a small circle on +/-45 degree scale using 3 different intercept trajectories at GCI choosing. As mentioned earlier only with datalink will HUD show PPS/HPRF or ZPS/MPRF, and only show target speed and altitude with datalink. Additionally radar using 6 bar rather then 4 bar scan with smaller scan zone that increases as range closes. Single bomb drop using training switch Correction for wind for rockets, guns, ams bombs. All wind/movement correction need a manual designation vs automatic in FC3 (which gives us auto wind correction for bombs atleast). You will dive on target, hold lock button, release it on target, and after 2-3 seconds when you place pipper on target the difference will be calculated and correction show. HMD in FC3 only shows search, lock by following the target, and then launch authority with the flash and outside gimbal limits with the X. It will likely ne similar graphical presentation as BS3, where it will show search as the ring, then flash for radar/IRST lock, crosshairs if Fox 2 is locked on, and flashing crosshairs for launch authority. When outside gimbal limits it will completely turn off. One interesting thing is I mentioned the cooperation switch that ties Radar and IRST together. In helmet and OPT modes it searches using both sensors at once, and first one to lock will be primary sensor. This cooperation switch might surprise users who are used to IRST/radar always picking up lost lock of other. By default the sensors won’t interact, but when moving cooperation switch forward they will. This also locks radar into MPRF/ZPS. So it cannot be used for all situations, thought MPRF should align with IRST range rather well. I have seen different info that selecting R-27R/ER might force it to use radar as primary, and verifiable info that if you have IRST lock but outside laser range, pressing lock will transition to radar. I’ve seen different sources saying that either it will try to laser range IRST target for 8 seconds before using radar, and other implying it will be instant until within laser range. Either way radar ranging with IRST track has special HUD symbol for range bar. Flare program allowing huge customization and 3 different modes, a default, a double mode, and a ground mode that automatically releases flares when weapons are released when in this mode. Flare usage will also automatically double above 6k meters. ARU being able to be selected to max deflection, this will bypass the 7-8 G turn restriction we have in FC3 (unless this is a bug and fixed in FM). You will be able to have your fuel range estimate change from the current FC3 “range you will have flying with the current throttle level and speed” to an “optimal” setting that tells you how high your range could be in perfect conditions, allowing you to get them as close as possible. You will have to deal with the 3-6.5 km range of your laser. Ground move will also thus be limited to 5 km, no more lofting bombs from 5-10 km away or dropping weapons from huge angles and altitudes above 5 km unless using the radar altitude/angle ranging backup that will be used if laser not available or burned out. Toss bombing (over the shoulder), if anyone is would want to do that! We should have much more realistic SPO-15, though unfortunately not the version that shows if x band radar is within or outside 15-20 km. We will have one less range zone, as its manual shows there is only one antenna for 50-90 degree zones, and it only determines if they are 90 degrees if there is enough overlap with the rear antenna on that side. Since the rear antenna also has less gain, this means that if implemented this way, at long range and 80-90 degree aspect it will still show “50,” then show “50/90” at closer range to say “they are 80-90 degrees from you. Along with of course the different categories, such as pulse and PD fighters split up, and no EWR/AWACs will be able to be seen on it. 3 waypoints, 3 airfields, simplicity! With RSBN correction won’t need to worry about drift! Weapon selector only has 2 positions. More simplicity! Goodbye R-27/R-73/R-60 loadout! We’ll have a working EKRAN! Without black shark we can take part in “WATCH EKRAN” !!! Noobs will be able to flip a switch that stops you from locking onto friendlies with radar? Less friendly fire maybe????? Of course there will be other differences with being able to interact with nearly all the cockpit objects, but these ones I expect to surprise some people.

The exact skin in the banner is a default skin in the game. The stripes don’t exactly make it hard to tell.

The banner is a Su-33 with a J-15 skin