Hello!
I tried to change a Classification of pont in Descartes SS3 as it was shown in movies and described in Help. But it doesn't work. Maybe is here any specific thing in this process?
In my point cloud all in class Unclassified and can change the collor for this class only, and can not set another class for selected area of poins (I've tried to select it by block, shape and slab).
Maybe anybody can guess the reasons of it?
Thanks for advanse,
Elena
Hi Keith and Martin!
Thanks for so quick answers.
I've checked all according to your remarks, but it doesn't work anyway. You can see in attached video what I was doing.
There was a small yellow exclamation in the message area. Can you click on that and see what it says?
Keith Raymond
It was from previous activity. I repeat it just now and there was no any exclamation.
Hi Elena,
Do you have write access to the folder where your attached Point Cloud is located?
The classification tool creates a *.classif "sister file" in the same folder as the .POD file that your are trying to reclassify. That file contains the classification editions. If that file cannot be created, you won't see the classification edition.
One way to test this would be to copy the POD file to a folder that you know you have write access, attach the POD file from there and try to reclassify it.
Pascal
Hi Pascal.
I have the write access and file ".classif" was created and updated after my attempt. i've just check it.
Elena,
From the video you have posted, I can see that you have CADScript installed. I installed it out of curiosity and was able to reproduce your issue. I think there is a conflict between CADScript and the display of modified classification.
Could you disable CADScript and retry to confirm?
Pascal, you are great!
It was really because of CADscript. I can see my classification after uninstall CADscript immediately!
Maybe this conflict appear because I've installed MicroStation SS3 over SS1 and CADscript SS1 remained on system.
Should I make a Trouble Request about it or you can send it to developer group directly?
Good to hear that we have identified the culprit. I have filed a TR for this issue.