AvroLanc Posted March 23, 2019 Posted March 23, 2019 So one of the updates in the hotfix was 'Change sidewinder HUD movable reticle to show only center of scan pattern' I'm assuming this was a correction that was needed? Was the old behavior wrong? I actually think the old Sidewinder behavior was better since it gave an indication that the seeker was scanning versus not scanning. Can devs confirm that the seeker still scans in the new mode? Does the cage/seam button still have the same effect? Playing around with it and it feels a lot less intuitive / clear as to what seeker head is doing....... I don't like, but if it's real behavior......
Naquaii Posted March 23, 2019 Posted March 23, 2019 (edited) The change was due to new information. The seeker itself is still doing the same thing, it's just the HUD visuals that changed. Edited March 23, 2019 by Naquaii
AvroLanc Posted March 23, 2019 Author Posted March 23, 2019 hmmm... Feels like a backward step. It's cheeky to ask but, is this 100% verified from more than one source? Your original modelling seemed more logical. I was under the impression as well that the seeker could be uncaged from boresight mode, and this was a change being looked at? Many thanks Naquaii, amazing work.
Naquaii Posted March 23, 2019 Posted March 23, 2019 The seeker being able to be uncaged from boresight is fixed, if not in now it will be next patch.
Top Jockey Posted March 23, 2019 Posted March 23, 2019 So one of the updates in the hotfix was 'Change sidewinder HUD movable reticle to show only center of scan pattern' I'm assuming this was a correction that was needed? Was the old behavior wrong? I actually think the old Sidewinder behavior was better since it gave an indication that the seeker was scanning versus not scanning. Can devs confirm that the seeker still scans in the new mode? Does the cage/seam button still have the same effect? Playing around with it and it feels a lot less intuitive / clear as to what seeker head is doing....... I don't like, but if it's real behavior...... hmmm... Feels like a backward step. It's cheeky to ask but, is this 100% verified from more than one source? Your original modelling seemed more logical. I was under the impression as well that the seeker could be uncaged from boresight mode, and this was a change being looked at? Many thanks Naquaii, amazing work. I also have my share of doubts on this matter, but the devs are inclined to the possibility that the symbol doesn't move... It has been mentioned already. https://forums.eagle.ru/showthread.php?t=236661 Jets Helis Maps FC 3 JA 37 Ka-50 Caucasus F-14 A/B MiG-23 Mi-8 MTV2 Nevada F-16 C MiG-29 F/A-18 C Mirage III E MiG-21 bis Mirage 2000 C i7-4790 K , 16 GB DDR3 , GTX 1660 Ti 6GB , Samsung 860 QVO 1TB
Victory205 Posted March 23, 2019 Posted March 23, 2019 ...Your original modelling seemed more logical. .... Why does it seem more logical? Fly Pretty, anyone can Fly Safe.
Top Jockey Posted March 23, 2019 Posted March 23, 2019 Why does it seem more logical? Essentialy because besides the AIM-9 audio growl tone, the seekerhead symbol scanning a specific zone in the HUD worked like sort of a "visual cue" also. After all, the VSL Low and PAL modes, do feature the diamond symbol scan pattern... Jets Helis Maps FC 3 JA 37 Ka-50 Caucasus F-14 A/B MiG-23 Mi-8 MTV2 Nevada F-16 C MiG-29 F/A-18 C Mirage III E MiG-21 bis Mirage 2000 C i7-4790 K , 16 GB DDR3 , GTX 1660 Ti 6GB , Samsung 860 QVO 1TB
Naquaii Posted March 23, 2019 Posted March 23, 2019 Ok, was misinformed as I've been away for a while. The change is that when slaved to a STT or TCS track it will now be directly slaved to that line of sight, no scanning. Sry for that.
AvroLanc Posted March 23, 2019 Author Posted March 23, 2019 (edited) Ok, was misinformed as I've been away for a while. The change is that when slaved to a STT or TCS track it will now be directly slaved to that line of sight, no scanning. Sry for that. Ok, so just so that I can clarify....we should see the scanning cue (double D) when no STT (old behaviour) but when locked to STT then seeker head should jump straight to STT and not scan around that.... If so, then yes, this seems much more logical. Maybe the old DD behavior will make it back? Edited March 23, 2019 by AvroLanc
Top Jockey Posted March 23, 2019 Posted March 23, 2019 Ok, so just so that I can clarify....we should see the scanning cue (double D) when no STT (old behaviour) but when locked to STT then seeker head should jump straight to STT and not scan around that.... If so, then yes, this seems much more logical. Maybe the old behavior will make it back? No, I'm afraid they meant that, there will be no "double D" visible at the HUD whatsoever... Jets Helis Maps FC 3 JA 37 Ka-50 Caucasus F-14 A/B MiG-23 Mi-8 MTV2 Nevada F-16 C MiG-29 F/A-18 C Mirage III E MiG-21 bis Mirage 2000 C i7-4790 K , 16 GB DDR3 , GTX 1660 Ti 6GB , Samsung 860 QVO 1TB
AvroLanc Posted March 23, 2019 Author Posted March 23, 2019 (edited) No, I'm afraid they meant that, there will be no "double D" visible at the HUD whatsoever... hmmmm that's not how I read Naquaii's post. He says there should be no DD scanning in a slaved state with a STT lock. This was old behavior and admittedly was a bit odd. Indeed, this was the change that should have been made..... This leaves the possibility that with a non slaved state, we should see the DD. I'm 90% convinced it's modeled wrong now. Edited March 23, 2019 by AvroLanc
Top Jockey Posted March 23, 2019 Posted March 23, 2019 hmmmm that's not how I read Naquaii's post. He says there should be no DD scanning in a slaved state with a STT lock. This was old behavior and admittedly was a bit odd. Indeed, this was the change that should have been made..... This leaves the possibility that with a non slaved state, we should see the DD. I'm 90% convinced it's modeled wrong now. I wish you were right - for me it also made all the sense the seekerhead symbol's scan pattern to be visible at the HUD. (But they mentioned, the pilots said it itsn't.) Again, the VSL Low and PAL modes (for instance), do feature the diamond symbol's scan pattern - so I really don't know why the AIM-9 seeker wouldn't. Jets Helis Maps FC 3 JA 37 Ka-50 Caucasus F-14 A/B MiG-23 Mi-8 MTV2 Nevada F-16 C MiG-29 F/A-18 C Mirage III E MiG-21 bis Mirage 2000 C i7-4790 K , 16 GB DDR3 , GTX 1660 Ti 6GB , Samsung 860 QVO 1TB
AvroLanc Posted March 23, 2019 Author Posted March 23, 2019 Can you link to where they said it wouldn’t be changed? I’m all for realism and if it 100% doesn’t depict the DD scan then fine, but something smells fishy and I think a piece of SME information has been misinterpreted somewhere along the line.
Naquaii Posted March 23, 2019 Posted March 23, 2019 The Double-D scan is removed completely, while a really cool function visually as far as we know it wasn't present in the modelled F-14. Some of our documentation is quite old, detailing functionality that was later removed. The remaining function of the BRSIT mode is the ability to force the AIM-9 to ADL even with a target.
Top Jockey Posted March 23, 2019 Posted March 23, 2019 The Double-D scan is removed completely, while a really cool function visually as far as we know it wasn't present in the modelled F-14. Some of our documentation is quite old, detailing functionality that was later removed. The remaining function of the BRSIT mode is the ability to force the AIM-9 to ADL even with a target. Ok then. By curiosity, did that function existed let's say, in the F-14A for the AIM-9G, (or any other airframe/missile configuration) ? Jets Helis Maps FC 3 JA 37 Ka-50 Caucasus F-14 A/B MiG-23 Mi-8 MTV2 Nevada F-16 C MiG-29 F/A-18 C Mirage III E MiG-21 bis Mirage 2000 C i7-4790 K , 16 GB DDR3 , GTX 1660 Ti 6GB , Samsung 860 QVO 1TB
AvroLanc Posted March 23, 2019 Author Posted March 23, 2019 Ok then. By curiosity, did that function existed let's say, in the F-14A for the AIM-9G, (or any other airframe/missile configuration) ? Yeah, that was going to my question. Presumably yes, since they have at least some supporting documentation, in that case maybe we can get the functionality back when the A is released.
Top Jockey Posted August 12, 2019 Posted August 12, 2019 Just to revive this mater. Although the movable reticle "double D" search pattern was removed, have anyone ever wondered: Why would "Fleet Defender" producers (MicroProse), featured a movable reticle (with circular search pattern) from the start ? Jets Helis Maps FC 3 JA 37 Ka-50 Caucasus F-14 A/B MiG-23 Mi-8 MTV2 Nevada F-16 C MiG-29 F/A-18 C Mirage III E MiG-21 bis Mirage 2000 C i7-4790 K , 16 GB DDR3 , GTX 1660 Ti 6GB , Samsung 860 QVO 1TB
Fri13 Posted August 12, 2019 Posted August 12, 2019 Just to revive this mater. Although the movable reticle "double D" search pattern was removed, have anyone ever wondered: Why would "Fleet Defender" producers (MicroProse), featured a movable reticle (with circular search pattern) from the start ? TOP GUN? i7-8700k, 32GB 2666Mhz DDR4, 2x 2080S SLI 8GB, Oculus Rift S. i7-8700k, 16GB 2666Mhz DDR4, 1080Ti 11GB, 27" 4K, 65" HDR 4K.
AvroLanc Posted August 12, 2019 Author Posted August 12, 2019 Just to revive this mater. Although the movable reticle "double D" search pattern was removed, have anyone ever wondered: Why would "Fleet Defender" producers (MicroProse), featured a movable reticle (with circular search pattern) from the start ? Haha, just when I’d got over this issue! Microprose probably we’re using similar reference material? This argument did occur to me months ago. I think we just have to go with HB now on this.
Top Jockey Posted August 12, 2019 Posted August 12, 2019 (edited) TOP GUN? Given the effort they've shown in depicting many realistic aspects avionics wise, I don't think so. (I mean, if they gave their best to realistically depict many other avionic features, why fictionalize at that one?) Also, they have publicized (at that time), the extensive research and counseling they had with NAS Oceana people. Edited August 12, 2019 by Top Jockey Jets Helis Maps FC 3 JA 37 Ka-50 Caucasus F-14 A/B MiG-23 Mi-8 MTV2 Nevada F-16 C MiG-29 F/A-18 C Mirage III E MiG-21 bis Mirage 2000 C i7-4790 K , 16 GB DDR3 , GTX 1660 Ti 6GB , Samsung 860 QVO 1TB
Recommended Posts