VTJS17_Fire Posted July 8, 2016 Share Posted July 8, 2016 Hi, I don't know if it's a bug or if we did a big mistake with the ILS alignment and waypoint selection. Four of us did the full alignment, as described: + battery: on + ground power: on + PCN operational mode selector: STS + INS/ PCN mode selector: ALN + VAL button: push(ed) ... waiting 8 minutes for the class 1 aligment, until pret glows (not flashing) + set DEST: insert 01 My comrades did the same and we all got the same LAT/ LONG coordinates, with the parameter selector set to L/G. 1. But we all got different ranges on the HSI to our waypoint 1 (which is also set to bullseye), from 20,9 NM, to 32NM and 41NM. The bearing is same for all of us. The waypoint 01 is the same for all of us in the missioneditor. 2. If I switch to CP/PD I should get the heading and range in the INS display, but only got "-- - ---". I attached the screens from three of us, the mission and my trackfile. Maybe you can help us or confirm this bug. Track (50 Mb) PS: After a few tests, my comrade got other ranges everytime he choosed a slot or restarted the mission.AerialRefueling_Caucasus.miz Hardware: Intel i5 4670K | Zalman NPS9900MAX | GeIL 16GB @1333MHz | Asrock Z97 Pro4 | Sapphire Radeon R9 380X Nitro | Samsung SSDs 840 series 120GB & 250 GB | Samsung HD204UI 2TB | be quiet! Pure Power 530W | Aerocool RS-9 Devil Red | Samsung SyncMaster SA350 24" + ASUS VE198S 19" | Saitek X52 | TrackIR 5 | Thrustmaster MFD Cougar | Speedlink Darksky LED | Razor Diamondback | Razor X-Mat Control | SoundBlaster Tactic 3D Rage ### Software: Windows 10 Pro 64Bit [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
Cantiga Posted July 8, 2016 Share Posted July 8, 2016 Four of us did the full alignment, as described: + battery: on + ground power: on + PCN operational mode selector: STS + INS/ PCN mode selector: ALN + VAL button: push(ed) ... waiting 8 minutes for the class 1 aligment, until pret glows (not flashing) + set DEST: insert 01 Have you corrected the WP00(aircraft position) coordinates? 2. If I switch to CP/PD I should get the heading and range in the INS display, but only got "-- - ---". Make sure your waypoint(WP01) is selected by PREP. Link to comment Share on other sites More sharing options...
Rlaxoxo Posted July 8, 2016 Share Posted July 8, 2016 Did you select the PCN mode to Normal (N)? Have you put the INS/PCN to Nav mode? [sIGPIC][/sIGPIC] Youtube Reddit Link to comment Share on other sites More sharing options...
Azrayen Posted July 9, 2016 Share Posted July 9, 2016 1. See Cantiga's answer, you forgot a mandatory step. 2. No you should not. CP/PD is not to display heading/range. See Razbam's manual ;) 1 Link to comment Share on other sites More sharing options...
VTJS17_Fire Posted July 9, 2016 Author Share Posted July 9, 2016 Have you corrected the WP00(aircraft position) coordinates? No, thanks. Is this a real step or just an WIP issue which will be solved in the future? Make sure your waypoint(WP01) is selected by PREP. Yep, it was. Did you select the PCN mode to Normal (N)? Yes. Have you put the INS/PCN to Nav mode? Yes. Forgot to mention these two steps above. 2. No you should not. CP/PD is not to display heading/range. See Razbam's manual ;) Thank you. I thought, I saw that in the previous versions. Hardware: Intel i5 4670K | Zalman NPS9900MAX | GeIL 16GB @1333MHz | Asrock Z97 Pro4 | Sapphire Radeon R9 380X Nitro | Samsung SSDs 840 series 120GB & 250 GB | Samsung HD204UI 2TB | be quiet! Pure Power 530W | Aerocool RS-9 Devil Red | Samsung SyncMaster SA350 24" + ASUS VE198S 19" | Saitek X52 | TrackIR 5 | Thrustmaster MFD Cougar | Speedlink Darksky LED | Razor Diamondback | Razor X-Mat Control | SoundBlaster Tactic 3D Rage ### Software: Windows 10 Pro 64Bit [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
Derbysieger Posted July 9, 2016 Share Posted July 9, 2016 No, thanks. Is this a real step or just an WIP issue which will be solved in the future? AFAIK it is. According to the manual you need to check wether WP00 has the correct coordinates prior to the alignment: 3. Check that the Aircraft position in Latitude, Longitude and Altitude indicated by the PCN are correct. Change them as needed (see Data Entry for more information). INS Alignment is covered from page 90 onwards CPU: AMD Ryzen 9 5900X | Mobo: Gigabyte X570 Aorus Pro | RAM: 64GB DDR4 3600 G.Skill TridentZ | GPU: Palit RTX3080 Ti 12GB | SSDs: 2xSabrent Rocket 1TB M.2 | Samsung Pro 256GB | Samsung EVO 850 500GB | Samsung QVO 1TB Peripherals: Warthog HOTAS | TrackIR 5 | MFG Crosswinds | 3xTM Cougar MFDs | HP Reverb G2 Link to comment Share on other sites More sharing options...
Recommended Posts