I just updated to Windows 10 and MicroStation and Bentley Map are behaving quite strangely.
Before I continue I should tell you that my colleague also updated to Windows 10 and everything works fine.
What has happened in my case is that suddenly all MicroStation and Map icons have administrator badge attached even though I'm working on a user with administrator priviledges.
Another thing, and more annoying, is that when a design file is opened in MicroStation or Map all kinds of lines appear:
These seem to be some kind of "ghost" lines as they do not appear when printed and cannot be selected or worked with. It's like the can be seen but aren't there. When all levels are turned off the lines disappear.
Is there anyone who has had a similar problem or is there a known solution?
The Windows 10 upgrade will upgrade your Graphics Drivers. For many NVidia cards this means you'll have to set QV_D3DVERSION=9 to get it to work again.
link (either as an environment variable or in the MicroStation configuration somewhere, user-level is fine).
You can try other options as suggested by Bentley, but I wouldn't even bother with those.
You won't be able to install an old driver to the new OS.
Answer Verified By: Bjorn Magnus Arnason
RegardsAndrew BellTechnical SupportBentley Systems
Upgrading MicroStation and Bentley Map to V8i SS4 or even CONNECT versions won't solve the problem, but at least those versions are officially supported on Windows 10. That's one less excuse available.
The dialog where you set those variables might look a bit different depending on Windows Display Language, but a search on "environment variables" without quotes should point you in the right direction in any language. No reboot required on this system. Set variable, OK, OK. Restart MicroStation, problem solved.
Even CONNECT Edition with QV_DISABLE_D3D11 not set to 1:
CONNECT with QV_DISABLE_D3D11 = 1
All V8i versions need QV_D3DVERSION=9 on Win10 if your card suffers from this problem with the latest Drivers.
I placed the variable in my .ucf file, so it only effected Microstation.
This is easier to do than a Windows variable.