Powerdraft problems with windows 10

I have changed my OS to windows 10 but unfortunately I got back same graphic problems I had when I installed powerdraft, the drawings are all jammed together. Would appreciate any suggestions. Sorry I know WINDOWS 10 is new but I believe Bentley has been preparing its launch for sometime.

Parents
  • Hi,

    as was discussed in another discussion you participated in, if you use Nvidia, the problems are caused by confirmed bug in particular Nvidia driver versions. So there is no way how Bentley can solve it ... of course it's probably possible to try to implement own workaround, but why, if other cards (AMD, Intel...) and other Nvidia drivers work without any problem?

    MicroStation PowerDraft is not certifid for Windows 10, so it's your responsibility and risk to install it. And after the mentioned problems appeared, did you try proposed workrounds? ... I guess to try another driver version may not work with Windows 10, but to set configuration variable should help.

    With regards,

    Jan
  • There have also been some issues in the past with certain Nvidia drivers and DirectX 11. Windows 10 uses DirectX 12, are you sure your card is capable or running with Driect X12?

    You can try forcing MicroStation to use the older DirectX 9 interface by setting a MicroStation configuration variable as it has been mention previously. Setting QV_D3DVERSION to a value of 9 (in the environment variables of Windows) will force MicroStation to use the DirectX 9 interface.

    This would simply be a workaround suggested for running PowerDraft on a uncertified platform at this time



  • Hi Andres,

    Unknown said:
    And I also understand, that if nVidia is not doing anything, then Bentley could do a workaround. But Bentley does not want to do that.

    With all respect, you don't know what you are talking about. DirectX is seriously complex low-level API, partially because natural complexity of 3D graphics, but unfortunately also because some (in my opinion) not good decisions done during DirectX API design (specifically Direct3D in this case) in the past. I "touched" this API only little in the past and I have to say I am happy I don't have to develop high performance 3D engines ;-)

    So to "do a workaround" probably requires a huge amount of work including testing that nothing else has been broken and all other variants (card types, driver versions) work fine. I don't know details how MicroStation DirectX engine is implemented, but based on blogs and articles from game engine developers I don't believe an acceptable ratio between cost and benefit exists. Especially if it's problem of some specific driver versions, not e.g. graphic processor used in some card series. And it would end with situation described by some driver developer (don't remember he was from AMD or Nvidia) that for some driver versions more than a half (!) of development were only workarounds for popular (and so imporant) games and other applications with wrongly implemented DirectX API ... which again demonstrates it's not well designed API :-(

    Let's imagine a situation you will produce motors for cars and very bad petrol is sold in some area, so a bunch of problems with your motors exist there. Will you change software in control unit and implement changes how the motor is constructed and produces and will go into risk you break something in well designed complex engine and perfectly tuned assembly line? Of course with the risk new problems will apear in areas with good standard petrol? Or you will require only clean correctly produced petrol has to be used?

    Unknown said:
    However Bentley has been collecting select subscription fee every year but i have not seen a product updates for almost 2 years... the bugs what were 2 years ago still exist, so I think I have the right to be upset.

    If there no upgrade for almost 2 years, it's reason to be upset. If there are bugs in Bentley code, reported but not solved, it's the reason to be upset. I agree with you. But in this specific case, you should be upset about Nvidia, because they know about this problem for long time, but it seems potentially thousands of their (Nvidia) users are not valuable enough to release correct driver.

    With regards,

      Jan

    Answer Verified By: J.Haizel 

  • Unknown said:
    But Bentley does not want to do that.

    QV_D3DVERSION is the implemented workaround. There is no other reason why this variable exists than to force MicroStation (or PowerDraft) to use older version of DirectX API (9 instead of 11 in this case) if any problems are experienced with DirectX 11. So what do you want more?

    Regards,

      Jan

    Answer Verified By: J.Haizel 

  • Thank you ladies and gentlement. I managed to upset few people but the debate my question has generated is encouraging. I love you guys. This site is better than any social media out there. Lets get this going. Few times I don't find answers on this site but I believe it does help Bentley development team to dig deep. The upgrades are eventually addressing some of the difficult questions I have had in the past.
    Thank you once again for all the contributions.
  • Jan

    I'm having problems with Powerdraft (08.11.09.829 SS4) on Windows 10 - graphics are completely jumbled.  According to Bentley download link this is Windows 10 compliant.  Version 08.11.09.459 SS3 does the same.

    Power Rail Track (08.11.09.845 SS4) does the same - not Windows 10 compliant.

    On another similar(?) machine PRT works fine.

    Could you please expand on your comment "QV_D3DVERSION is the implemented workaround".  How do I access and set this variable?

    Desperately need advise on this one.

    Regards 

    Neville du Plessis

    Rail Design

  • Jan
    I have found your earlier posts re: QV_D3DVERSION. Will try that.
    Thanks

    Neville du Plessis

    Rail Design

Reply Children