AeriaGloria

Hello, I spent the last few days over Lazur GCI guidance information and a Vozduch-M GCI manual. And it occurred to me a possibly easy way to implement it both quickly and a way that works with recent infrastructure that ED has made for their module eco system. You could adapt the Petro/George interface as a way of “talking to GCI.” You could go the way of “player is directed to closest/most dangerous target” and give them no control over it, and this might work out for EA, but it’s my understanding that pilots were usually in radio contact with their GCI often relating when they had radar contact at the very least. And this could be a way of simulating that while giving the player more options. You would have a bind to bring up the menu “Lazur Menu”, “up long” would cycle between “automatic target selection” using target type, range, and closure, and “manual target selection.” You could then use “up/down short” (just like DCS Mi-24P/AH-64) to cycle through a target list, with perhaps the HSI showing range, bearing and speed/altitude (or even just leave player to see this on HUD), and showing if any other MiG-29s are assigned the same target. You would then select the target with “right short,” and then use “left short” or “right short” again to select the 3 intercept geometries, intercept, chase (you could call it direct), and maneuver (or call this pursuit). If target selection is set to auto via “up long,” intercept geometry is automatically picked from the 3 depending on aspect to target when guidance begins (front-intercept, beaming- chase, rear- maneuver or even just chase), but you could still leave the option to manually change it with “left/right short.” You could just tie all coalition EWR together as one IAD, and base the range restrictions (90 km at 500m alt up to 350 km at 10 km alt) on closest/non terrain obstructed coalition EWR (avoiding the need to create new Vozduch-M GCI units). So the first 8 spawns would go, Spawn 1: Wave: 1, Cipher: 1, Separation: 1 Spawn 2: Wave: 1, Cipher: 1, Separation: 2 Then once you get to max Separation number of 8 (spawn 8= Wave:1, Cipher:1, Separation:8), next spawns would be Spawn 9: Wave: 2, Cipher: 1, Separation: 1 Spawn 10: Wave: 2, Cipher: 1, Separation: 2 It is My understanding that Cipher# is basically which of 3 groups are you, and Separation# one of 8 targets each IAD can store, each Lazur IAD network can send 3 groups/units/Cipher #s to 8 different targets each for a total of 24 groups controlled against 8 enemy groups/units. But for our purposes here everyone needs a “unique possible target” effectively limiting us to the 8 targets controlled by the separation dial and the wave number which decides IAD network. So by using separation number and wave number, that gives us up to 160 total unique spawns. Way more than any MP server would need leaving plenty of empty slots so no one “interferes.” Spawn 160 = Wave: 20, Cipher: 1, Separation: 8 Then start over again using any combination not currently used. Of course not entirely realistic to have 2 or more overlapping IAD networks, but it would still be somewhat realistic and most importantly engaging. In such an implementation, there would be no purpose to the “Cooperation” command that gives a 800 hz sound signal and requires pilot to move the dials to commanded position and press AUT, but perhaps it is just not needed and might help save development time. Or you could even have everyone spawn with a currently unused combo of the 160 Wave/Separation numbers, and when they manually select a target or choose auto select have them receive “cooperation” command and switch the dials and press AUT upon switching targets atleast the first time, as if you are being “handed” off to the IAD network with your assigned target. Maybe not the most realistic. But might work well in MP. This could also allow you to “funnel” all the active Lazur users into as few IAD networks as possible, and even have those assigned to the same target use the same Wave/Separation numbers but different Cipher number, just like how multiple groups would be guided to one target in reality. When target is changed you get “!” If altitude is less then target and no radar on command transmitted yet you get “B” to climb If speed is less then target you get “φ”For afterburner. Gorka “r” AFAIK is only depending on deltaH knob and target you have locked. To fly above/below until close to missile range then zoom towards ( other then its toss bomb use) If target disappears and no new target possible, display “ T.” Then, you basically have complete system!

