I am a long-time user of the RevoScan scanners and software, and have observed a software bug specific to the Range 1 scanner.
RevoScan 5.4 and later version seem to have broken marker tracking for the Range 1. Installing Revoscan 5.3 on the same PC and using the same scanner fixes the issue, with marker tracking working again. It appears to be a software bug that is reproduceable simply by installing 5.3 which works, or 5.4 (or later) which is broken.
The specific software versions I am testing are:
RevoScan5-5.3.4.941-windows-x86_64.exe
RevoScan5-5.4.3.724-windows-x86_64.exe
Unfortunately I don’t have copies of 5.4.1 or 5.4.2 available to test, but if you can provide a download link it would be interesting to try them.
It’s interesting to note that RevoScan 5.4.2 introduced support for the Range 2, so perhaps that introduced marker tracking issues for the Range 1?
Is this a known bug? Later versions of RevoScan have introduced some very useful features (e.g. global marker mode), but unfortunately I am not able to upgrade beyond RevoScan 5.4.2 until this bug is resolved.
Testing with the Pop 3 scanner shows that marker tracking works fine in RevoScan 5.3 and 5.4, so the bug is specific to the Range 1 scanner.
Please let me know if you require further detail, screenshots, videos, etc to help identify the issue and hopefully find a solution.
Thank you for the little research , it looks like you are on something here because I have a user that have issues as well , however if the marker mode don’t works proper the scanner can’t scan proper either as it relays on this feature and not only in market mode .
I will test it out tomorrow when I am back at work to check if it is really the issue for the confirmation .
RevoScan 5.4 .2 is one of the most solid versions for the early scanners as well so it may explains a lot .
I will test it tonight since I have all Range versions
The problem may be that Revo Scan 5.4.2 can use different types of marker and not need just reflective , the changes was adjusted so only reflective markers works now correctly as regular will not reflect proper the infrared .
I just tested old non-reflective markers and they work fine.
What I have observed with the Range that may or not be related is that it doesn’t like to recognize overexposed markers. You’d think that a clipped white circle would be the same thing but it doesn’t appear to be the case. I usually get out the OG Range for difficult surfaces because it seems to be the strongest projector out of all the scanners (including Range 2) so I’m usually driving it pretty hard.
That’s not the case , the markers are recognized by the RGB camera and the software . Not enough environmental lighting may affect the results with none reflective markers .
The exposure will do nothing
If there are any issues with markers the first things what need to be done is re calibration .
Thanks for all your messages on this issue. I think the quickest way forward is for me to post some video clips to illustrate the problem, so I’ll try to upload those latest today.
I will also have a look at RevoScan 5.4.12 - thanks Ivan. I don’t suppose you also have 5.4.1 and 5.4.2 do you?
For clarification, the issue is observed using the RevoPoint 6mm retroreflective markers supplied with the scanners. Have RevoPoint supplied matt markers at any point - I thought they were all retroreflective? The problem is reproduceable across a range of lighting conditions (indoor lighting, cloudy natural light, etc) - I’ve tested it a different times of day and in different rooms.
Regarding reflective markers: they were indeed reflective at the beginning (at least with pop1) ,but I don’t remember exactly when they switched for the reflective ones. I am sure @PUTV remembers🙂
The range 1 scanner has already been recalibrated as part of the testing. Recalibration (and calibration check) has no effect on the observed performance.
You mean recalibrated with 5.4.9 or early version of Revo Scan ?
I don’t mean the latest version of the software .
If you did with the early version and the same , then I suggest you don’t waste time anymore and contact technical support for checking your hardware as that we can’t fix in the forum .
Video is s very good idea to show to the technician when you have an appointment.
I have tried to demonstrate the Range1 marker tracking issue in the following video clips. The first video shows that the Range1 is able to track markers successfully in RevoScan 5.3.4, whereas the second video shows that the same hardware cannot track markers in RevoScan 5.4.3. Later versions of RevoScan also cause marker tracking to fail for the Range1 scanner.
The following additional video clips are provided to show that marker tracking works fine for the Pop3 scanner using either RevoScan version. In other words, the issue is specific to the Range1 scanner.
