RE: J-Field 3.0.11.816
Background
Project was originally run with the wrong geoid (EMG2008, my rusty inattentive bad) on Triumph-LS Plus (00881), archived, and shared - Many thanks to Linda Campbell for her help! Later, the archived project from 00881 was unpacked on another friend's Triumph-LS (00833) - Many thanks to Sage Collins for the loan of his Javad gear! The correct geoid (Geoid18B) was selected, and for good measured, I went ahead and re-DPOSed the project without issue.
This morning I noticed that the Batch Export halted with the GVX option checked, but did not have any problem exporting all other formats when GVX was unchecked. The issue is reportedly linked with a missing base, though its name is not clear, and for this project, there was only one base (Triumph-1M). Once the message about being unable to create a valid GVX and OK is tapped, the batch export halts, returning to Homescreen1. The workaround allowing for the batch export to complete without issue is to uncheck the GVX option.
Background
Project was originally run with the wrong geoid (EMG2008, my rusty inattentive bad) on Triumph-LS Plus (00881), archived, and shared - Many thanks to Linda Campbell for her help! Later, the archived project from 00881 was unpacked on another friend's Triumph-LS (00833) - Many thanks to Sage Collins for the loan of his Javad gear! The correct geoid (Geoid18B) was selected, and for good measured, I went ahead and re-DPOSed the project without issue.
This morning I noticed that the Batch Export halted with the GVX option checked, but did not have any problem exporting all other formats when GVX was unchecked. The issue is reportedly linked with a missing base, though its name is not clear, and for this project, there was only one base (Triumph-1M). Once the message about being unable to create a valid GVX and OK is tapped, the batch export halts, returning to Homescreen1. The workaround allowing for the batch export to complete without issue is to uncheck the GVX option.