Hi Stefan,

When ‘Render to Depth’ is turned off, the billboard is actually placed twice in the Unreal level—first in the depth (which will be picked up by reflections and other effects). Unfortunately, the billboard rendered for depth will also be visible to the actual camera. Normally, you would not notice this, as it should always be fully behind the actual billboard that is not rendered to depth.
The unusual glow you see is likely caused by Depth of Field (Focus) being applied to the billboard rendered for depth. To fix this, you should ensure that the billboard is always in focus.

In V Cam (Virtual Camera), you can adjust the focus as described here: https://aximmetry.com/learn/virtual-production-workflow/starting-with-aximmetry/aximmetry-composer/camera-mover-mouse-control/#focus
In T Cam (Tracked Camera), make sure the talent remains in focus with your studio camera (if you have focus tracking) or override the tracked focus in Aximmetry. In the next version of Aximmetry, there will be a parameter in the INPUTS to override only the focus value per INPUT. Until then, you can achieve this with some additional logic in the Flow Editor; if needed, I can describe how to do so.

Regarding the green spill, it appears the above Depth of Field effect is simply blurring away the spill. This can occur if the keyed talent has transparent parts. You should make sure the Low and High Cut settings make the talent opaque in Matte Monitor Mode: https://aximmetry.com/learn/virtual-production-workflow/green-screen-production/keying/keying/#low-cut
Otherwise, try adjusting the Despill parameters of the keyer: https://aximmetry.com/learn/virtual-production-workflow/green-screen-production/keying/keying/#despill-strength
Alternatively, you might be able to hide the green spill using Light Wrap, afterall it is similar to what the Depth of Field's blur artifact did:

To use Light Wrap, the Use Billboards must be enabled.

Warmest regards,

Hi Eifert,

thanks for your prompt reply. So what version do you expect that bug to be fixed? Does it still occur with 2025.1 ?

Hi Stefan,

It might not occur in version 2025.1.0, as some related issues were fixed in previous versions. There is one last issue that will be fixed in the next release of Aximmetry (2025.2.0).

Warmest regards,

Hi Eifert,

do you already have a timeline for 2025.2.0 ?

Hi Stefan,

Unfortunately, we cannot provide a specific timeline for updates.
In the worst-case scenario, if you have an upcoming production in the next few months and version 2025.1.0 does not resolve the issue, I can guide you through the necessary steps to fix it.

Warmest regards,

Ok, so it seems that issue has been fixed in 2025.1.0. Thanks for that.

However 2025.1.0 has a few new things...

First of all, how do I get rid of the warning message when I select a lower output resolution than the project render resolution at startup? I want and need to do this (capture, keying and rendering in UHD, but recording and streaming externally in 1080p) and it's annoying.

Secondly, I have a presentation computer live input that comes in on HDSDI, just like the cameras but in 1080p. I would like to take it to fullscreen without having to mess with the signal routing, so I just assign it as an input on V CAM 2. But how do I get it to appear full screen without endlessly fiddling around with the billboard and the V Cam position? Just inputting 0 on all transformations  and scaling up to match UHD does not seem to do the trick...

Hi Stefan,

Note that having a different aspect ratio for the input compared to the rendering is not possible for tracked cameras, due to multiple technical limitations. However, with virtual cameras, you can use different aspect ratios for the inputs and the render, and that would likely cause the discrepancy you are experiencing.
Also, maybe you are using cropping in the CROP panel, which could also explain what you are experiencing.

Warmest regards,