Octav

April 1st... :mrgreen:

One more thing, Olgerd - in chapter 5, "Operation in combat", the fi0 mode is described as being of use in case all the other modes fail (thus so are the RLS and TP). Yet, you still have to set the PPS/ZPS switch (so it supports the theory that it's used to alter some parameters in the IR missiles, based on the attack hemisphere, not in the onboard systems). Octav

Hello Olgerd, I also found the gain function referenced in my copy of the manual, in Chapter 8, subchapter "aircreft armament". I don't think this function is limited to some aircraft batches only. Our 29's were delivered between 1989 and 1992, and even the 9.13 model we had had this function - if this function wasn't necessary, I think they could have removed the ZPS/PPS labels, and kept only the SNP label on one side of the switch. But, there is absolutely no reference that the pilot has to place the switch to PPS if he's in V mode, or in ZPS if he's in D mode, to enable SNP - SNP is enabled by placing the switch to PPS position. So maybe this sould be in the list for the new patch, after 1.1 (if now this thing is too late to be done). And, one more thing - in the same chapter, at the subchapter describing the weapons system controls, the function of the PPS:ZPS switch is described as, and I quote : "the SNP:PPS/ZPS switch function is to select the engagement of the SNP mode, when placed in the SNP:PPS position, and to select the attack hemisphere, when the currnet distance to the target is missing in the SHLEM, OPT, TP, FI0 modes", end quote. And, by the way, KY comes from кнoпка управления, and it seems that everything related to weapons systems control in that aircraft has the -31 in int's designation - you have the PSR-31 main weapons systems control panel, the PUR-31 radar control panel, the PU-S-31 cannon and bombing control panel, and the PK-31 control panel. ;) Cheers, Octavian

Hello Andrew, and a Happy New Year. The BAZA (base) knob is located on the main armament control panel (on the front upper left part of the instrument panel, on the left of the alpha/G indcator). It is the knob nearest to the alpha/G indicator, and it has 2 functions - first one is to enter the target's wingspan, for the usage of the cannon in funnel mode. Also, based on that, the weapons computer (SUV) adjusts the sensitivity of the R-27's proximity fuse. The knob's position starts from Small (fully turned to the left), to Medium (center) and Large (fully right). If no accurate data on the target's wingspan is known, the following positions are used: Small for drones and cruise missiles, Medium for fighters, and Large for bombers. The KU (actually it is written in Russian KY) switch is the leftmost switch on the stick. It is a four-way switch (left/right, up/down), used to control the STROB (target designator box). It can also be depressed, triggering a fifth switch, which has several functions. In SNP mode, depressing it allows the pilot to move the strob to another target, and releasing it will instruct the computer to prioritize that target. Also, when jamming is present, in a lock-on-jam situation, by depressing the switch you cand then enter the distance to the target manually, by keeping the switch depressed and moving it up/down, to move the arrow on the distance scale. I hope this was clear. Cheers, Octavian

Ok then.. I'll wait to 1.15 :D Regarding the info - the pilot's manual states the fact that the switch is used to set the attack hemisphere only if the distance to the target is missing, and the pilot told me (and his source was a Russian missile engineer, which came here to assist some live firing tests) that based on that switch, or the target's aspect (if known), the SUV will adjust the gain of the seekers. Well, we already know that the SUV can alter parameters in the missiles, based on the position of cockpit switches and knobs - one example is the roximity fuse gain of the R-27's radio fuze, based on the position of the BAZA knob. And this is also documented in the manual. Octav

Re: Devs, please read - Russian radar related (again) Are you sure about this function of the switch? Can you call sources of the info? Hello Olgred - well, the manual clearly states the fact that the switch position is only useful when the distance (and hence the aspect) to the target is unknown. And a pilot told me that the seeker head gain is adjusted depending on target aspect, which makes sense - otherwise, why use it only when you don't have a distance, and leave it to ZPS otherwise? Octav P.S. By the way, any chances the devs might fix the way the SNP:PPS/ZPS switch works ( not necesarily the seeker head gain part, but the way it is used to select SNP - and the fact that SNP uses ONLY medium PRF)

Re: Devs, please read - Russian radar related (again) All of them are still in vacation? :drinkers:

