Archived: LabVIEW for myDAQ EAR Known Issues

NI does not actively maintain this document.

This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.

Overview



This document contains the LabVIEW for myDAQ Early Access Release (EAR) known issues that were discovered before and since the release of LabVIEW for myDAQ EAR. Not every issue known to NI will appear on this list; it is intended to only show the severe and common issues.

Contacting NI

You can contact us by phone, email, or the discussion forums. Visit the NI Website to contact us.

Known Issues by Date

The following items are known issues in LabVIEW for myDAQ EAR sorted by Date.

400799 Error when saving Guided Help project with large videos
459492 Context Help and/or Guided Help are blank
463364 MathML is not supported in the Guided Help Editor
467462 "Video playback was aborted" error when exporting Guided Help with video
472586 Palette text can be larger than intended when running LabVIEW for myDAQ on a MacBook Pro with Retina display on a Parallels VM
475304 Getting Started Video playback can be choppy



ID Known Issue
400799

Return
Error when saving Guided Help project with large videos
All Guided Help assets are loaded into memory when saved. If the save process can't load all assets into memory, it will fail with an out of memory exception.

Workaround: Close any unnecessary applications and try again. Alternately, use a placeholder video and edit the project XML to link to the correct video.

Reported Version: 1.0    Resolved Version: N/A    Added: 05/30/2014
459492

Return
Context Help and/or Guided Help are blank
If the machine running LabVIEW does not have a DirectX 9 compatible graphics card, the browser will use software rendering instead of hardware rendering. In software rendering mode, the browser can only be displayed with a color depth of 32 bits.

Workaround: If the user is connecting to the machine locally, they need to change the colors setting on the monitor to "True Color (32 bit)". If the user is connecting to the machine remotely, they need to change the colors setting in the remote client to "True Color (32 bit)" before connecting to the machine.

Reported Version: 1.0    Resolved Version: N/A    Added: 05/30/2014
463364

Return
MathML is not supported in the Guided Help Editor
MathML rendering will work in the Guided Help Viewer, but is not supported in the Guided Help Editor.

Workaround: N/A

Reported Version: 1.0    Resolved Version: N/A    Added: 05/30/2014
467462

Return
"Video playback was aborted" error when exporting Guided Help with video
Guided Help videos are in OGV format, and can only be played with a subset of internet browsers. If your default browser is anything other than Google Chrome or Mozilla Firefox, you will receive this error. This error does not affect the The Guided Help content will work correctly within the software.

Workaround: Open the exported html file in a browser capable of displaying OGV files.

Reported Version: 1.0    Resolved Version: N/A    Added: 05/30/2014
472586

Return
Palette text can be larger than intended when running LabVIEW for myDAQ on a MacBook Pro with Retina display on a Parallels VM
The text may clip and you may observe other graphical glitches.

Workaround: You may be able to resolve the issue by:
1. Opening Parallels Options (Virtual MachineÈConfigure)
2. Select the Video setting
3. Select either Scaled or More Space
4. Reboot your virtual machine

Reported Version: 1.0    Resolved Version: N/A    Added: 06/18/2014
475304

Return
Getting Started Video playback can be choppy
Video playback can be choppy when LabVIEW for myDAQ is running on a virtual machine.

Workaround: Increase CPU and memory resources available to the virtual machine.

Reported Version: 1.0    Resolved Version: N/A    Added: 06/18/2014

Document last updated on 6/18/14

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).