This represents UE4/Main @18073326, Release-5.0 @18081140 and Dev-PerfTest @18045971
[CL 18081471 by aurel cordonnier in ue5-release-engine-test branch]
- Add a few DataDrivenPlatformInfo ShaderPlatform flags for METAL_SM5.
- Attribute dual-source blending targets.
- Match the RWBuffer type for RWScreenProbeRadianceSHDirectional between the HLSL and C++ code.
- Update PF_FloatRGB buffer format to RG11B10Float.
#rb Daniel.Wright, Richard.Wallis, Lukas.Hermanns
#jira UE-117253
#rnx
#ROBOMERGE-SOURCE: CL 16972126 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v838-16927207)
[CL 16972351 by will damon in ue5-release-engine-test branch]
Renamed FDataDrivenPlatformInfo::AudioCompressionSettingsIniSectionName to TargetSettingsIniSectionName. It's now used to populate PlatformMask at runtime, to make sure that it matches between cook and runtime. Before it was possible to cook with e.g. GRayTracingPlaformMask=0, but then the cooked game would run with GRayTracingPlaformMask=1.
#rb Patrick.Kelly
[FYI] Patrick.Kelly, Daniel.Wright, Josh.Adams
#ROBOMERGE-OWNER: krzysztof.narkowicz
#ROBOMERGE-AUTHOR: krzysztof.narkowicz
#ROBOMERGE-SOURCE: CL 16825469 via CL 16825718
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v836-16769935)
[CL 16825756 by krzysztof narkowicz in ue5-release-engine-test branch]
- MediaModule now uses the platform Guid from DDPI instead of having a per-platform MediaInfo module that only supplied a Guid. Deleted many platform extension modules
#rb thomas.engel
[CL 14824685 by Josh Adams in ue5-main branch]
- Formalizing all TargetPlatforms to have a Client version, rename WindowsNoEditor to Windows, and removing DDPI specification of TargetPlatforms, and generate them programmatically
- Updated names DeviceProfiles and Build scripts, as above
- Some PlatformInfo class cleanup
- Added a TNonDesktopTargetPlatformBase class to make most TargetPlatforms simpler
- Added "No Compiled Support" to the Turnkey LaunchOn menu when the TargetPlatforms aren't compiled in (to show that even if you install an SDK, you will need to compile before you can LaunchOn)\
- Starting the transition away from PlatformInfo::FPlatformInfo to FDDPI
[CL 13966487 by Josh Adams in ue5-main branch]
- Renamed FDataDrivenPlatformRegistry::FPlatformInfo to FDataDrivenPlatformInfo
- Moved some fields from PlatformInfo::FTargetPlatformInfo to FDataDrivenPlatformInfo, and cleaned them up in the process
- Fixed the DataDrivePlatformInfo.ini files to match the previous items
- Removed FVanillaPlatformEntry, and now just using FTargetPlatformInfo to manage flavors under a vanilla PlatformInfo (see PlatformInfo::GetVanillaPlatformInfoArray())
- Cleaned up TPerPlatformValue, as it was often misused (took a group and platform name, but we can get the group from the platform name) [AnimationSharingManager.cpp, *Engine.cpp, Runtime\Engine\*, ]
- Fixed FBlueprintNativeCodeGenPaths::GetDefaultCodeGenPaths() to use IniPlatformName instead of some hacky code [BlueprintNativeCodeGenManifest.cpp]
- Fixed various Turnkey bugs that recent testing exposed
- Enabled AUTOSDKS_ENABLED in both Mac and Linux on the Editor side (not that there are much set up to use it)
- Using Turnkey to get the SDK status instead of ValidatePlatforms (gives more detailed information - may want to go back to ValidatePlatforms so only UBT is needed, but change it to give more info)
- Moved OnDeviceDiscovered and Lost delegates from each platform's TargetPlatform class to a static in ITargetPlatform - there was no need for per-platform implementations
- Started working on allowing for SDK to be installed with editor running and not need to restart editor - Work in Progress! It is not usable yet.
#fyi jack.porter
#rb pete.sauerbrei
[CL 13816905 by Josh Adams in ue5-main branch]
New feature for controling which platforms use certain aspects of Niagara.
Current users include;
- Emitter Enabled/Disabled switch
- System level scalability settings in EffectType and overrides in System.
- Emitter level scalability settings in EffectType and overrides in Emitter.
This entirely replaces previous Detail Level feature and all related code.
Now we allow users to select from EffectsQualitiy levels as a basic use case for scaling across platforms.
Further fine grained control can be acheived by setting per device profile overrides to this.
For example all Effects Quality levels could be enabled but Android could be specifically disabled. Or some subset of mobile devices.
TODO: Code is in place for this to cook out emitters but there are other impediments stopping this currently.
TODO: Sebastian has more UI changes incomming but as a v1.0 this is funtional.
#rb Josh.Adams
#ROBOMERGE-OWNER: simon.tovey
#ROBOMERGE-AUTHOR: simon.tovey
#ROBOMERGE-SOURCE: CL 11292064 via CL 11292069
#ROBOMERGE-BOT: (v647-11244347)
[CL 11292627 by simon tovey in Main branch]