Hello devs, Happy new year, first of all. I've noticed some things in Cat's review, regarding the N-019 radar, that I want to discuss about: The ony switch that selects the encounter/pursuit mode is the V/D/AVT switch - this one controls the PRF AND the doppler filter banks, appropriate to each mode. The SNP:PPS/ZPS switch has no control over the PRF and the Doppler filter bank selection - in V or D mode, setting it to SNP:PPS will enable SNP mode. Setting it to ZPS will disable SNP mode. It's real function is to select seeker head gain for IR missiles, when the distance to the target is missing (so it's used mainly in the optical modes, when there is no laser distance to target, or when jamming is ussed, depending on the aspect of the target: ZPS for rear aspect (less gain), PPS for front aspect (more gain). So, normally, you only use the SNP:PPS/ZPS switch when you want to enable SNP - you do not have to fiddle with it every time wou switch radar modes. Another thing is the detection ranges in the AVT mode - the only limitation it has is compared to the V mode, which has a max range of 150 km, versus only 100 in AVT mode. Otherwise, receding targets will be detected at the same range as in D mode - the only problem with the AVT mode is that it's scan time is double - instead of scanning the four lines like H:H:H:H (in V mode) or M:M:M:M (in D mode), the radar scans in 2 interleaved full frames H:M:H:M, then M:H:M:H, so if you have a target that's at 67 km, it will appear in one scan frame, then it will disappear in the other, until it will be close enough to be detected in D mode. One more thing about SNP mode - usually the radar's computer automatically selects the most dangerous target, and, via another switch, is instructed wether to automatically lock the target when almost in the range of the currently selected weapon - how will the player be able to change the target (in real life, the pilot will press the KU switch on the stick, and then move the strobe to another target), and if we will have the option to choose wethwr to auto-lock the target or not. This should be it (for now). All the best, Octavian P.S The source is the flight manual and pilot info.

D-Scythe - let's talk on your comments, one by one: - regarding "miss"iles and "hitt"iles :lol: I'm not sure how much info you have regarding the live firing of russian missiles - believe me, even an old R-60, which had it's useful lifetime expired for 2 years, managed to hit a flare, if fired under the right conditions - and target flares wobble quite a bit, because of their parachutes - from that aspect they can be more maneuvrable sometimes than a target drone. So please allow me to "acuse" :D you of being subjective. - as far as I know, every missile, at least from the Sidewinder B and the K-13 era and so far on, had impact and proximity fuses (some of them have self-destruct timers, as well, but not all of them - one example being the R-27) - having 2 types of of fuses is't a waste, after all - the impact fuse is quite cheap, compared to the proximity fuse and other important components in the missile, and after all, a direct hit is the desogn goal of a missile - that expanding rod or blst/fragmentation warhead will do more damage if it explodes in a confined space (inside the target, for example), than if it will detonate in the proximity of the target - for it's cheapness, an inpact fuse is also a backup system - the proximity fuse is armed some time after the missile leaves the rail, for safety reasons - you don't want it to proximity detonate near the launching platform, so it may fail to arm properly later on. And a prox fuse is quite small - a spring-loaded switch, with a damper, designed not to make contact to the acceleration forces of the missile, but to make contact on an impact - it's pretty much failsafe, due to it's simplicity. And proximity fuses, either radio or laser, have a lot of components that can fail, especially on older missile generations (before the 120 and the 77). Do not forget that a lot of AA missiles were using vacuum tubes, and those hat the bad habbit of failing more often than necessary :D. Even the transistor era missiles weren't much better, and even in today's state of the art electronics, all those vibrations and shocks mai losen wires, connectors and other parts. GGTharos - well, interesting fact with that AIM-7 truck kill - but that guy was going pretty fast to exceed even the smallest noth gate on the F-15's radar... Well, happy new year guy's - I'm leaving to a mountain resort for the new year, so I'll see you next year. Cheers, Octav

The proximity fuse is looking at the sides, not at the front - so a direct hit detonation via the impact fuse is the only way to do it - and i think you could disable a ZSU-23 or a Gepard with such a thing - of course, if another damage model is implemented, instead of the curret life bar - for example, a hit by an R-73 would definetly trash the Gepard's radar.... Octav

Well, there should be something already done, since they implement some sort of IR mapping in 1.1 - didn't play with the A10 so much, so I don't remember exactly what's the situation in 1.02. Well, I'm not sure if all the APC's ant tanks or other vehsicles carry IR jammers and flares - so.... And since they are launched in bore mode against a contrasting non-maneuvering target (I wouldn't call an APC maneuvrable by a missile's point of view), this shouldn't be a problem. Octav

Hello devs, Merry Christmans and a Happy New Year (in advance). One question - browsing through the MiG-29 manual, I've remembered one very intetresting feature: in OPT mode, you could use the R-60 and the R-73 missiles as guided A-G missiles, by locking their seekers onto ground IR contrasting targets - could you consider introducing that feature (not necesarily in 1.1)? It would be quite interesting, and an R-73 I think it could be used to disable a light armoured vehicle. Cheers, Octav

