Morpheus Platform Release v31
See this guide on how to update your existing project to a new editor release.
Version Released:
Morpheus Platform Release v31
15/11/2024
Latest Binary Version 31.0.0
Please note v31 removes support for any build on v26.0.0 on Pixel Streaming.
Background character inspection
We've exposed the Raycastable System configurations to be in blueprints, specifically the raycastable prioritization config.
We demonstrated this by adding more functionality to the Morpheus Inspector:
Allow the users to force Morpheus Actors into Foreground
Allow users to select Crowd Members via mouse clicks utilizing the Raycastable system.
Documentation is available in the Raycastables system page.
Party Functionality Permanently Disabled
Affected Features: Parties
What’s broken and why?
As part of the M2 Platform simplication process, we have permanently disabled parties and related functionality. As such, it is no longer possible to:
Enable party support
Create a party
Join a party
Leave a party
Send a party message
Receive party messages
Use party voice chat
The Party Component is still present but is no longer functional. It will be removed in a future version of the M2 Platform.
How to fix it?
If parties are required in your project, you will need to create or integrate a third party solution. Contact your support representative if you require assistance.
Removed UM2_WebPlatformRealtimeNFTWebsocket
Affected Features: Collections
What’s broken and why?
As part of M2 platform simplification, the UM2_WebPlatformRealtimeNFTWebsocket class has been removed.
How to fix it?
If you require this funtionality, you can implement it in your own project by using the Web Socket Connection and M2 Web Platform API documentation
Interface Change: UM2_WebServicesRoleDataProvider / UM2_WebServicesProfileDataProvider
Affected Features: Web Platform Integration
What’s broken and why?
The interfaces to UM2_WebServicesRoleDataProvider / UM2_WebServicesProfileDataProvider have changed. Instead of taking FM2_AuthUserContext as a parameter, they now take int LocalUserIndex. This is to simplify / remove assumptions about users for custom web platform integrations.
This change should not impact anyone yet unless they have implemented their own data providers.
How to fix it?
Instead passing FM2_AuthUserContext to any of the functions (which was hard to determine in Blueprint), you can pass LocalUserIndex. In 99% of cases, this will be 0, except for bots, which would be the index of the current bot.
How to test it?
Profile and role fetching should function as normal.
Deleted UserRolesSubsystem / UserRolesService
Affected Features: Services
What’s broken and why?
As part of MSquared platform simplification; the C++ querying of user roles has been removed to allow users to perform their own queries to either the web platform, or a service of their own choosing.
As a result of this, existing C++ Web Platform roles integration code has been removed.
This change should not impact users as it extremely unlikely that you’ll be manually querying role data.
How to fix it?
If previously you queried roles via either the UserRolesSubsystem or the UserRolesService (Web Platform), then you need to replace those calls with a Get World Service query, passing M2 Web Platform Roles Data Provider or an explicit derivative.
How to test it?
Role querying should work as normal.
CorrelationId added to Response of SendHttpRequest
Affected Features: Http
What’s broken and why?
CorrelationId has been added to the Response event used by SendHttpRequest. This is to allow users to correlate a response event with the request that initiates it; which is useful for storing state between the sending and response handling.
However, if you are using a bound function to handle the responses, you will experience a blueprint compile error due to the signature of the event changing.
How to fix it?
For every function you have bound to the completion delegate of SendHttpRequest, you must add an extra parameter to the Signature:
Name: CorrelationId, Type: Guid
Once you have done this, try compling the blueprint again and saving it.
How to test it?
If the blueprint compiles correctly, then no further action is required (once you’ve saved it).
Skin PDAs need a resave
What’s broken and why?
The underlying skins logic has been moved, but PDAs don’t handle redirectors nicely. As a result, without a resave of the active skin, PIE will be blocked in the “waiting for HUD” step.
How to fix it?
If you have a custom skin for your project, find it, and resave it. Easiest way to check what skin is being used is by going to the project settings → M2 UI Skins, and checking the Default Skin
How to test it?
If you can PIE and successfully enter the world, it has been fixed!
Disabled Remote Viewers Web Platform Connectivity
Affected Features: Remote Viewers
What’s broken and why?
The Remote Viewers feature is being removed as part of platform simplification. This step disables the connectivity of the Remote Viewers system to the M2 Web Platform services, effectively disabling the feature.
Last updated
Was this helpful?