Jump to content

flyingflatfour

Members
 View Profile  See their activity

  • Posts

    66

  • Joined

  • Last visited

 Content Type 

Everything posted by flyingflatfour

  1. flyingflatfour
    Here are a couple of screenshots trying to help understanding what is going on. The first one shows the status of VAICOM and SRS when pushing the Comm switch forward (physical "VHF" marking on the Cougar TQS), the second one backward ("UHF") in the F-5E using CTS. Could you also clarify the Cougar reference for this aircraft when VAICOM and SRS are activated in the script? Comm switch forward is shown as "PTT Common", backward as "AI Comms / CommState". Best regards
  2. flyingflatfour
    I've been fiddling a bit more into DCS today, here's what I found: 1) SRS device recognition problem: fixed by creating a blacklist.txt file excluding the HOTAS Cougar device (found in clientlog.txt), giving way to the Thrustmaster Virtual Device. "Allow other devices" should be turned off. :thumbup: 2) PTT common: I am confused as to what this actually implies. The CTS manual states that if VAICOM and SRS are used together, then PTT Common cannot be used as a feature on aircraft with multiple mic switches. If I understand this correctly, PTT Common means that there is one physical mic switch that triggers the selected radio if multiple radios are available? What is actually meant when saying that you "choose to use PTT Common" ? SRS by default will only switch to a radio when it's button is pressed and then needs the PTT button to be pushed to actually talk. There is however a setting that turns the radio buttons into individual PTTs. Could it therefore be clarified what to do if using VAICOM + SRS with the following aircraft?: Su-27, Su-33, F-5E, F-18 ? 3) A-10A profile: (HOTAS Cougar + shifted trim=1) the pitch trim is reversed
  3. flyingflatfour
    That would work, since I either use TS3 with a permanent transmission for early training flights in MP or I shut it down completely for full immersion using VAICOM + SRS :thumbup:
  4. flyingflatfour
    Not sure what you mean by global routine, since the radio mappings are different for each module? As far as I understood I thought all that was needed was to remap the switch to VAICOM TX5 for the F-5E profile when using TQS + VAICOM option ticked in CTS? Wilco :thumbup: My pleasure !
  5. flyingflatfour
    After doing some research in this thread I have not been able to find a clear solution to the following problem when trying to configure SRS inputs: - hardware: Thrustmaster Cougar HOTAS - software: Windows 10 / SRS / VA + VAICOM Pro / Thrustmaster TARGET / Home Frie’s CTS profile for TM hardware and DCS. Everything is up to date. CTS helps build a complex script according to the settings you specify in it’s GUI, then runs it via TARGET. TARGET is supposed to aggregate all Thrustmaster hardware inputs into one virtual device, and hide away the various hardware thus aggregated so they don’t interfere with the virtual device. The issue is, for no apparent reason, it seems that this hiding doesn’t occur in Windows 10... This hasn’t been an issue until trying to make SRS work, as all I had to do within DCS was to clear out any bindings related to the HOTAS Cougar and focus on the TM Virtual Device only. So the issue is that when I try to bind my joystick buttons to SRS, it picks up the HOTAS Cougar hardware inputs instead of the TM Virtual Device inputs. I thought this wouldn’t be an issue but unfortunately once the binding is done, pressing the button doesn’t trigger SRS... More information and screenshots in the following post under the CTS thread: https://forums.eagle.ru/showpost.php?p=3723855&postcount=963 Has anyone had the same issue ? Any help appreciated :thumbup: PS I have tried to use the “allow more devices” option and I am running both TARGET and SRS as an admin
  6. flyingflatfour
    Thank you SO much!! Would you consider as per previous post modifying the F-5E TQS mapping when using VAICOM to re-assign the comms switch aft position to intercom so as to be able to talk to the ground engineer using VAICOM without talking over SRS in multiplayer ? Concerning SRS, any idea on how to deal with the problem regarding Windows 10 not hiding away the Cougar when Thrustmaster Virtual Device is running? And last but not least, have you been able to think of a work-around for us VR players not using MFDs? :D Thank you very much Home Fries for your great work, best wishes for next year to you and your beloved ones! :thumbup:
  7. flyingflatfour
    I was also wondering, since more and more players are moving over to VR, if you would consider making the MFDs optional altogether? Although I understand they really bring a lot to those who are playing on a conventional screen, they are arguably an immersion breaker in VR. I realize this would potentially mean a lot of work, so maybe you would like to consider having a poll? When playing in VR, the functionality brought by the MFD's could for instance be replaced by: - aircraft systems interaction with all the virtual cockpit switches (easy to do in VR with 6 DOF and the mouse mapped to HAT1) - a status box of the same sort as VAICOM that can be switched on and off, allowing profile hot-swapping, gear state change, status LEDs etc What do you think? :wub:
  8. flyingflatfour
    Hi HomeFries! Reporting back on 2.27B :thumbup: - the CommState FC3 fix works ; I've successfully built and run the script with the A10A profile. - so I've tried to assign the commands in SRS but I am getting another problem: since Windows 10 is causing an issue with TARGET by not hiding away the HOTAS Cougar controller when launching the Virtual Combined Device, SRS is picking up the former instead of the latter... I thought this wouldn't really be an issue but in fact it seems like SRS doesn't react to the input, the radio box LED doesn't light up when pressing the TQS CommSwitch fwd / VHF button. Vaicom does pick it up on TX1 though. - I was wondering, since the F-5E only has one radio (UHF), would it be possible for those using VAICOM, to assign the AI COMMS/CommState (TQS CommSwitch aft / UHF) to Interphone, so as to be able to talk to the ground engineer without having everyone else on SRS hearing you out aloud? If I understand correctly you should be able to have VAICOM still pick it up by mapping it to TX5? - Any idea why the VAICOM control box only shows AUTO channel with the NORM setting? When I switch to MULTI it then shows the UHF, interphone and AUX channels BUT then I loose the mic switch functionality... When using the A-10C it shows up all channels right away. - the RDR range and mode are still acting in the reverse sense with the F-5E (CW vs CCW) Keep up the good work! :thumbup:
  9. flyingflatfour
    Right, that makes sense! Tried to build the script with the A-10C as default (I don't have the MFDs so I can't hotswap profiles), the following error message popped up :huh: (see screenshot attached)
  10. flyingflatfour
    Gotcha. Now the values I find are very close to the default ones. I think I was confused with this feature as I thought it would actually remap the throttle axis so that 0 throttle would equal idle detent, I guess these are only settings for the start/stop routines? If yes, will any axis setting within DCS affect the routines? Such ticking the "cursor" button and setting a saturation value so that the actual idle detent position corresponds to 0% throttle input to the game? See attached screenshot. Unfortunately the engine stop routine doesn't work in the F-5E... S3 + throttle aft of 1st detent for 2 seconds, right?
  11. flyingflatfour
    Please find attached a screenshot of the DCS controls menu with the VR=0 specific .lua file. The assignment for VR center doesn't work with S3+S4. Can I provide you with any other useful information? Thanks! NEVERMIND - I've cleared and reloaded the .lua, it's working now for no obvious reason...
  12. flyingflatfour
    One more question regarding the VAICOM + SRS integration: would it be possible for the F-5E, since it only has one radio, to affect the COMM SWITCH aft button to interphone (TX5) instead of AUTO (TX4)? That way I could talk to the ground engineer for air supply without everyone else hearing over SRS in multiplayer sessions :thumbup:
  13. flyingflatfour
    I think I am starting to understand but things are still confused in my head - how can the MIC SWITCH Left / Right on the TQS be used simultaneously for Radio2 / TS3 and for Radar Range DECR / INCR on the F-5E ? :helpsmilie: Furthermore how do I assign the proper buttons in SRS ? When the script is running and configured for the F-5E module, pressing the MIC SWITCH forward or aft doesn't make SRS react when trying to assign radios. MIC SWITCH Left and Right works but shows up as Keyboard 13 and 12 respectively... :helpsmilie:
  14. flyingflatfour
    Hi HomeFries, Reporting back on 2.27, I can confirm that the T7 button mapping is fixed for the F-5E. :thumbup: The mappings on the COMM SWITCH for the radar mode and range are still half-broken though: CW and CCW are still inverted:joystick: :D. Concerning the VR center issue I was having, you suggested modifying the TrackIR center command in CTS settings to the one used by my VR setup. However, I did configure CTS for VR and loaded the corresponding .lua for the UI layer in DCS. What I did instead was to directly edit the Thrusmaster Virtual Device assignment in the DCS controls menu under UI layer - VR - VR center and pressed S3+S4 on my Cougar, which now works. Maybe the VR lua that you provide was broken for this function? Concerning the TQS detents, I carefully read the references and I am confused at to what the Idle detent actually is: do we agree that it is the second click when you move the TQS from full aft? If yes, then measuring the axis values I find 1.5% and 8.4% respectively which I have setup in the CTS GUI. The behaviour I now get is that I need to set the TQS in between the two clicks for the engines to run at idle. Is this correct? As a sidenote, by default the HOTAS CCP axis values have a 5% upper and lower deadzone for the throttle, making it impossible to read the appropriate raw values for the calculation. Maybe it would be useful to add this information in the references? BTW, do the CCP settings for axis have any influence when using TARGET? Keep up the good job :thumbup:
  15. flyingflatfour
    Thanks! :thumbup:
  16. flyingflatfour
    Right, got it now ;-) I guess I should be able to remove that mapping in the controls menu ? On the other hand if I can get VAICOM to work properly I will eventually configure it to disable the comms menu altogether. May I suggest that you offer an alternative by making the script customizable for the F-5E with an option for manual engine start? In this case the player is still responsible for calling air supply (comm menu or VAICOM) and pressing the engine start buttons in the virtual cockpit, whilst still providing a routine that uses the TQS detents to move the throttles one by one from CUTOFF to IDLE? From my perspective as a VR user I believe this gives the most realistic and immersive experience. I have been going though that section several times, but I still can’t figure out how to assign DX buttons 20-23 to SRS: I can only assign a physical button by pressing it on the HOTAS...which physical buttons do they correspond to? Plus, the SRS GUI has evolved and doesn’t correspond to the manual anymore :smilewink: And I still don’t understand how, once everything is setup, CTS manages to integrate VAICOM and SRS at the same time? Which TQS buttons are used in this case and how can I as a player choose to speak to SRS or to VAICOM? For instance if I want to request air supply from the ground engineer how is that prevented from being transmitted over SRS at the same time? I am really sorry for bothering you with these questions but I am totally lost when it comes to this... :doh: Thank you, I will be looking into that. One more issue I am having concerns the TQS throttle axis mapping: even though I checked that CTS is properly configured for the various detents, in DCS when in IDLE detent the engines spool way above idle and will only sit at idle if the TQS is pulled all the way back to CUTOFF... should I play with DCS axis settings? Have a good day! :thumbup:
  17. flyingflatfour
    One more question: which combination centers the view in VR with the specific VR UI layer loaded and CTS configured accordingly? I couldn't find the information in the manual or references yet there is a mapping apparently. Best regards
  18. flyingflatfour
    Good morning Home Fries, Thank you for looking into these issues and for addressing them! :thumbup: Concerning the S3 button bringing up the comms menu, I’m not sure of what you mean by it being an F-5 thing? Will report further... As for the MFDs and the start routine: since I play in VR I don’t see how they could be of any real use... would it be possible to trigger the engine start by clicking the actual eng start buttons in the virtual cockpit instead of the MFD physical buttons, or else to map the throttle movements from CUTOFF to IDLE to the HOTAS? I have another question regarding VAICOM + SRS implementation. The CTS manual seems to be a little outdated and confusing regarding this, so that in the end I don’t understand how to map the directx buttons in SRS and I don’t understand how the HOTAS mapping works with with these utilities? Ideally I would need to have one mic switch to talk to VAICOM for instance to have the ground crew connect the ground air supply, and another mic switch to talk on the radio via SRS to other players in a MP session, but right now I don’t understand which buttons on my TQS are supposed to do that... Thanks for your help! FFF
  19. flyingflatfour
    Actually there is another issue I just found out for the F-5E: the H4 switch is correctly mapped for DM (forward) and DG (backward) radar modes, but it is showing reversed on the profile layout. ;)
  20. flyingflatfour
    Last problem I have found so far has to do with the S3 button: sometimes it just seems to pop up the communications menu for no reason? Sometimes, but not always though. Really strange... Other than that everything else seems to be working fine. As a conclusion it seems that all bindings that are assigned via the LUA file for the HOTAS Cougar are OK, but some of the ones assigned via the LUA file for the keyboard are broken: radar mode, range and flaps. Could this be related to my french version of DCS or Windows? Please let me know if there is anything I can do to help resolve these issues. :thumbup:
  21. flyingflatfour
    Another issue I have is with the flaps switch. Weirdly enough, the fixed (CTR) and up (T8 ) positions work, but the auto (T7) is broken. :shocking: Screenshot of the commands menu below. "volets" = flaps "commande au pouce" = thumbswitch "rentrés" = up "maintien" = fixed
  22. flyingflatfour
    Next problem I have encountered is with the Radar mode and range functions. According to the layout for the F-5E and HOTAS Cougar, the COMM switch is mapped as followed: LEFT = Radar range decrease RIGHT= Radar range increase /I LEFT= Radar mode CCW /I RIGHT= Radar mode CW For me however this is what happens: LEFT = Radar mode CW RIGHT= Radar mode CCW /I LEFT= Radar mode CW /I RIGHT= Radar mode CCW Attached are screenshots of the commands menu for those functions. "sens anti-horaire" = CCW "sens horaire"= CW "sélecteur portée - augmenter"= range - increase "sélecteur portée - diminuer"= range - decrease
  23. flyingflatfour
    After that I could finally start testing the profile in the game. I am currently flying the F-5E only. I began testing the engine start sequence. Unfortunately it doesn't work as it is supposed to according to the reference manual. Since I don't own the Cougar MFDs I manually ask for the air supply to be connected and applied via the communication menu, then I move the TQS to idle and click on the cockpit engine start button. According to the references this should automatically move the relevant in-game throttle to idle and startup the engine, but nothing happens. I believe this is due to the fact that there are no MFDs installed? Would it be possible to make it work even without MFDs please?
  24. flyingflatfour
    Sorry for the long delay but I have finally found some time to investigate further into the troubles I have been having with CTS. Last time I posted things had made progress - thanks to The_Nephilim: + TM Virtual Device finally working with all axes and buttons showing up + no more conflicts in the commands setup page within DCS (see below) - Cougar still showing up in the list of joysticks (doesn't seem to be a problem) - bindings don't seem to work as layed out for the F-5E After looking deeper into this, here are my findings: Concerning the issue I used to have with conflicts within the command setup, I found out this was caused by the fact that the modifiers' names that I added as required by CTS had to be manually changed from "Touche-JOY_BTNXX" to "JOY_BTNXX". I believe this is due to the fact that only the US language version of the game, or maybe of Windows, has the correct default names that will work with CTS. See screenshots below
  25. flyingflatfour
    Hi! For some reason I can't explain the TM Virtual Game Controller is now working properly all of a sudden... :doh: All buttons and axes are therefore properly showing up in DCS. So you might think hurray this is it! :lol: Unfortunately it seems like the bindings aren't doing what they should be doing according to the F-5E layout ... :cry: I will be looking deeper into this and will report back with a few examples so we can try to understand what's going on :joystick:
×
×
  • Create New...