Upgrading from beta 4 to beta 5

General Feedback & Requests
, , , , ,
1

Hi,

Are there any release notes for upgrading between beta 4 and beta 5?

So far I’ve found the following issues:

  1. The folder containing the Rocket project file now has to match the name of the Rocket project in order to be able to generate the Visual Studio files.

  2. AGameInfo needs to change to AGameMode.

  3. The Rocket project needs to be updated and all of my old level data has been replaced with (what appears to be) the default project. My PlayerController isn’t running anymore and it doesn’t appear to be using my camera class either.

What are the changes that are meant to happen to be able to upgrade?

Thanks!

2

+1 for the change-logs / new release notes. Please

3

To run game in editor you need to use Development_Editor or Debug_Editor build option. Otherwise compiler will not generate DLL.

4

Yup, I caught that (and should have mentioned it in my question!). I’m doing this and I see it hit breakpoints when the editor starts up - but not when I try the “Play In” button it’s not hitting my breakpoints.

Commenting out code proves that it’s not using either my camera, HUD or PlayerController code… :-/

5

https://rocket.unrealengine.com/docs/ue4/INT/Support/Builds/ReleaseNotes/2013/Oct/Rocket/index.html

It says October but this is the newest log on Builds section.

6

Thanks! That’s still for Beta 4 unfortunately.

7

I apologise Mehmet, you were right!

8

wait, when did you get the new beta?

9

nevermind, turn out the mail was in my spam folder (first time for everything)

10

Hi Neil, release notes should have been linked in the Beta5 email, but they can also be found here:
https://rocket.unrealengine.com/docs/ue4/INT/Support/Builds/ReleaseNotes/2013/Oct/Rocket/index.html

  1. We’re aware of this issue, although this should only be a problem when upgrading Beta3 projects to Beta5. The workaround is to rename the parent folder to match the project name. Please let us know if this is instead a problem upgrading Beta4 project as we would definitely like to know.

  2. Looks like that change wasn’t included in our Upgrade Notes section. We’ll try to improve our process for catching these items, but the heads up is much appreciated.

  3. Yes, the editor will prompt you to update your project file when you load up a Beta4 project in the new Rocket version. But it shouldn’t be replacing any code or content in your project. What might be happening is that the defaultmap setting has been hooked up differently in the project settings UI and you need to set it back up. As for your blueprints no longer working, those are most likely a result of changes to BP pins/functions/classes. Info on what been changed for these items should be in the “Upgrade Notes” section of the release notes.

As for the expected process for updating your project…

  • If it’s a code project, delete your visual studio files, saved and intermediate folder
  • Regenerate your sln and recompile
  • (for both code and content) Load up your project in the editor
  • When prompted, update your project file
  • If any items are broken, look at the “Upgrade Notes” section of the release notes.
  • If the necessary info isn’t found, and you created a project from a template, you can always diff the code/BP files from the Beta4 and Beta5 versions to see what changed, and implement those changes.

I do want to reassure you that we’re investigating and developing internal tools so that any of these game breaking changes can be reported and conveyed to you more efficiently. We do understand that this is a painful process, so we’re improve our tracking system internally and trying to get the majority of game breaking engine changes done sooner rather than later.

11

Are you sure that’s the correct URL? The build numbers don’t appear to match. My build number is 1904627 but that documentation says build number 1897729.

  1. I was upgrading from Beta 4 to Beta 5 so it looks like a new issue. It wasn’t a huge problem though - it just meant having to reconfigure my Perforce workspace after renaming the directory.

  2. You were correct about the default map setting, that brought back the old map. It still isn’t using my PlayerController though so I’ll have to diff between a template and what I currently have.

Thanks!

12

Hi Neil,

Yes, those are the release notes for this build. While we were hoping to get the build out in October, it unfortunately ran into the next month. But that still means we need to update the title in addition to the CL# :slight_smile:

13

Okay, so there were numerous undocumented breaking changes. Here’s what I had to do to get it to work again.

  1. Open the .uproject file and add the following JSON:

    “Modules”: [
    {
    “Name”: “”,
    “Type”: “Runtime”,
    “LoadingPhase”: “Default”
    }
    ],

Without that, it wasn’t loading the DLL so none of my source was being used.

  1. In Rocket, I had to specify the default map (Edit → Project Settings → Maps).

  2. In DefaultEngine.ini I had to change:

  • DefaultMap → GameDefaultMap
  • EditorMap → EditorStartupMap
  • StartupMap → ServerStartupMap
  1. In DefaultGame.ini I had to change:

GlobalDefaultGameType → GlobalDefaultGameMode

Those changes plus the ones I mentioned in my question led to a working C++ project again after upgrading.

14

#Regarding Getting the Right Maps to Load

also in defaultengine.ini, you could set the map this way, I observed this from 3rd person code starter project, the names are slightly different now:

[/Script/EngineSettings.GameMapsSettings]
GameDefaultMap=/Game/Maps/Victory
ServerStartupMap=/Game/Maps/Victory
EditorStartupMap=/Game/Maps/Victory

#Regarding Getting the Right Game Type to Load

In DefaultGame.ini

[/Script/Engine.WorldInfo]  ;beta4
GlobalDefaultGameType="/Script/VictoryGame.VictoryGameGameInfo"

becomes

[/Script/Engine.WorldSettings]
GlobalDefaultGameMode="/Script/VictoryGame.VictoryGameGameInfo"
GlobalDefaultServerGameMode="/Script/VictoryGame.VictoryGameGameInfo"

please note VictoryGameGameInfo is my AGameMode extending class