the problem was within the atiogl.xml which stores the workstation profiles for the opengl capabilities for programs like maya, ideas, solidworks, pro/engineer. Recently there have been a lot of reports about missing viewport performance in maya. This applies to xp32,xp64, win7/vista 32bit and win7/vista 圆4 you need to get the atiogl.xml from here : in your windows you can either find it in the hardware manager, or at the display properties ( adapter).ĥ. So when you browse the list of device id´s at ati you´ll see that the Firegl v3600 and FireGL v5600 do have that RV630 chip also) the chip used on that card is RV630, and the firegl-equivalent of that chip is the RV630GL. in the case of my notebook, i have the hd 2600 mobility. Have a look at the device id´s of ati´s graphics cards : if you don´t know, you should discuss this here with other members. you need to use the install routine for the correct chip. It is necessary for the diver installation. you need to figure out what the Firegl/Firepro Equivalent to your card is. the corresponding FireGL/FirePro driver from AtiĤ. the latest patchscript ( watch for the driverversion it applies to)ģ. rivatuner ( it is needed to apply the patchcripts)Ģ. Things you need before starting to patch:ġ. as a side effect the new people on this board can read the answers and solution also. Other experienced users can give a solution to your question. This is done via applying a patchscript that forces the driver to use the device id you want.Ĭlick to ease don´t use a pm for that. You might reckon that the basis for a patch might be adding a certain device id (of a radeon card of course.) to the list of cards that have professional opengl caps, or more or less force the driver to use the professional opengl caps for a certain device id. the two kernels for xp and win7/vista use this device id to decide whether the driver should have proffesional opengl capabilites or not. the question that arises here is, how does the kernel know what capabilities a certain graphics card should have.Īt this point you will have to be aware, that every device ( graphics card) has a unique device id. Inside the kernel there are routines that allow/disallow the professional capabilities for certain graphics cards. The kernel for XP is the ati2mtag.sys, the kernel for vista/ win7 is the atikmdag.sys. If you try to understand how the differentiation via a graphics driver is done you will see there must be a core element of the driver ( the kernel). those device drivers are nearly identical, means they share the same component libraries ( *.dll) for direct3d and opengl. This allows Ati to simply make one driver for the consumer radeon cards, and one driver for the professonal firegl/firepro cards. The differentiation what capabilities a graphics card has is done by the device driver. Since the design and the production of those grapics chips does cost money both big players in graphics business have decide to produce only one graphics chip that has all the functions. Ati and Nvidia produce graphics cards for normal use ( radeon) and for professional users that have a few capabilities for accelerating viewport performance in opengl. What is softmodding, and why does it work.Ī. The PC, workstation, or server that the Stream environment is running on has to be an x86 or 圆4 processors that supports SSE 3.X or higher multimedia instructions.Q. The SDK supports FireStream 92 GPU co-processors and a variety of FirePro and Radeon graphics cards. (Where are proper commercially supported server operating systems, particularly the HPC variants?) The SDK can work in conjunction with Microsoft's Visual Studio 2008 Professional Edition, Intel's C compiler 11.X, or the open source GNU compiler collection 4.3 or later. If Linux is your thing, the SDK is limited to openSUSE 11 and Ubuntu 9.04. The Stream SDK v2.0 software runs on Windows XP SP2 and SP3, Windows Vista SP1, or Windows 7. (This is akin to the OpenCL and OpenGL integration above.) The Stream SDK v2.0 also has a preview of Microsoft's DirectX 10 graphics and multimedia APIs running in conjunction with the OpenCL stack so that Windows can take advantage of extra GPU processing oomph without making the round trip to the CPU. The SDK is also previewing OpenCL-OpenGL interoperability, which will allow calculations made using the OpenCL stack to be rendered and displayed by the OpenGL stack without having to send the data back out across the PCI-Express bus to the CPU where it is just dispatched back to the GPU for rendering.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |