Announcement

Collapse
No announcement yet.

Universal Laser Code Implementation

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Universal Laser Code Implementation

    I saw for the a-10C II a discussion about setting laser codes for weapons. It brought to mind the fact that the implementation is non standard across modules. They also pointed out that it is not possible to change the weapon codes inflight IRL.

    Here is a possible way to implement it that could be standard across all modules and intuitive for new users. It would also give a mechanism for preventing inflight reassignment of codes (or allow it if you want to appease fans) without making the modules' avionics unrealistic.



    The idea is simple. If you select a laser guided weapon during rearm, it would pop up a box beneath it to enter in the laser code. You may need to also implement some message that pops up as error or defaults back to 1688 if an invalid code is entered. If a player wanted to review their codes inflight they could just pull up the rearm screen again. If you wanted to be nice to players who like changing their codes inflight maybe put a button in there to update codes. (this button could also be the way to trigger the "Invalid Code" message if a code entered was outside of acceptable ranges.

    #2
    Good idea, much better than kneeboard.
    Computer: Potato
    Modules: FC3 | M2000C | A/V8B | Viggen | F-5E | F-14B | F-16C | F/A-18 | A-10C | Supercarrier | UH-1 | MI-8 | Gazelle | KA-50

    Comment


      #3
      That's exactly what I proposed couple of months ago.

      Sent via mobile phone using Tapatalk

      Comment


        #4
        +1

        Very good idea indeed!

        This way, there's also no more need for unrealistic code changing from inside the cockpit
        System specs:
        Spoiler:
        System specs: i7-8700K @stock speed - GTX 1080TI @ stock speed - AsRock Extreme4 Z370 - 32GB DDR4 @3GHz- HP Reverb v2 - Saitek Pro pedals - TM Warthog HOTAS - TM F/A-18 Grip - TM Cougar HOTAS (NN-Dan mod) & (throttle standalone mod) - Pointctrl & aux banks <-- must have for VR users!! - Andre's SimShaker Jetpad - Fully adjustable DIY playseat

        Comment


          #5
          Originally posted by sirrah View Post
          +1

          Very good idea indeed!

          This way, there's also no more need for unrealistic code changing from inside the cockpit
          Just curious, is the F/A-18 implementation realistic? That's the only module I own that can change codes inflight. Super practical, I am just wondering if that is the case IRL.
          The kneeboard thing is a real hassle for me in VR (when I fly the Viper). This new idea is really good, I support it wholeheartedly.

          Comment


            #6
            Originally posted by sirrah View Post
            +1

            Very good idea indeed!

            This way, there's also no more need for unrealistic code changing from inside the cockpit

            Except when dealing with AI JTACs. Currently, there is no way of telling the JTAC which code to use. Fixing that issue is a prerequisite before removing the in-flight code change workaround.

            Comment


              #7
              Originally posted by Qiou87 View Post
              Just curious, is the F/A-18 implementation realistic? That's the only module I own that can change codes inflight. Super practical, I am just wondering if that is the case IRL.
              The kneeboard thing is a real hassle for me in VR (when I fly the Viper). This new idea is really good, I support it wholeheartedly.
              It's only realistic for the Maverick. It's made up for the other weapons.
              476 vFG Discord | 476 vFG Website

              Comment


                #8
                +1 awesome idea!
                Modules I own: F-14A/B, F/A-18C, Supercarrier, F-16CM, AJS-37, F-5E-3, MiG-21bis, Ka-50, A-10C (+ A-10C II), UH-1H, Mi-8MTV2, P-47D, P-51D, FC3, MiG-15bis, Yak-52, CA, C-101, Hawk
                Terrains I own: Syria, The Channel, SoH

                System (RIP my old PC): Dell XPS 15 9570 w/ Intel i7-8750H, NVIDIA GTX 1050Ti Max-Q, 16GB DDR4, 500GB Samsung PM871 SSD (upgraded with 1TB Samsung 970 EVO Plus SSD)

                VKB Gunfighter Mk.II w. MCG Pro

                Dreams: https://uk.pcpartpicker.com/list/mBG4dD

                Comment


                  #9
                  This has been proposed several times over the past few months/years. Having to set the laser code on the rearming window as shown above is the best possible solution!
                  Intel i7-4790K @ 4x4GHz + 16 GB DDR3 + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

                  DCS Panavia Tornado (IDS) really needs to be a thing!

                  Comment


                    #10
                    Just keep in mind that this there are two parts to this. The first is the great idea you suggested, and the second is making the AI JTAC capable of changing laser codes when communicating with a plane.

                    I always thought making those changes is low priority since making an overhaul to the JTAC system is probably low priority as well. After the F16 came out with a more true to life way ot changing the code, I don't know what's their take on this anymore.

                    Comment


                      #11
                      Great!
                      B450 Gaming Pro Carbon AC, Ryzen 3600, 32Gb DDR4 3600MHz, GTX1070Ti, CH Stuff, Oculus CV1

                      Wishlist:
                      AH-64
                      F-15E
                      F-117A

                      Comment


                        #12
                        Originally posted by BarTzi View Post
                        Just keep in mind that this there are two parts to this. The first is the great idea you suggested, and the second is making the AI JTAC capable of changing laser codes when communicating with a plane.

                        I always thought making those changes is low priority since making an overhaul to the JTAC system is probably low priority as well. After the F16 came out with a more true to life way ot changing the code, I don't know what's their take on this anymore.
                        I don't really understand why changing the laser code implementation would also require changing the laser code handling by the JTAC? You could still use the 1688 code regardless, even with the proposed new laser code implementation.

                        Of course it would be nice, if we could ask the JTAC to change it's code, but I don't see a dependency.
                        Intel i7-4790K @ 4x4GHz + 16 GB DDR3 + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

                        DCS Panavia Tornado (IDS) really needs to be a thing!

                        Comment


                          #13
                          Originally posted by QuiGon View Post
                          I don't really understand why changing the laser code implementation would also require changing the laser code handling by the JTAC? You could still use the 1688 code regardless, even with the proposed new laser code implementation.

                          Of course it would be nice, if we could ask the JTAC to change it's code, but I don't see a dependency.
                          I think it is because in a multi location Mission. You don't have the freedom to engage targets with multiple jtacs without either you changing codes inflight or the jtac changing codes to match your stores.

                          I would not be opposed to having a mission preset to allow or deny inflight code changing.

                          I could see how allowing players to tell the JTAC what code to lase could be very useful for pilots or could be hell for multiplayer servers.

                          In any case, standardizing it across modules would be a step in the right direction

                          Comment


                            #14
                            May I suggest an improvement over OPs solution? How about a button instead of the input field for the laser code. Pressing the button opens a new window that allows to configure the settings of the weapon(s!) on the respective pylon: laser codes, pre-planned JDAM coordinates, and in general all kind of fuze settings (--> CBUs!).


                            A separate window is probably easier to implement for the devs as the implact of such a change on existing code should be minimal and also allows for far more flexibility.
                            Did you know? True Harrier fans contribute to the AV-8B Community Bugtracker!

                            Comment


                              #15
                              I'm in full support for this, so long as AI JTAC gets the ability to change laser code. This has bugged me for a long time, and a consistent (and realistic) implementation of this system should be undertaken, where laser codes are not changable in flight.

                              Comment


                                #16
                                Originally posted by tech_op2000 View Post
                                I think it is because in a multi location Mission. You don't have the freedom to engage targets with multiple jtacs without either you changing codes inflight or the jtac changing codes to match your stores.

                                I would not be opposed to having a mission preset to allow or deny inflight code changing.

                                I could see how allowing players to tell the JTAC what code to lase could be very useful for pilots or could be hell for multiplayer servers.

                                In any case, standardizing it across modules would be a step in the right direction
                                You can't change the code inflight on the F-16, F-5, F-14 and M2000 already. The proposed implementation wouldn't change anything in this regard.

                                But yeah, the ability for the JTAC to be able to change laser designator code on request is needed anyways.
                                Intel i7-4790K @ 4x4GHz + 16 GB DDR3 + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

                                DCS Panavia Tornado (IDS) really needs to be a thing!

                                Comment


                                  #17
                                  Yes +1000, this should really be the only way to adjust it as it is the closest thing as changing the actual dials!!
                                  They should also do a similar thing for the dials on the GBU-24 to set it’s delivery mode! The Arming menu is 100% the best place to do these kinds of things
                                  sigpic

                                  Comment


                                    #18
                                    +1
                                    All knee-board (and non-kneeboard) settings should be put in an updated loadout/ream page.

                                    Big project, but a Rearm Page API for all module makers would be a huge improvement.
                                    Jarl at YouTube
                                    DCS Service Span and Wishlist Spreadsheet

                                    Forum post for discussion of above spreadsheet
                                    Retro Electro Playlist on Spotify

                                    Comment

                                    Working...
                                    X