Jump to content

=36=Witcher

Members
 View Profile  See their activity

  • Posts

    429

  • Joined

  • Last visited

 Content Type 

Everything posted by =36=Witcher

  1. =36=Witcher
    I already have an idea on how this could work. Of course I'll have to wait for the module to test it. For anyone interested, and using Home Fries CTS Profile, my idea is here Since we're here, am I missing some other input changes? It doesn't look like, but I'd rather be sure.
  2. =36=Witcher
    Hi Home! RAZBAM announced here that there will be some changes in the upcoming updates for the M2000 according to AdA feedback. I cannot be sure about how this will turn out exactly until the updates are released, but if I'm not mistaken we will need a new button mapping since TWS/STT (H2 UP) will only switch the radar mode and won't perform AA Designate anymore. Again we'll have to wait for the module to understand whether I'm right or wrong, but should I be right (something which rarely is :D) I would propose these changes: A first, more invasive but slightly more realistic alternative, can be: - H2 UP will switch TWS / STT but won't lock the target anymore - Slew Control Push will perform AA Designate - H4 Push won't do Target Unlock / Special Mode Deselect anymore, but will do Magic Slave / AG Designate/ INS Position Update - Shift + H4 UP or DOWN perform Target Unlock / Special Mode Deselect, unchanged from current profile Another more intuitive, although a bit less realistic, alternative could be: - H2 UP will switch TWS / STT but won't lock the target anymore - Slew Control Push performs Magic Slave / AG Designate / INS Position Update, unchanged from current profile - H4 Push won't do Target Unlock / Special Mode Deselect anymore, but will perform AA Designate - Shift + H4 UP or DOWN perform Target Unlock / Special Mode Deselect, unchanged from current profile What do you think?
  3. =36=Witcher
    I wasn't complaining or anything, just asking! I know that the Magic slave and Magic unlock are working :) I'm just concerned for my HOTAS profile. As of now, in my Warthog profile, I have the AA Designate / TWS/STT switch on H2 UP (Stick), Magic Unlock on H2 Down (Stick) and Magic Slave / Ground Designate on TDC Press (Throttle). With this updates, I need a new button because: - H2 Up won't A/A Designate anymore, only switch TWS/STT - A/A Designate is moved to TDC press, so TDC press won't Magic Unlock / AG Designate anymore So now I need another button for Magic Unlock / AG Designate. Also, this is something I'm just reasoning about, I may be wrong, but I'm afraid I have to rethink the layout.
  4. =36=Witcher
    Also, if the TDC button will lock the contact, which button should we use for the Magic Uncage?
  5. =36=Witcher
    So, how will we choose to mount DDM? Ground crew?
  6. =36=Witcher
    I don't know if it's the same for the Cougar, but for the Warthog, once the CTS script starts, you have to map Thrustmaster Virtual Device on DCS, not the independent devices.
  7. =36=Witcher
    Please don't get me wrong: as a disclaimer, I am a software engineer myself and I know that software development can be an incredibly complex activity. Everyone who denies this simply doesn't know what he's talking about. Having said that, yes: the Mirage is still not in a good shape, unfortunately. A lot of systems suffer from bugs of various severity, new ones seems to surface every update, bugs reported as fixed in release notes are not actually fixed in a given release, and some stuff has been even broken from the beginning. It's a shame, really. M2000 is still my main and it will be for quite some time due to my squadron activity, but I have to admit the urge of migrating to another module gets stronger every day. Comparing the quality of the F-14 (the latest module I bought) to the M2000 makes the choice between the two a no brainer, speaking of only the perceived quality of the module. Moreover, I don't own other RAZBAM modules, but from what I hear other modules are not that different. However I'm just speaking about what I read, so it doesn't really matter. I really hope things can change in the future, but my hopes are not that high in this moment. We'll see.
  8. =36=Witcher
    It also depends what are you trying to achieve. In my experience, nothing has been more valuable than finding a virtual squadron and joining them. I'm not only learning how to fly the plane properly but I'm also learning a lot of soft skills such as proper communications, teamwork, tactics. Of course it all depends on the people you get in touch with, but I'm sure I would have dropped DCS a long time ago if I hadn't crossed paths with my virtual squadron.
  9. =36=Witcher
    I can confirm that using your version of F-14 Controller LUA Improvements fixes all my other issues about nose strut, stick hiding and LANTIRN. Sorry about that! Just one last question: will you update your version of the mod with the differences you found between the Mod and the original LUA? Also, in your mod, three bindings are missing from the Alerax mod: {down = device_commands.ENGINE_Throttle_Temp, cockpit_device_id = devices.ENGINE, value_down = -1, name = _('-Throttle Temp COLD'), category = { _('-MODIFICATIONS')}}, {down = device_commands.ENGINE_Throttle_Temp, cockpit_device_id = devices.ENGINE, value_down = 0, name = _('-Throttle Temp NORM'), category = { _('-MODIFICATIONS')}}, {down = device_commands.ENGINE_Throttle_Temp, cockpit_device_id = devices.ENGINE, value_down = 1, name = _('-Throttle Temp HOT'), category = { _('-MODIFICATIONS')}}, in Alerax mod, they're located between {down = device_commands.INLET_RAMPS_RightSwitch, cockpit_device_id = devices.AICS, value_down = 1, name = _('-Stow Inlet Ramps Right Switch STOW'), category = { _('-MODIFICATIONS')}}, and {down = device_commands.ENGINE_Air_Start, cockpit_device_id = devices.ENGINE, value_down = 0, name = _('-Engine Airstart NORM'), category = { _('-MODIFICATIONS')}},
  10. =36=Witcher
    In my controller mod the stick hiding was missing altogether, and the kneeling command was under -MODIFICATIONS instead of being under Flight Control. We are talking about the same mod, aren't we? :huh: I'm using the file downloaded from the first post of this thread EDIT: Oh, after using CTS for almost three years I JUST DISCOVERED the "_Custom LUAs for DCS World Main Install" folder. So I guess you're talking about THAT mod version! I'll just make the comparison, but I have no doubt you're right about it. And this also answer my question about LANTIRN. I'll report soon.
  11. =36=Witcher
    I can confirm that both Sitck Show/Hide and Nose Strut bindings are missing from Improved Controller Mod, so enabling the mod will break that functionality. I manually added them again and now I have those bindings. Probably the mod was build on an older version of the F-14 module, and now the two files diverged. I'll try to get in touch with the Mod author to check if he can update it. My only question is about LANTIRN now.
  12. =36=Witcher
    Hey Alerax, I just purchased F-14 and I discovered your great mod. However, by doing some research, in your keyboard.lua there's some command missing here and there -- I compared the two of them and I can spot several differences, not just your new commands; for instance, one of the missing binding is Control Stick Show/Hide and all related bindings. Do the mod need to be updated with a newer base? If so, do you plan to do that or we should do that on our own? Thanks!
  13. =36=Witcher
    What's the name of the control exactly? I couldn't find anything reated to hiding the stick... Maybe it's Improved LUA Controller Mod again?
  14. =36=Witcher
    Also, still in the F-14 Pilot: -Nose Strut switch is not working. Improved LUA Controller Mod is installed but the profile does not have any binding for those controls -Is LANTIRN supposed to work with Improved LUA Controller Mod? The box in the Profile JPG says it should, but I have no LANTIRN command on the profile, and I couldn't figure out how to make it work...
  15. =36=Witcher
    I know this has the lowest priority of all the issues you ever came across, but I'm reporting it just for the sake of it. F-14 Pilot, TEMPO Shift+ROSB15 doesn't trigger Walkman Switch Side. Additionally, the default key binding (RAlt+B) conflicts with the default Tacview Bookmark hotkey. Another issue: Shift+JOY_BTN5 doesn't perform Stick Show/Hide. It looks like the command is missing from the DCS Controls page, but it could be me...
  16. =36=Witcher
    Just out of curiosity, i tested the airbrakes binding yesterday. If I'm nof wrong, I could stop airbrake extension mid course, but when I would retract it, it would retract completely.
  17. =36=Witcher
    Another question about F14: is there any chance you could implement the binary discrete/binary momentary airbrake logics switch, like M2000C has?
  18. =36=Witcher
    Copy!
  19. =36=Witcher
    Hi. I just bought F-14, but I can't figure out why the RIO profile has JOY_RZ associated to HCU Vernier Thumbweel. Which axis/combination should it be tied to? Also, is that correct that both the Throttle axis are not used in RIO mode?
  20. =36=Witcher
    My suggestion is to go on the Squadron Recruitments section of the forum (https://forums.eagle.ru/forumdisplay.php?f=665) and collect infos about some of them, or straight ask for some of them who trains with the Mirage in your time zone. EDIT: oh, you already did that :D but, just out of curiosity: why do you prefer Discord over SRS? It's a nice step forward in simulating the radio, and once you configure it properly (and believe me, it's really easy) works like a charm. RAZBAM has no financial issues AFAIK. It's just that... let's say, development isn't always as smooth as we would like to, with new issues popping up from time to time and long standing issues not yet fixed. You will learn more by reading this forum and its subsections.
  21. =36=Witcher
    How about some screenshots?
  22. =36=Witcher
    Where are you from? I bet there are virtual squadron who would be happy to teach you for free!
  23. =36=Witcher
    Awesome! Thank you!
  24. =36=Witcher
    Have you had any chance to consider mu M2000C suggestion? Just to know what you think about it ;)
  25. =36=Witcher
    Hi Home. I had another idea for the Mirage yesterday, when I was practicing emergency procedures. Bear with me, this is huge :D The Mirage has an alternative emergency throttle that the pilot can use in cause of emergency, who has its own axis. I know that the right throttle with the Warthog is basically ignored in single engine jets (at least, with the Mirage is) but it would be great if I could assign the emergency throttle to the left throttle lever because in an emergency situation I really don't want to have an eye costantly in the cockpit (moreover, the throttle is in a really inconvenient position and is really hard to interact with it using the mouse). Since this throttle is only active when a small plate is pulled, I think it could work like this: Axes for both the normal throttle and the emergency throttle are always assigned in DCS, but the levers are kept linked with the physical link. When in need, I can activate the emergency throttle in the cockpit and unlink the levers, only using the left one. The odds of going back to the main one is very low (the emergency throttle is a last resort most of the times, and you have to RTB immediately anyway since it responds with a considerable lag); but anyway, should that be the case, I can deactivate the emergency throttle in the cockpit and go back using the right one (or try to re-link them). What do you think? Would that work? And most of all, would that be too much of a pain for you to implement it? Maybe with a configuration option?
×
×
  • Create New...