horus-DCS

Yes DCS 2.9.3.51704 Still broken. Sent from my iPad using Tapatalk

Thanks! Sent from my iPad using Tapatalk

For example, I would run some trigger action if a longbow FCR is equipped on a particular apache unit. Is there a simple script code to do that? Thanks in advance. Sent from my iPad using Tapatalk

2.9.1.48111 update still broken...

2.9 updated but not fixed yet

They can see me behind the trees without any problem. Please check the replay. This is a critical issue for the helicopters performing popup attacks over the trees. And it doesn't look like AI related issue, but the tree objects have another issue as well. Projectiles penetrate the woods. Also seen in the replay. I've never seen these issues before. Some sneak attack tactics using trees as covers are completely useless for now. seethrough.trk

Same here. Actually this issue has been there for a long time. Looks like this module is almost abandoned...either from users and devs

This report is correct and the issue is still there. The 430 overlay window size is affecting the brightness of the main display. I can't use this module anymore because of the issue.

I don't know about BS2 as I went to BS3 immediately, BS3 is fine

I believe that the hardware trim is already working for the recent R3L version, is there anything new in the R3L Mk2 trim function?

I'm curious how it will work in DCS

I have this issue too, never had before the 2.8. It should be fixed Sent from my iPad using Tapatalk

Yeah even though it took over a year I'm happy to have the option anyway

There are 2 pin holes for the finger-detecting IR sensor on the frontside of the grip. Just block one of them completely with a piece of duct tape Sent from my iPad using Tapatalk

Could you elaborate on the advantage of the Rhino compared to the Brunner?

You've probably pasted them into 'joystick axis' section in the file. They must be in 'key commands' section, I should've made it more clear. Just use my file. I've added more key commands for toggle switches. It would be useful for cockpit builders. PS. Remember, the file will be restored by the original if it's updated. Some key commands are still being added or modified as the module is a beta, so simple reuse of the file could conflict some new entries. Then I would recommend to copy '--Custom' section and paste it into a new updated control file. default.lua

Yes, those will control the CPG's functionalities directly. If you have a human CPG, you don't need to control them yourself anyway

{down = tedac_commands.LHG_TADS_SENSOR_SELECT_SW, up = tedac_commands.LHG_TADS_SENSOR_SELECT_SW, cockpit_device_id = devices.TEDAC, value_down = 0.0, value_up = 1.0, name = _('Custom_LHG TADS Sensor Select Switch - TV/FLIR'), category = {_('Custom')}}, {down = tedac_commands.LHG_TADS_SENSOR_SELECT_SW, cockpit_device_id = devices.TEDAC, value_down = 1.0, name = _('Custom_LHG TADS Sensor Select Switch - FLIR'), category = {_('Custom')}}, {down = tedac_commands.LHG_TADS_SENSOR_SELECT_SW, cockpit_device_id = devices.TEDAC, value_down = 0.0, name = _('Custom_LHG TADS Sensor Select Switch - TV'), category = {_('Custom')}}, {down = tedac_commands.LHG_TADS_FOV_SW_Z, up = tedac_commands.LHG_TADS_FOV_SW_Z, cockpit_device_id = devices.TEDAC, value_down = 1.0, value_up = 0.0, name = _('Custom_TADS FOV Switch - Z (Zoom)'), category = {_('Custom')}}, {down = tedac_commands.LHG_TADS_FOV_SW_M, up = tedac_commands.LHG_TADS_FOV_SW_M, cockpit_device_id = devices.TEDAC, value_down = -1.0, value_up = 0.0, name = _('Custom_TADS FOV Switch - M (Medium)'), category = {_('Custom')}}, {down = tedac_commands.LHG_TADS_FOV_SW_N, up = tedac_commands.LHG_TADS_FOV_SW_N, cockpit_device_id = devices.TEDAC, value_down = -1.0, value_up = 0.0, name = _('Custom_TADS FOV Switch - N (Narrow)'), category = {_('Custom')}}, {down = tedac_commands.LHG_TADS_FOV_SW_W, up = tedac_commands.LHG_TADS_FOV_SW_W, cockpit_device_id = devices.TEDAC, value_down = 1.0, value_up = 0.0, name = _('Custom_TADS FOV Switch - W (Wide)'), category = {_('Custom')}}, Copy these lines and paste to your \Mods\aircraft\AH-64D\Input\AH-64D_PLT\joystick\default.lua You'll find these functions in the 'Custom' category. # 1~3rd lines : TV/FLIR 1st line is for a toggle (on-off type) switch, 2~3rd lines are for push switches. # 4~7th lines : TADS zoom

I'm not on my PC for now, I'll post it later It won't work if you just copy and paste the line from the CPG control file. You have to write the code to be compatible with the corresponding entries in "clickabledata.lua". I'll post the correct line later Sent from my iPad using Tapatalk

Basically no, but it’s possible by adding the CPG control functionality in the PLT’s control lua file Sent from my iPhone using Tapatalk

It would be great to be able to rearm from some supply cargos too. That'll expand cargo helos task tremendously Sent from my iPad using Tapatalk

I can't explain specifically for now(not on the PC), but in short, find and open the device init lua files in ah-64 cockpit script folder and change the viewport names. Default names are LEFT_MFCD and RIGHT_MFCD as I mentioned. Of course you have to make a new entry for the device in your monitor config file if you change them. If you can't find the files I'll report it later Sent from my iPad using Tapatalk

It looks like the CPG’s MPDs always ‘overwrite’ the pilot’s. I had to rename the CPG’s and place them some other coordinates to get the pilot’s normally. ED devs, I think the CPG’s MPDs should be removed as the player occupies the pilot seat. Sent from my iPhone using Tapatalk

The MFD export actually works but I've only got CPG MPDs either in the pilot's cockpit or CPG's. The viewport names are default(LEFT_MFCD, RIGHT_MFCD). Do I miss something?

Thank you sir! I think the 107 still has some bugs? Please check the attached mission. 1. I can't hear the sound for the 'complete' message, because it's activated over the previous msg('checking...') ongoing 2 'checking...' msg should be displayed only for 2s, but it doesn't disappear until the next msg('complete', 10s) is gone. 3. (I'm not sure if it's a bug, just a normal question) The mist msg doesn't work for individual ground units with an input value of msgFor = {units = ~~} ? test.miz