🔒 Locked
D3DSpy
Advertisement
Original Post
Yes, I use it for seeing what D3DX does internally, among other things
A forum just for D3D has been discussed before, and the general concensus is that it wouldn't be worth it, since a lot of DirectX code is similar anyway.
A forum just for D3D has been discussed before, and the general concensus is that it wouldn't be worth it, since a lot of DirectX code is similar anyway.
When you use D3Dspy, does it consume a lot of RAM? I tried it and memory usage went up near 700MB for my application, so total system usage was above 1 GB. I was getting a lot of hard disk access. Is this normal for it to use a lot of RAM?
I could not stop it so I End Tasked.
My application alone doesn't take more than 30MB.
To me, a D3D only board would be cleaner. Each DX component is different thing. That's the way it is on MS servers.
I could not stop it so I End Tasked.
My application alone doesn't take more than 30MB.
To me, a D3D only board would be cleaner. Each DX component is different thing. That's the way it is on MS servers.
I've tried using it a couple of times, but because I can't find a way to attach to an application mid-process, I've never gotten useful information out of it. I start it up with my app, then wait five minutes for it to process all the calls I make during my init process... then use my app to navigate to the thing I want to examine, hit break on D3DSpy, and wait to see if it stops before giving up 20 minutes later and killing it...
Hopefully PIX's full call stream capture will be more useful, when I finally start using it properly...
Hopefully PIX's full call stream capture will be more useful, when I finally start using it properly...
I haven't noticed any extreme memory usage with D3DSpy, although I haven't really looked at the task manager to check. I'm certainly not getting hard disk access (which is caused by Windows paging memory in and out when it runs low).
Quote:
Original post by Evil Steve
A forum just for D3D has been discussed before, and the general concensus is that it wouldn't be worth it, since a lot of DirectX code is similar anyway.
I agree with this. This forum *literally* is the Direct3D forum anyways, if you look at the ratio of D3D posts to non-D3D posts. Surveying the first 2 pages, it's about 35:10. The 2nd most popular topic seems to be linker errors [sick]
Quote:
Original post by superpig Quote:Well, that's a problem wherever you go. And we have such a lovely Forum FAQ, too. [sad]
Original post by V-man
haven't read the FAQ.
Ah, yes. Coder has done an awesome job with it - too bad nobody reads it. It needs to be more prominent, like:
(a) An 'FAQ' button, like the 'New Thread' button
(b) At the top of the Post-A-Topic page (maybe you are even required to visit it)
The FAQ link on the main forum listing is a step in the right direction, though.
Topic Locked
This topic has been locked by a moderator. New replies are not allowed.
Sign in to reply to this topic.
Advertisement