We use a synchronous card produced in 2025 to start one machine as the master. After setting up synchronization, using NV sync and starting a UE5.5 project with sw, the process freezes and fps drops to 0. If the sync strategy is changed to None, it works normally.
We tested firmware 2.02 and 3.06 on the synchronous card produced in 2025 , and neither worked properly.
[Image Removed]
We determine the production year based on the 6th and 7th digits of the serial number.
[Image Removed]
If we switch to the synchronous card produced in 2022, all functions will be able to return to normal.
All synchronized cards produced in 25 years cannot be used normally
We bought about 30 of these cards and none of them work properly. Is there any way to resolve this? How can we identify a batch or model of synchronized cards that will work properly?
[Attachment Removed]
Here’s an update on the latest progress: We found that the older sync cards also had issues, so the focus for solving the problem shifted from the hardware itself to the software environment. Our machines need to connect to two LED processors, so we need to stitch the mosaics together. The resolution of a single screen is 1296*2592. Together, two screens would be either 1296*5184 or 2592*2592. Both of these resolutions cause the FPS to drop to 0 after startup. If we change the overall node resolution to a power of 2, such as 2048*2048, 4096*4096, or (2048+1024)*(2048+1024), or (2048+512)*(2048+512), UE can start normally and sync is locked. Ultimately, to be close to the original size without being smaller, we used the resolution (2048+512+64)*(2048+512+64) for displaying on one machine, which worked correctly. Today, we plan to set all machines and LED processors to this resolution to see if they can sync properly.
[Attachment Removed]
Hi. Our test stage hasn’t experience this, but the Quadro Sync II cards are not 2025. I believe there are new cards in new machines that are to become operational in a month or so and I can report back if the issue is reproduced. Other than that, the typical reason for qsync deadlocks is related to something breaking independent flip, such as pop ups or windows task bar.
[Attachment Removed]
Currently, several of the 20 machines are experiencing synchronization issues at a resolution of 1296*(2592*2), and using mosaic stitching results in an FPS of 0. After replacing the synchronization cards, the machines work normally, suggesting the problem is related to the synchronization cards. Currently, there seem to be two ways to solve the synchronization problem: 1. Change the resolution to a power of 2. 2. Shut down the machines and start them one by one to identify the machine affecting synchronization and replace its synchronization card.
[Attachment Removed]