Sim Flyer Posted February 19, 2016 Posted February 19, 2016 Hey I am having some problems with the M2000C's radar, when i have a contact on the radar i lock him one time and i can see him on the HUD but when i try to lock him the second time to get guidance for the 530 then the radar turns blank and all contacts dissapear even the one i am trying to lock up. Is this a confirmed bug or me doing something wrong?
Zeus67 Posted February 19, 2016 Posted February 19, 2016 Hey I am having some problems with the M2000C's radar, when i have a contact on the radar i lock him one time and i can see him on the HUD but when i try to lock him the second time to get guidance for the 530 then the radar turns blank and all contacts dissapear even the one i am trying to lock up. Is this a confirmed bug or me doing something wrong? Hmm, no. First time I heard this. I made a fligth in 1.5.3 and had not problem with the radar. If the problem persists, please save a track file and send it to us. "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."
baltic_dragon Posted February 19, 2016 Posted February 19, 2016 I've had that happen to me occasionally but only when trying to lock at long ranges. Below 40 miles it never happened. For more information, please visit my website. If you want to reach me with a bug report, feedback or a question, it is best to do this via my Discord channel. Details about the WinWing draw can be found here. Also, please consider following my channel on Facebook.
PiedDroit Posted February 19, 2016 Posted February 19, 2016 I had this too in OB 1.5.3. I will try to make a track out of it if it happens again, in the release. Also, the radar unlocks when pressing lock again while already locked in PIC, which doesn't help. I don't know how it is in the real aircraft, but a lock button should never behave as unlock IMO :music_whistling:
Zeus67 Posted February 19, 2016 Posted February 19, 2016 I had this too in OB 1.5.3. I will try to make a track out of it if it happens again, in the release. Also, the radar unlocks when pressing lock again while already locked in PIC, which doesn't help. I don't know how it is in the real aircraft, but a lock button should never behave as unlock IMO :music_whistling: Ok, that could be on me. I'll check and fix. "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."
PiedDroit Posted February 19, 2016 Posted February 19, 2016 Ok, that could be on me. I'll check and fix. Cool thanks! Regarding that lock problem, I didn't have it again so far, in the release (100% sure I had it in 1.5.2, not so sure for 1.5.3). Maybe it's was only me hitting the lock button too much, will keep an eye open.
unknown Posted February 20, 2016 Posted February 20, 2016 I had this too in OB 1.5.3. I will try to make a track out of it if it happens again, in the release. Also, the radar unlocks when pressing lock again while already locked in PIC, which doesn't help. I don't know how it is in the real aircraft, but a lock button should never behave as unlock IMO Ok, that could be on me. I'll check and fix. Actually i like this behavior, one button less to configure on my HOTAS. ;) Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings
Voodooflies Posted February 20, 2016 Posted February 20, 2016 Actually i like this behavior, one button less to configure on my HOTAS. ;) Use a modifier. :music_whistling: [sIGPIC][/sIGPIC]
QuiGon Posted February 23, 2016 Posted February 23, 2016 I experience the same problem. The second press of the lock button doesn't hardlock the target but turns the radar screen blank (all contacts disappear including the target). The contact also doesn't show up on the HUD and the only way to get the radar back working is to press the unlock button. Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
millenix Posted February 23, 2016 Posted February 23, 2016 I can confirm same issue here. Millenix | 68th Virtual Fighter Squadron AV8B | AJS-37 | F-5E | Mig-21bis | P-51D | Spitfire Mk IX | Bf-109 | M-2000C | A-10C | U1-H1 | Ka-50 | FC3
Fab Posted February 23, 2016 Posted February 23, 2016 I dont get a blackout, but loose the contact, and get my radar picture wiped.... If I try to make hard lock, or lock on target allready locked... Intel Core i7-6700K Cpu 4.00 GHz OC 4.8 GHz Water Cooled|32 GB DDR4 ram OC| Nvidia RTX 2080Ti| TrustMaster Warthog|Saitek Battle Pro Pedals | Logitec G13| Oculus Rift S :joystick: I´m in for a ride, a VR ride:pilotfly: https://www.youtube.com/channel/UCBX_-Hml7_7s1dggit_vGpA?view_as=public
Zeus67 Posted February 24, 2016 Posted February 24, 2016 Hey I am having some problems with the M2000C's radar, when i have a contact on the radar i lock him one time and i can see him on the HUD but when i try to lock him the second time to get guidance for the 530 then the radar turns blank and all contacts dissapear even the one i am trying to lock up. Is this a confirmed bug or me doing something wrong? It is a bug caused by a self-check function. If the radar contact does not pass the check, the function resets the radar. This self-check function is required to prevent CTDs. Can you please provide the mission where this happened? "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."
QuiGon Posted February 24, 2016 Posted February 24, 2016 It is a bug caused by a self-check function. If the radar contact does not pass the check, the function resets the radar. This self-check function is required to prevent CTDs. Can you please provide the mission where this happened? I experience this bug when I'm flying the M2000 in the BlueFlag online campaign which is the only mission I play atm. It's not a rare problem, but happens with about 50% of the contacts I want to lock up. Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
Zeus67 Posted February 25, 2016 Posted February 25, 2016 I experience this bug when I'm flying the M2000 in the BlueFlag online campaign which is the only mission I play atm. It's not a rare problem, but happens with about 50% of the contacts I want to lock up. Ok. I will check. Actually I will enable a logging function in the target check. This way if it happens, you can send me the log file and I can see what is happening. Should be available for the next update. "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."
Madman777 Posted March 26, 2016 Posted March 26, 2016 I have this issue a lot. I assumed it was because I wasn't slewing the TDC cursor close enough for the second lock. And if I try to lock nothing, the screen goes blank. Sent from my SGH-M919 using Tapatalk i7-12700k, 32GB Ram, RTX 3060 12GB, TrackIR 5, Lots of SSD Space, etc etc DCS World - All the cool modules
speckfire Posted March 29, 2016 Posted March 29, 2016 I have this issue too. I loose contacts and drop lock Speed is life !!!
Slipp Posted March 29, 2016 Posted March 29, 2016 Same issue here. First lock works ok, second lock makes radar go blank.
Azrayen Posted March 29, 2016 Posted March 29, 2016 Guys, it may be "normal" (on some cases). The distance where you get a radar spot is > than the distance where you can secure a STT lock. TWS lock seems to be possible at same distance as radar spot; this may be the issue? Would crosscheck with other fighters...
speckfire Posted March 29, 2016 Posted March 29, 2016 Happens at any range with me Azrayen. Does not happen with the Migs, Su's and Eagle. Speed is life !!!
Azrayen Posted March 29, 2016 Posted March 29, 2016 Mhmm, perhaps I misunderstood. Are you talking about being unable to STT lock a contact you already have locked in TWS? That what I had in mind. If you're talking instead about radar loosing lock to easily (without pilot input) then it's a different issue.
Svend_Dellepude Posted March 29, 2016 Posted March 29, 2016 Are you talking about being unable to STT lock a contact you already have locked in TWS? That what I had in mind. This I think, because i have this issue too. When trying to STT lock the target from TWS, display blanks out and all info is lost. Regardless of range. I noticed that while in TWS the horizontal sweep marker at the top of the display is only visible on the other side of the screen from the target. At least while you are in 60° azimuth. [sIGPIC][/sIGPIC] Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD.
Azrayen Posted March 29, 2016 Posted March 29, 2016 When trying to STT lock the target from TWS, display blanks out and all info is lost. Regardless of range. Well I remember having this too, at long range; will check again at shorter ones, but can't remember of a problem there. I noticed that while in TWS the horizontal sweep marker at the top of the display is only visible on the other side of the screen from the target. At least while you are in 60° azimuth. Yep, saw that too; looks like a +/- bug to me. I'll report it to Razbam now that I have confirmation it's not only me :)
OldE24 Posted March 29, 2016 Posted March 29, 2016 (edited) yeah confirm this if target it FAR like 30+ miles if you try to STT it will drop the lock. ALSO IF you point your elevation UP and LOCK SOMEONE it points the radar down and WILL drop the Lock so almost no point of using the Elevation function right now. Quote: Originally Posted by Svend_Dellepude View Post I noticed that while in TWS the horizontal sweep marker at the top of the display is only visible on the other side of the screen from the target. At least while you are in 60° azimuth. Yep, saw that too; looks like a +/- bug to me. I'll report it to Razbam now that I have confirmation it's not only me I seem to only see this if you drop a lock it will go off to one side and you just slew to get it back to the TDC. Edited March 29, 2016 by OldE24 8700k@4.7 32GB ram, 1080TI hybrid SC2
speckfire Posted March 29, 2016 Posted March 29, 2016 If you're talking instead about radar loosing lock to easily (without pilot input) then it's a different issue. Yes this point exactly. Speed is life !!!
Recommended Posts