1 reply to this topic

[AlexGamezo]

Hi, I'm working with Managed DX and C# and I have a really weird issue coming up that I don't know how to deal with. I do a Mesh.Intersect test on a custom mesh that I create for the terrain. On my 3-4 year old laptop till runs fine and only minutely effects the frame rate (135 cut down to 125), while on a new computer with a much more modern graphics card it cuts it from over 1700 fps to 17-20 fps. It was suggested that this might be due to the fact that the laptop does everything in software and thus doesn't waste time on any sort of data transfer into system memory while the newer computer does ...... but if this is true, then how would i go about dealing with the problem? I can't understand the rationale behind the error so I can't come up with a solution. Anyone come up against this problem before and gotten past it? Thank you for any help you can offer.

Alex G

[Kenneth Gorking]

You could easily test that theory be forcing DX to put the data of the mesh into system memory, instead of video memory. If the fps-drop goes away, you have found your culprit.