dresoccer4 Posted March 23, 2020 Posted March 23, 2020 hi there, quick q: when attempting to initialize the INS, the lat/long numbers simply blink on and off and i can't change them (as shown in screenshot). i've tried turning the INS off and on again but that didn't reset it. i tried changing the alignment to stby/fast/nav and that didn't do anything either. any tips? [ATTACH]230462[/ATTACH] Acer Predator Triton 700 || i7-7700HQ || 512GB SSD || 32GB RAM || GTX1080 Max-Q || FFB II and Thrustmaster TWCS Throttle || All DCS Modules
AeriaGloria Posted March 23, 2020 Posted March 23, 2020 (edited) It usually happens before it’s in NAV but still in STBY but you said you did that. You didn’t move during alignment either? I don’t think its required but you pressed NAV on AAP? Edited March 23, 2020 by AeriaGloria Black Shark Den Squadron Member: We are open to new recruits, click here to check us out or apply to join! https://blacksharkden.com
dresoccer4 Posted March 23, 2020 Author Posted March 23, 2020 It usually happens before it’s in NAV but still in STBY but you said you did that. You didn’t move during alignment either? I don’t think TD required but you pressed NAV on AAP? sorry, still fairly new to this jet and don't have all the acronyms down yet. what do you mean press NAV on AAP? Acer Predator Triton 700 || i7-7700HQ || 512GB SSD || 32GB RAM || GTX1080 Max-Q || FFB II and Thrustmaster TWCS Throttle || All DCS Modules
Rudel_chw Posted March 23, 2020 Posted March 23, 2020 sorry, still fairly new to this jet and don't have all the acronyms down yet. what do you mean press NAV on AAP? Here I have a detailed startup procedure, check your own steps against mine, to see where they differ. https://1drv.ms/b/s!Ai6cuX3YQI26hqY40gQFLY9sxXOVBg For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar Mobile: iPad Pro 12.9" of 256 GB
dresoccer4 Posted March 23, 2020 Author Posted March 23, 2020 thanks for the responses. i restarted the mission and did a regular startup just fine. so i must have done something weird before. would be good to know how to remedy that situation in case i ever get in it again, bug it'll have to stay a mystery for now because i can't reproduce it Acer Predator Triton 700 || i7-7700HQ || 512GB SSD || 32GB RAM || GTX1080 Max-Q || FFB II and Thrustmaster TWCS Throttle || All DCS Modules
foxwxl Posted March 24, 2020 Posted March 24, 2020 Don't switch to FAST/NAV before you entered the WPT00 information. Power AAP-> input WPT 00 coordinates->switch to FAST/NAV/GC to start alignment. If you use FAST make sure you input the true heading of A/C. If things go wrong, INS to standby, AAP INS power off(hold it for serval seconds), and try start again. Deka Ironwork Tester Team
dresoccer4 Posted March 30, 2020 Author Posted March 30, 2020 ... If things go wrong, INS to standby, AAP INS power off(hold it for serval seconds), and try start again. it happened again, the blinking. this was AFTER i put in waypoint 00 coordinates, then switched INS to NAV.i tried following your instructions of switch NAV to STBY and holding INS for several seconds until it turned off. but once i clicked INS again to turn it on, the coordinates immediately resume blinking. need to find another way to reset the INS calibration, because currently it seems stuck in a loop :helpsmilie: Acer Predator Triton 700 || i7-7700HQ || 512GB SSD || 32GB RAM || GTX1080 Max-Q || FFB II and Thrustmaster TWCS Throttle || All DCS Modules
dresoccer4 Posted March 30, 2020 Author Posted March 30, 2020 i think i figured it out. this happens if the coordinate direction switches. in this example the N switched to a S. this causes the whole thing to lock up even after restarting the entire INS. once you switch the S back to N it lets you continue Acer Predator Triton 700 || i7-7700HQ || 512GB SSD || 32GB RAM || GTX1080 Max-Q || FFB II and Thrustmaster TWCS Throttle || All DCS Modules
uboats Posted March 31, 2020 Posted March 31, 2020 since in current dcs, no map covers both N/S or E/W. So by default, no need to touch the sphere when entering coord. [sIGPIC][/sIGPIC] My DCS Mods, Skins, Utilities and Scripts | Windows 10 | i7-4790K | GTX 980Ti Hybrid | 32GB RAM | 3TB SSD | | TM Warthog Stick | CH Pro Throttle + Pro Pedal | TIR5 Pro | TM MFD Cougar | Gun Camera: PrtScn |
unknown Posted March 31, 2020 Posted March 31, 2020 since in current dcs, no map covers both N/S or E/W. So by default, no need to touch the sphere when entering coord. That is not entirely true, the Normandy map covers the Prime meridian(E/W). 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
Recommended Posts