Announcement

Collapse
No announcement yet.

[Fix Incoming] Seriously damaging change to Online Subsystems in 4.20

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

    [PROGRAMMING] [Fix Incoming] Seriously damaging change to Online Subsystems in 4.20

    https://answers.unrealengine.com/que...ml?sort=oldest

    You now cannot create your own Online Subsystems as plugins, as you have to modify the engine to support a custom OSS. This seems like an enormous step backwards and a huge oversight. I can't really understand why this was necessary? IMO the engine should be opening up to supporting more modular features.

    There have been several major changes to OSS' in 4.20 which initially led to many projects (particularly Steam) not working online at all until the 4.20.1 hotfix. Not to be a pitchfork-wielder, but this feels a little bit like features are being shoehorned in from Fortnite and we're suffering as a result.

    Please maintain modularity - it's one of the engines strengths and frankly needs more focus.

    #2
    I'll also raise a pitchfork here.It's been frustrating that the current version of of Unreal doesn't match the most recent version of steamworks, but this is unwise.

    Comment


      #3
      Also interested in this

      Comment


        #4
        Adding a fourth voice to the issue, it's a gigantic problem for us.

        Comment


          #5
          I bet this is coming from someone not tracking state of the pre-built (Launcher) engines... With head too deep into GitHub ecosystem.
          | Finite State Machine | Auto-Save Plugin | USQLite Plugin | Object-Pool | Sound-Occlusion | Anti-Cheat Plugin | Property Transfer Tool | Magic Nodes |

          Comment


            #6
            Adding a sixth voice.

            Comment


              #7
              Pitchfork raised.

              Comment


                #8
                I'm adding a voice too.

                Comment


                  #9
                  +1 here, doesn't effect me yet, but could affect our networking going forward - don't really want to have to end up doing custom engine builds for the entire team when half of us work remotely.

                  Comment


                    #10
                    It's been a few days and seen some tweets go out about this. Wondering when it will have anyone look into it =/

                    Comment


                      #11
                      Unless you poke someone at Epic directly (via @ here or on Twitter or on Discord), no one will chime in to explain why it was done and what do expect moving forward.

                      Comment


                        #12
                        Tried twitter with no avail. Not sure who to tag here, but feel free peeps.

                        Comment


                          #13
                          i support this thread, hoping someone from Epic will read it.

                          Comment


                            #14
                            Hey all, just wanted to let you know we hear you and I'll start the conversations internally about this.

                            Thanks!

                            Comment


                              #15
                              Please try not to break the engine in future updates @Epic

                              Check out my discord -> https://discord.gg/kQdVwJ3

                              Follow us on twitter to get updates on new products and special offers -> https://twitter.com/BlackFangTech

                              Black Fang Technologies' products -> https://www.unrealengine.com/marketp...20Technologies

                              Comment

                              Working...
                              X