Wicked.- Posted December 21, 2019 Posted December 21, 2019 While in RWS and TWS I was unable to scale out the radar range by moving the cursor up. Neither myself nor a friend I was flying with were able to do it. [sIGPIC][/sIGPIC] Intel i9 9900K @ 5.1Ghz HT Disabled, Asus RoG Strix z390E Gaming, 64GB G.Skill Trident Z 3200, Asus RoG Strix RTX2080Ti OC @ 1.9Ghz, 1TB Samsung Evo 970Pro M.2 TM Warthog, CH Pro Pedals, Saitek Pro Rudder Pedals, Samsung 49" Curved Gaming Monitor, Samsung 50" 4KUHD TV, Acer 27" Touch Panel, CV1, Pimax 5K+, Valve Index, FSSB3 Lighting, F-16SGRH, 3 TM Cougar's and a Saitek X36 that I can't bring myself to part with.
unknown Posted December 21, 2019 Posted December 21, 2019 Works for me in RWS not in TWS, SP here. 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
Emmy Posted December 21, 2019 Posted December 21, 2019 Already documented that you can’t bump the range in TWS. [sIGPIC][/sIGPIC] http://www.476vfightergroup.com/content.php High Quality Aviation Photography For Personal Enjoyment And Editorial Use. www.crosswindimages.com
Wicked.- Posted December 22, 2019 Author Posted December 22, 2019 Already documented that you can’t bump the range in TWS. I guess I didn't look hard enough! Roger that! [sIGPIC][/sIGPIC] Intel i9 9900K @ 5.1Ghz HT Disabled, Asus RoG Strix z390E Gaming, 64GB G.Skill Trident Z 3200, Asus RoG Strix RTX2080Ti OC @ 1.9Ghz, 1TB Samsung Evo 970Pro M.2 TM Warthog, CH Pro Pedals, Saitek Pro Rudder Pedals, Samsung 49" Curved Gaming Monitor, Samsung 50" 4KUHD TV, Acer 27" Touch Panel, CV1, Pimax 5K+, Valve Index, FSSB3 Lighting, F-16SGRH, 3 TM Cougar's and a Saitek X36 that I can't bring myself to part with.
Dee-Jay Posted December 22, 2019 Posted December 22, 2019 (edited) Hi! Already documented that you can’t bump the range in TWS. I don't know on what document you have seen this (?) ... For F-16C BLK 40/42 & 50/52 (APG68 radar), in TWS, range scales are changed as in RWS. But ... the range scale will not decrease if the TOI cannot be displayed on the lower range scale. The range scale will automatically decrement when the TOI is at a range less than 45% of the range scale, and when the ACQ cursor is less than 5% of the range scale. Note also that the TOI will force an auto range scale increase when its range approaches the maximum range of the currently displayed range scale. That is how the system is designed and how it works on the real stuff. Regards. Merry Xmas to everyone! Edited December 22, 2019 by Dee-Jay ASUSTeK ROG MAXIMUS X HERO / Intel Core i5-8600K (4.6 GHz) / NVIDIA GeForce RTX 3080 Ti FE 12GB / 32GB DDR4 Ballistix Elite 3200 MHz / Samsung SSD 970 EVO Plus 2TB / Be Quiet! Straight Power 11 1000W Platinum / Windows 10 Home 64-bit / HOTAS Cougar FSSB R1 (Warthog grip) / SIMPED / MFD Cougar / ViperGear ICP / SimShaker JetPad / Track IR 5 / Curved LED 27'' Monitor 1080p Samsung C27F396 / HP Reverb G2 VR Headset.
Frederf Posted December 22, 2019 Posted December 22, 2019 Dee Jay, by HAF document TWS range bumping is explicitly said not allowed. But of course this document is for a different, older version. I don't know if this is different for APG-68v5 of BLK50 ~2007. If you have better info you should share it with devs.
Dee-Jay Posted December 22, 2019 Posted December 22, 2019 (edited) That is basically what I am doing (more or less) ;) ... it is not something that we can't found elsewhere on other sim". But I won't send such documents for obvious reasons. Dee Jay, by HAF document Not the -1 right? But the 3-4 correct? (I don't refer to GR docs as DCS-F16 is not HAF version) Edited December 22, 2019 by Dee-Jay ASUSTeK ROG MAXIMUS X HERO / Intel Core i5-8600K (4.6 GHz) / NVIDIA GeForce RTX 3080 Ti FE 12GB / 32GB DDR4 Ballistix Elite 3200 MHz / Samsung SSD 970 EVO Plus 2TB / Be Quiet! Straight Power 11 1000W Platinum / Windows 10 Home 64-bit / HOTAS Cougar FSSB R1 (Warthog grip) / SIMPED / MFD Cougar / ViperGear ICP / SimShaker JetPad / Track IR 5 / Curved LED 27'' Monitor 1080p Samsung C27F396 / HP Reverb G2 VR Headset.
Wicked.- Posted December 23, 2019 Author Posted December 23, 2019 Hi! I don't know on what document you have seen this (?) ... For F-16C BLK 40/42 & 50/52 (APG68 radar), in TWS, range scales are changed as in RWS. But ... the range scale will not decrease if the TOI cannot be displayed on the lower range scale. The range scale will automatically decrement when the TOI is at a range less than 45% of the range scale, and when the ACQ cursor is less than 5% of the range scale. Note also that the TOI will force an auto range scale increase when its range approaches the maximum range of the currently displayed range scale. That is how the system is designed and how it works on the real stuff. Regards. Merry Xmas to everyone! What I was referring to when using the cursor to scale out the radar range was simply that. Using the cursor to increase my scanning distance instead of the MFD OSB’s. I did not have any targets locked at the time. Am I not able to do this? Even when in NAV mode with the FCR page up? [sIGPIC][/sIGPIC] Intel i9 9900K @ 5.1Ghz HT Disabled, Asus RoG Strix z390E Gaming, 64GB G.Skill Trident Z 3200, Asus RoG Strix RTX2080Ti OC @ 1.9Ghz, 1TB Samsung Evo 970Pro M.2 TM Warthog, CH Pro Pedals, Saitek Pro Rudder Pedals, Samsung 49" Curved Gaming Monitor, Samsung 50" 4KUHD TV, Acer 27" Touch Panel, CV1, Pimax 5K+, Valve Index, FSSB3 Lighting, F-16SGRH, 3 TM Cougar's and a Saitek X36 that I can't bring myself to part with.
Dee-Jay Posted December 23, 2019 Posted December 23, 2019 to increase my scanning distance Maybe you already know that, but it doesn't change anything to "scaning"distance. radar power/gain remains the same. It only act on display. ASUSTeK ROG MAXIMUS X HERO / Intel Core i5-8600K (4.6 GHz) / NVIDIA GeForce RTX 3080 Ti FE 12GB / 32GB DDR4 Ballistix Elite 3200 MHz / Samsung SSD 970 EVO Plus 2TB / Be Quiet! Straight Power 11 1000W Platinum / Windows 10 Home 64-bit / HOTAS Cougar FSSB R1 (Warthog grip) / SIMPED / MFD Cougar / ViperGear ICP / SimShaker JetPad / Track IR 5 / Curved LED 27'' Monitor 1080p Samsung C27F396 / HP Reverb G2 VR Headset.
Frederf Posted December 23, 2019 Posted December 23, 2019 That is basically what I am doing (more or less) ;) ... it is not something that we can't found elsewhere on other sim". But I won't send such documents for obvious reasons. Not the -1 right? But the 3-4 correct? (I don't refer to GR docs as DCS-F16 is not HAF version) DCS has already decided that TWS doesn't have that feature. Either they don't know what you are saying or they're not allowing themselves to know it. I think a private message from you or something with proper knowledge would be the only way.
Dee-Jay Posted December 23, 2019 Posted December 23, 2019 Well ... if [CORRECT AS IS], then it is [CORRECT AS IS]. No big deal. There are other more "critical" things on other aspects for the time being. ASUSTeK ROG MAXIMUS X HERO / Intel Core i5-8600K (4.6 GHz) / NVIDIA GeForce RTX 3080 Ti FE 12GB / 32GB DDR4 Ballistix Elite 3200 MHz / Samsung SSD 970 EVO Plus 2TB / Be Quiet! Straight Power 11 1000W Platinum / Windows 10 Home 64-bit / HOTAS Cougar FSSB R1 (Warthog grip) / SIMPED / MFD Cougar / ViperGear ICP / SimShaker JetPad / Track IR 5 / Curved LED 27'' Monitor 1080p Samsung C27F396 / HP Reverb G2 VR Headset.
Wicked.- Posted December 24, 2019 Author Posted December 24, 2019 radar power/gain remains the same. It only act on display. This I did not know... I could have sworn I've used it like that in the past, both with the other Viper sim and DCS. No worries. If it's correct, then it's correct. [sIGPIC][/sIGPIC] Intel i9 9900K @ 5.1Ghz HT Disabled, Asus RoG Strix z390E Gaming, 64GB G.Skill Trident Z 3200, Asus RoG Strix RTX2080Ti OC @ 1.9Ghz, 1TB Samsung Evo 970Pro M.2 TM Warthog, CH Pro Pedals, Saitek Pro Rudder Pedals, Samsung 49" Curved Gaming Monitor, Samsung 50" 4KUHD TV, Acer 27" Touch Panel, CV1, Pimax 5K+, Valve Index, FSSB3 Lighting, F-16SGRH, 3 TM Cougar's and a Saitek X36 that I can't bring myself to part with.
antsh Posted January 3, 2020 Posted January 3, 2020 Radar Scale - Automatic Change I know this has been discussed somewhere, but I can't find it, so I figure I'd ask. Under what conditions does the radar scale automatically change with respect to the current range of a locked target? I know I have seen this behavior sometimes, and not others. I know it might be different under different situations; can someone confirm or edit the below statements: In STT lock mode: When the target closes to <45% of the current range scale, the range scale automatically decrements. For example: radar scale at 80nm, target is locked in STT and is out at 60nm. When it closes to under 36nm, radar range scale (and HUD Launch Zone scale) decrement to 40nm. I might have read somewhere that the radar cursor must also be in the lower 5% of the FCR, but not sure if that is true. In SAM lock Mode: Does the above take place or is it STT only behavior? In TWS mode with a bugged target: Does the above behavior also take place with a bugged target in TWS, or is it an STT only situation? Also, is the above true for different modes in reverse? When a target is cold and approaching the limits of the current radar scale, will it increment? Thanks!
Dee-Jay Posted January 3, 2020 Posted January 3, 2020 Hi! Here: https://forums.eagle.ru/showthread.php?p=4148599#post4148599 ;) Regards. ASUSTeK ROG MAXIMUS X HERO / Intel Core i5-8600K (4.6 GHz) / NVIDIA GeForce RTX 3080 Ti FE 12GB / 32GB DDR4 Ballistix Elite 3200 MHz / Samsung SSD 970 EVO Plus 2TB / Be Quiet! Straight Power 11 1000W Platinum / Windows 10 Home 64-bit / HOTAS Cougar FSSB R1 (Warthog grip) / SIMPED / MFD Cougar / ViperGear ICP / SimShaker JetPad / Track IR 5 / Curved LED 27'' Monitor 1080p Samsung C27F396 / HP Reverb G2 VR Headset.
antsh Posted January 3, 2020 Posted January 3, 2020 That's where I saw it! So, two questions around: "The range scale will automatically decrement when the TOI is at a range less than 45% of the range scale, and when the ACQ cursor is less than 5% of the range scale." 1. The ACQ cursor is the slewable box when using the TDC? 2. TOI is defined as an STT only, or does it apply to STT, SAM and TWS bugged targets?
Frederf Posted January 4, 2020 Posted January 4, 2020 1. Yes. Most accurately the control is called the cursor/enable switch (enable refers to the press in button aspect of the control.) The part of the display in CRM that you move around is called the acquisition cursor. 2. TOI is target of interest is defined in any mode that has a bug and applies in SAM, TTS, TWS, VSR, etc.
antsh Posted January 4, 2020 Posted January 4, 2020 (edited) Just checked and this doesn’t happen in TWS mode. Bugged a target at 60nm with a scale of 80nm. Kept tracking until he was within 10nm, and the scale remained at 80nm. Same experiment with an STT moves the scale down as he approaches as you’d expect. I’m assuming this is a bug or WIP because I can’t imagine a pilot would need to take his hands off the controls just to hit the osb. Note: this is different than bumping the scale which I know doesn’t work in TWS, but I assume scale changes as a toi approaches should still adjust? @Bignewey? Edited January 6, 2020 by antsh Emphasis
Frederf Posted January 4, 2020 Posted January 4, 2020 AFAIK TWS should range scale down just like RWS-SAM or STT based on bugged target position. It might not scale down if certain other interesting symbols might leave the display like AIM-120 guiding on farther tracks but otherwise yes.
antsh Posted January 4, 2020 Posted January 4, 2020 Bignewy said he’ll take a look. Mods, can we moved this to bugs?
antsh Posted January 7, 2020 Posted January 7, 2020 Can this be changed from correct as is since my other thread was merged into this? @Bignewy said he would investigate, please note my emphasis above, this is different than range bumping.
Deano87 Posted January 7, 2020 Posted January 7, 2020 Range bumping should work in the downward direction in TWS I believe. At least it did on the Danish AMs my brother flew. Proud owner of: PointCTRL VR : Finger Trackers for VR -- Real Simulator : FSSB R3L Force Sensing Stick. -- Deltasim : Force Sensor WH Slew Upgrade -- Mach3Ti Ring : Real Flown Mach 3 SR-71 Titanium, made into an amazing ring. My Fathers Aviation Memoirs: 50 Years of Flying Fun - From Hunter to Spitfire and back again.
antsh Posted January 16, 2020 Posted January 16, 2020 (edited) @BIGNEWY can you take a look at this one as well? I can't believe that the FCR doesn't reduce scale automatically in TWS mode (or that you can't decrease range manually, actually). Otherwise the pilot would have to either exit TWS mode, or take hands off the controls. This also has a knock on effect of having the DLZ scale being really compressed if you start using TWS while a bandit is say in the 80nm scale. Edited January 16, 2020 by antsh
Deano87 Posted January 16, 2020 Posted January 16, 2020 My bro who flew Danish F-16AMs for 4 years around 2012 told me that you can reduce range with the cursor while in TWS... In fact he was extremely confused while using my sim over Xmas why he couldn't. I don't see why the Block-50 would be different from that... but who knows. Proud owner of: PointCTRL VR : Finger Trackers for VR -- Real Simulator : FSSB R3L Force Sensing Stick. -- Deltasim : Force Sensor WH Slew Upgrade -- Mach3Ti Ring : Real Flown Mach 3 SR-71 Titanium, made into an amazing ring. My Fathers Aviation Memoirs: 50 Years of Flying Fun - From Hunter to Spitfire and back again.
Recommended Posts