ETABS is unable to create rendered view when changing to the DirectX mode. 1

[serrojo]

Hi guys!

I have trouble when changing to the directX visual mode.

Etabs shows message: Unable to create rendered view. Model window will be closed.

I am struggling with it because when I create a big project it is faster to pan and scroll on the results on the directX view.
I have tryed:
* To update the video driver (I have a NVidia Quadro 4000 2Gb DirectX11 my actual version is 376.84)
* To install all the .Net frameworks 4.6.2.
*To install all directx files available.

All thoughts will appreciated, thanks.

Best regards.

MSc. Eng. Serguei Joa
Structural Engineer
Bouygues Batiment International, Cuba.

 

[James Schuman]

# First install latest DirectX 9 [link]https://www.microsoft.com/en-us/download/details.aspx?id=8109[/url].
Remember that DirectX 9 installs and runs separately from DirectX 11, and many softwares require it even on systems with DirectX 11 installed.

[highlight #FCE94F]If it didn't solve the problem do the following steps, it may solve your problem:[/highlight]

# Check the DirectX Installation:

Press "Windows+R" to open Run. Then enter "dxdiag", click "Yes" to run the DirectX Diagnostic Tool.
Open the "Display" tab to see the status of Direct3D and other graphics components in DirectX.
Read the "Notes" box to learn about any errors with Direct3D. If DirectX is installed correctly, it will read "No problems found."
Read the "Feature Levels" line in the Drivers section to see which versions of DirectX your video card supports. Programs that require a version other than those listed will not work on your computer.
Check the DirectX Features section to make sure each line reads "Enabled." If any line does not, you need to enable hardware acceleration.

# Enable Hardware Acceleration:

Right-click the desktop and choose "Screen Resolution" (Win7~8) or "Display settings" (Win 10)
Click "Advanced Settings."
Open the "Troubleshooting" tab and click "Change Settings." Enter the administrator password if prompted.
Slide the "Hardware Acceleration" option to "Full."

# Update DirectX and Video Drivers:

Run Windows Update from the Control Panel to install updates for DirectX 11. Download and open the DirectX End-User Runtime Web Installer to update DirectX 9. DirectX 9 installs and runs separately from DirectX 11, and many softwares require it even on systems with DirectX 11 installed. So install the latest version of DirectX 9.
Update your video drivers either through Windows Update or by downloading drivers from the NVIDIA, ATI or Intel website, depending on your graphics hardware. If you already have the newest version from Windows Update, check the hardware manufacturer's website, as it may offer an even newer driver.

# If there is an Integrated Intel graphics hardware (it's on-board), switch between NVIDIA GPU and integrated Intel graphics hardware, you might need to update both the NVIDIA and Intel graphics drivers. Here's how to switch between NVIDIA GPU and Integrated Intel graphics hardware:

1. Right Click on Desktop
2. Select NVIDIA Control Panel
3. In left panel select "Manage 3D Settings"
4. In right panel select Global Tab
5. Under "Preferred Graphics Processor" select "Auto-Select" and hit APPLY button

Now try again and see if it properly selects correct GPU. If not
6. Repeat steps (1) through (3) above
7. In right panel select "Program Settings" tab
8. Under section (1), check the box for "only programs on this computer"
9. then hit the "Add" button and find the program that you want to run on NVIDIA card
10. Go down to section (2) and select NVIDIA processor

# If the problem persists, open the NVIDIA Control Panel, click "Manage 3D Settings" and select the program in the "Program Settings" tab. Change the graphics processor to the opposite of its current setting to try running it with the alternate graphics hardware.

 

[serrojo]

Thank you for your detailed answer! Indeed the issue was due to some faulty DirectX 9.0c modules installed by a software, so when I preform the dxdiag tool it only reflected the DirectX 11 status, but did not check the DirecX 9.0 capabilities!

So I went on removing the soft, installed since the date I knew everything was running OK, and finally found the trouble Rhino 5 (free trial) was the conflict.

Thanks again!



MSc. Eng. Serguei Joa
Structural Engineer
Bouygues Batiment International, Cuba.