- Fix not joining multi user section
- Fix engine dir browse requesting file instead of folder
- Fix values from new config dialog not carrying over to project settings
- Fix source control group box not using project setting values
#jira UE-138421
#rb none
#ROBOMERGE-AUTHOR: dominik.peacock
#ROBOMERGE-SOURCE: CL 18541362 in //UE5/Release-5.0/... via CL 18541376
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v899-18417669)
[CL 18541378 by dominik peacock in ue5-release-engine-test branch]
This is also in preparation to the new nDisplay config file changes for 5.0.
#rb andrey.yamashev
#jira
#ROBOMERGE-AUTHOR: alejandro.arango
#ROBOMERGE-SOURCE: CL 18481284 in //UE5/Release-5.0/... via CL 18481577
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v899-18417669)
[CL 18481839 by alejandro arango in ue5-release-engine-test branch]
Now it will only appear highlighted when the user has traces enabled.
The previous behavior was to be highlighted when any setting was different than the default.
#rb
#jira
#ROBOMERGE-AUTHOR: alejandro.arango
#ROBOMERGE-SOURCE: CL 18429293 in //UE5/Release-5.0/... via CL 18429299
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v897-18405271)
[CL 18429302 by alejandro arango in ue5-release-engine-test branch]
Switchboard will read the resources from ../resources.py and not from resources.qrc.
So when adding a new image, copy it to /images and then manually reference it in resources.qrc.
Then run this script, which will check out ../resources.py from perforce and update it.
It requires pyside2-rcc.exe to be in the path (typically found inside <python>/Scripts).
You should also add resources.qrc and the image files to your perforce changelist.
#rb
#jira
#ROBOMERGE-AUTHOR: alejandro.arango
#ROBOMERGE-SOURCE: CL 18415708 in //UE5/Release-5.0/... via CL 18415710
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v897-18405271)
[CL 18415713 by alejandro arango in ue5-release-engine-test branch]
The old way of clicking on settings menu and then on settings submenu is still there.
#rb
#jira
#ROBOMERGE-AUTHOR: alejandro.arango
#ROBOMERGE-SOURCE: CL 18415623 in //UE5/Release-5.0/... via CL 18415631
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v897-18405271)
[CL 18415644 by alejandro arango in ue5-release-engine-test branch]
#jira UE-126791
#rb none
[FYI] zach.brockway
#ROBOMERGE-AUTHOR: jason.walter
#ROBOMERGE-SOURCE: CL 18397481 in //UE5/Release-5.0/... via CL 18397491
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v896-18170469)
[CL 18397511 by jason walter in ue5-release-engine-test branch]
This avoids an issue where if the map name coincides with a commandlet, the commandlet will be run. In particular, SmokeTest map was triggering the run of SmokeTestCommandlet.
By having -game before the map, it triggers a slightly different initialization path that doesn't have this behavior. It still finds the correct map name because -game is moved to the end of the command line, so the map name becomes the new first token.
#rb
#jira UE-136719
#ROBOMERGE-AUTHOR: alejandro.arango
#ROBOMERGE-SOURCE: CL 18392884 in //UE5/Release-5.0/... via CL 18392894
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v896-18170469)
[CL 18392898 by alejandro arango in ue5-release-engine-test branch]
dominik peacock
alejandro arango
jason walter