Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by horus-DCS

  1. 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
  2. Could you elaborate on the advantage of the Rhino compared to the Brunner?
  3. 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
  4. Yes, those will control the CPG's functionalities directly. If you have a human CPG, you don't need to control them yourself anyway
  5. {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
  6. 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
  7. 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
  8. 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
  9. 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
  10. 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?
  11. 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
  12. Thanks Grimes as always. But I still have a question... mist.message.add and other msg functions won't remove previous messages even after its determined display time. mist.message.add{text = 'TEST1', displayTime = 5, msgFor = {coa = {'all'}}} --screenshot's code, MIST 4.5.106 After a while I have to see the messages all over the screen! If I use a name of the message the text won't stack but I still get permanent messages of other names when any message is activated.
  13. I've been using FSSBs(R2/R3) for 15 years and never had a problem to fly helos. Actually it's the best for me to fly helos among the bases I've tried including FFB. It doesn't matter whether the aircraft is FBW or not. Even the huey can be controlled flawlessly with the base. Sent from my iPad using Tapatalk
  14. Hi, I have a question. I've been testing 4.5.106 and want to use groupToRandomPoint function for a respawned group. It would set the route correctly, but the group doesn't move initially after it spawned. I have to increase speed bar manually as a JTAC or TACCOM to move it. The previous version(4.4.78) I've used didn't have this problem. Do I miss something? Should I add some tasks? test.miz
  15. Hi, Is it possible to get a data of collision / hitting object events? Boolean data is good enough, but any detailed damage data would be better. I want to use it as a trigger for some actions.
  16. 1470 euro is already unaffordable for most of the simmers, but it’s still fine, the list price is 3200 even without shipping fee…! If this pre-order process doesn’t fulfill 200 units in 90 days we have to pay whole 3200 to get a unit, that’s what they said. I can’t judge its value easily because I don’t have the product, but I doubt that they want to really sell it for ‘home simmers’. Anyway I would be in for the pre-order, let’s see how it will go. Sent from my iPad using Tapatalk
  17. The amount of pre-order should reach 200 units at least, even in a month and a half, to get the unit at the lower price….? This sounds so pessimistic, but who knows. Sent from my iPad using Tapatalk
  18. Modified init.lua files for changing/adding viewport names to export them individually are completely blocked now. In short this patch screws up hardcore home cockpit setup. For example> Ka-50 Mods\aircraft\Ka-50\Cockpit\Scripts\PUI_800\PUI_800_init.lua (exporting digits) Mods\aircraft\Ka-50\Cockpit\Scripts\PVI\PVI_init.lua (exporting digits) Mods\aircraft\Ka-50\Cockpit\Scripts\clickabledata.lua (adjust key press gains for binding on physical rotary encoders) NS430 Mods\aircraft\NS430\Cockpit\Scripts\NS430_init.lua Mi-8MTV Mods\aircraft\Mi-8MTV2\Cockpit\Scripts\AI\ControlPanel\g_panel_page.lua (changing AI control panel position) UH-1H Mods\aircraft\Uh-1H\Cockpit\Scripts\AI\ControlPanel\g_panel_page.lua (changing AI control panel position)
  19. The hind is randomly uncontrollable like a brick. Check the track please. It wasn't recorded correctly (as always...), but you can see the part what I mentioned anyway. From the mission time 6min, the hind started to roll full left without any actual left roll input(I released the stick as soon as this happened). The direction isn't only full left like this, but also full forward sometimes, generally I can't recover even with a full opposite direction input once it happens. Never had this problem with other choppers. Turned AP off, no joy. Trimmer mode is default (NOT CENTRAL POSITION) Checked controller option twice, no unintentionally assigned controllers. 2.trk
  20. Will we have mirror removal function someday? I mean like what we do for removing stick and seat. I don’t realy turn on mirror because it kills my FPS anyway but still is almost useless for not having any angle adjustment gimmick. And if I turn it off, the mirror try to blind my eyes by reflecting the sunshine insanely. For now it’s noting but a sight blocker. Please let us have removal option! Sent from my iPhone using Tapatalk
  21. Same problem here. It seems like the calibration via SimAppPro doesn't work at all. Even if I set the range differently every time, it always shows same result(probably default). The gap between the XY axis is not so big so it won't be a serious issue for now but I don't think the calibration process works properly for now. Or did I miss something...?
  22. Very nice. I’m looking forward to getting further informations. Sent from my iPhone using Tapatalk
  23. Sure I’m interested. Do you have any mockups? Sent from my iPhone using Tapatalk
  • Create New...