Jump to content

[REPORTED] ADF Manual Frequency keybindings


Rudel_chw

Recommended Posts

I can tune the radio using the mouse, by clicking and dragging up or down, but I would like to be able to tune it using my Hotas or the keyboard, so I binded them like this:

 

6oR40N0.jpg

 

However, neither of these bindings seem to work, they move the tuning knob erratically if at all. Please take a look at them and, if possible, make the adjustment increment fine rather than coarse.

 

Thank you.

 

Eduardo

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600X - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to comment
Share on other sites

Unfortunately, this Bug is still there, on 2.5.5 version .. hopefully the developer will take a look into it and it will be fixed an a future update :(

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600X - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to comment
Share on other sites

As the campaign makes use of manually dialed ndbs quite a lot, it's very tiresome to try to tune the adf. Will postpone the campaign until this is fixed.

Windows 10 64bit, Intel i9-9900@5Ghz, 32 Gig RAM, MSI RTX 3080 TI, 2 TB SSD, 43" 2160p@1440p monitor.

Link to comment
Share on other sites

  • 2 weeks later...
Thank you for sharing this one, i will have a look

 

Thank you :) hopefully it should be something simple to fix, but it will make much easier to tune the radio.

 

PS: please take a look also on this other issue, as it is of the same kind: https://forums.eagle.ru/showthread.php?t=242229

 

PS2: not wanting to be greedy, but if you can, also see if something can be done about this: https://forums.eagle.ru/showpost.php?p=3939121&postcount=25

 

Thanks a lot, and best wishes :)


Edited by Rudel_chw

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600X - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to comment
Share on other sites

  • 2 weeks later...

