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.
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Hi Andres,
Unknown said:Bentley could put on it's website a sticker, that you don't recommend to install Windows 10 because Bentley products are not certified yet.
Why they should do it? I have not seens anything similar on web of other GIS and CAD software providers. This is users' responsibility and freedom at the same time to decide if they want to use a chosen product on Windows 10. And Bentley today offer several hundreds of applications and software modules, so general information about Windows 10 would be pretty useless. What a particular product is certified for is mentioned in its readme file.
Unknown said:I think it's not a huge work for webmaster, but could save a lot of people from trouble.
It seems to me you missed important fact the mentioned problem has nothing to do if PowerDraft is certified for Windows 10 or not. This is problem of Nvidia, not Bentley and not Microsoft, and is reported for older Windows version for some cards and drivers also. PowerDraft works fine, despite of it's not certified, on Windows 10 with e.g. AMD or Intel graphic cards.
Unknown said:But where can I find that QV_D3DVERSION?
Did you try to search this forum? It was discussed so many times. I recommend to put QV_D3DVERSION = 9 to e.g. standards.cfg file, which is in PowerDraft workspace folder structure (something similar to C:\ProgramData\Bentley\PowerDraft\WorkSpace\Standards\). If it doesn't help, you can also try to set it as Windows variable as mentioned by Jon.
With regards,
Jan
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.
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,