Hello Matt,
Warm-Up Frames: Added warm-up frames in MRQ as you mentioned, I noticed that the first 3 frames need to be skipped to avoid sync mismatch. These frames include 2 pre-render engine setup as you mentioned and one Frame before start. (Tested with multiple random cases, its 3 frames all the time. So, this could be treated solved by skipping 3 frames)
Viewport Resolution Issue & Event Repeater CSV Logging Context: (Pending Main Issue)
I suppose query related to this was not conveyed clearly earlier. I am adding some more info and context:
The resolution is unexpectedly changing during rendering and doesn’t align with the resolution explicitly set in MRQ. I’ve configured MRQ to render at 800x600, and this is correctly reflected in the shot setup logs:
LogMovieRenderPipeline: Finished setting up rendering for shot. Shot has 1 Passes. Total resolution: (800x600) Individual tile resolution: (800x600). Tile count: (1x1) However, during execution, the viewport automatically resizes to 1920x1008, as shown in the logs:
LogViewport: Scene viewport resized to 1920x1008, mode Windowed. LogWindows: resolution: 1920x1080, work area: (0, 0) -> (1920, 1008), device: '\\.\DISPLAY17' [PRIMARY]This resolution change happens after Render execution begins, and it causes a mismatch between expected render resolution and the actual player viewport dimensions.
Context:
We’ve added a function that triggers every frame via the Sequencer Event Repeater, logging some data. This data logged has dependency on viewport size and hence the change in viewport resolution is affecting the accuracy of data.
Here’s a snip from viewport settings (Editor settings -> Play) where the dimensions are getting set back to 1920 x 1008 post rendering though the resolution set was 800x600.
Camera Perspective Shift Issue: As per your inputs, tried the take recorder & also checked the playlevel.cpp for finding the player controller’s current camera.
Take recorder: a) Doesn’t seem to be recording the actor component attached to actor (which we need); b) Creates an non-editable sequence; c) Not accounting for the data inconsistency issue while camera changed in a sequence
So, we are thinking to create separate sequencer in MRQ on our own for each camera.
Engine version used: 5.2 (Vanilla version)
Regards,
Indrajith