I'm dissapointed to report that, after today's update of Openbeta, this bug is still present :(

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600X - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to comment
Share on other sites

Dear Razbam, this bug is really spoiling an otherwise very enjoyable module, and a great campaign.

Please reassure us that you are looking for a fix, it's been going on since day one!

If you feel it is OK, let us now how to use...

Details:

Asus Z-170E, Intel i5-6600K @ 4.2GHz, 16GB RAM

MSI GTX970 Gaming 4G

Win 10 Home

Link to comment
Share on other sites

To improve a little bit, you can change in mods/aircraft/Mig19-P/Cockpit/clickabledata.lua line 338 :

 

elements["PTN_353"] = default_axis_cycle(_("ARK-5 Frequency Fine Tuning Handle"), devices.ARK5_CONTROL, radio_commands.ARK5_freq_tunning, 353, 0, 0.2, false, true)

 

the value of 0.2 (instead of 0.05) seems to improve decrease the sensitivity of mousewheel when turning the handle, so you need less turns to move around the frequencies.

Details:

Asus Z-170E, Intel i5-6600K @ 4.2GHz, 16GB RAM

MSI GTX970 Gaming 4G

Win 10 Home

Link to comment
Share on other sites

To improve a little bit, you can change in mods/aircraft/Mig19-P/Cockpit/clickabledata.lua line 338

 

Thanks for the tip, but what I actually needed was to be able to bind the most used dials to my HOTAS ... pity that it has got so frustrating to me, that I've opted to park my MiG on the Hangar and dedicate my time to learning the Hornet instead :(

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600X - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to comment
Share on other sites

  • 3 weeks later...
  • 3 months later...

Come on, still not fixed. Cant be serious.

Ryzen 7 2700X | MSI Trio 1080Ti | MSI X470 Plus Motherboard | 32GB Kingston HyperX Predator 2933 DDR4 | M.2 XPG GAMMIX S11 Pro SSD | Virpil Mongoost-50 throttle | Thrustmaster Warthog Stick | MFG Crosswind | Rift S

Link to comment
Share on other sites

  • 1 month later...
  • 4 weeks later...
  • 2 months later...
  • 1 month later...

You can assign axis to this frequency knob to reduce a chance of hitting the ground while trying to turn it with mouse wheel. Mini-stick has nothing to do in MiG-19 anyway...

 

 

Modify ..aircraft\MiG-19P\Input\MiG-19P\joystick\default.lua, add

 

 {action = radio_commands.ARK5_freq_tunning,    cockpit_device_id = devices.ARK5_CONTROL,    name = _('ARK-5 Frequency Tune Knob'),    category = _('Radio Navigation')},

to res.axisCommands section.

 

It rotates jerky just like with mouse wheel control, and gets stuck sometimes. But if you play with stick up/down a bit, it goes on, and you can finally tune ARK and fly at the same time, by listening Morse codes or making brief looks at the frequency dial.

 

I've tried to assign +/- buttons to this axis, but no luck. Knob turns nice and smooth, dial doesn't rotate at all. Original +/- buttons still work absolutely erratically.

Link to comment
Share on other sites

  • 1 month later...

Tuning this thing is not pleasant. Any chance of a fix soon? :helpsmilie::joystick:

MODULES: A10C Warthog,AH-64 D APACHE,AJS Viggen,AV8B Harrier,BF109 K4,C101 Aviojet,F14 Tomcat,F15E Eagle,F16 Viper,F5 Tiger,F86 Sabre,FA18C Hornet,FW190A8,FW190D9,I16 Ishak,JF17 Thunder,KA50 Blackshark,L39Albatros,Mirage2000C,Mirage F-1,MI24P,MI8MVT2,MIG15BIS,MIG19P,MIG21BIS,Mosquito FB VI,P51D Mustang,P47D Thunderbolt,SA342 Gazell,SpitfireIX,TF51D,UH1H Huey,Yak52.

OTHER:Flamming cliffs,Combined Arms,WW2 Assets Pack,SuperCarrier.

TERRAINS: Nevada,Caucasus,Normandy,Persian Gulf,Syria,Channel,Marianas. 

 

Link to comment
Share on other sites

Tuning this thing is not pleasant. Any chance of a fix soon? :helpsmilie::joystick:

 

It’s been more than a year since reported, so ... no, a fix isnt likely :(

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600X - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to comment
Share on other sites

That's a shame.Would of been nice.:(

MODULES: A10C Warthog,AH-64 D APACHE,AJS Viggen,AV8B Harrier,BF109 K4,C101 Aviojet,F14 Tomcat,F15E Eagle,F16 Viper,F5 Tiger,F86 Sabre,FA18C Hornet,FW190A8,FW190D9,I16 Ishak,JF17 Thunder,KA50 Blackshark,L39Albatros,Mirage2000C,Mirage F-1,MI24P,MI8MVT2,MIG15BIS,MIG19P,MIG21BIS,Mosquito FB VI,P51D Mustang,P47D Thunderbolt,SA342 Gazell,SpitfireIX,TF51D,UH1H Huey,Yak52.

OTHER:Flamming cliffs,Combined Arms,WW2 Assets Pack,SuperCarrier.

TERRAINS: Nevada,Caucasus,Normandy,Persian Gulf,Syria,Channel,Marianas. 

 

Link to comment
Share on other sites

Yes it is a shame. This stupid little bug has essentially ruined the module for me. I like DCS but I don't have enough time to be faffing around struggling to make a dial turn.

 

Despite an included BD campaign (the reason I got the module) I can't possibly recommend it to anyone else, and it has put the brakes on any future Razbam product purchases. A year of not being able to really use this module because of such a simple thing -> I know Razbam gets a lot of vitriolic heat from some people, but clearly sometimes there is a reason behind it.

CPU:5600X | GPU:RTX2080 | RAM:32GB | Disk:860EVOm.2

Link to comment
Share on other sites

Yes it is a shame. This stupid little bug has essentially ruined the module for me ...

 

+1 .. same for me.

 

I fully supported Razbam, being latinamericans and all, and bought every one of their aircrafts up until the Mig-19 .. now, I regretfully have discontinued my support and won't buy neither the Falklands Map nor the MiG-23 if they ever came out. :cry:

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600X - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to comment
Share on other sites

  • 5 weeks later...

At long last, today's patch brings a fix for this long standing bug:

 

DCS 2.5.6.54046 Open Beta

...

DCS MiG-19P by RAZBAM

ARK-5 Frequency tuning handle issues fixed.

 

Downloading the patch at the moment, will report later today.

 

Edit:

 

Well, this was a let down ... after waiting for so long :(

 

On the positive, the tuning crank can be increased/decreased using the mouse or the mousewheel. It has a fine adjustment, but that makes it really tiring to adjust using the mouse if the frequency change is large as it requires a lot of mouse dragging or mousewheel turning.

 

On the negative, I tried to bind the crank keybinds, as follows:

 

6oR40N0.jpg

 

On both cases: keyboard and Hotas, only the ADF Manual Frequency DOWN binding works as intended, having a smooth and gradual action ... but instead of decreasing the frequency, it INCREASES it.

 

The ADF Manual Frequency UP, does not work at all, neither with the keyboard nor the HOTAS.

 

RAZBAM, I expected a proper fix ... and you deliver this :( .. I don't want to say things I might regret, I will just park the MiG-19 on the hangar once more ... pity. :(


Edited by Rudel_chw

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600X - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...