https://forums.vipm.io/discover/VIPM Community - All ActivityenI recently had this error. Antoine's method did not fix the issue for me. I also tried mass compile many times. What helped was I switched the build target from 2019 64-bit to 2019, build was then successful and then switched back to 2019 64-bit. Really strange.Wed, 18 Feb 2026 13:22:01 +0000I cannot see the image you posted. It shouldn't be that hard to install. It is one quick drop VI with no other dependencies.Fri, 30 Jan 2026 20:14:38 +0000Sun, 25 Jan 2026 17:07:40 +0000Found that I can get it pack and install only when I move it in to a folder and mark it "Place Folder Contents in Destination" in the file destinations.Mon, 19 Jan 2026 16:21:53 +0000Hi, Lately I'm having trouble packing a packed library (.lvlibp) in the VIP build. Attached here a sample project that has single VI in PPL which doesn't seem to pack (only 4kb .vip file) and doesn't seem to distribute the ppl. Is this expected behaviour that packed library doesn't pack in vip? Regards, Ajay ppl_vip_test.zipSun, 18 Jan 2026 09:44:52 +0000Sat, 29 Nov 2025 17:49:54 +0000Hi Ajay, Thanks for reporting. I will ask if possible to report at the Gitlab issues page as I don't watch the discussions here, as it seems vipm.io is not notifying us. https://gitlab.com/felipe_public/json-pretty-printer/-/issues I have an idea of the issue is (the code should ignore any {} in between double quotes), and I will take a look as soon as I can, although feel free to submit a fix through MR if you feel like. Be aware that this code has known issues with large json files (probably larger than yours, MB range), https://gitlab.com/felipe_public/json-pretty-printer/-/issues/6. In any other case, I will see if I can find some time on the upcoming weeks to take a look at this issue. Best regards,Sat, 08 Nov 2025 07:48:33 +0000Coming back to the abs function. The abs function of a complex value in LabVIEW as well as in ArrayFire returns a real vаlue or but not the complex value as in the G2CPU toolkit.Sun, 26 Oct 2025 14:10:16 +0000Performance of versions 1.4.2.3 and 1.6.0.15. For comparison, I provide the results of several performance tests of version v1.4.2.3. System info: Computer Intel Core i7-12700K with DDR5 4800MHz. Windows 10 Pro 22H2. LabVIEW 2022Q3. ArrayFire v3.9.0 (CUDA, 64-bit Windows, build b59a1ae53) Platform: CUDA Runtime 12.2, Driver: 12090 [0] NVIDIA GeForce RTX 3070, 8192 MB, CUDA Compute 8.6 Windows high-performance power plan is on. The GPU clock is set to 1740 MHz and the memory clock is set to 13600 MHz using the 'Always 3D Clock' settings in the ASUS GPU TweakII utility. The 100MB u8-array G2CPU speed test shows 17.2 for upload and 13.2 GB/s for preallocated download. Values are very close to the CUDA-Z utility performance results for pageable memory copy. For pinned memory the utility gives 22.6/24.1 GB/s. I was curious to note that the performance of sequential code increases by 20-30% when the G2CPU_MULTI_DEVICE parameter in the project settings is set to TRUE. It's even faster than the same code written in C. Moreover, I was very surprised by the additional G2GPU performance boost of up to 20% when enabling Hardware Accelerated GPU Scheduling (HAGS) in Windows settings. Overall, version 1.4.2.3 demonstrates very good computing speed. Typical code execution time jitter (milliseconds) versus loop iteration index in version 1.4.2.3 is shown in the following figure. But the same code running in version 1.6.0.15 produces a completely different result. The average execution time becomes significantly longer: The AFGarbageCollector or 2CPU_MULTI_DEVICE project settings don't matter.Sun, 26 Oct 2025 13:49:21 +0000Attached a larger JSON File that is does some errors in lines 1267, 1814, 1875, 2645, 3616 3622 Example screenshots below Incorrect Formatting Correct Formatting vi_metadata (incorrect prettying).json vi_metadata.jsonSun, 19 Oct 2025 16:08:17 +0000BUG: Just installed Flat controls + Design panel. CTRL+space opens the design panel. The LabVIEW quick-drop is visible for a fraction of a second before the design panel takes over and the quick-drop closes. Same on BD and FP. But Shift+Ctrl+Space does nothing. I have checked that I do not have Shift stuck or "sticky keys" active and I have checked on the on-screen keyboard that shift is not pressed. To make quick-drop work, I have to have the submit-message window opened (this one:) But when I then send feedback that way it tells med "there was a problem" in a dialog, but also "Submitting... Thank you for your feedback". A bit ambiguous. LabVIEW 24.3.4f4 No VM, English Windows. --- And then Submit is not working. Nothing happens. And in the lower right this is displayed and cannot be seen no matter how I resize the window: . But after logging in it disappeared.Fri, 17 Oct 2025 06:13:18 +0000VIPM 2026 Beta is coming soon! Here is a sneak preview of the Linux install process and the VIPM CLI installing on ubuntu.mp4Thu, 16 Oct 2025 12:41:12 +0000VIPM 2026 Beta is coming soon! Here is a sneak preview of the Linux install process installing on ubuntu.mp4Thu, 16 Oct 2025 12:39:43 +0000A Linux API (VIPM CLI) is fast approaching! Stay tuned.Tue, 07 Oct 2025 13:04:20 +0000Hi Mads, In the latest release of VIPM (25Q3f1) there is a preview feature with an enhanced search algorithm. Give that a go and see if that helps your usecase.Tue, 07 Oct 2025 13:01:46 +0000Hello twalter, We recently released VIPM2025Q3f1 that should resolve this issue. I'm sorry reinstalling VIPM took so long for you. Uninstalling / reinstalling VIPM (which I do reguallry as a VIPM developer) should be a straightforward process that takes 5 or 10 minutes, what was the process you went though? For reference, when downgrading, I uninstall VIPM though "Add or remove programs" in Windows, then choose my desired VIPM version here: https://www.vipm.io/desktop/versions/Tue, 07 Oct 2025 12:58:36 +0000Hi Tom, what version of VIPM did you download for Sonoma 14.4.1? Thanks,Mon, 29 Sep 2025 16:40:32 +0000Hi Jim, is VIPM 2022 for MacOS still downloadable? I don't see it anywhere @VIPM.io. Thanks,Mon, 29 Sep 2025 16:36:11 +0000Hei, I really like the tool and started using it a lot for teaching, but i feature me and my student were missing is a way to keep the inspector up after the application closes. Currently when all the actors have closed down the inspector window also closes forcing you to go through the menu to open it again next run. If it could just be up there until i choose to close it. I understand you are busy, so i do not really expect anything, but i thought it would not hurt to ask. Cheers JørgenFri, 26 Sep 2025 07:21:51 +0000I was curious about the primary use case for this library. The ergonomic improvements (separating Add and Update, for example) seem very niceWed, 24 Sep 2025 01:11:32 +0000Hello, dear developer In my usual projects, I usually don’t use a higher version as 2024, and at most 2020. Do I have any plans to support earlier versions?Tue, 23 Sep 2025 00:53:13 +0000I am finding that builds using 2025.3 are now installing files into the incorrect directory. Specifically a build installing a ProjectTemplate is installing without the correct parent directory. To resolve I went back to 2025.1 VIPM. The same project builds and installs correctly in that version. For debugging/reference I downloaded and installed 2025.3 from NIPM. (Which as a seperate note, I won't do again as the install took 5 hours to complete yesterday).Mon, 22 Sep 2025 20:06:51 +0000As I'm gearing up for a new release, I thought I'd close the loop on this: At its core, Nominal IO is a data platform for managing and analyzing large test data sets. I (as a JKI software dev) have been working with Nominal to create a LabVIEW interface for their platform. That explains why you're seeing my name on the package, JKI partnered with Nominal to develop the LabVIEW toolkit. Although related, STAR-GOAT is a separate software product from JKI currently being used by aerospace companies for acceptance testing. I'm not on the STAR-GOAT dev team, but streaming data from STAR-GOAT to the Nominal platform would be a good fit.Thu, 18 Sep 2025 13:49:14 +0000Hi Alexander, Thank you for reporting this. I've reported this as a bug on our issue tracker.Thu, 18 Sep 2025 10:05:56 +0000I have found a bug with how the "Set Cluster Element" VI handles DAQmx tasks. These tasks can be put into a cluster, the cluster turned into a variant, and the variant back to a cluster, and it maintains the task. However, if I use the Set Cluster Elements VI, the DAQmx task is not preserved after the block. I have attached a photo showing a before and after state of the DAQ task and you can see once it comes out of the OpenG block the task is now empty.Fri, 22 Aug 2025 23:57:17 +0000