Kondor77 Posted August 18, 2019 Share Posted August 18, 2019 (edited) I can't get Jester to give me a correct waypoint via the F10 menu. Is this a bug? Attached pictures of what I see. This happens in SP and MP. Starting cold/hot doesn't seem to make a difference. Cold I always go to fine alignment. Anyone else getting this? I have a feeling it's something on my end since I can't find any other posts on this. Edited August 20, 2019 by IronMike Link to comment Share on other sites More sharing options...
Knock-Knock Posted August 18, 2019 Share Posted August 18, 2019 Yes https://forums.eagle.ru/showthread.php?t=247681 - Jack of many DCS modules, master of none. - Personal wishlist: F-15A, F-4S Phantom II, JAS 39A Gripen, SAAB 35 Draken, F-104 Starfighter, Panavia Tornado IDS. | Windows 11 | i5-12400 | 64Gb DDR4 | RTX 3080 | 2x M.2 | 27" 1440p | Rift CV1 | Thrustmaster Warthog HOTAS | MFG Crosswind pedals | Link to comment Share on other sites More sharing options...
IronMike Posted August 20, 2019 Share Posted August 20, 2019 Thank you, this is already fixed internally and will be included in the next patch. Heatblur Simulations Please feel free to contact me anytime, either via PM here, on the forums, or via email through the contact form on our homepage. http://www.heatblur.com/ https://www.facebook.com/heatblur/ Link to comment Share on other sites More sharing options...
grant977 Posted August 21, 2019 Share Posted August 21, 2019 I don’t think this made today’s patch just fired up the jet cold start with stored heading alignment and still exists. Link to comment Share on other sites More sharing options...
IronMike Posted August 22, 2019 Share Posted August 22, 2019 No, sorry, what I meant was the next regular patch, the hotfix only reflected on our black wing hotfix and the ARAK fix for the Viggen. Heatblur Simulations Please feel free to contact me anytime, either via PM here, on the forums, or via email through the contact form on our homepage. http://www.heatblur.com/ https://www.facebook.com/heatblur/ Link to comment Share on other sites More sharing options...
viper2097 Posted August 22, 2019 Share Posted August 22, 2019 Tested it today with the Viggen on the NTTR map and everything was fine, so was the NTTR not affected? Steam user - Youtube I am for quality over quantity in DCS modules Link to comment Share on other sites More sharing options...
grant977 Posted August 22, 2019 Share Posted August 22, 2019 Cool no worries thank you for the clarification. Link to comment Share on other sites More sharing options...
IronMike Posted August 24, 2019 Share Posted August 24, 2019 Tested it today with the Viggen on the NTTR map and everything was fine, so was the NTTR not affected? Likely, in this case. Heatblur Simulations Please feel free to contact me anytime, either via PM here, on the forums, or via email through the contact form on our homepage. http://www.heatblur.com/ https://www.facebook.com/heatblur/ Link to comment Share on other sites More sharing options...
draconus Posted August 24, 2019 Share Posted August 24, 2019 But the F-14B still bugged even on NTTR. Just FYI Win10 i7-10700KF 32GB RTX3060 Rift S T16000M TWCS TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria Link to comment Share on other sites More sharing options...
leonardo_c Posted August 24, 2019 Share Posted August 24, 2019 Tested today the Viggen and it was working perfectly. The Tomcat appears still broken though. ;) Entering coordinates manually still works however. My DCS Campaigns - DOWNLOAD Link to comment Share on other sites More sharing options...
-IRRE-Rolluptito Posted August 28, 2019 Share Posted August 28, 2019 Not solved for me, I still have the problem. (Tested on Persian Gulf, cold-started and with fine alignement) Owned modules: P-47 | P-51D | Spitfire MkIX | I-16 | Bf 109 K-4 | Fw190 D-9 | Fw190 A-8 | Yak-52 | MiG-15 | F-86F | C-101 | A-10C | AJS-37 | L-39 | F-5E | M-2000C | MiG-21bis | F-14 | AV-8B Harrier II | F/A-18C | F-16C | FC3 | Ka-50 | SA342 | UH-1H | Mi-8MTV2. Maps: Syria, Nevada TTR, Persian Gulf, Normandy 1944, & The Channel. Hardware: GeForce 1080TI, I7 7700K, 32GB RAM. https://www.lesirreductibles.com - Link to comment Share on other sites More sharing options...
viper2097 Posted August 29, 2019 Share Posted August 29, 2019 Viggen is fixed, Tomcat ist broken. HB did already fixed it internally, but ED decided to not make an OB update this week. So we'll have to wait for the next OB to fix that issue. Steam user - Youtube I am for quality over quantity in DCS modules Link to comment Share on other sites More sharing options...
RSharpe Posted August 29, 2019 Share Posted August 29, 2019 Are all waypoints set by Jester broken, not just those designated on the F10 map? I've been trying to enter waypoints in manually through the Jester menu. In every case, Jester will only allow me to enter the first 5 digits. It won't allow me to enter the 6th digit, so instead of N 42 55 19, I would get N 42 55 1. Jester simply stops inputting after the 5th digit, and moves on. I think this is the same problem as the F10 map. Unfortunately, ED chose not to roll out a beta update this week, so I'm not sure if this has been internally addressed. Link to comment Share on other sites More sharing options...
near_blind Posted August 29, 2019 Share Posted August 29, 2019 Are all waypoints set by Jester broken, not just those designated on the F10 map? I've been trying to enter waypoints in manually through the Jester menu. In every case, Jester will only allow me to enter the first 5 digits. It won't allow me to enter the 6th digit, so instead of N 42 55 19, I would get N 42 55 1. Jester simply stops inputting after the 5th digit, and moves on. I think this is the same problem as the F10 map. Unfortunately, ED chose not to roll out a beta update this week, so I'm not sure if this has been internally addressed. Thats not a jester issue, the Tomcat's INS only stores coordinates to the first seconds digit. Welcome to the 1970s. Link to comment Share on other sites More sharing options...
draconus Posted August 30, 2019 Share Posted August 30, 2019 Thats not a jester issue, the Tomcat's INS only stores coordinates to the first seconds digit. Welcome to the 1970s. So for N 42 55 19 I should rather input N 42 55 2, right? Win10 i7-10700KF 32GB RTX3060 Rift S T16000M TWCS TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria Link to comment Share on other sites More sharing options...
near_blind Posted August 30, 2019 Share Posted August 30, 2019 So for N 42 55 19 I should rather input N 42 55 2, right? That's best practice, but if we're being real honest the difference between 42 55 1 and 42 55 2 is ~1000 feet. I can't imagine doing anything in the Tomcat reliant upon the INS alone where that sort of error really matters. Link to comment Share on other sites More sharing options...
draconus Posted August 30, 2019 Share Posted August 30, 2019 That's best practice, but if we're being real honest the difference between 42 55 1 and 42 55 2 is ~1000 feet. I can't imagine doing anything in the Tomcat reliant upon the INS alone where that sort of error really matters. I could think of this http://www.heatblur.se/F-14Manual/weapons.html#computer-initial-point Win10 i7-10700KF 32GB RTX3060 Rift S T16000M TWCS TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria Link to comment Share on other sites More sharing options...
Recommended Posts