Re: Normal Maps / Depth Maps - Testers Needed! V1.0
Posted: 10 Jun 2010, 15:57
I actually only intended to make my point once and not have to make any follow up points at all, but you obviously misunderstood so I clarified, I was not being argumentative, I was just saying something you didn't like or particularly want to read properly.
The first place to look for when errors occur is your own code, were your users, treat us professionally, so far you've assumed one of your users can't do basic control tests and then attacked another user for pointing it out, all unnecessary for you to do, and damaging
I would suggest since you admit you don't know what is happening, that you investigate using some simple metrics. Logic would suggest that since he is running on a 9600, ( IIRC you are running in a 9xxx class nvidia gpu no? ) that shaders are less likely to be at fault, but timers would improve this guess a lot.
A modified version of both codebases that printed out time overall would give a good indication of the differences in CPU usage, and if the results are promising you can fine-tune with more timers to figure out where to start looking.
The first place to look for when errors occur is your own code, were your users, treat us professionally, so far you've assumed one of your users can't do basic control tests and then attacked another user for pointing it out, all unnecessary for you to do, and damaging
I would suggest since you admit you don't know what is happening, that you investigate using some simple metrics. Logic would suggest that since he is running on a 9600, ( IIRC you are running in a 9xxx class nvidia gpu no? ) that shaders are less likely to be at fault, but timers would improve this guess a lot.
A modified version of both codebases that printed out time overall would give a good indication of the differences in CPU usage, and if the results are promising you can fine-tune with more timers to figure out where to start looking.