Jump to content

Oiz0

Members
 View Profile  See their activity

  • Posts

    29

  • Joined

  • Last visited

Personal Information

  • Flight Simulators
    DCS, MSFS2020, IL2GB
  • Location
    France
  1. Oiz0
    Hi Home Fries, I think I have found a problem on Viggen Cougar profile Airbrakes don't work fine. They almost don't move. If it can help to figure out what is the cause , I reported you similar issue for AV-8B Harrier (8 October 2021 - page 79) and you solved it
  2. Oiz0
    Hi Home Fries, Thank you for your response. Yes, it's minor issues. I have a workaround for the Mig-21Bis, configuring VoiceAttack profile. And for Mirage Radar range, it's easy to change the range, simply sliding the TDC on top/bottom edge of radar VTB Just few others sugestions about M2000C and VR : With M2000C, I have problem with antenna elevation sensibility I use a HOTAS Cougar, and looks like Razbam has changed key/axis mapping of the Radar Antenna elevation I think before (?), the antenna elevation was possible using an Axis, and as I remember it was progressive. Something has changed ... Looks like it's no more possible to use axis and it has been replaced by 2 keys Radar Antenna DOWN/UP With this new mapping, "Range Knob" is difficult to use and because it's All or Nothing. I must very quicky put the axis in center afeter activate one of the key with "Range Knob", to avoid large movements. But even doing that, it's very imprecise I don't know if there is a way to ameliorate this, to be able to adjust "Range Knob" sensibility I also use VR and it would be nice to map keys "toggle Zoom VR" and "Recenter VR Headset", may be using same keys as the /I TriggerZoom Toggle and TrackIRCenter (S3+S4), because when VR is activated, I think these functionalities are useless ? I simply hope DCS will ameliorate Zoom VR because it not very good as it distords the view, but it's sometimes useful in VR to read the cockpit buttons text that are a little blured
  3. Oiz0
    Hello Home Fries, May be I'm wrong but I think I have found 2 little issues (I use HOTAS Cougar) I'd like to report M-2000C : The Radar Rng Disp Decr & Radar Rng Disp Incr don't seem to work anymore, pressing S3+H2L or S3+H2R as indicated in the Profile JPG document It's not a drama as there is another way to increase/decrease radar range (eg. sliding the cursor on top/bottom edges of radar) Mig-21Bis : I use Vaicom and PTT (MSD) doesn't work (anymore ?). I guess it was working last time I (seriouly) used the Mig-21Bis (several years ago !). Looking Vaicom, I see they map the radio on TX2 ... I suspect the MSD call TX1. As workaround, I first set the PTT on Vaicom to SNGL ... but I found a topic explaining how to set a Conditional (if statement) in VoiceAttack. https://forum.dcs.world/topic/254389-per-aircraft-ptt-buttons/ So, when current module is MiG-21Bis, when I press Button 20, it executes TX2. I simply hope it will continue to execute TX1 for my other modules
  4. Oiz0
    Even if it can take a while (what I understand), nice to hear that
  5. Oiz0
    Hi Home Fries, Just wondering if you plan in short/medium future to acquire Mirage F1 module and develop a profile for it ? I am hesitating to purchase a module when it doesn't have a profile in CTS
  6. Oiz0
    As you notice you must configure your Track IR Center function with Ctrl + Shift + F12 In CTS Hardware Configuration, have you set Head Tracking Hardware to 1 ? Have you tested this combinaison of keys outside DCS to check if it center well your track IR ? Have you tested to check "Exclusive" for the Track IR profile you have defined for DCS and that use this combinaison Ctrl + Shift + F12 , to be sure it's this one that is run ?
  7. Oiz0
    Thank you for your work I have installed the F-15E profiles for Cougar All looks fine for pilot, but for WSO, there are plenty of red alerts. I have well created the 3 modifiers 30, 31 and 32, as for others planes Do you have also that ? Is it simply because it's in WIP or do I have miss something ?
  8. Oiz0
    Hi Home Fries, I understand. Cougar has less possibilities than Warthog and it's not easy to implement all on this HOTAS (eg. A-10C) I'm learning Apache and for the moment and I don't really know how this "Sight Select Switch" is important I'm using VR, so personnaly SHIFT + H2 would be fine. Or SHIFT + H3 but you need to move IHADSS toggle somewhere else (Control Ovly Toggle is less important to have on Hotas, I think ...) I see you never/rarely use SHIFT + (T2, T3, T4, T5) on throttle. I guess there is a reason.
  9. Oiz0
    Hi Home Fries, Yes, I have well my 3 modifiers defined for this module But I don't find what correspond, for example the JOY_BTN31 + JOY_BTN_POV1U combinaison I've also checked your profile documentation for AH-64D and I don't find where are defined the 4 "Sight Select Switch" commands asscoiated to these combinaisons PS : in fact, on Warthod doc profile, I see "Sight Select Switch" on the throttle, but of course not on Cougar as doesn't have such POV on throttle. Is it already defined somewhere else on Cougar ?
  10. Oiz0
    Hello, I am trying to learn AH-64D (not easy !) and I'd like to use "Sight Select Switch" commands but I don't find how on my HOTAS Cougar In profile, I see for example "Sight Select Switch - HMD/Up" is mapped to JOY_BTN31 + JOY_BTN_POV1U How can I activate this, and in general what correspond JOY_BTN31 ?
  11. Oiz0
    Thank you. I have sucessfully installed CTS with these zips
  12. Oiz0
    Hi, Is server down ? I try to reinstall CTS, but since yesterday it can't connect I see there is a version.txt attached in original post. Do I need to replace the one from the 2.55 installer by this one ? I have tried both, but without success
  13. Oiz0
    Hello, For AH-64, we have 2 profiles for keyboard : TARGET AH64D PltCPG kb v264aN.diff.lua TARGET AH64D PltCPG kb v264N.diff What means the "a" in profile name version ?
  14. Oiz0
    Thanks you for Apache addition. I was waiting this (and Chuck Guide I hope) before start to learn the module. And thank you too to continue to support the HOTAS Cougar. I was a little worry you focused only on Warthog
  15. Oiz0
    Hi, For DCS, I use CTS+VAICOM+SRS I have configured these softs as below to use Dynamic Switching, to be able to choose to talk to AI (VAICOM) or humans (SRS) This works fine with M2000. When I select the TX1, I can talk to Vaicom (AI). On SRS overlay, it shows a * in front of the selected radio If I say "Switch", then it switches to Voip (human) and on SRS overlay, I can see *+TR These tags on overlay are very useful to know who I'm talking to But in A-10C II, it seems not work so well. I can communicate with Vaicom (AI) but I don't see the * and when I switch to Voip, I don't see any *+TR I have a doubt if this is only a visual issue or if really, my voice is not transmitted to SRS (I may need to do some tests with mates ...), despite I see the RLY orange light in Vaicom PTT tab Anybody has an explanation/solution why I don't see the * and *+TR tags on A-10C II ? • (SRS Settings Page) Radio Switch works as Push To Talk (PTT): ON • (SRS Settings Page) Allow INCOCKPIT DCS Controlled PTT: OFF • (SRS Settings Page) Allow VAICOM TX Inhibit: ON
×
×
  • Create New...