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 don't know why it took a couple of builds to actually register the change in the values, but in the end I made it work, and I think it's perfect. Thank you!
  2. =36=Witcher
    Ok, I'll test it as soon as I can and report back!
  3. =36=Witcher
    Great news :) Whenever you have time, no pressure ;)
  4. =36=Witcher
    Hey there! Just a question, since I'm at work and can't test: does the Speedbrake switch on the throttle register an input in the middle position? Just asking because I was having a look at the M2000C DCS manual, and noticed the part about the real speedbrake throttle switch behaviour (attached). It would be cool if we could recreate the same scheme!
  5. =36=Witcher
    Hey there. As Home Fries surely knows, I've been using CTS with the M2000C for quite some time now, and I can assure everything works fine once you setup everything. Feel free to get in touch via PM or Discord or whatever messaging system you prefer!
  6. =36=Witcher
    So, a little update. I managed to disassemble the whole throttle, and I played around with the position of the sensors. I am pretty sure that they are the ones to blame: [photo] because as soon as I moved around the axis data would change drastically. However I couldn't find a sweet spot to improve my scenario... I only managed to make it a little worse before going back to the point I was at before. So... I guess that the Z axis sensor is faulty, at least partially. How it happened after two years from one day to another is beyond me, but whatever. Now: unfortunately it seems that since this is a refurbished unit bought from the Thrustmaster store the warranty lasts only six months, and I am well beyond that limit. The tech support told me that they usually send a lot of spare parts, but I was wondering if they would also send that specific sensor. Also, given this new data, could it be the magnet itself that is somehow discharging? If so, do they send over that one as well?
  7. =36=Witcher
    From what I understand from Google Translate, it's unlikely we have the same issue although the symptoms are really similar: he experienced the issue from day one, while I've been flying fine for almost two years (with a few months og hiatus). Anyway, the guy is talking about a magnet but I can't quite understand where this magnet should be. Where can I find some detailed info about it?
  8. =36=Witcher
    Hi all. I bought an official refurbished Warthog from Thrustmaster almost two years ago, and it always worked flawlessly. In the past few days I had a few issues with the scripts not correctly loading, but whatever, I blamed TARGET, rebooted and always fixed these issues. Until this evening... The right throttle lever is acting really crazy, with two issues at the same time: 1- From Device Analyzer I can see it correctly at the end of its range while in IDLE, but bringing it to MAX only reaches almost 60% of the range (Device Analyzer reads it at 5418 out of 16383, should be 0) 2- When lifting up the lever and bringing it to OFF, it suddendly spikes from 0% to 100% just when touching the end point I already tried the calibration tool multiple times (1.07 is the last one, isn't it?) and also tried Windows calibration. While the TM Calibration tool doesn't change anything, the Windows calibration actually seem to bring the situation normal for 1 but not for 2. Also, in TM Device Analyzer I still can see the throttle only on the 0%-60% range, even if on Windows Control Panel it shows as 0%-100%. Is there anyone here to give me some hint, please? Thanks!
  9. =36=Witcher
    Sounds fair! Thank you :)
  10. =36=Witcher
    Hey there, another MFD JPG fix needed. High contrast M-2000C, right MFD, BRT switch: sts mode / n mode should be written in green italic lowercase (both tempo + S3), PSM cycle should be written in green lowercase (S3). Also, normal JPG has that switch in an old version I think (it doesn't mention n / sts but it shows VENT switch)
  11. =36=Witcher
    I knew there had to be a reason :) I guess I'll follow your advice. Thanks again!
  12. =36=Witcher
    Gosh, I feel like an idiot. I spent hours scouring the profile JPG searching for it. Thank you! While we're here, just a question, still for the Mirage: I noticed that the Antenna Scan Bars switch has some delay, and that if I quickly switch from 4 to 1 or from 1 to 4 it will miss the second input, keeping the bars at 2. Is this a known issue that you cannot work around in other ways? If yes, can I tweak some profile settings in order to make it more responsive?
  13. =36=Witcher
    Hey man, I have a small request for the Mirage 2000. Could you find room for In-Flight Start Switch (RCtrl+RShift+I)?
  14. =36=Witcher
    Isn't Flashlight LAlt+L?
  15. =36=Witcher
    +1
  16. =36=Witcher
    Also, in F/A-18C the Dispenser Switch only updates the first time in the AMPCD SnapView. All subsequent changes of the switch are done but the SnapView doesn't update.
  17. =36=Witcher
    Hey there! I'm back after a couple of years hiatus, this time learning F/A18C after my previous Mirage journey (not ended... but will pick up some time in the future) I noticed a really minor error in the Warthog PDF: the Engine Crank positions are inverted, so Aft is left engine and Fwd is right engine in the profile. Should I see additional issues I'll let you know!
  18. =36=Witcher
    I'm sorry, could you please explain a little your issue? I flew the Mirage usually, but can't understand exactly what you're talking about...
  19. =36=Witcher
    A question about profile switching. I'm looking into make TARGETGUI script launch the profile at startup; I managed to automatically hide the window (thanks to a utility called NirCmd) but I'd like to mute the voice that sounds when the profile initialization is complete but not the ones I hear when I switch profiles through MFDs. I tried disabling "Speech enabled on aircraft cycle" in CTS options and rebuilt the profile, but the voice is still there (for both the initialization and the profile switching, by the way, which shouldn't be if I understand correctly). Anyway, it would be great if you could separate the speech options, letting me disable the initialization one but keeping the selection one.
  20. =36=Witcher
    Sorry not being clear, I was referring to the Mirage PSM selector (RBRTUP and RBRTDOWN).
  21. =36=Witcher
    Great, I love when things fall nicely in place :) So... Only thing I have to report is some strange behavior I experienced today with PSM up and down, it looked like only working with gear down a couple of times... But then raising and lowering once or twice apparently fixed it. It's odd, but I'd say that's nothing to worry about. Thanks for all your efforts!
  22. =36=Witcher
    You're the best :D About my shifted states finding? Any confirmation? EDIT: I may add the confirmation myself. Of course, once the gear is up, the command is ignored because on the throttle the APU START switch needs to be able to trigger the Inflight Start switch. Am I right?
  23. =36=Witcher
    Thanks for the update! However... sorry to crash the party, but it looks like the handbrake from the MFD is not working now. I mean, the actual control doesn't trigger, not the shifted state. The APU START + Gear Down State triggers both the LED and the control instead. In the meanwhile I think I figured out the problem with the shifted states: simply the parking brake state doesn't trigger if the gear is up. Sounds legit, if this is the case: can you confirm, so we can dismiss this issue?
  24. =36=Witcher
    Yeah, I'm aware of this, since this always happened when, for example, I jump in an instant action and already airborne. However, it looks like that shifted states are completely dead after the first crash: this means that even lowering/raising the gear or the parking brake doesn't change the state (and the related LED in the MFD stays off). However, I'll test this properly in a few hours, so I hope to be back with a more detailed response.
  25. =36=Witcher
    Yep, that did it. I completed a full-ish review, and these are my findings: - It looks like Gun Arm TOGGLE is by default assigned to Keyboard on LCtrl+6, but then the EAC switch on the throttle doesn't trigger. The only way I could find to fix it is to assign JOY_BTN26 (the switch itself) to Gun ARM, Else SAFE (3-Pos. Switch Abstractions), that had no binding by default. - The TOT/PAR switch (ROSB4 simple click, which is bound to JOY_BTN32 + JOY_BTN4) acts a bit weird, since it has to be clicked twice to record one input. - LOSB16 (if I understood the numbering correctly -- however, the one just above Selective Jettison) is currently associated to "Air Refueling Lights ON/OFF" command in the Controls page (I'm not in front of DCS right now, so I'm going on with only my memory. Will update the post as soon as I get back home). However, this switch actually controls the "SEPRAM Recorder" switch in the cockpit (the switch before Taxi Lights, left console); and according to the Mirage manual such switch should be not operational, since it's not even mentioned in it. The actual Air Refueling switch is a 3-Way switch (OFF, ON without lights, ON with lights) placed above the emergency throttle (still in the left console). So I suggest you to map LOSB16 to this switch (again, will update the post with exact mappings as soon as I get home), with the same logic of the other views (TEMPO: upper position; simple click: middle position, shift+simple click: lower position) - Something not strictly related to the key bindings: As soon as I enter cockpit for the first time after loading the profile, all the "shifted state" (Gear up/down, Parking brake up/down) commands are working fine. However, as soon as I crash the plane (or possibly just quitting to the main menu? will test further) it seems that shifted states are not working anymore. Will test further to see if I can find any specific pattern in this - Also not related to bindings, sometimes it looks like snap views are not immediately available, but only by using some specific key combination in H3 seems to fix this. Again, will test better for a specific pattern. I will be editing this post until your next reply in order to not to make the thread unreadable with many posts. Take care!
×
×
  • Create New...