Kenan Posted March 29, 2016 Posted March 29, 2016 Quick question: MIrage 2000C radar shows range values in NAUTICAL miles? [sIGPIC][/sIGPIC] Commanding Officer of: 2nd Company 1st financial guard battalion "Mrcine" See our squads here and our . Croatian radio chat for DCS World
Voodooflies Posted March 29, 2016 Posted March 29, 2016 Quick question: MIrage 2000C radar shows range values in NAUTICAL miles? Yes. [sIGPIC][/sIGPIC]
jaguara5 Posted March 29, 2016 Posted March 29, 2016 TDC data: Range (left center) Max search altitude (right top) Min search altitude (right bottom) Altitudes are in Fight Level values e.g: 319 == 31900 feet. I thought that the Flight Level is displayed with 2 digits http://rafalefan.e-monsite.com/medias/images/2000c.jpg Perhaps this is a different version
Azrayen Posted March 29, 2016 Posted March 29, 2016 Nope, the version if good & you're right, just a confusion (already reported). My mistake, I guess, I spoke of FLs (when it's not!) in an earlier discussion about this Zeus.:doh: It shoudl indeed be 2 digits, and (accordingly) thousands of feets.
jaguara5 Posted March 31, 2016 Posted March 31, 2016 (edited) Two more questions : 1) moving up/ down the TDC on the display souldn't change the radar range ? 2) Are we get in the near future the ccm Auto lock / magic seeker slave functions? Edited March 31, 2016 by jaguara5
jojo Posted March 31, 2016 Posted March 31, 2016 Two more questions : 1) moving up/ down the TDC on the display souldn't change the radar range ? Yes, like FC F-15C. Mirage fanatic ! I7-7700K/ MSI RTX3080/ RAM 64 Go/ SSD / TM Hornet stick-Virpil WarBRD + Virpil CM3 Throttle + MFG Crosswind + Reverb G2. Flickr gallery: https://www.flickr.com/gp/71068385@N02/728Hbi
jaguara5 Posted April 1, 2016 Posted April 1, 2016 When switching from PID to PIC (stt) a number appears to left of the TDC (where without any lock the range is displayed). Is this the aspect angle to the target?
mattebubben Posted April 3, 2016 Posted April 3, 2016 What means PIC and PID? IIRC PID is TWS and PIC is STT. Could be the other way round but i think that was the order =P.
Voodooflies Posted April 3, 2016 Posted April 3, 2016 (edited) IIRC PID is TWS and PIC is STT. Could be the other way round but i think that was the order =P. Correct ! :thumbup: Moreover if you wanna learn some french : *PIC = Poursuite sur Information Continue *PID = Poursuite sur Information Discontinue Edited April 3, 2016 by Sacha [sIGPIC][/sIGPIC]
Exo7 Posted April 3, 2016 Posted April 3, 2016 Au pluriel les informations ;) Non mais allo quoi ! [sIGPIC][/sIGPIC]
spiddx Posted April 3, 2016 Posted April 3, 2016 Je ne comprends rien. Merci. Oh là là! :music_whistling: Specs: i9 10900K @ 5.1 GHz, EVGA GTX 1080Ti, MSI Z490 MEG Godlike, 32GB DDR4 @ 3600, Win 10, Samsung S34E790C, Vive, TIR5, 10cm extended Warthog on WarBRD, Crosswinds
Aeons Posted April 4, 2016 Posted April 4, 2016 does anyone know why I get this circle on screen everytime I land and rearm?
Aeons Posted April 4, 2016 Posted April 4, 2016 This is linked to the POL (police) mode. ok but even when im not in police mode I get this. no matter what I do it wont go away
Fer_Fer Posted April 4, 2016 Posted April 4, 2016 well, a few observations, ran a few tests against IL 78M's and for some dark reason, the RDI just drops the contact at random moments. secondly the RDI's ability to burn through jamming is nil, is this working as intended?
Azrayen Posted April 4, 2016 Posted April 4, 2016 secondly the RDI's ability to burn through jamming is nil, is this working as intended? By nature, this can't be right. So if your observation is correct (didn't check myself), then you must assume radar vs jammer is still WIP ;)
jojo Posted April 4, 2016 Posted April 4, 2016 well, a few observations, ran a few tests against IL 78M's and for some dark reason, the RDI just drops the contact at random moments. secondly the RDI's ability to burn through jamming is nil, is this working as intended? I don't what version of DCS are you using. But in 1.5.3 stable release, I can lock in PSIC (STT) a Su 27 with ECM pod at 42Nm (which may be over performing BTW). My PSIC attempt were broken at further distances. But I didn't check every nautical miles. Mirage fanatic ! I7-7700K/ MSI RTX3080/ RAM 64 Go/ SSD / TM Hornet stick-Virpil WarBRD + Virpil CM3 Throttle + MFG Crosswind + Reverb G2. Flickr gallery: https://www.flickr.com/gp/71068385@N02/728Hbi
SFJackBauer Posted April 4, 2016 Posted April 4, 2016 (edited) Are the TDC slew axes not working yet? And, in the final version, will we have a radar elevation axis? Actually, is it even working right now on beta? Ive mapped Home and End to RADAR ANTENNA UP/DOWN on Sensors page but I dont see any change in the scope. Edited April 4, 2016 by SFJackBauer
Azrayen Posted April 4, 2016 Posted April 4, 2016 Are the TDC slew axes not working yet? Yes, for some time now (no change in last version AFAIK); you still want to avoid setting much saturation on those axis, as doing so "break" them. Actually, is it even working right now on beta? Ive mapped Home and End to RADAR ANTENNA UP/DOWN on Sensors page but I dont see any change in the scope. I use keyboard/HOTAS buttons for this (no axis) and it works like a charm. This too is not brand new, been there for some time now. And yes, changes are visible on the scope.
SFJackBauer Posted April 4, 2016 Posted April 4, 2016 Yes, for some time now (no change in last version AFAIK); you still want to avoid setting much saturation on those axis, as doing so "break" them. I use keyboard/HOTAS buttons for this (no axis) and it works like a charm. This too is not brand new, been there for some time now. And yes, changes are visible on the scope. Glad to know its just me... :D Well not glad. I can't figure out how to fix it. My TM Warthog and my keybindings works fine in all other modules. Any ideas? (except for reinstalling, because this has just been installed from scratch) The slew works with the default keyboard keys (,.;/), but the axis does not work no matter how I fiddle with them. The Sensors page have no default keybinds set at all, but if I bind some of them they work (like the Azimuth NARROW/WIDE), but none of the antenna left/right/up/down work. Did I somehow got an earlier version of the module? I installed it inside the DCS 2.0 itself. (And yes, the radar is turned on, in EM mode, I can see the antenna sweep indicator on top and even co-altitude blips.
Azrayen Posted April 4, 2016 Posted April 4, 2016 Been a while since 2.0 was updated. I was talking about 1.5 actually.
Zeus67 Posted April 8, 2016 Author Posted April 8, 2016 (edited) These are the changes that will come for the 1.5.3 stable release: I think this little table provides a better understanding of the next changes made to the radar: PRF limitations. Doppler filtering limits and RCS based detection are not enabled and depends on ED confirming some data. Doppler filter indicates the possiblity that ground clutter is filtered out. At 0% the contact can be masked by the ground. DEC = Terrain Advoidance. Cannot enable until AG radar is available. Next Issue is the Lock/unlock, TWS/STT buttons. No changes have been made yet but they will change. As of now, the LOCK button now does the following: 1. Locks the target and put the radar in TWS mode. 2. Toggles between TWS and STT modes. To unlock you will have to use the UNLOCK button. On next iteration the functionality will be: 1. UNLOCK button will become a LOCK/UNLOCK toggle. 2. LOCK button will become a TWS/STT toggle. It will only work if there is a locked contact. This way we will better simulate the actual HOTAS button functions. Note: I already know that I marked the wrong button in the stick, but the issue remains. SHB = STT + TA Edited April 8, 2016 by Zeus67 1 "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." "The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."
karl_T Posted April 8, 2016 Posted April 8, 2016 I think this little table provides a better understanding of the next changes made to the radar: PRF limitations. Doppler filtering limits and RCS based detection are not enabled and depends on ED confirming some data. Doppler filter indicates the possiblity that ground clutter is filtered out. At 0% the contact can be masked by the ground. DEC = Terrain Advoidance. Cannot enable until AG radar is available. This will be very helpful . Will this table be published in the manual?
Zeus67 Posted April 8, 2016 Author Posted April 8, 2016 This will be very helpful . Will this table be published in the manual? I made some changes but I was out of time. The entire radar chapter will be rewritten for clarity once it is finalized (soon I hope). "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." "The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."
Recommended Posts