Just the manual and ED campaign really. Things we know will be improved eventually but are not necessarily EA are stuff like R-60 locking onto ground (dependent on IR rework), visible cargo/passenger (cargo rework), other various system enhancements like more Petro voice lines and tweaking. L-166V will only come when early MANPADs are introduced like Redeye and Strela. Other than the manual and a campaign, it is very complete.

Yea, dust filter will visibly use up 2.5% thrust or so

Ah, thank you very much!!! If I wanted to edit the samples, is there a good resource for that?

The version with ATGM is using TV2 engines. Different and weaker than what we have. Mi-171 is basically a whole new module in terms of system management and displays

I think it would offer interesting gameplay as a more accurate weapon then S-5/8, but still less accurate then the nose gun atleast horizontally. Wouldn’t have the range of the rockets, but would open up being able to snipe single units in a way you need the majority of a rocket pod for. EDIT: damn, let me back track! I just read about its export use, 1. it required a separate position on the weapon selector; which would deter from the 100% USSR version we have. 2. And a bigger deal for me, it did not have CCIP! You have to aim manually! In such a case, your only aiming aid would be the scale telling you approximate range to target. So I rest my case, it might not actually be that accurate unless you were 2-3 corrections in. And barely more accurate than using it from Mi-8. Big sad

As others have said, it could be dust related. But check that temperature is not below 0 during flight, ice damage is cumulative. Even 5-10 minutes of flying in sub zero temps without anti icing will cause cumulative ice damage. It takes up 15-17% power, so you may need to quickly disable it in tough spots like landing takeoff or emergencies. A few minutes is fine. There is no gauge to check damage, however your EPR gauge is directly telling you how much torque the engines are putting out corrected for temperature and altitude. Get used to checking EPR when at cruise (8-11 degrees collective) and such and you will quickly notice when it’s too low. There is also no benefit to flying with rotor rpm between 87-91%, the governor commands full engine power at 92% rpm with default settings.

Thank you. It is the gametrix jetseat

The MiG-29B non Warsaw pact version would mostly have differences for the player only in IFF. Instead of automatically interrogating anything on radar, you need to manually press an interrogate button on the stick that replaces the normal “unlock” button. And on 9.12B, in order to then unlock a target you need to press a button in front of the throttle. On 9.12/9.12A, this button instead is a switch that allows the radar to lock on to only enemies or also friendly IFF signals. So to the player, if we got 9.12B the only extra thing we would need to do is manually interrogate, and we wouldn’t be able to have it only lock onto enemy contacts or both enemy/friendly. This thread has some good posts on it, you’ll just need to scroll down a bit https://www.secretprojects.co.uk/threads/soviet-russian-iff.792/#post-9051

Is there a way to create a profile that temporarily disables certain motors, such as the back ones? I have relatively minor back surgery I may need, and would really like to still use the leg motors which would pose no issue to me!

Are you by any chance confusing radar with IRST? The 29 IRST cannot be skewed up or down, only radar.

Look at two different Petro command graphics here. With your buttons found to up/down/left/right, up can if pressed shortly either -command search/ie designate -move up the list of acquired targets -change flare interval when entering countermeasure menu from short left press And a long press might either warm up weapons or change ROE. And if you are CPG, it does many different things. So you see, designate is only one of these functions.

I think USA mean to be both faster and longer range. Having the same turbo generator time is related to the modularity principle of construction. Any chart or mention of range will show it does 40-60% more

There is a table to change it according to barometric pressure, but generally you never touch it. The manual talks about 2 other uses of it though that both work in DCS. If you raise it all the way, your rotor and tail rotor spin faster. This gives you better control authority, especially at high altitude, and your autopilot more control, and overall more lift until you reach the power limit of the engines about 2-3% rpm below the normal speed (95% default, with 92% if you decrease it all the way and 98-99% if you increase it all the way). If you decrease it all the way to 92%, you have less lift, but gain 2-3% fuel economy. Conversely increasing it to max reduces fuel economy by 2-3%

