Hi, RS team. We're experiencing an (unfortunately blocking) editor crash in our new Unreal 5.1.1 project connected to the rs1.30 v6 plugin.
(Note that this is our first implementation of rs1.30 -- previous projects used rs1.29 so it's hard to speak to when this may have been introduced).
(Also note that our projects use RenderStream to bridge nDisplay content rather than single camera content).
Seemingly the plugin is attempting to resize a vector but that vector's max_size() is -1 and it's choking on the operation.
Here's the most straightforward path to reproduction followed by a secondary path for comparison:
Steps:
Create a fresh ndisplay/workload/stream config from Disguise r23 (single node mapping on to a single display, retrieve the .ndisplay file from the renderstream_workloads folder)
UE5.1.1 project with rs1.30 latest enabled: Create a new nDisplay configuration asset.
Import .ndisplay file into asset.
Result: Editor crashes with the above exception (I did a bit of logging to console: it's trying to resize m_schemaMem which has a max_size() of -1 for some reason)
Observe: File contains a PostProcess json object with type: renderstream_capture defined
Modified Steps for Confirmation:
Create a fresh ndisplay config in Unreal 5.1.1 directly (rs1.30 latest enabled)
Setup a single node and mesh-based mapping using the editor
Observe: nDisplay preview working / reprojecting as expected in editor preview window
Add Custom Output Settings "rs" w/ type "renderstream_capture"
Result: Editor crashes with the above exception
So... it seems as though the codepath in the renderstream plugin doesn't execute until the "rs"/"renderstream_capture" key is present... as to why it's having trouble with the vector however...
Hi, RS team. We're experiencing an (unfortunately blocking) editor crash in our new Unreal 5.1.1 project connected to the rs1.30 v6 plugin.
(Note that this is our first implementation of rs1.30 -- previous projects used rs1.29 so it's hard to speak to when this may have been introduced). (Also note that our projects use RenderStream to bridge nDisplay content rather than single camera content).
Seemingly the plugin is attempting to resize a vector but that vector's max_size() is -1 and it's choking on the operation.
Here's the most straightforward path to reproduction followed by a secondary path for comparison:
Steps:
Modified Steps for Confirmation:
So... it seems as though the codepath in the renderstream plugin doesn't execute until the "rs"/"renderstream_capture" key is present... as to why it's having trouble with the vector however...