Brett Witters's Communities Activities

Ask A Question II

Wed, 04 Jan 2023 13:57:20 GMT

Ask 10 questions in a forum.

Some features not plotting from print organizer, but do when sheet model is plotted individually

Brett Witters — Wed, 04 Jan 2023 13:57:19 GMT

Good morning. We have been having a recent issue in MicroStation ORD 2021 Release 1 with print organizer. We noticed that one certain feature we need to show up on our PDF plots are not showing up when plotted using print organizer, but it is if we plot directly from the sheet model itself. The strange thing this is, other identical features, on the same levels, etc, that show up on other sheets are plotting correctly

Here is what the sheet model looks like itself:

Here is what the PDF looks like when plotted using print organizer:

Here is what the PDF looks like when the sheet model is plotted individually:

Both PDFs are using the same print driver, etc. I also tried to delete and reload that specific sheet model into the sheet index/print organizer and that did not work.

Any idea what is causing this or how to fix it?? Thanks in advance

How do I restrict level display and symbology access in a referenced container file??

Brett Witters — Tue, 19 Apr 2022 12:59:14 GMT

Recently our firm upgraded from V8i to CONNECT and noticed an issue with how CONNECT seems to allow level display and symbology control in nested references. In our current workflow, we create a container (mosaic) DGN that references our existing and proposed reference files, then we attach this container file with live nesting on to our plan sheets. We would set the level display and symbology in the container file for the desired presentation we needed once referenced into our plan sheets. V8i would not allow any of the level display or symbology in the container file to be changed while working in the file that it is attached to. It now seems, that CONNECT allows changes to be made to nested reference level display and symbology in the active plan sheet file. We foresee issues with this workflow, as users will be able to easily change level display and symbology in the plan sheet files without opening the container and making changes there. We would prefer to set our level display and symbology in the containers and not have users be able to make any changes to that while they are working in a file that has the container referenced into it. What settings or configurations would I need to revise in order to restrict access to level display and symbology for a nested reference?? Hopefully my description of the issue is clear. Thanks

Converting V8i linestyles to CONNECT edition

Brett Witters — Mon, 14 Feb 2022 13:22:04 GMT

Good morning. My firm is in the process of upgrading from V8i to CONNECT edition and have noticed that our custom linestyles no longer display correctly. I am assuming that is due to the differences in resolution between V8i and CONNECT edition. V8i has a resolution of 1000 and CONNECT has a resolution of 10000. Is there an easy was to convert our old linestyles so they display correctly without having to recreate them individually in CONNECT?? Thank you.

Shift linestyle command not working

Brett Witters — Thu, 28 Oct 2021 12:23:00 GMT

Good morning. I am trying to shift a stream edge linestyle so it shows up correctly with triple dots centered on line. Typically I use the SHIFT command under the MODIFY LINESTYLES toolbar. I have used this command 100s of times and for some reason it is not working this time. Any ideas why?? Thanks.

[CONNECT] Is it possible to set up different standards for each workset??

Brett Witters — Wed, 31 Mar 2021 12:46:22 GMT

Good morning. I am working on migrating our firms v8i workspaces to the CONNECT edition. With v8i we have USERS that correspond to our clients, usually a DOT and PROJECTS that correspond to different versions of DOT workspaces we need to sometimes use for working with our subconsultants. Each PROJECT has different STANDARDS files for each subconsultant WORKSPACE. When I use configuration migration for CONNECT to attempt to convert these .UCF and .PCF to the WORKSPACE.CFG and WORKSET.CFG files, the standards are automatically stored based on the WORKSPACE itself rather than the WORKSET. For example, I set up a WORKSPACE called XXDOT, and a WORKSET called DOT_2017 for the version of the workspace we want to use. However, the STANDARDS seem to be tied to the XXDOT WORKSPACE rather than the WORKSET. This will not work for us since each PROJECT/WORKSET will need to use diff STANDARDS. The only solution I see is to create a separate WORKSPACE for each of our old .PCF files, rather one WORKSPACE from .UCF with multiple WORKSETS based on our .PCF files? Is there a way to set the diff STANDARDS to work with the WORKSET?? Hopefully that makes sense. Thanks.

File Navigator tool missing

Brett Witters — Tue, 16 Feb 2021 12:47:21 GMT

Does anyone know how to load the file navigator tool that will allow you to navigate to the next or previous DGN file in your project folder without closing MicroStation?? I used to have it docked in my preferences, but for some reason it disappeared. Thanks

Configuration questions

Brett Witters — Tue, 09 Feb 2021 11:39:06 GMT

My firm recently released a new MicroStation V8i config to replace the old one we used to use and we are noticing some consistency issues we would like to fix.

1. How and where can you set V8i to always open using the last workspace you had used in your previous session??

2. Where does MicroStation define the default folder it browses to when you select a certain workspace??

3. Some users lost their duel screen functionality when installing our new config. Found that some people could fix it by clicking off/on the "OPEN TWO APPLICATION WINDOWS" box under WORKSPACE>PREFERENCES>OPERATION and saving settings. This did not work for other users, any idea why that might be happening??

Thanks for any help you can offer.

Loss of dual screen operation

Brett Witters — Mon, 01 Feb 2021 14:05:32 GMT

I recently created a new v8i configuration at our firm in order to ensure that all MicroStation users were accessing the necessary resource files via our network drives rather than locally. Since this update my dual screens no longer work. I did double check that the Workspace>Preferences>Operation "Open two application windows" box was checked on but it is not working. Anyone have any idea why this would be??

Tool icons disappearing from toolboxes

Brett Witters — Mon, 27 Apr 2020 13:31:05 GMT

Recently, the element information tool icon disappeared from the primary toolbox in MicroStation V8i. All other tools that usually appear in that toolbox seem to still be there.

Also, linestyle pulldown has disappeared from the attributes toolbox. Any idea what could cause this??

Brett Witters

Ask A Question I

Mon, 27 Apr 2020 08:09:06 GMT

Ask a question in a forum.