Must’ve mistaken with MiG-29, thank you!

1. Petrovich up allows you to use any command associated with hat up, designate is only using the designate function 2. No, but you can always confirm that it is designating where you want by pressing Petrovich up short again 3. your periscope has 25-30 degree roll limits. Petrovich will often close them before you exceed this limit but not all the time. If you exceed those limits with it open your sight is effectively broken and won’t look straight. So before banking more then about 25 degrees always give Petrovich down short to close the sight. Just allow Petro auto closing it as a backup when you forget

This is not possible IRL unless you turn on training mode

I had a recent reaction, so let me update after I did some testing It is still using S-8 CCIP, but adjusted to the 4.5 degree lower mounting of the rocket. So if S-8 was fired 4.5 degree lower and had CCIP, it would be the CCIP you see with S-24 currently. The thing is, S-24 will always impact around d 1-1.5 degrees lower if fired from exactly the same angle. This means that if using S-24 and CCIP, don’t aim at the center of the pipper, but aim about halfway down or slightly lower. Maybe more like 2/3rds down. Set it to fire at medium or long burst so two fire in quick succession before the recoil really pushes the nose down fast Surprisingly, I haven’t been able to identify any boresight error, even if firing as far as 3 km away

It likely is connected to that a while ago there was a bug where the sight was stuck open when observing AI or any other player. ED fixed this to have it closed, but must’ve not been “complete” enough to also allow it to open back up when necessary, compared to the player model that does do it correctly.

I am just saying what ED has said, the memory mode is meant to continue R-27R/ER guidance when activated and lock regained inside gimbal limits. Whether there are documents that show this is how it should work in reality or not, the memory does work, just not when exceeding gimbal limits.

Hello, I realize I mentioned some of this in another thread today but let me clarify everything that both ED has said on this matter and what can be gleaned from documentation. 1. The datalink doesn’t mean you can press unlock and then regain it and have missile continue, this is an assumption. There are conditions that stop the 60 sec emission of the CW guidance beam, and pressing unlock button is one of them. If it goes into memory mode after losing lock naturally and either radar picks it back up within 3.5s of memory mode or IRST (within 15 km only, which must be a bug), it will continue guidance. The datalink is not there to allow you to unlock a target manual and regain it. And not all datalinks behave the same. There are only 2 “spaces” for datalink transmission by the radar, and by pressing “unlock” you are basically telling the radar to throw away the datalink/guidance of that missile and prepare a new one. 2. ED has said before that from documents they believe that exceeding gimbal limit causes complete loss of track and thus ceasing of CW emission. It is not the same as memory mode being entered due to loss of lock inside gimbal limits in this case. I’ll play your tracks though in a bit and see if I notice anything EDIT: okay, both tracks I see all 4 missiles the radar gimbal limit ts are exceeded which makes the missile go dumb. I know it’s tricky, but you just have to get as close to gimbal limits as you feel safe without exceeding it to crank.

Was this “lock the target inside 2 seconds” after manually unlocking or exceeding gimbal limits? Whatever AIM-7 does has no bearing on R-27R/ER

This is correct and intended. Pressing unlock cancels the pseudo CW emission that the missile guides off the reflection of. Only if it reacquires within the 3.5 sec memory time can it do this, or if system switches to IRST mode within 15 km so IRST guide the pseudo CW emission of the radar. Which I think must be a bug, as there is no reason to limit it to 15 km.

The backup move is automatic. If Doppler beaks, it will use IAS. No reason to use airspeed to DISS

It is mistake. Both MiG-29 and Su-27 have a switch that allows single missile launch and salvo. What you’re reading seems to imply that it will fire one of each type, but it would fire 2x of what you have selected. The manual also says it is up to the pilot to wait a set amount of time after firing a missile before firing an IR missile, depending on how long the motor burns. It also takes some time for the “missile preparation” when switching weapons.