-
Posts
3130 -
Joined
-
Last visited
-
Days Won
2
Content Type
Profiles
Forums
Events
Everything posted by IvanK
-
The radar had reliability issues but in its day was a pretty clever bit of kit .... certainly way way better than the MIG21 version we see in DCS. Quite a difficult radar to jam after it was locked on. The Gunsight likewise was pretty advanced and provided steering orders for all missiles and a NAV function as well. HOTAS 1960's style: Mirage III Radar Hand controller .... TDC plus other controls like Azimuth scan selection, Spiral scan acquire, Direct lock on, Wobulating lock on, break lock, Manual gain control and Antenna elevation control The R530 was unbelievably unreliable and probably more dangerous to the shooter than the target :) Mirage IIIO Radar in AG mapping mode Large Black area on the radar scope near the bottom is terrain shadow caused by a large mountain left of the nose.
-
Ahhh A true French Lady in DCS that would be something :) Poetry in motion Eats F5's for breakfast :)
-
So we have a logic problem. Most of the jamming we currently see is Noise jamming. That is the multiple azimuth strobes. Now for the first time (for me anyway) we see False target jamming effects in the Mir2K. However as I understand it this is because the Mir2K coders have chosen to show jamming as false targets. Take the situation you set up a Mig29S versus Mir2K and F15 and an SU27. The Mig29 is jamming, the F15 and SU27 sees this jamming as Noise jamming (Azimuth strobes), the Mir2K sees it as False target jamming .... alas the DCS MIG29s is coded as a noise jammer is he not ? So why should the Mir2K see false targets .... should it not be seeing the same jamming type as SU27 and F15 ? Perhaps the Mission designer should have the option to choose what jamming mode he wants the emitter to have ? .... That is Noise or false targets
-
My 2 Cents worth ... a Non FFB user. Seeing the pitch trim change with flap and gear is the important thing. If the trim change is there you will still react "naturally" by doing what you need to do with the Stick first to hold the desired nose position. So for a FFB user he applies a force for the non FFB user he moves the stick..... then both trim. Reaction to Flap and gear is going to very from type to type. To me the important thing is the trim change is present. IRL the pilot just does what is needed to counter the trim change ... there is no perceived I need to hold force or move the stick you just do what needs to be done.
-
If DCS can provide Noise and or False targets for the coders then logic says the option should be coded by the emitter. So as the receiver you will get to see the emitters jamming style. If I read it correctly in the Mir2K the coders have arranged so regardless of the emitters mode you only see jamming as false targets ?
-
Well that is good news as it adds to the ECM suite that coders can employ in DCS.
-
Eddie No I have not seen RGPO in DCS. So far the only airraft I have seen with False targets generated is the DCS Mir2K when going up against a DCS jammer.
-
Go on Eddie tell me .... When I see Jamming strobes all over my B scope I see noise jamming ...... When I see False discreet targets I am not seeing NOISE jamming, That is A false target generator ECM or repetitive jammer doing its stuff , When I see Locked targets rapidly moving I am seeing Range Gate Pull offs working.
-
Why are we seeing these False targets on the Mir 2K when we dont see them on any other aircraft in DCS ? As I understand it in DCS the only jamming modeled is Noise jamming. There are no false target generators in DCS. So imo all we should be seeing are jamming strobes ... like you see for the SU27/MIG29 and F15..... or however the RDI depicts them.
-
When are we likely to see R550 30deg x 30deg search and auto lock implemented ?
-
Hmmm a far better book and far more objective "Hostile Skies" by David Morgan ...none of the emotive FIGJAM stuff you find in Wards book :)
-
"I guess I need to read a little bit more into how jamming works to figure out if it makes even sense in terms of physics if narrowing the beam would mean faster burn through. Intuitively it seems so (the more focused beam could be distinguished from the noise created by the jammer earlier than a beam which energy is spread over larger area), but my intuition has been wrong before " In a former life using the Cyrano II in the Mirage III a standard technique to increase burn through range against a simple noise jammer was to Spotlight the target. This was done by stopping the antenna azimuth scan over the jamming strobe (Physically you placed the Lock on cursour or TDC at the same azimuth as the jamming strobe but not at target range). You then pressed the lock on lever. This then stopped the azimuth sweep and provided a narrow pencil beam. If successful the target blib would then appear in the jamming strobe, You now had Azimuth and range.... though of course this technique could also be taken by the jammer as an attempted Lock on also.
-
The pre purchase info says ...."Martin Baker SIII S-3 ejection seat" .... No such animal :) Most F5E's stuck with the original US Northrop seat. Some countries upgraded to a Martin Baker BRQ7A seat (Brazil and Iran for example). The SIII S-3 moniker sounds more like a Stencil seat designation ... not that the F5E was equipped with these either. The images released show the Belsimtek F5E to be equipped with the Northrop seat.
-
in the Mirage III the Bog Standard R530 had an Auto fire capability as well. With Auto Fire selected on the R530 would fire at a point known as Topt. this was about 2/3 of the Rmax of the missile. In current terminology you could consider it as Rmax2/Rttr
-
V1 is runway stop speed :), Vr is rotate speed :)
-
Probably closer to the FA18A avionics wise ... display format and mechanization was almost identical.
-
+1 great read and infinitely better than harrier over the Falklands by Sharkey Ward
-
"I think the radar can switch automatically from PID to PIC (FC3 radars do) on certain conditions but I'm not sure it's implemented right now. Didn't test that actually." Its an assumption but I would presume that if a Super R530D launch is tried from PID(TWS) the radar should attempt to go PIC(STT) automatically before launch. This is how the FA18A was with if an AIM7M launch was attempted on the TWS L&S target.
-
Thanks Rlaxoxo... not running any mods. might try editing the magictone sdf
-
Hear like helmet unticked ... will tick and try again
-
Even with the Miss Vol switch full clockwise the R550 tone is too soft imo.
-
Given its a straight pulse radar then very limited. It would rely on judicious pilot use of manual gain control and use of antenna elevation to maximize the use of side lobes (keeps target out of main beam clutter). lookdown detection ranges will be very low.
-
NCTR doesn't talk to the on board IFF interrogator. An NCTR ID just "adds" to the ID matrix
-
I figured that GG but its French :)