Jump to content

Recluse

Members
 View Profile  See their activity

  • Posts

    1134

  • Joined

  • Last visited

 Content Type 

Everything posted by Recluse

  1. Recluse
    The current ScratchPad v0.7 that Draken posted combines the utility of the Scratchpad + Keyboard with the Scratchpad PLUS ability to enter coordinates into various aircraft. The README explains it and you can look for YOUTUBE videos for the general process in pulling COORDS off the F10 Map. The current iteration combining the two looks slightly different, but the concept and basic mechanics are the same In the current iteration, insertion into the JET is via the LOAD WAYPOINTS button: null Ideally the COORDS are pulled off the MAP, but, with the Keyboard, you can enter them as well Note that COORDS are formatted based on the current aircraft, as coordinate systems may differ. For the F/A-18, you should go to HSI-->DATA and box PRECISE before loading for WP's in the DD.MM.mmmm format If you are programming PP JDAM's, note the coordinates in the Hornet are DD.MM.SS.ss which are also handily provided though cannot be instered automatically.
  2. Recluse
    Glad it worked out for you!! I fly mostly in VR and don't have the issue as frame rates and thus timing are much lower, but I occasionally have still seen the glitch in the initial Waypoint. LOL, my Callsign/Handle was self-bestowed and came from my early days of discovering Flight Sims where I would spend my entire weekend in front of the computer and never venture out of the house. Era of MPS original Gunship circa 1987. Maybe even earlier than that.
  3. Recluse
    You can try increasing the TICKS parameter COULD be a timing issue. I have seen something similar on occasion The "fix" for me, if you can call it that, was to delete all but the first Waypoint and re-insert it in the WP1 position. Second time it seemed to work.
  4. Recluse
    OK that does sound like some Windows 11 strangeness. As far as I can recall, the folder was created automatically, but I have been using ScratchPad in it's many iterations for so long that I cannot be 100% sure that I didn't create it at some point. Important thing is that it is working now!!
  5. Recluse
    Better late than never!! Welcome to the party! It is a great tool ESPECIALLY in VR.. @TheRustyTigger I can confirm it still works and is persistent in the location indicated by @AdrianL (Windows 10, though, but I think you just had the wrong location null
  6. Recluse
    Based on the terrain and the orbit, I have found that occasionally the Predator AFAC will drop the laser designation based on LOS, but usually it is high enough that this is not an issue. If it is consistently dropping right after firing vs. a coincidental loss of LOS then something else is going on. I haven't experienced this, though.
  7. Recluse
    Well, when I started making the Video, I got errors, and, as posted above, I realized that I was re-using coordinates I had captured from another aircraft (MIRAGE) and the non-Precise coordinates seemed to transfer correctly into the Hornet without changing timing. I will still do a video one of these days Still having issues getting ANYTHING to work in the M2000, though. Odd..
  8. Recluse
    OK, I just tried it again, and you DEFINITELY will have to edit the TICKS parameter to slow things down. (Or fly in VR) It originally worked for me because I used the coordinates I generated in the Mirage 2000 which were NOT precise, and they entered into the HORNET correctly with no errors even in 2D. When I generated coordinates starting from the HORNET, I did get the PRECISE coordinates and it ERRORED out when loading. I had exactly the same issue with SP Plus, actually, but @Draken35 made some edits to the lua to add delays. EDIT: Our posts crossed. Glad you got it working!!!!!
  9. Recluse
    I will make a short video. MEANWHILE, you should know that there are TIMING issues that come into play sometimes with very fast framerates, that error condition occurs. Usually I fly in VR, and it isn't an issue, but in 2D I would often get the errors. Oddly enough, I tested in 2D, and everything worked fine. You can try adding a delay by editing the first line of the 02-QWERTY_KB and Load Coordinates.lua file int he Scratchpad\Extensions folder Will upload video shortly
  10. Recluse
    I tried it in the Hornet using exactly the same process as I used with SP Plus. Worked for me just fine. I didn't use the WSS or WDES parameters, just set the HSI to my desired start WP and let her rip since:
  11. Recluse
    Thanks for the info!! I was going by this image in the manual which seemed to show a SPIN parameter on the CBU-97 Mainly a Hornet/Harrier driver so the CBU-97 is a shiny new toy with much greater capability than the Mk.20 or CBU-99. The MIRAGE 2000 Belouga's are similarly better than the Rockeye/CBU-99 but a bit more difficult to deliver accurately, though ACCURATE and CLUSTER BOMB should not necessarily need to be uttered together. Have had a little experience with the A-10C CBU-97/103/105 but have barely flown the Warthog.
  12. Recluse
    A good trick I learned in one of the videos is to cycle through the available TIME fuzing choices until it disappears, then you can use burst height only. Or so it seems. Worked well for me when I tried it. Note: using CBU-97 I never did see the SPIN option.
  13. Recluse
    A few recent videos with good information on Markpoints!
  14. Recluse
    Just a quick sanity check.. (LOL...that's dangerous where I am concerned...but I digress....) When turning on a TACAN and selecting TACAN steering in the HSI, I still get the pointer (Heading Command Bug) in the HUD pointing to the selected Steerpoint NOT the TACAN. Is this CORRECT AS IS? OR did I forget some setting. I get all the TACAN steering information in the HUD DATA block and the TACAN location and either CDI or PLAN CRS line in the HSI, only the HUD indicator is pointing elsewhere. Thanks.. EDIT: OOPS!!! RTFM!! (this is in the ADI section, but I assume it applies to the HUD as well) P age 217
  15. Recluse
    Yes, so a sequence can have 15 Waypoints, but the database of Waypoints and Markpoints can be scrolled through continuously. As in the video below, I scroll through 60 WP's (I guess 59 +0) and 10 Markpoints. There is only a single SEQUENCE (with 15 WP's) but I can still scroll through the entire database when the Sequence is not SELECTED, so this method of creating multiple small sequences and selecting them should definitely help.
  16. Recluse
    You might be right that it is a DCS'ism.. It just struck me as odd that most of the other aircraft allow you to directly input the WP of choice and I got to wondering why the Hornet (that we have) does not. I have to say that I have seen sequences with many more than 9 Waypoints. Specifically, in the FOOTHOLD Dynamic mission we fly, there are at least 40 WP's in the default sequence. but I tend to create TARGET WAYPOINTS by over-writing a range of WP's that I am not using for the particular part of the map I am on, but then I might need to Divert to another WP earlier or later in the sequence, or toggle back to WP 0 to return to HOME PLATE (if there is no TACAN ) and that is a lot of TOGGLING. Creating a new sequence with a subset of WP's seems like it would work.
  17. Recluse
    So as I have been learning the F-15E, I am reminded that of the aircraft I fly, the Mudhen, the Harrier, the Mirage (don't recall the A-10C) all have a mechanism to punch in a desired Waypoint and jump straight to it for Navigation. Pretty sure the VIPER can too (from my BMS days) I have not found such a mechanism in the Hornet!! IN some missions we fly (e.g. FOOTHOLD) there are MANY MANY waypoints and it is annoying and cumbersome to have to scroll up and down with the appropriate PB to get to the desired WP. Is there a way to do this via the UFC that I have been missing all this time?? Seems like an odd omission for a modern aircraft when it is present in so many others.
  18. Recluse
    Thanks for the response and for the clarification!! I was thinking the mod randomly spawned clients of the selected mods for use. I guess I was over thinking things.
  19. Recluse
    Tape/Post-it over the sensor. Problem solved (for now...it would be nice to fix it on the DCS end) Just be sure to shut down the headset manually when you are done with it.
  20. Recluse
    So, I can confirm this as well. FOR ME, TRIM RIGHT activates the animation of the START/STOP/REWIND button (but doesn't actually seem to perform the function) Similarly, TRIM DOWN activates the animation of the CLOCK TIME Adjustment switch, but unlike a mouse click, it doesn't stay in that position, just toggles. I do not see TRIM adjustments when I mouse click the knob/switch though. (WINWING ORION F-18 HOTAS)
  21. Recluse
    Indeed. A temporary workaround is all.
  22. Recluse
    Interesting!!! I have used the ALT-TAB trick in the past for FPS decreases, but it never seemed to work for me with the F10 issue. Not sure how long I held it for, but usually, I would wait until I observed the FPS coming back and then switch back to DCS. FOR ME, the F10 issue totally disappeared when MSAA was turned off (though that is not everyone's experience).
  23. Recluse
    I have been looking for the expansion script referred to in the documentation (FIGHTERS MOD) to configure the addon mods I have downloaded. I cannot seem to find the .lua file to download or edit. Or do I need to create it? Sorry if I am being dense. I looked through the .zip file and in the Trigger's section and couldn't find it. Thanks for pointing me in the right direction. Hehe: I found it in the zip file for the OTHER TTI maps. It was not present in the Las Vegas TTI .zip! The .lua I found in the Persian Gulf and Marianas TTI zip files didn't seem to have the UH60L in it. Will it work if I just add the lines for the UH60L and then plug that expansion into the Las Vegas TTI?
  24. Recluse
    Since turning off MSAA, I haven't had this issue on my QUEST 2. Generally, though, I didn't get the black screen in the headset, just stuttering and single digit frame rate.
  25. Recluse
    Same on Oculus Quest 2 + Open XR +MT Semi-randomly after spending time on F10 map, return to cockpit results in drastically decreased Frame rate . Sometimes freezing and crashing, but usually just unplayable (single digit) frames. Compared to other instances where frame rate may be recoverable by ALT-TABBING or switching views, this seems un-recoverable. EDIT: Setting MSAA to OFF seems to have helped with this issue. I was pretty sure I saw this issue even with it OFF, and I had reset it recently. I turned it off again and in some limited testing, prolonged F10 excursions didn't seem to cause the issue. I only tested in Single Player and the problem seemed more prevalent in Multiplayer scenarios, so will keep testing.
×
×
  • Create New...