Navigation and Weather Routing software

AppStore PlayStore

Contact us for support or information: contact@meltemus.com

iPad bugs?

  • Farrcical
  • Topic Author
  • Offline
  • New Member
  • New Member
More
2 months 4 days ago #2600 by Farrcical
iPad bugs? was created by Farrcical
HiI am a very new user of this product. I specifically want to use qtVLM on my iPad. I have successfully managed to create some POI's ( waypoints) and I appear to have added said waypoints into a route. I add the POI’s in sequence rather than alphabetically to construct the race course. 

The 1st thing I observe is that even though I add all the marks in order sometimes marks are missed or skipped. For example in the picture below I added Languard after Cliff Foot and before Outer Ridge but the path plotted seems to have skipped Landguard.

The 2nd thing ( in the same picture ) is that I add Cork Sand after Outer Ridge and the system seems to have added a strange leg and not made it to Cork Sand. Finally whenever I click on Route Legend to view the entire route the app crashes and the route is lost.

Regards

Paul
https://share.icloud.com/photos/00e1OJQXZz6J6zh6wTQIWyWHg
 

 
  • Please Log in or Create an account to join the conversation.

    More
    2 months 4 days ago #2601 by maitai
    Replied by maitai on topic iPad bugs?
    Hi,
    First of all the crash is absolutely abnormal. More info is needed, to start with what do you call "Route Legend" that wording does not exist in qtVlm.

    Then a route is a complex object that calculates ETA between points and the best way to reach a POI. On you screenshot we see that several points have the same ETA, meaning either that the distance between points is ridiculously small or that your polar is for a really fast boat. Which polar are you using ?
    qtVlm uses a internal step of 5 minutes (unless you changed that, did you ?), and therefore a route can never reach exactly a POI, it is either before or after it. I don't want to enter to much in the details, but a POI will be considered reached if within the last 5 minutes distance (it is more complicated than that).

    The main question is: can you post your polar and show boat->boat's settings polar and engine/tack tabs ?
    Best
    Philippe

    Please Log in or Create an account to join the conversation.

    • Farrcical
    • Topic Author
    • Offline
    • New Member
    • New Member
    More
    2 months 3 days ago #2602 by Farrcical
    Replied by Farrcical on topic iPad bugs?
    Thanks for coming back to me so quickly

    Please find attached my polar
     

    File Attachment:

    File Name: FX2.txt
    File Size:3 KB


    I do not seem to be able to see the polar, or any polar, even the ones included in the polar directory. I just get a big red square, its the same on the iPhone.

     

    The app crashes whenever I select the "Route Logbook"

    Attached are the screenshots you requested. I have not changed much. 


     
    Regards

    Paul


     
  • Please Log in or Create an account to join the conversation.

    More
    2 months 2 days ago #2603 by maitai
    Replied by maitai on topic iPad bugs?
    Hello,
    Tested here with your polar on iPhone and iPad, no issue at all.
    What qtVlm version are you running ? (Help->About qtVlm)

    Please Log in or Create an account to join the conversation.

    • Farrcical
    • Topic Author
    • Offline
    • New Member
    • New Member
    More
    2 months 2 days ago #2604 by Farrcical
    Replied by Farrcical on topic iPad bugs?
    5.12.904 build 2 (Jul 3 2024)
    IOS 17.5
    Qt 5.15.16
    Memory size: 15,680 Gb
    CPUs: 8

    Please Log in or Create an account to join the conversation.

    More
    2 months 2 days ago #2605 by maitai
    Replied by maitai on topic iPad bugs?
    That is OK
    I have no idea of what is happening to you, to be honest.
    If possible (meaning you don't have any paid products like VMH charts, S63s or Meltemus charts packs), I would suggest to uninstall/reinstall and start from scratch.

    Please Log in or Create an account to join the conversation.

    Time to create page: 0.171 seconds