Author Message
 Post subject: WindowsGDI & Direct3D Interface Working?
PostPosted: 31 Oct 2016, 20:32 
Offline

Joined: 31 Oct 2016, 20:06
Posts: 1
I noticed immediately after a DipTrace update that I could only get the OpenGL interface mode to work properly. The others are extreme.......ly slow. They were plenty fast in the recent past. The OpenGL interface seems not to quite have the same quality on this machine. I forced a GPU driver update and just had a Windows 10 update (after the problem appeared). I have:

DipTrace Full 2.4.0.2 Build 21 July 2014 (which seems ancient...I get the update wrong?)

PC
Toshiba Qosmio X70-A, i7-4700MQ 2.4GHz 4 core Intel
Windows 10 Home 10.0.14393
NVIDIA GTX 770M GPU is set to be default display driver
I use HDMI connected MX279 1920x1080 LCD
Operating System: Windows 10 Home, 64-bit
DirectX version: 12.0
GPU processor: GeForce GTX 770M
Driver version: 369.09
Direct3D API version: 12
Direct3D feature level: 11_0
CUDA Cores: 960
Core clock: 705 MHz
Memory data rate: 4008 MHz
Memory interface: 192-bit
Memory bandwidth: 96.19 GB/s
Total available graphics memory: 7130 MB
Dedicated video memory: 3072 MB GDDR5
System video memory: 0 MB
Shared system memory: 4058 MB
Video BIOS version: 80.06.51.00.0F
IRQ: Not used

-- 01 Nov 2016, 08:25 --

This may be related to the topic "3D preview doesn't work under windows 10/64bits" which I discovered latter. If I use some alternate graphics modes like Direct3D, then it takes a very long time before I get an image. If one was impatient (like waiting 'only' 15 seconds or so), then one would see nothing. So this may be the same thing.

I am upgrading to ver 3.0 regardless but since I have the trial version in place already (note I was using version 2.4 unlimited before), I can see that the same situation persists. Direct 3D seems to work on the machine with game & graphics demos from NVIDEA that are intended to exercise the GTX770M GPU.

I confirmed that the GPU was running for this program, then turned it off and confirmed the same problem with the Intel integrated processor. I confirmed that we had the same problem with both displays (likely anyway).

I have a (only partly informed) guess that this has to do with changes in Windows 10 Direct3D interface compared to Windows 8...unless it is happening on Linux as well.

-- 01 Nov 2016, 08:31 --

I should point out that by 'long time' I mean not to just first display of the image (could be forever in some cases but usually loooong time) but also for every image thereafter. Subsequent displayed frames are like 1 to 2 seconds apart and the board has moved quite some bit before the next image appears....jerky that is. This does not happen using OpenGL.


Top
 Profile  
 
 Post subject: Re: WindowsGDI & Direct3D Interface Working?
PostPosted: 02 Nov 2016, 04:06 
Offline
Technical Support

Joined: 14 Jun 2010, 06:43
Posts: 2762
Thank you for the report. We will investigate the issue. We thought updating video driver should fix the problem but it seems the issue is more complex.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 2 posts ] 

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 4 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group