Draken35 Posted November 5 Posted November 5 49 minutes ago, DasSven said: Thanks for the quick reply. So basically you're thinking that the success of the keypress timing relates to FPS? Maybe that's why it works flawlessly on my VR system and intermittent on my flatscreen system? On my VR system I am using version 240430 it works like a charm on the Hornet. On the flatscreen I got the most recent version 250917 I think. I can tell the slower keypresses, but it was still missing digits here and there. Usually it would miss the first digit of the Precision numbers and that would throw everything off. Now it just errors from the beginning. Again, thanks for what you do Keypresses timing do depend on FPS.. Usually they need to be slowed down in pancake mode. Now, it the specific case of the Hornet, not only they depend in FPS but also in which key of the UFC is been pressed. Initially, all the keypress had the same timing... At some point, late last year or early this one, some of the Hornet UFC keys required a longer time and others, a shorter one. I discovered the issue around June, I don't fly the bug much, and made an initial attempt at fixing it, which is the latest published version, ... It improved it a lot, generating only the occasional error (in my setup anyway) and a rerun of the WP load usually corrects it This version has 2 different timings for the key presses but it looks like that, a least, 3 different timings are needed.. I'm currently testing a newer version with 3 timings for the Hornet.
mdtenor22001 Posted November 6 Posted November 6 Draken, I'm clearly late to the game here and have just started using your branch of Scratchpad for the Apache. Thank you for continuing to maintain this! I may be doing something wrong, but I read your Readme and searched this forum and still can't figure it out. Specifically, I'm trying to follow the method of creating target points (or Control measures) instead of the default WP type. From the readme, it appears that inserting a "T" where the # is in the string ("@|T| coords") should create a point as a Target Point with the default abbreviation of TG. However, when I do that, it just creates a standard waypoint. Same for when I use a "H". I must be doing something wrong (especially since I don't find a mention of that problem in this thread). Any ideas? Thanks in advance.
Draken35 Posted November 6 Posted November 6 (edited) 6 hours ago, mdtenor22001 said: Draken, I'm clearly late to the game here and have just started using your branch of Scratchpad for the Apache. Thank you for continuing to maintain this! I may be doing something wrong, but I read your Readme and searched this forum and still can't figure it out. Specifically, I'm trying to follow the method of creating target points (or Control measures) instead of the default WP type. From the readme, it appears that inserting a "T" where the # is in the string ("@|T| coords") should create a point as a Target Point with the default abbreviation of TG. However, when I do that, it just creates a standard waypoint. Same for when I use a "H". I must be doing something wrong (especially since I don't find a mention of that problem in this thread). Any ideas? Thanks in advance. Not you. Doesn't seem to be working right. ETA: Turns out that the Apache issue was a bug in my code. Surprised nobody spotted it before, Good find! Testing a fix, will publish it in the next few days. Edited November 6 by Draken35 1
DasSven83 Posted Friday at 05:27 PM Posted Friday at 05:27 PM Got on there with my son the other day, excited for the update, sad to say that it still don’t work for me. Was better than before (which is was only errors). This time when loading coordinates into the Hornet..it would drop some numbers usually at the beginning of the East coordinates. For instance if the East coords was 044° it would get entered as 4°
Draken35 Posted Friday at 05:51 PM Posted Friday at 05:51 PM (edited) 25 minutes ago, DasSven83 said: Got on there with my son the other day, excited for the update, sad to say that it still don’t work for me. Was better than before (which is was only errors). This time when loading coordinates into the Hornet..it would drop some numbers usually at the beginning of the East coordinates. For instance if the East coords was 044° it would get entered as 4° It works for me in pancake mode and VR, so this is a timing issue in your system. There is a parameter in the extension to allow slowing the process down: Do a search in this thread for "Ticks". I think somebody increased it to 2 (iirc) to solve problems similar to yours Edited Friday at 05:53 PM by Draken35 1
Recommended Posts