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
    Hey there. I just bought Thrustmaster MFDs, so I began testing them with the Mirage. First thing I noticed is that the Formation Lights ON switch has no keyboard binding, thus is not working on the MFD. Dim and Off works fine. EDIT: now that I know the plane a little better since I've been flying it for a few months I plan to do a full review of the Mirage scheme, so I can report any other issue I may encounter.
  2. =36=Witcher
    Don't worry, if you have a look at the link I attached previously you can see the issue acknowledged by Razbam with a fix coming in the next update
  3. =36=Witcher
    Hi all, I just discovered TacView and I absolutely love it. Anyway, since I manly fly Mirage 2000C I noticed that both Matra Magic and 530D are listed as Matra in TacView. I did my homework and searched for info about this, and it seems it was actually an issue in the past that now is supposed to be fixes. Just to understand, did it regress somehow in newer versions? And are we aware of this? I'm using latest DCS beta and TacView 1.7.0.
  4. =36=Witcher
    Hey Home, I was wondering if you had a chance to look at this. Thanks! EDIT: It looks like a module bug: https://forums.eagle.ru/showthread.php?t=191194
  5. =36=Witcher
    Hello, it's me again. I found something really strange about Gun Arm in Mirage 2000C. When clicking on the switch with the mouse in the cockpit, the switch works as intended: UP stands for guns armed, while down stands for guns safe. When using the assigned switch on the HOTAS, instead, the switch moves correctly up and down in the cockpit, but even when safe the guns are still fired pressing the trigger on the joystick. I wonder if this is something related to the profile or a bug of the Mirage 2000C itself...
  6. =36=Witcher
    Well... Honestly, it's the "feature" that has no place to be in the first place... I mean, if I want to open the CommsMenu why should I want do this with the pinkie? But whatever. I'll keep it disable and live with it. I guess there's no perfect solution, at lest for me, here. Now, just a question while we're here: I noticed that I can't shut down both engine simultaneously: if I stop both my throttle by lifting them and bring them full stop only one of them gets stopped in the sim. It looks like DCS can't somehow handle the double event, and doesn't seem to be profile-specific. Of course, using two engines I guess I should stop them separately anyway, so no real issue, but can you confirm just for the sake of curiosity?
  7. =36=Witcher
    Ok, I can confirm. We can call this fixed :) Uhm... I don't know about this. At least in 1.5 S3 still toggles CommsMenu, but of course having set Clear CommMenu to 0 it now stays open.
  8. =36=Witcher
    Well... I double checked, but importing the WH profile doesn't assign the TDC Azimuth and Range axis, while it assigns the four cursors keys in the keyboard. I do have to assign them manually, and then the TDC is correctly assigned to the analog slew control. EDIT: sorry for keeping two different issues in one place, but I also made a little discovery about the radio comm issue. It seems that even with "Clear CommMenu after holding S3" is set to 1 in CTS, BTN20 actually fires if, and only if, the APU Start switch is set to off, according to the device analyzer. Here's what happens in game instead: Standing on the ground, APU ON: nothing happens Standing on the ground, APU OFF: CommMenu toggles when pressing, nothing on release Flying, gear down, APU ON: CommMenu toggles when pressing, nothing on release Flying, gear down, APU OFF: CommMenu toggles when pressing, and toggles again on release Flying, gear up, APU ON: nothing happens Flying, gear up, APU OFF: nothing happens
  9. =36=Witcher
    I have a Warthog and of course loading the wh profile. Which axis do I need to assign?
  10. =36=Witcher
    Yes, at least from what I saw from the controls. I'm still a newbie in DCS so perhaps I missed something, but didn't seem to find anything related to the radar in the Axis page.
  11. =36=Witcher
    So... I tried what you said, and apparently nothing changed: Comms Menu still pops up when pressing S3. So, I rolled back to the previous value (1) and now the Comms Menu pops up but then it's cleared on release, and this is correct since S20 is correctly firing. I guess that this is the intended behavior, so that's ok. Now, another question: by reading the scheme it looks like H1 should control the POV while holding S3 should control trim; at least, this is what I understand from "Trim Shifted". Instead, I control the Trim without S3, and the Padlock with S3, which is consistent with the /I labels. I'm a bit puzzled here... All I can say is that using the TARGET Device Analyzer, BTN30 is actually pressed every time I use H1 without the S3, while BTN32 is also shown as pressed if using S3. I'd be really glad if you (or anyone) could shed some light here. Sorry if my question should be a really basic one, but didn't find anything in the docs.
  12. =36=Witcher
    Ok... I remember the CommMenu popping out also when taxying, but probably I was already fiddling here and there with the scheme, so I guess I may be the one to blame there. Anyway this evening I'll try to set the flag in CTS and report back. So glad is an easy fix :) Speaking of the radar gate moved with the slew control, instead: I investigated it a bit and noticed that the slew control is mapped as two axis, while DCS expects button. Is this the reason the slew control can't be used for the radar gate?
  13. =36=Witcher
    Great! Thank you!
  14. =36=Witcher
    Following up to the above post, it seems the issue is not strictly related to the automatic firing of BTN20 since, according to analyzer software, BTN20 results as pressed only when releasing S3, while the Communication menu appears when pressing S3. Any tip?
  15. =36=Witcher
    Hi there. I think you already know, but let me tell you this anyway: AWESOME work. Now, a little question. I loaded the F-5e profile in DCS and started the script; everything looks good (at least, so it seems) apart from two annoyances: 1- When i press S3 to use it as shift the Communication menu pops up. It seems that releasing S3 fires BTN20, which is indeed assigned to Communication menu in DCS. Is this correct? EDIT: I even removed all the bindings in the DCS profile to Communication menu, but it keeps popping up. 2- Why the slew control does not emulate the radar gate? Is it on purpose? Thank you!
  16. =36=Witcher
    Even better :) Thanks!
  17. =36=Witcher
    Thank you! So I suppose this is something that will be fixed in the future (I hope with 2.5, but it's not that important after all). Thanks again :)
  18. =36=Witcher
    Hey all. I'm a newcomer in DCS; i bought the A10C and F5 after some years of hiatus from flight simulation. I wanted to get my feet wet with A10C, and was going to check the Vegas Tour mission; however, I can't understand if it's supposed to be playabler or not. As soon as I get in the mission, I only have an external view, and the A10 goes on its own, controlled by the AI. It takes off and follows a weird path, not even matching the marked waypoints, and it even crashes through the building at some point. I'm using DCS 2.2, and was wondering if I'm missing something. Thanks!
×
×
  • Create New...