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
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
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
Hi Neville,
Unknown said:I have found your earlier posts re: QV_D3DVERSION. Will try that.
You should be aware this variable is the workaround only, not the solution and as such is not supported by Bentley for production use (but many users use it every day ;-)
The solution recommended by Bentley is to upgrade Nvidia drive to the latest one and to check if it works fine and if not, to downgrade to the latest version that worked fine in the past.
With regards,
The problem is that the Windows 10 update forcefully updates your graphics drivers. The newer drivers are the ones causing the problem. Updating drivers won't solve anything. The older drivers, that used to work, simply can't be installed on Win10. The official recommendation is pure waste of time in the case of an upgrade to WIn10.
http://communities.bentley.com/products/microstation/f/273/p/117684/362239#362239
http://communities.bentley.com/products/microstation/f/273/p/118467/365109#365109
The problem has existed for years, so don't hold your breath for NVidia to fix the problem.
The QV_D3DVERSION=9 is the only way to go if you want to keep using MicroStation V8i with the same graphics card on Windows 10.
If you ever upgrade to MicroStation CONNECT on that system, you'll need to set QV_DISABLE_D3D11=1 or you'll have the same problem again.
Jan / Koert
Thank you for the assistance. Your comments have been very helpful.
I placed the following variable in the Personal.ucf (this is for Powerdraft CONNECT) and it solved the problem:
QV_DISABLE_D3D11 = 1
So Powerdraft is now happily running on DirectX 9
The machine has the NVIDIA drivers; 3D Vision Driver 341.95, Graphics Driver 341.95
On another similar machine with the NVIDIA Graphics Driver 353.3 all is fine using DirectX 11. I will try to upgrade the above driver to 353.3 as well, and see what happens.
Koert, my only question is; for Power Rail Track SS2 and SS4 (i.e. pre-CONNECT) where should I put the QV_D3DVERSION=9 variable? For the above Powerdraft CONNECT I placed it in the Standards.cfg but it made no difference. PD still insisted on using DirectX 11.
Hi neville,
Unknown said:for Power Rail Track SS2 and SS4 (i.e. pre-CONNECT) where should I put the QV_D3DVERSION=9 variable?
Standards.cfg shoud be fine to place QV_D3DVERSION variable definition. The workspace structure and some file names are different in V8i and CONNECT Edition, so
Alternatively you can also define this variable in Windows, not in workspace configuration, so it will be used by all installed V8i products.
Unknown said:On another similar machine with the NVIDIA Graphics Driver 353.3 all is fine using DirectX 11. I will try to upgrade the above driver to 353.3 as well, and see what happens.
It's pretty interesting findings. I am curious what the result will be and if the newer driver will solved the problem.