Jump to content

Oiz0

Members
 View Profile  See their activity

  • Posts

    37

  • Joined

  • Last visited

 Content Type 

Everything posted by Oiz0

  1. Oiz0
    Thank you Zabuzard, I'm sorry, but after some tests, I think all is my fault and my problem was due to I use a wrong joystick profile. I use CTS utility by Home Fries but he seems to have stopped his utility development and he has not yet developed a profile for the F-4E, so, I tried to use his generic DX profile but it doesn't work. If I load the F-14 profile, it works (I guess I loaded the key/joystick mapping from the F-14 profile what also may have caused the issue loading DX profile) I will have to find the best way to do between using/adapting his F-14 profile, or use his DX profile, or simply not using CTS when I use the F-4E module. What confused me was I saw the stick moving, so I thought it was changing the trim, but looks no. Now, I see that when I trim, it moves also the little stick hat (with a green dot), what it didn't do before ... Again, sorry as it's a false issue, all my fault !
  2. Oiz0
    Thank you all for your responses and explanations. Unfortunatly, if I continue to trim nose down (> 30 secs), and this even after the stick has moved fully forward as you described, the pitch trim gauge still doesn't move I guess my stick trim mapping is fine, else my stick would not move even forward when I use it, no ? FYI, I have just started the engines, and set LGEN AND RGEN to ON Do I have to enable some other things to make this work, eg. the STAB AUG switches ? Do I have to respect a sequence ? I have trying with and without and it doesn't seem to change anything. Thanks
  3. Oiz0
    Well, searching info in this forum, in pinned topic "Issues you may encounter when trying the F-4E for the first time, and how to avoid them.", I read this : Issue: My trim is not working on the ground, the stick is either full forward or full back and when I trim it does not change position. Fix: This is correct as is on the ground. The bellows system pulls at the stick with increasing airspeed, while the bobweight system pushes the stick forward with increasing G. In flight and when you are trimmed out well, these forces roughly balance each other out naturally. On ground however, the bellows measure airspeed 0 and hence do not add any force that would counter the bobweight system pushing the stick forward. You also will not see trim doing anything in that situation, since the trimming merely changes the length of the lever to which the bellows can apply force to the stick and do not move the stick around directly. I'm not sure to understand well (English is not my native language) and if it's normal, why it's working in some youtube videos. has that changed since 1 year ? And if it's "normal" that trim indicator doesn't work, how can we know how to trim to 3 degrees nose down during pre-takeoff setup ?!
  4. Oiz0
    Hi, I'm starting with this module, and during the F-4 startup procedure, I see it's recommended to set trim nose down to 3 degrees. I try to do so, and I see well my stick move forward, but the pitch trim indicator needle doesn't move ! I have watched startup videos and needle moves there. So, I suppose I don't understand something and/or I have not done something, but could someone explain me whhat happens and what I have to do ? Thanks
  5. Oiz0
    Hi, When I launch CTS (and so Target GUI), I get many warnings "USB HID device with hardware id ... cannot be found" Do you know from where these "unknown" devices come from ? I suspect it's old devices I connected before. I don't think it's a big problem as CTS seems to work fine, but is it possible to cleanup these devices to have something clean during startup ? Thanks PS : sorry, after some search, in fact these warnings seem to be normal as these "not found" devices are declared in target.tmh file. For example VID_044F&PID_040E is for TCASidestickXPilot device that I have never owned/plugged. I simply never took care and noticed these warnings before.
  6. Oiz0
    Well, after done a backup of my ..\TARGET Profiles\CTS\DB and ..\TARGET Profiles\CTS\DCS folders (hoping its enough ), I have tried to modify all occurences in tmc files of &Joystick and Joystick[ by &AVA_F16 and AVA_F16[ And looks like it works ... at least it integrates now the AVA base in the Combined controller After, I don't know if the the fact to change the base the buttons mapping, and so if CTS profiles are still valid. I have very quicky tested M2000 and few buttons and it looks ok for the moment.
  7. Oiz0
    Hi Home Fries I have recently acquired a new Thrustmaster AVA base (so replacing the Warthog base), but when I try to use CTS, it doesn't work The AVA base is not "integrated" in the combined virtual control Any idea/instruction how I could adapt your scripts to make my AVA base recognized ? PS : I have found this on net. I will try ... In which file(s) I must replace the &Joystick ? In all .tmc files ?
  8. Oiz0
    Hi, I hope also . I see last time HomeFries has visited this site was mid October. I assume he has others preoccupations. Or may be he's developing CTS 3.0 ? Let's hope. I'd need furiously profiles for the F-4 Phantom & Mirage F1 I have bought this year. Without CTS, I must admit I'm quite lost and I have not really the motivation and competencies to build my own profiles, that would be far less good as the ones HomeFries develop.
  9. 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
  10. 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
  11. 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
  12. Oiz0
    Even if it can take a while (what I understand), nice to hear that
  13. 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
  14. 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 ?
  15. 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 ?
  16. 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.
  17. 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 ?
  18. 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 ?
  19. Oiz0
    Thank you. I have sucessfully installed CTS with these zips
  20. 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
  21. 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 ?
  22. 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
  23. 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
  24. 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) Thisworks 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
  25. Oiz0
    I start to understand I need to read carrefully the Multiplayer (VOIP INTEGRATIONS) chapter of VAICOM user guide (pages 23 to 27) and I need to use Dynamic Switching I have configured VAICOM+CTS+SRS sofwares as above screenshots It seems to work fine with M2000. When I select the TX1, I can talk to Vaicom (AI). On SRS overlay, it shows a * 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 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 So, I have a doubt if SRS catch and transmitt my voice, despite I see the RLY orange light in Vaicom PTT tab I will need to do some tests with humans to clarify this ... PS : I will probaly post on DCS-SimpleRadio Standalone topic of this forum as this is probably not a CTS issue. Thank you
×
×
  • Create New...