One problem in investigating D3DWindower behaviour is the difficulty to correlate events between different sessions. Let me know if you have any good idea:) Last edit: gsky916. Even the api tracing idea was come from you, you are much more experienced than me.That's why i suggest you to take a look by yourself, maybe you could find out some more useful details? Now the difficulty is, the information is still very limited.I'm not clear what can be do in the next step. However, I didn't get any debating yet, i'm also confusing about your statement? Anyhow it is what i'm trying to do, I posted few investigation result in the localization thread.Here: The most recent discovery could confirm D3DWindower is taking advantage of GPU. Since there are too much to do for the performance.I suppose investigating d3dwindower efficient schema could be a breakthrough point. That is why I suggested to concentrate on one point. Shall we limit it to a smaller scope at the beginning? D3DWindower could be a very wide ranged topic. It's not necessary to restart another one. Windows 7 ultimate black edition 2010 benjamin.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |