I recently upgraded to windows 10. I installed Sketchup 2016. The graphics card I have is a FireProGl V7800. Unfortunately, sketchup is not detecting my graphics card so I'm unable to take advantage of all its features.When I open a large file the frame rate is choppy and sometimes sketchup freezes when loading. I updated the drivers but still this version of sketchup cannot see my card. Apparently, Sketchup 2016 uses Open Gl 2.0. So, is my card outdated, is this a windows 10 issue or did I install the wrong drivers? I attached specs of my rig. Thanks

Operating System: Windows 10 Pro 64-bit (10.0, Build 14393) (14393.rs1_release_inmarket.160906-1818)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: BIOS Date: 10/29/10 22:06:58 Ver: 08.00.15
Processor: Intel(R) Core(TM) i7 CPU X 980 @ 3.33GHz (12 CPUs), ~3.3GHz
Memory: 12288MB RAM
Available OS Memory: 12280MB RAM
Page File: 3449MB used, 21117MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Not Available
Microsoft Graphics Hybrid: Not Supported
DxDiag Version: 10.00.14393.0000 64bit Unicode

Display Devices

      Card name: ATI FirePro V7800 (FireGL V)

   Manufacturer: Advanced Micro Devices, Inc.

      Chip type: AMD Radeon Graphics Processor (0x6889)

       DAC type: Internal DAC(400MHz)

    Device Type: Full Device

     Device Key: Enum\PCI\VEN_1002&DEV_6889&SUBSYS_03061002&REV_00

  Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] 

Device Problem Code: No Problem

Driver Problem Code: Unknown

 Display Memory: 5874 MB

Dedicated Memory: 2034 MB

  Shared Memory: 3840 MB

   Current Mode: 1920 x 1200 (32 bit) (60Hz)

   Monitor Name: Generic PnP Monitor

  Monitor Model: PA246

     Monitor Id: ACIFF24

    Native Mode: 1920 x 1200(p) (59.950Hz)

    Output Type: Displayport External

    Driver Name: aticfx64.dll,aticfx64.dll,aticfx64.dll,amdxc64.dll

Driver File Version: 8.17.0010.1404 (English)

 Driver Version: 15.201.2401.0

    DDI Version: 11.2

 Feature Levels: 11_0,10_1,10_0,9_3,9_2,9_1

   Driver Model: WDDM 1.3

Graphics Preemption: DMA

Compute Preemption: DMA

       Miracast: Not Supported by Graphics driver

Hybrid Graphics GPU: Not Supported

 Power P-states: Not Supported

Driver Attributes: Final Retail

Driver Date/Size: 11/3/2015 8:00:00 PM, 1448296 bytes

    WHQL Logo'd: Yes

WHQL Date Stamp: Unknown

Device Identifier: {D7B71EE2-2BC9-11CF-CE76-0C23BEC2C535}

      Vendor ID: 0x1002

      Device ID: 0x6889

      SubSys ID: 0x03061002

    Revision ID: 0x0000

Driver Strong Name: oem59.inf:cb0ae414ffe4100b:ati2mtag_EvergreenGL:15.201.2401.0:pci\ven_1002&dev_6889

 Rank Of Driver: 00D12001

    Video Accel: ModeMPEG2_A ModeMPEG2_C 

    DXVA2 Modes: DXVA2_ModeMPEG2_IDCT  DXVA2_ModeH264_VLD_NoFGT  DXVA2_ModeVC1_VLD  

Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive

                 {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 

                 {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 

                 {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 

                 {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 

                 {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 

                 {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

                 {3C5323C1-6FB7-44F5-9081-056BF2EE449D}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 

                 {552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 

                 {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 

                 {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 

                 {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 

                 {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

                 {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

                 {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

                 {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

                 {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

                 {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

   D3D9 Overlay: Not Supported

        DXVA-HD: Not Supported

   DDraw Status: Enabled

     D3D Status: Enabled

     AGP Status: Enabled

       MPO Caps: Not Supported

    MPO Stretch: Not Supported

MPO Media Hints: Not Supported

    MPO Formats: Not Supported

Hi all,

Attached are images showing the kind of look I want for my glass. I've been having trouble trying to get the same coloured tint, strong reflection but medium transparency. Do I colour the glass using the fog option or do I specify the colour in the reflection colour slot? Do I use the refraction for the transparency or lower the transparency in the diffuse channel? To get the strong reflections do I raise the IOR value or keep it at 1.52 and adjust the reflection colour? If any one can help me with this I would greatly appreciate it.

I use SketchupPro 8. That plugin doesn't work with this version of Sketchup. On a side note, Solo I've seen some of your working using Vue and I'm very impressed. I tried rendering using Vue and I was unsatisfied with the long render times and poor quality end result therefore I have yet to use it for a commercial project. Can you provide me some do's and don't s when it comes to lighting an exterior scene in Vue. I want decent quality and reasonable render times. I'd really appreciate that. Thanks

Thanks for the response daarboven. I've tried the .3ds format. Coming from a 3dmax background, I'm very familiar with it. The problem with this format is that the cameras are facing the wrong direction and you can't see the cameras once I import them into modo. Is there a bug in modo? The 3ds format also has a face import limitation that basically caps my workflow. Textures are missing from the models I import so I have to re-texture them in modo. In modo I like to have my z-axis as the up axis as my preference. In modo the default up axis is the y-axis for some strange reason so every time I import a .3ds file I have to rotate it which is a bit of a drag. The .obj file format doesn't have these issues but it is missing a camera export option. I like rendering in Sketchup using Vray but because Shetchup is a 32bit program it has it's limitations on scene size. I have a 64bit system and I want to take advantage of modo's 64bit rendering speed since it has no limitations. If any one models in sketchup but renders in either modo or vue I would really like to know your workflow. Thanks

Hi All (Sketchupcationites?)

I finally got myself registered to this great site. I'm starting a one man Arch Viz studio. I use a number of software that I keep on adding to my workflow. I have Sketchup Pro as my primary modeller and I render in Vray. I also have Vue 9 complete and Modo 501 which I'm still trying to get comfortable with. I want to get all these programs to "play nice" together. The one thing that I still haven't had any luck in resolving is matching the Sketchup camera view in modo and vue. I want to have the flexibility of overlaying the Sketchup lines on the output from these programes. The camera doesn't get exported into modo when using the .obj format. I tried to match the Sketchup camera values and entered them into a modo camera and the view is off even when I match the exact location, focal length etc. The view is off in Vue even when I use the SketchuptoVue plugin. If anyone can offer any assistance regarding this issue, I'd really appreciate it. Thanks