[V8i] A Bug in Display Styles?

I wanna know why Bentley designed this display style but the newly modified settings in wireframe cannot apply on this. I've also tried to find out if there any ways to set the "Default Display Style" when the dgn's display style is undefined but nothing was found.

Of course, after defining the display style is "Wireframe", modified wireframe settings will work well.

Parents
  • Hello,

    I guess to answer your question we have to look at how a display was setup prior to V8i.  In the older versions a view had a render mode, not a display style. When you open a file that has never used v8i before we have to infer the (render mode display) display style. We did this versus create a display style that could possible conflict with your company standards.

    Regarding setting a default display style, this can be done in your seeds.  We do not have the concept of an active display style that all views use.

    I hope this answers your questions, please let me know if I need to clarify anything further.

  • John, I have one more question. I would like to understand what is the "Software Graphics" mean? Some of V8 DGN appear this after converting from V7 DGN format. I did a search, to enable it we have to set "MS_FORCE_SOFTWARE_RENDERING = 1" but i didn't set it. How would it affect the display?

  • If you could set QV_GLSTATS=1 in your environment, run MicroStation, reproduce it switching to Software Graphics, then send a copy of everything printed to the MicroStation Text Window to me, we should be able to tell you why it's switching.

  • I didn't see anything changed in the text windows after reproducing the problem. And you may be a bit upset because I'm not using DirectX 11.

    ===========================================

    QVision version 03.35.23 - 09.Nov.2012

    32-bit compilation: 4 byte QvIDs

    System Information:

       Computer:

           Name:    CAD1

           Mfgr:    Hewlett-Packard

           Model:   HP xw4400 Workstation

       OS:

           System:  Microsoft Windows XP Professional

           Version: 5.1.2600  Service Pack 3

           Memory:  2.00 GB

       Processor:

           Name:    Intel(R) Core(TM)2 CPU          6600  @ 2.40GHz

           Addr:    32

           Cores:   2

       Graphics Adapter 1:

           Name:    ATI FireGL V3400

           Mode:    1280 x 1024 x 32-bit color @ 60 Hz

           Memory:  128.00 MB

           Drivers: ati2dvag.dll

           Version: 6.14.10.6912

           Date:    12 February 2009

           Feature: D3D9

           DevID:   PCI\VEN_1002&DEV_71D2&SUBSYS_2B021002&REV_00\4&14DB2FCF&0&0008

       Graphics Adapter 2:

           Name:    ATI FireGL V3400 Secondary

           Mode:    1280 x 1024 x 32-bit color @ 60 Hz

           Memory:  128.00 MB

           Drivers: ati2dvag.dll

           Version: 6.14.10.6912

           Date:    12 February 2009

           Feature: D3D9

           DevID:   PCI\VEN_1002&DEV_71F2&SUBSYS_2B031002&REV_00\4&14DB2FCF&0&0108

       Monitor 1:

           Name:     ATI FireGL V3400

           Adapter:  1

           Origin:   0, 0

           Size:     1280 x 1024

       Monitor 2:

           Name:     ATI FireGL V3400 Secondary

           Adapter:  2

           Origin:   1280, 0

           Size:     1280 x 1024

       Main Window:

           Origin:     -4, -4

           Size:       1288 x 1002

           On Monitor: 1

       Time Zone:

       DirectX:

           Version: DirectX 9.0c (4.09.0000.0904)

    Seurat Context [1]:

     Image Format = 8-bit int per band

     Depth Format = 32-bit float

     D11 disabled - at user's request

    Adapter count 2

    Adapter 0: 1280 by 1024, format X8R8G8B8

    Floating point render target available, no blend

    Direct3D9 Context for hwnd 60716 on adapter 0:

     HAL/hardware Device, level 2 (generation 0)

     Color Bits = 24

     Alpha Bits = 8

     Depth Bits = 24

     Stencil Bits = 8

     Graphics Card Driver from ATI

     vertex shader version 3.0 - enabled

     pixel shader version 3.0  - enabled

     maximum number of lights: 8

     additional clip planes: 6

     largest texture: 4096 by 4096

     D3D capabilities:

         occlusionQuery 1

            scissorTest 1

             uvwSupport 1

              colorMask 1

     Glib Init -  using level 2

                 vertex level 2

                  pixel level 0

  • I'm surprised that there were no prints when it switched to Software Graphics. Here are a couple of things that can happen with regard to D9:  1) Running out of graphics card memory could cause some views to switch but not necessarily all of them.  2) In a slow state as you described, if we got a "device lost" status from the graphics card and we were unable to successfully reset it, then all of the views would switch to Software Graphics.

  • I'm curious for "we were unable to successfully reset it".

    So if the "device" suddenly be detected again, could MicroStation switch back to D9 mode without restarting application or re-opening the dgn? :)

  • No, sorry, on the automatic switch back to D9. If that was happening, it would be much slower to keep trying to re-create a context to see if the card was responding. And since there were no prints, it turns out that it's likely not the "device lost" that's happening.  We'd be curious to know how many views you have up and their approximate sizes.  Also, do all of the views switch to Software Graphics or just some?

    Thanks,

    Russell

Reply
  • No, sorry, on the automatic switch back to D9. If that was happening, it would be much slower to keep trying to re-create a context to see if the card was responding. And since there were no prints, it turns out that it's likely not the "device lost" that's happening.  We'd be curious to know how many views you have up and their approximate sizes.  Also, do all of the views switch to Software Graphics or just some?

    Thanks,

    Russell

Children
No Data