Jump to content

ArturDCS

Members
  • Content Count

    602
  • Joined

  • Last visited

About ArturDCS

  • Rank
    Member

Personal Information

  • Flight Simulators
    DCS
  • Location
    Kaarina, Finland
  • Interests
    Reading, Programming, Netflix, Ice-cream, Snus
  • Occupation
    Retarded

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Please create an issue on Github and explain when this happens. Also post your profile.
  2. I suggest you head on over to Discord too and ask F-14B pilots there.
  3. Can you head on over to our Discord server? Easier to exchange info via chat.
  4. OK so if you configure "A" it produces 2 A's? Is it when using VK_NULL? edit: I've been testing here and it does seem to work? What could it be, are anyone else having these problems?Check your profile, post the relevant part of the profile here. Fallen_Tyrael, you can test by opening Notepad and while clicking see how many letters are produced, for example letter A. I don't have a problem here so atm I don't know what is going on.
  5. I did a release with a new key value named VK_NULL. This key doesn't do anything and with it you can do what you described. Of course you can use the OEM or what is was. Report if there are any problems using it. This is the easiest way for me, instead of having texts for single key stroke. That would mean more programming.
  6. Thanks for the information! Had no idea about that aspect. Yes will change it so that the user will be asked whether to use pre-programmed radio or not.
  7. What I see is one (1) virtual key stroke. If you there would save and exit the key sequence window DCSFP would treat it as a single virtual keystroke, not a keysequence. Try adding 2 virtual keys to a sequence and save. Does it look the same then too?
  8. If you start adding a key sequence but you end up with just one entry (change of mind), DCSFP will treat it as a simple virtual key stroke and there won't be any need for Break(s).
  9. Right Click on the field only offers to change timing, and not to edit the sequence Break means the time it will wait before executing the virtual key press. Look at the screenshot for this sequence: RadioPanelKeyDialPos{LowerDME}\o/{1LowerCOM1}\o/OSKeyPress{INFORMATION=^Key press sequence^[FiftyMilliSec,VK_A,FiftyMilliSec][FiftyMilliSec,VK_B,FiftyMilliSec][FiftyMilliSec,VK_B,FiftyMilliSec]} This is how it is saved into the file.
  10. Hello and thanks for the donation. :) I am working on DCSFP fixes today and yes this is a bug. I found the problem. This generic radio panel should now send DCS-BIOS commands. I will make a release asap.
  11. Not much out there but it isn't difficult making formulas if they are linear. Just look at the value from DCS-BIOS while flying and format accordingly. There is also the formula sandbox in DCSFP. HTH
  12. Radio panel support for F-14B ARC-159, ARC-182 and Pilot + RIO TACAN A-10C, new sync method used which basically means instant transfer of STBY => ACTIVE Known issues: F-14B UHF & VHF Preset Channels do not sync properly with radio panel You need the latest (>=0.7.25a) DCS-BIOS for this to work. HERE :pilotfly:
×
×
  • Create New...