Re: LO 1.02 bug report psst.... The Su27 has NO ailerons... FLYING CONTROLS: Four-channel analogue fly-by-wire, with no mechanical back-up; artificial feel; relaxed longitudinal stability; no ailerons; full-span leading-edge flaps and plain inboard flaperons controlled manually for take-off and landing, computer-controlled in flight; differential/collective tailerons operate in conjunction with flaperons and rudders for pitch and roll control; flight control system limits g loading to +9 and normally limits angle of attack to 30 to 35?; angle of attack limiter can be overruled manually for certain flight manoeuvres; large door-type airbrake in top of centre-fuselage. Octav

Re: Any news about a release date ? already out... that was a sick joke - my hart missed a beat. :wink: :twisted: :twisted: :twisted: :twisted: :twisted: :twisted: :twisted:

C удовольствием, мой дорогой друг :D Octav

Seems it measures only the fuel flow that goes in the combustion chamber - the AB flow is not measured, as it is transfered by another pump. Octav

Re: Any news about a release date ? already out... It's already available for download, since December 1st. Go to the downloads section, it's there. Octav

OK - if you manage to find something out please let me know. And maybe the devs would consider modifying the way D is introduced. Octav

Hello Andrew, I'm very sure - you can find this in the MiG-29 weapons systems usage manual, which was on the net a while ago - I think you have it. Also, it is detailed in the pilot's manual. It is part of the training to adjust dH, if you loose the target while moving the STROB (gate) towards an inner altitude. By the way, the elevation is calculated for the point between scan bars 2 and 3 - so at the upper and lower limits of the scan patterns, elevation is up or down by about 7 degrees, if I remember correctly - so this should be able to lossen up the problem a bit. Let me give you some numbers: Case 1: D mode, dH 2km, STROB moved to 25 km Center elevation angle is 4.6 degrees, upmost part of the scan zone is at 11.6 degrees, lower partt of scan zone is at -2.4 degrees. At the 25 km range, the antenna scans a vertical zone from -1.1 km to 5 km - so aprox 6 km. At the maximum range of the D mode, the antenna scans from -2 to +10 km - so that is 12 km - I think there is a large enough magin of error. Case 2 : AVT mode, dH -1 km, STROB to 50 km Center elevation angle is -1.15 degrees, vertical angular scan zone ranges from +5.85 to -8.1 degrees. Vertical scan zone, in km, at 50 km is from -7.1 to +5.1 km, and at max range for the mode, the antenna scans from -14 to +10 km from the aircraft's altitude. Let's have here a case 2b, as most players I think would use that mode, with dH set to +1, and D set to 33 km: Center elevation 1.75 degrees, full vertical scan zone goes from -5.3 to +8.75 degrees, at the set distance that means from -3 to +5 km, and at max range from -9.2 to +15.2 km. Case 3 : V mode, dH +4km, STROB to 75 km Center elevation angle is 3.1 degrees, angular vertical scan zone from -3.9 to 10.1 degrees, in km at the set distance that means from -5.2 to +13.1 km, and at max range for that mode it will go from -10.3 to +26.2 km. Based on the numbers above, and with a bit of practice, it shouln't present too much probems - maybe we'll get the GCI instructions in the near future, to compensate :). By the way, could you please comment on the issue about the loss of lock while in a roll at low altitudes, which I think shouldn't happen below a certain range - maybe 10-15 km or so? Check my earlier post for details. Cheers, Octavian

by the way, looking at the bug fixes list, I've noticed the following thing: The way of changing dH is good, but D is altered in real life by moving the target designator box on the radar scope - is it possible to implement it the same way? It would save 2 more keys or buttons (apart from being realistic) Octav

Drako_MDx, you should remove the pic from your sig - read the first sticky of the forum Thanks, Octav

Thanks Andrew, now that's an explanation... but how is this "probability" implemented? Any help of somme lobby over there for the implementation, in the next patch, of the target boxes specific to each mode? I believe that now the V mode geometry is used for all modes. Octav EDIT - there seems to be something missing, though... In the close combat modes, I've never heard anything about loosing lock while flying inverted and low. Should it be the fact that the distances involved alre low (below 10 km) and thus the sidelobe is far smaller than the target's signal? If this is the case, then the loss of lock in the BVR modes should happen only beyond certain distances... isn't it?

Thanks Mark, Could you try a complete roll in a BVR lock mode, at low altitude (below 100m), and at about 20-30 km to target, so that the issue isn't masked by a switch to TP (EOS) mode? Octav

bump... Chizh, Han, any answers?

If the seeker loses it's target, does it look for a new one, coast, or detontate? It will NOT detonate - the R-27 has no timer - so it will coast until it finds a target, if not it will loose energy until ut crashes into the ground - ant it will be detonated on ground impact. Octav