Incompatible resolution, color depth, color bits, colour buffer, etc. (case 17147)

[jarvis24]

IN your folder where the DirectRT input file is located--is there a .drt style file? If so, is that where you set the 1366 x 768? If so, Is it listed as available on the pull down list of available resolutions? Also, does the same error occur if you run the input file outside of MediaLab?

[Grenose]

Yep, I set the display using the dropdown menu in DRT. I'm not experienced with the program so its the simple way for me.

Gren.

[jarvis24]

Gren-- does it happen if you run the input file alone with no other programs running (including MediaLab). And if you run it in an alternate resolution such as 1024x768 (just for testing purposes)? If yes to both of those, what about the sample files--do they produce the same error? If yes again, then can you please check the exact version of DirectRT you have installed, i.e., 20xx.x.x.x?

[Grenose]

I tried Direct RT by itself and it was exactly the same. Then Direct RT by itself with the resolution set to 1024*768 and it was exactly the same. The file was originally written by a PhD student who has gone on to better things and completely forgotten about Direct RT. If I drop the whole folder/drive path into an XP based computer it just runs. That wasn't possible for the Win 7 computer as the Documents and Settings folder is managed differently.
The other odd thing is the creation of an empty 'Voice' folder in the data folder.

Version is 2008.2.103.1115.

Regards,

Gren.

[jarvis24]

And what about that one last test I mentioned--i.e., running the samples that come with DirectRT--same thing?

[jarvis24]

RE errors such as "no compatible resolution" "can't determine refresh rate" "no compatible color depth" "color buffer" and such.. It turns out it can be a very important issue as to whether or not your system can detect that Windows DirectX has been properly installed. This applies to most ALL versions of DirectRT because they DEPEND tremendously on the proper installation and operation of Windows DirectX. Fortunately there is a way you can tell if your system is setup to go. Try creating a dxdiag.txt file and see if anything looks like this (below) in the "display properties":

Video Accel:
Display Memory: n/a
DDraw Status: Not Available
D3D Status: Not Available
AGP Status: Not Available

If so, then DirectRT is extremely unlikely to run. If this is the case, then take a look here:

http://www.empirisoft.com/Support/showthread.php?t=5697
http://www.empirisoft.com/Support/showthread.php?t=550

Note: If you want to try running a system diagnostics test like this, here is how you do it: Type "dxdiag" from the "Run" command on the Windows "Start" menu. You will get a complete diagnostic description of your system. If you then click "Save All Information" you can save it as a text file and view it in notepad or wordpad etc. Scroll down to the "Display Properties" area to check out values mentioned above.

[Rene Kopietz]

Dear Blair,

we have a similar problem and neither the manual nor this thread did help in solving it. The attached study does not run on some of our machines. I ran the DirectX diagnostics and it seems to be everything in order (see attached). Changing the resolution does not help. Using a colour.txt file with both 24 and 32 does not work either.

The error message indicates a 13xx x XXX resolution, but neither the screen,the style file inside the experiment folder, and not the style file inside the drt specify this resolution. In fact, bot define HD resolution (the native screen res.).

We are running DRT2010 (latest build) on a up to date Win7 machine.