3D plot hangs with Labview 64-bit, stable and reliably quick with 32-bit Labview

[blessedk]

My 3D plot works pretty well with Labview 32-bit, but hangs/slows with the Labview 64-bit. Has anyone noticed this or have a solution?

[altenbach]

There are plenty of 3D graphs. Can you be more specific?

Also, what is your LabVIEW version?

[blessedk]

Labview 64-bit 2015 evaluation. Parametric graph.

[billko]

---

@blessedk wrote:
Labview 64-bit 2015 evaluation. Parametric graph.

---

Is there a reason for LabVIEW 64-bit?  It's better to run LV 32-bit unless you absolutely need the extended memory available with a 64-bit application or unless you have to use dlls that are 64-bit and don't have their 32-bit counterparts (you can't mix and match 32-bit and 64-bit dlls).  LV 64-bit has limited-to-no compatibility with LV toolkits, and if any of the dlls you are using are 32-bit, it's a no-go.

[blessedk]

I understand that the 32-bit is more stable but I really really need the extended memory advantage that the 64-bit offers. I have both the 32-bit and 64-bit installed in my machine

[altenbach]

---

@blessedk wrote:
Labview 64-bit 2015 evaluation. Parametric graph.

---

Still not specific enough.

There is the "3D parametric graph" but there is also the "Active X 3D parametric graph". Which one?

Do you have a simple VI that demonstrates the problem? How many points are you graphing?

[blessedk]

Pretty large number pints being plotted. About 10700 rows and about 50 columns. I believe it's only paranetric, not active x parametric

[Bob_Schor]

10,700 * 50 = 535K.  If each entry is a point, and you are doing a 3D plot, that means you need 1.5M points for coordinates, and if they are all Dbl, this would require 12MB, which is a lot, but less than 4GB (32-bit memory space).

But how do you expect to meaningfully visualize that many points?  Something you could try would be to pick, say, 5000 points at random and plot those.  You can use all of the points when you do the fits (to get better accuracy), but you might also start with fewer points so as to see what you get without "choking" the algorithms.

So if the number of points isn't an issue, if 32-bit seems to work and 64-bit doesn't, why must you run on 64-bit LabVIEW?  What, specifically, is holding you back with the 32-bit ("stable and reliably quick") LabVIEW?  Might seeing the code (VIs, please, no pictures) help us understand?

Bob Schor

[altenbach]

The 3D parameteric graph will coerce all to DBL. No real choice in datatype.

[blessedk]

I definitely need the 64-bit because the file sizes I read in for this application can be anywhere from 1KB to 1GB. I tried reading a file in with 32-bit but an error message saying "not enough memory resources to ..." Came up on my screen, which was what prompted me to install the 64-but in the first place