Jump to content

Wostg

Members
  • Posts

    297
  • Joined

  • Last visited

Everything posted by Wostg

  1. It would be cool to use the 7 digit scratchpad, and the long numbers can scroll right to left like a calculator, but it can't display letters so it would get awkward trying to enter grid coords. You could use the 2 extra letters to the left (fixed to AH here) as abbreviations for LL, ID for IDENT, MR for MANUAL RANGE? etc, but you couldn't type in A for auto, PBQ as above unless you made them show up somewhere else which is getting too weird
  2. Ok you can pretty much put anything you want there now, either one letter or 2 numbers.
  3. Ok here is my Apache script - I would have sent to @prestonflying but I will leave for him to decide if he wants to publish this at this stage. Please note the attached file is just his most recent release (that had the skyhawk), but the changes are a modified ufcPatch.lua and added ufcPatchAH64.lua if you prefer not to trust the whole package. The top level is extremely basic, just generic heading, TAS, RALT, BALT and VSI. When the KU is activated it should take over options1-5 and allow for text entry to be displayed as you go. When entering long coordinate info past 20 characters it should scroll back to let you see what you're typing. You can use the in-game keyboard, the numpad on the UFC, streamdeck or whatever else. You can display /, -, and * but not + or much else so good luck with equations. After 7 seconds of inactivity (i.e. after a lone cursor has disappeared) it should revert back to top level. Please note that it works for both pilot and CPG but if both have data up at the same time it will flick back and forth between the two which is annoying so tell your gunner to stop playing with the buttons. @android please feel free to use if helpful at all! wwtapache1.zip
  4. I know @ANDR0ID@ANDR0ID is hard at work on it but I've been playing with the KU for the apache and just about got that presentable at least
  5. No I'll figure it out from Chucks etc, but thank you for asking. That was just the next gripe that came to mind of things that either aren't covered, or appear to have changed since early release. (not harrier related) With Chucks, youtubes etc there's plenty to work with. What I'd really like is for advanced beginners guides that DON'T spend 30% of their time telling you how to decide between VR and TRACKIR, but instead talk about actually playing the game e.g. what's SEAD all about? (yes SEAD is in the core DCS manual)
  6. Cheers, it's a little thing but confusing (see also: we haven't covered radios yet but set it for kobuleti and request takeoff. Also simple comms is disabled lol)
  7. 'Anchor' means active pause right? I'm hitting all the waypoints but the next sections never trigger
  8. Check out the A4e panel - nav, weapons (master arm on), landing (gear down), refuel (probe light and/or tank refuel switch) modes. Its kind of a mile wide and maybe 2 inches deep but I like it. The scratchpad localizer(!) is a bit of a novelty but I'll try to make it more helpful, and there's a couple issues like Baro needs pressure adjustment but let me know what else I can do to spoil this analogue beauty.
  9. Lol for my part I got annoyed with the DED so took a small diversion which I'm gonna send to @prestonflying shortly... Might be good news (to someone)
  10. Ok, total fuel, flares, IAS, bearing, and 4 digits alt above sea level are showing in the 5 option boxes. I'd hoped to use the Comms boxes for chaff/flares but they get weird below 11 as they want to display 'Lo'. There's plenty of examples of DED being exported out there so should be possible, aiming to have the entered-box display on the scratchpad, active steerpoint in a comms box and something else useful on the other. Would still like to do dynamic things with the scratchpad but first things first. e: Now have working chaff, flares, steerpoint, fuel totaliser, velocity, alititude, bearing, distance to target, and time to target, however they're dependent on the active HUD and crash the UFC if you hit dogfight. Almost there...
  11. I'm playing with the F16 - what would actually be helpful to put on the UFC that's not already in front of you on the HUD and DED? I think it would be neat to have the missile (and bomb) launch envelopes shown somehow, and maybe the HARM scan or status boxes, depending on what can be shown in letters or just numbers
  12. I found some more at:
  13. Hey I was playing with them as well and think I stopped at about the same place - its not broken as such but nothing displays. No doubt you have these already but below are refs, with thanks to CaptZeen for his Helios work. There's also that high-fidelity-FC3-cockpits mod in development - I wondered if the UFC could piggyback on top of it, if it builds on any display outputs? -- FLAMING CLIFFS AIRCRAFT -- -- FC aircraft don't support GetDevice -- function ProcessFCExports () local myData = LoGetSelfData() if (myData) then local altBar = LoGetAltitudeAboveSeaLevel() local altRad = LoGetAltitudeAboveGroundLevel() local pitch, bank, yaw = LoGetADIPitchBankYaw() local engine = LoGetEngineInfo() local hsi = LoGetControlPanel_HSI() local vvi = LoGetVerticalVelocity() local ias = LoGetIndicatedAirSpeed() local route = LoGetRoute() local aoa = LoGetAngleOfAttack() local accelerometer = LoGetAccelerationUnits() local glide = LoGetGlideDeviation() local side = LoGetSideDeviation() local distanceToWay = 999 local navInfo = LoGetNavigationInfo()
  14. Hi thanks for these. Sorry if I missed this earlier but is there an M05?
  15. Same, worked direct from mission editor but the same saved mission crashed from the menu.
  16. Hi I just wanted to say thanks very much for making this, Its opened up parts of the blackshark I would never have gotten to otherwise. In time it's going to assist me to learn these functions the long way.
×
×
  • Create New...