questions regarding the symbols not matching the Properties

hello all, 

I'm learning/using Microstation V8i (SELECTSeries 10).
I found a big hurdle that in many cases the Properties list the information does not match what I see in the screen. As a result, I don't know what or where to look for. 

For example, in the screenshot below, the selected purple line is supposed to have a specific line style as Silt Fence, as the Properties shows. However, it shows as continuous on the screen. I imported the line style from an RSC file and checked the line style scale, nothing seems wrong. If I open the exactly same file on another computer in our network, the line style looks alright. 



In another file, I have sheet view referencing a model, which contains some texts. The texts are of Arial Fonts and they look alright in the Model view, but in the Sheet view, all these texts are without fill, just the frames/outlines of the texts. I checked the Properties of the text, they look nothing wrong and I checked the attributes of the Sheet view, the Fill option is ON. 

I can list many cases like this, that is, the line style/fonts/symbols/colors listed in the Properties do not match what they are on the screen. 
Where or what should I look for in such situation? 

Thanks

Best regards
Daniel

Parents
  • Hi Daniel,

    Some things come to mind concerning the line style.

    Make certain linestyle Symbology Override is not activated for the level that line resides on. Go to the Level Manager and check.



    Hit CTRL+B on your keyboard to bring up View Attributes where you can turn of the Level Overrides altogether. See what happens if you toggle Level Overrides. (Notice the difference in name: Level Override and Symbology Override?)

    Check if the resource is being read by microstation. Go to your Attributes toolbar and see if your line style Silt Fence shows up there. If so, that's a good start. If not, it is not being read. Opening the rsc in the line style editor is not the same as reading it at start up. The properties dialog telling wich line style it is, is just telling you what the linestyle is suppost to be, not if it's there. (Would be nice if a warning came up at start up or during inquiry).

    Make certain the rsc is located in a place where Microstation can find it (MS_SYMBRSRC). Go to pull down menu "Workspace > Configuration > Symbology > Symbology resources" to find the location.

    Make certain MS_SYMBRSRC is actually looking for that rsc. Putting the rsc there may not be enough if MS_SYMBRSRC is looking for specific files hardcoded in the variables and not for just any *.rsc.
    MS_SYMBRSRC=c:\MyDir\*.rsc       #will look for any file on c:\MyDir\
    MS_SYMBRSRC=c:\MyDir\MyLines.rsc       #will only look for file MyLines on c:\MyDir\

    Make certain all components of the linestyle are being copied. A linestyle can be an assembly of different components like internal, points strokes. Or even other linestyles.


    A Tip: Just copy the entire correct rsc file instead of parts of it.

    Another tip: If you store this kind of data on a shared network drive and tell all pc's running Microstation to look there, then all Microstations in the office should have the same data to work from. You can put just about anything in a network library and any changes are reflected allmost immidiatly. If not, a restart of Microstation is enough. Cells, line styles, fonts, solar data, 3D textures, GUI, tools. No copying from pc to pc. Some people here may remember the days of running around with a diskette and putting it in every diskdrive in the office, listening to the humming of the drive while it was copying a staggering amount of 720 kb worth of files.

    I hope some of this helps you.

    Ivo Blaauw
    = = = = = = = = = = = = =
    Look what the CAD dragged in...

    Answer Verified By: Daniel Ling 

Reply
  • Hi Daniel,

    Some things come to mind concerning the line style.

    Make certain linestyle Symbology Override is not activated for the level that line resides on. Go to the Level Manager and check.



    Hit CTRL+B on your keyboard to bring up View Attributes where you can turn of the Level Overrides altogether. See what happens if you toggle Level Overrides. (Notice the difference in name: Level Override and Symbology Override?)

    Check if the resource is being read by microstation. Go to your Attributes toolbar and see if your line style Silt Fence shows up there. If so, that's a good start. If not, it is not being read. Opening the rsc in the line style editor is not the same as reading it at start up. The properties dialog telling wich line style it is, is just telling you what the linestyle is suppost to be, not if it's there. (Would be nice if a warning came up at start up or during inquiry).

    Make certain the rsc is located in a place where Microstation can find it (MS_SYMBRSRC). Go to pull down menu "Workspace > Configuration > Symbology > Symbology resources" to find the location.

    Make certain MS_SYMBRSRC is actually looking for that rsc. Putting the rsc there may not be enough if MS_SYMBRSRC is looking for specific files hardcoded in the variables and not for just any *.rsc.
    MS_SYMBRSRC=c:\MyDir\*.rsc       #will look for any file on c:\MyDir\
    MS_SYMBRSRC=c:\MyDir\MyLines.rsc       #will only look for file MyLines on c:\MyDir\

    Make certain all components of the linestyle are being copied. A linestyle can be an assembly of different components like internal, points strokes. Or even other linestyles.


    A Tip: Just copy the entire correct rsc file instead of parts of it.

    Another tip: If you store this kind of data on a shared network drive and tell all pc's running Microstation to look there, then all Microstations in the office should have the same data to work from. You can put just about anything in a network library and any changes are reflected allmost immidiatly. If not, a restart of Microstation is enough. Cells, line styles, fonts, solar data, 3D textures, GUI, tools. No copying from pc to pc. Some people here may remember the days of running around with a diskette and putting it in every diskdrive in the office, listening to the humming of the drive while it was copying a staggering amount of 720 kb worth of files.

    I hope some of this helps you.

    Ivo Blaauw
    = = = = = = = = = = = = =
    Look what the CAD dragged in...

    Answer Verified By: Daniel Ling 

Children