图形驱动程序崩溃-输入的像素过多? [英] Graphics driver crash - too many pixels as input?

问题描述

不确定是否有更好的论坛.查看论坛列表，这和驱动程序开发都似乎很合适.

Not sure if there is a better forum. Had a look at the forums list, this and driver development both seemed suitable.

我有一个应用程序，可以在地球/地球上显示大量数据点，这些数据点代表地震以及发生位置，震级和强度.颜色(红色表示大地震).数据从excel输入到应用程序中，并且该应用程序显示 地球，并在上面绘制数据点.
(参见此页面，位于下面的教程一:地震数据"下方-在步骤6中.黄色，白色，绿色是一些数据点.如果仔细观察，我们会发现点的大小不同 用于不同的颜色/大小.随着大小的增加，点的颜色和大小也会增加.红色(未在图像中看到)的幅度很大，并且其点比看到的要大得多.数据基本上是形式，数据点及其大小. 小幅度有一个小点作为屏幕上的数据点.幅度越大，点越大.

I have an app where we are displaying on the earth/globe numerous data points which represent earthquakes along with location of occurance, the magnitude & color (red signifies major quake). Data is fed into the app from excel, and the app displays the globe and with the data points drawn on it.
(see this page down below at - "Tutorial One: Earthquake Data" - its in step 6. Yellow, white, green are some data points. If you observe closely we see that the size of dots are different for different colors / magnitude. As magnitude gets higher, color and size of dot increases. Red (not seen in image), is significant in magnitude and its dot is much larger than what was seen). Data is basically of the form, data points and its magnitudes. Small magnitude has a small dot as a data point on screen. Larger magnitude has a bigger dot.

当太多这样的数据点(例如一百万个)作为输入输入时，驱动程序似乎崩溃了，这会导致BSOD. (当数据点集中在某个点附近时，我经历了崩溃.)当数据最初显示为 大约一百万个点集中在一个较小的区域，我们将所有大约一百万个点视为一个小点，因为将初始状态缩小后可以看到整个地球.当我们放大时，现在大约在上百万个数据点上绘制了更大的表面积 屏幕.放大的响应速度变慢，最终如果继续进行放大，则会崩溃.这是特定于数据的(更多点及其数量级可能会崩溃).
有人告诉我这是一个渲染问题，并且正在馈送过多的数据点以至于无法绘制图形.是吗?

When too many such data points (like a million) are fed as input, the driver seems to crash and it results in a BSOD. (I have experienced this crash when the data points are concentrated around a certain point.) When the data is displayed initially with million or so points concentrated around a small region, we see all of the million or so points as a small dot, since initial state is zoomed out to see the whole globe. As we zoom-in, the million or so data points, now get drawn on a larger surface area on the screen. The response of the zooming-in slows down, and eventually if we continuue to zoom it crashes. This is data specific (more points combined with its magnitude can crash). 
I was told this is a rendering issue, and that too many data points are being fed for graphics to draw. Is it?

我们探索过的一种可能的解决方案是在将数据馈送到我们的应用程序(数据源为excel)时，我们在源级别进行检查并以某种方式计算数据是否会导致崩溃.但这适用于特定的图形卡.我想知道是否有可能 具有基于数据的动态解决方案，并比较graghics是否具有绘制功能. (不同的用户使用不同的卡，因此功能也不同).如果可以，我该怎么办?

A possible solution we had explored is when feeding data to our app (data source is excel), we check at the source level and calculate somehow if the data can cause a crash. But this works for a specific graphic card. I would like to know if it is possible to have a dynamic solution based on the data and compare if graghics has the capability to draw. (different users different cards and hence different capability). If yes, what could i do?

推荐答案

好的，

我建议您更改此操作的方式.您真的需要一百万分吗?是的，我知道您有100万个数据点-但是缩小后看不到100万个数据点-那么为什么要渲染它们呢?放大时-您看不到一百万点 当您靠近时看不到整个地球-那么为什么要渲染它们呢?

I would suggest you change the way you are doing this. Do you really need a million points? Yes, I know you have a million points of data - but zoomed out you do not see 1 million points - so why render them? When zoomed in - you do not see 1 million points as you are closer and do not see the whole globe - so why render them?

当您完全放大地球仪时，图像非常详细-但是仅渲染了地球仪的一小部分，而缩小图像时，则没有详细信息.

When you zoom fully in the globe image is very detailed - but only a small part of the globe is being rendered and when zoomed out the image is not detailed.

您需要以相同的方式处理您的点.

You need to process your points in the same way.

重新编码显示逻辑以仅呈现可见内容将解决您的问题

Re-coding your display logic to only render what can be seen will solve your problems

这篇关于图形驱动程序崩溃-输入的像素过多?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！