However, ATi has recently change how memory management works, it seems, at the driver level, and this change is evident in apps that feature the aforementioned support for memory use monitoring. It's built into Crysis as well, and, of course, most other engines, but this needs to be enabled inside the app, rather than using an external tool.
Cheer curiosity. I could almost bet my neck this is the v10.4b(8.721.3.0000) and updated in v10.4 WHQL->after. Would also explain hell a lot other things which I've been
working on. (of course officially this would be v10.3b, but wth). As for explain. Well, I don't honestly even wanna go to devel forums. I know I will not
find answer there more likely they'll ban my ars for questioning too much, heh. As for 'inside application' only problem in this really is that not all the engines
comes with the support (like Bioware 'Eclipse'-engine Would love to get this engine statistics on screen anyway).
I'll find a way and query in 'live' sense only has to be done when executed so I think I can deal with some sort of coding here which would simply push
hotkey -> drop OSD flashing couple times of current memory in each chunk, but I just don't know where to begin really here, but just saying I'm sure no
real live 'OSD' Style of memory usage would even be needed to just understand a momentary memory usage.
i think ATI needs to add code to support Ram usage monitoring, im sure it could possibly done atm (check ram useage) but its likely to be inefficient and possibly give incorrect resualts.
Well, I'm not saying they wouldn't be capable of doing this and probably some new series will have this in the end, but considering atm drivers they are
building and as I see clear as a daylight all the issues there is on OpenGL 4.0 implementation, DirectX 9-10 on latest (10.6) CFX and older drivers (<-10.5a) DX11 (nor OGL 4.0).
I am just referring that there is, atm, so many very difficult problems on ATI lair and PR sawing wooden 'Flash is now working'-crap that I doubt there is
a room for any 'extra' code as they are doing probably the best just to keep up and fix the crap they made up.
@commonly
and o as for PhysX flaming. Well, I don't really care does the PhysX work on ATI cards or not it is not even on NVIDIA hardware worth a cent. I'd consider
maybe DirectCompute 11 as for the moment slow version of physics acceleration through all hardware not even OpenCL as it is so so so early stage of
development (although, working in my sense, but not for the people as only driver where this works is 10.3b officially and that's just crap. New drivers
comes with new CAL DD and that breaks with GTK the OpenCL functionality completely).