RTX4050 works already with the old version from 30x to 40x series
Only RevoScan MetroX
RTX 2060 was added to the new upgrade today of RevoScanMetroX
Regular version of RevoScan don’t support GPU acceleration, only RevoScanMetroX and only using Laser mode while scanning and nothing else.
If your frame rate speed is 57-60 while scanning with laser mode then the GPU acceleration is working .
If not , update your driver and setup GPU acceleration under the software settings.
At this moment both of your cards are supported already with 5.6.5 version of RevoScan MetroX when using GPU acceleration and laser mode.
my intel i7 12th gen 12800h and 32Gb ram was working fine with 5.6.4. now it is just lagging and can’t see markers (almost like the marker tracking is not prioritized. i’m on CPU only since T600 gpu not supported. same problem on another PC with i7 9850h that was scannin poorly but doable. is now unable to use. so basicly CPU scanning is broken for me
The minimum is Intel i7 10th Gen 10700 so you should be able to use it normally yet it will be not the optimal results.
Lagging in what mode ? laser ?
Check your graphic card to make sure it is set on performance or change the viewport preview thickness of the lines to lower before starting scanning.
Avoid too many markers that are too close , at least 3 cm distance if on flat surface.
I can still use Full Field and Auto mode on my win tablet with i7 8th gen without issues for scanning .
The Markers works differently in laser mode than Full Field , since only 800K points are activated at once compared to 7 millions in Full Field that have bigger range of view and markers detection at once.
P.S without markers the laser will not fire or scan anything , it is the priority to even start
I suggest your check your calibration results as bad calibration starts with markers being not detected.
Anyway thanks for the feedback, I will forward it to the team.
yes. i have about 3-4 cm between the markers. on 5.6.4 the “frames” per second is about the same as 5.6.5 but the markers are not tracking. i must keep the scanner 90 degree perpendicular to the turntable or else it is not detected and the “point cloud” preview is like 1-2 frames per second (not the same as frames per second capture) when scanning in 5.6.4 i get about the same frames per secound 43 fps as in 5.6.5 but now the Markers are detected at at least 45 degree angle to the turntable and is 25-30 frames per second updating the point cloud preview"