Announcement

Collapse
No announcement yet.

DCS World TARGET profile for TM Cougar and Warthog + MFDs

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #21
    Hi Home Fries,

    Thank you for your help. What I did was just running the script en keep the Target Script editor open. But I think right now I have to use the Target Profile program as well...... and load the profile...

    Yes I did get several red lines.... I think it is becoming clear now. I paid only attention to the Target script editor..... (I'm such a fool....)

    Then I have a small remark about the other manual. You forgot in that one the page numbers as far as I can see. Maybe to look after that with the next version? I thought just mention it.

    I will check it out and drop a message here.

    I'm very exited to test your profile with the Su-25.

    /Arthur

    Comment


      #22
      Thanks, ArtMan. I'll look at that for the next release. Funny; the installation guide at one point didn't really need page numbers, but now with all of the modules and 4 appendices it exceeds 40 pages.

      Don't worry; you only really need the first 20 or so.
      -Home Fries


      My DCS Files and Skins
      My DCS TARGET Profile for Cougar or Warthog and MFDs
      F-14B LANTIRN Guide

      Comment


        #23
        Still no joy

        This is the outcome when I run the script with Target GUI:

        Code:
        *** Allocated ProcInstances found from the previous run: use FreeProcInstance() *** 
        Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll"
        Physical USB HID devices managed by script!
        Currently plugged USB HID devices[3]:
        1: "Thrustmaster HOTAS Cougar" - "USB\VID_044F&PID_0400&REV_0110&MI_00"
        2: "F16 MFD 1" - "USB\VID_044F&PID_B351&REV_0100"
        3: "F16 MFD 2" - "USB\VID_044F&PID_B352&REV_0100"
        USB HID device with hardware id "VID_044F&PID_0404" cannot be found
        USB HID device with hardware id "VID_044F&PID_0402" cannot be found
        USB HID device "F16 MFD 1"(USB\VID_044F&PID_B351\5&15D9C317&0&1) selected
        USB HID device "F16 MFD 2"(USB\VID_044F&PID_B352\5&15D9C317&0&2) selected
        USB HID device "Thrustmaster HOTAS Cougar"(USB\VID_044F&PID_0400&MI_00\6&61CFCED&0&0000) selected
        USB HID device with hardware id "VID_044F&PID_B10A" cannot be found
        Virtual HID devices managed by script!
        Connecting virtual joystick...Done
        Device name set to Thrustmaster Combined
        Connecting virtual keyboard...Done
        Connecting virtual mouse...Done
        
        
        DCS_Init (Profile v1.10):
           Map HOTAS Cougar:
              Axis mapping Cougar Stick...Done!
              Axis Mapping TQS......Done!
        
         Axis and MFD Init Complete!
              Init Trim with Padlock for TrackIR Users.
                 Hat1 (Trim)...Done!
        Flaming Cliffs 3/Su-25T Config (Profile v1.10):
           Enabling Aircraft Modules...Done
           Map Cougar Left  MFD (DX31)...Done!
           Map Cougar Right MFD (DX32)...Done!
           Map HOTAS Cougar for FC3 Config:
                 Initializing Throttle Engine Start/Shutdown Routines...Done!
              Button Mapping:
                 Shift Commands: S3+T7/T8 all momentary...Done!
                 Cougar Stick Buttons......Done!
                 Hat2 (TMS)......Done!
                 Hat3 (DMS)......Done!
                 Hat4 (CMS)......Done!
                 TQS Buttons......Done!
           HOTAS Cougar Mapping Complete.
        
        Setting Landing Gear Indication...Set!
        
         Flaming Cliffs 3/Su-25T Init Complete!
        
         DCS Init Complete!
        Setting Landing Gear Indication...Set!
        
        main returned 0
        In the first line I see an error message: "[CODE]*** Allocated ProcInstances found from the previous run: use FreeProcInstance() *** "

        I guess you have to program in this line in your script to free up earlier programmed Thrustmaster devices? When I restart my rig the MFD's are still in the same mode as programmed by your script before. I can imagine programming twice the same device can give errors?

        Then I see an other kind of error message:

        USB HID device with hardware id "VID_044F&PID_0404" cannot be found
        USB HID device with hardware id "VID_044F&PID_0402" cannot be found

        What is your script looking for kind of HID device?

        I still have no "Thrusmaster Virtual Game Controller (root)" as showed on page 17 but according to the outcome of the script as shown here:

        Virtual HID devices managed by script!
        Connecting virtual joystick...Done
        Device name set to Thrustmaster Combined
        Connecting virtual keyboard...Done
        Connecting virtual mouse...Done


        I should have a virtual joystick...

        Can you please tell me where I have to store the folders in the zip file. Maybe I made a mistake with that?

        Thanks again for your help.

        /Arthur

        Comment


          #24
          Home Fries,

          Just for your information:

          I only installed DCS world, FC3 and, of course by default, SU-25T

          In the game controllers settings I have only Thrustmaster Combined during runnning the Target script

          /Arthur
          Last edited by ArtMan_NL; 02-13-2014, 09:55 PM.

          Comment


            #25
            Arthur,

            Everything you posted looks normal. The *** Allocated ProcInstances found from the previous run: use FreeProcInstance() *** line happens often, and I don't know of a way to clear it at the start of a profile (running FreeProcInstance() causes its own error). Also, TARGET not finding certain HID devices is also normal; it found your Cougar HOTAS and MFDs so that's all you need to worry about.

            The initialization ran properly, so the files are in the correct folders. The big question I have now is when you go into the options menu in DCS World, do you see separate controllers for the Thrustmaster Cougar, F-16 MFD1 and F-16 MFD2? Or is there a single controller with something like "Thrustmaster Combined" or similiar?
            -Home Fries


            My DCS Files and Skins
            My DCS TARGET Profile for Cougar or Warthog and MFDs
            F-14B LANTIRN Guide

            Comment


              #26
              Hi Home Fries,

              Thanks for your quick reply. You were early this morning

              Yesterday evening I did some testing and here is my small report:

              As soon as I run your script my listed controllers: Thrustmaster Cougar, MFD1 en MFD2 change in Thrustmaster Combined. So under game devices in Windows 7 64Bit Ultimate (English Version) I see Thrustmaster Combined and in the Options menu of DCS as well.

              I don't have a virtual joystick at all so I used the "Thrustmaster combined". I have the idea that it is working now. I didn't get red lines in the options menu.

              I did a small testing and the SU-25 use his brakes when I touch the pinky "flipper" switch (S4 I believe?). Also the airbrakes are working as you described.

              So, its looking good?

              For your information: I use PeterP's trackir mod from your profile. Very nice you put that in the profile as well.

              Anyway, I didn't know the Target software has so much power. I thought for powerful profiles Foxy was the software.

              /Arthur

              By the way: sorry for my European style English hope I made myself clear
              Last edited by ArtMan_NL; 02-14-2014, 01:24 PM.

              Comment


                #27
                Thanks, Arthur. Glad everything is working well.

                I'll be sure to put "Thrustmaster Combined" in the manual as well for the next release.

                For S4, it does work as wheelbrake when the gear is down (you'll know this if you have LMFD LED2 illuminated). As soon as you retract the gear, S4 is responsible for autopilot override (Su-25T) or disconnect (everything else except for the Su-25 which has no autopilot).

                I agree about the power of TARGET. I hit the wall with Foxy a few years ago (40 logic flags just aren't enough, as it takes 3 logic flags just to do a simple if-then routine). If you can program in C++ or JavaScript, TARGET will let you do just about anything you want.
                -Home Fries


                My DCS Files and Skins
                My DCS TARGET Profile for Cougar or Warthog and MFDs
                F-14B LANTIRN Guide

                Comment


                  #28
                  Thanks Home Fries

                  I'll try to make a screenshot so you can include it in your manual as well.

                  Tonight I do some more testing but I think everything works well.

                  You did a great thing for the community by sharing this profile.

                  If you need a beta tester for upcoming profiles just give me a call. Later on I will use your profile for the Black Shark as well. I'm wondering how to this chopper fly with the cougar because the times I flown this bird I used my MS FFB (but that was a long time ago.....)

                  Ciao,


                  /Arthur

                  Comment


                    #29
                    Originally posted by ArtMan_NL View Post
                    I'll try to make a screenshot so you can include it in your manual as well.
                    Thanks for the offer, but I can easily make an update to the text without adding another figure.

                    Originally posted by ArtMan_NL View Post
                    You did a great thing for the community by sharing this profile.
                    You're quite welcome.
                    Originally posted by ArtMan_NL View Post
                    If you need a beta tester for upcoming profiles just give me a call.
                    It appears your PM function is disabled, but please feel free to send me a PM and we can discuss this.

                    Originally posted by ArtMan_NL View Post
                    I'm wondering how to this chopper fly with the cougar because the times I flown this bird I used my MS FFB (but that was a long time ago.....)
                    Funny you should mention the MS FFB; while I use the Cougar stick for the Ka-50 (which is easy enough to fly without FFB), for the UH-1 and Mi-8 I use my MS FFB2 as the cyclic and the Cougar throttle/pedals/MFDs for everything else. I have made those profiles (along with the P-51) less dependent on S3-shifted commands to allow use of a FFB stick with the profile. You lose CommState (the routine that lets you select communications menu function keys with hats 2-4), but that's about it.
                    Last edited by Home Fries; 02-15-2014, 07:21 AM. Reason: clarity
                    -Home Fries


                    My DCS Files and Skins
                    My DCS TARGET Profile for Cougar or Warthog and MFDs
                    F-14B LANTIRN Guide

                    Comment


                      #30
                      It appears your PM function is disabled, but please feel free to send me a PM and we can discuss this.
                      Strange, I will investigate this.

                      Still very happy with your profile but there is 1 very small issue. That's about the flaps. When I use shift + H3 (not shure H3 or H2) then I get only full flaps (= same as 2x button F instead of 1x button F)

                      This happens when I fly SU-25T.

                      regards,

                      Arthur

                      Comment


                        #31
                        I'll look into it, thanks.

                        I have S3+H3U/D set for flaps up and down respectively, but if what you say is true then those commands do full flap deflection and there are 3 states in the Su-25T. Those commands work with the incremental flaps in the A-10A and A-10C (though the C uses S3+H2), so I'm not sure why the 25T is different. Like I said, I'll look into it.

                        Thanks for the feedback.
                        -Home Fries


                        My DCS Files and Skins
                        My DCS TARGET Profile for Cougar or Warthog and MFDs
                        F-14B LANTIRN Guide

                        Comment


                          #32
                          You welcome,

                          I double checked this night when I was practising touch and go's with the SU-25T. You mentioned in your message 3 states in the SU-25T for flap deflection. I think you mean 2? The first state is for manoeuvring and deployed if you do an attack. The second state is for landing. The flaps will then be full deployed.

                          If I use S3+H2 I get only Full flap deployment. Maybe it is a good idea to do some time management for flap deflection? Because you are using the first flap statement by your Cougar quite a lot it must be activated when using S3+H2. The second state should be activated when you hold for 0.5 or 1 second the S3+H2 down. But that's only a suggestion.
                          Last edited by ArtMan_NL; 02-17-2014, 09:09 PM.

                          Comment


                            #33
                            ArtMan,

                            Thanks for uncovering this for me. I figured any multi-stage flaps would be treated like the A-10A (up or down does one increment), but the Su-25 does it differently as you described. The up/down commands do the discrete retracted and landing flaps states, and the only way to access maneuvering flaps is with the flap toggle "f".

                            For the next portion of the post, I should clarify that I really did mean 3 states for the Su-25. The states are landing flaps, maneuvering flaps, and retracted. So we were both in agreement, but I was counting the retracted setting as a state (which is necessary when thinking about mapping these things to arrays).

                            I thought about doing some sort of tempo like you suggested, but without a discrete keypress for maneuvering flaps it makes things difficult with very little upside, especially since S3+H3 tempo is shared with the landing gear and the Su-25 differs from the rest of the FC aircraft (with exception of the A-10A all other FC aircraft have only two states).

                            The solution I offer is fairly simple: I can keep the TARGET routine as is but change the mapping in the Su-25 and 25T in the LUA files so that S3+H3U performs the flap toggle instead of the flaps up command. Since the function is a toggle you don't lose any functionality, but without having a discrete "flaps up" command you will need to pay more attention to your instrument panel for flap state.

                            What are your thoughts?
                            -Home Fries


                            My DCS Files and Skins
                            My DCS TARGET Profile for Cougar or Warthog and MFDs
                            F-14B LANTIRN Guide

                            Comment


                              #34
                              but without having a discrete "flaps up" command you will need to pay more attention to your instrument panel for flap state.
                              I have no problems with that. It is always a very good idea to look at your instrument panel.

                              You are right about the 3 state. It is a different approach for looking at it

                              One thing I didn´t check yesterday evening. Did you make a function for the brake-parachutes in your profile? Sometimes I´m messing things up during the landing and it isn´t clear for me if I deployed the parachutes or not. Sometimes I have to double check with the outside view if I deployed them.

                              I have to sort this out. I´m not sure if there is a instrument panel warning light for those parachutes.

                              /Arthur

                              Comment


                                #35
                                Home Fries,

                                Don't mean to hijack your thread, but how do you make such great MFD printouts?

                                Have been working on some TARGET profiles for a couple games and the only way I have found to make the MFD printouts is Thrustmaster's online program. Am getting tired of looking at the same green background. Not to mention the lousy text formatting in TM's program.

                                Comment


                                  #36
                                  Ssnake,

                                  It's actually pretty easy if you have some photo-editing skills and software that allows layers. Just import a thrustmaster printout (save as pdf or bitmap) into your editing software and use this as your background. Add guides to represent the boundaries of each button (as shown on the printout), then select the white space surrounding the printouts (i.e. magic wand). Copy this and make it your top layer so you will always have your outline (you can even add a 1 point border if you're feeling fancy). Between the guides and the borders in the top layer, you can do anything you like in the middle.

                                  As a tip, I recommend using 6-7 point font for the text in each of the button spaces. It's easy enough to see but lets you get 3-4 good lines in before it gets too crowded.
                                  Last edited by Home Fries; 02-22-2014, 06:26 AM.
                                  -Home Fries


                                  My DCS Files and Skins
                                  My DCS TARGET Profile for Cougar or Warthog and MFDs
                                  F-14B LANTIRN Guide

                                  Comment


                                    #37
                                    Thanks much for the detailed explanation.

                                    Unfortunately my photo-editing skills are even worse than my targeting skills. I didn't even understand some of the terms you were using, but after a little googling found the program paint.net.
                                    Looks like it has the editing tools you were talking about. Will give it a try.

                                    Again, thanks.

                                    Comment


                                      #38
                                      You have to start somewhere, Ssnake. I'm self-taught; I started tweaking skins in Flanker 2.0 and it grew from there.

                                      As long as you learn to use the layers, it will come easy. The polish may take time, but that's to be expected.

                                      One technique I also like to use if I want to try something new: duplicate the layer and practice on the duplicate. If it works, delete the original layer, or hide it and drop it in the layer order if you're concerned about losing your history.
                                      -Home Fries


                                      My DCS Files and Skins
                                      My DCS TARGET Profile for Cougar or Warthog and MFDs
                                      F-14B LANTIRN Guide

                                      Comment


                                        #39
                                        Hello Home Fries,

                                        First thank you for the great work with this profiles!

                                        I'm a returnee to simualtions and dusted off my cougar! And it seems i've forgotten about everything.

                                        I'm using it with DCS world 1.28 RC1 beta for the F-15C and i'm having trouble because some functions seem not to work or i don't get the timing.

                                        I can't get many things like airbrakes, trim or dofight swith BVR mode working. I the flaps working (once i got the tempo ) but then in flight they didn't work anymore.

                                        Is it me? or your profile maybe do not fully work with 1.28?
                                        Core I7 4770K-16Gb DDR3 1800- SLI MSI GTX 770 Lightning 2Gb-Win 7 64 bit - TM Cougar

                                        Comment


                                          #40
                                          I'm working on a 1.2.8 compatible version of the profile, but the release is only 1.2.7 compatible right now.

                                          Since 1.2.8 changes the format of the included LUA files (which are very necessary for the profile), the only real option is to take your joystick and keyboard lua files from 1.2.7 and put them in the proper 1.2.8 folders (deleting the diff.lua files). That should provide the solution for everything except for the autopilot and nosewheel steering on the F-15C.
                                          -Home Fries


                                          My DCS Files and Skins
                                          My DCS TARGET Profile for Cougar or Warthog and MFDs
                                          F-14B LANTIRN Guide

                                          Comment

                                          Working...
                                          X