Skip to main content

Constantly have to reapply the correct altitude when inserting stops

Guys, I am losing my mind…every time I insert a new point in between a location it does two things.

  • Resets the timeline lengths

  • The newly added are zooms into a ridiculous 3 km off the ground.

If I have a 12 spot locations with a point either side to slow down the entry and exit this means another 5 minutes of putting the correct values in again…just to move forward. Then …if i need an other the whole process has to be done again.

I’m working on 18 videos for a client and trying to sync voiceovers as well. I have to say that at this stage I am so frustrated with the app…once this job is finished I will never make one again for a client.

(So far this project has blown out so far I am losing money and time delivering it.)

Thanks

Craig

Status: Completed6 comments

Log in to comment and vote

Comments6

  • Tobias Cichon

    Team•

    Jan 9

    This has now been fixed and the calculation of the elevation chart kicks in every time the route or the duration of the video changes.

  • Craig Wells

    •

    Jan 5

    Thanks, I have just gone back in for the first time and the very first 5 credit export failed to load the first symbol ….ARGH!!!!!!. You can see Perth there an no pin.

    • Tobias Cichon

      Team•

      Jan 9

      Hi Craig,

      Yes, it looks like the symbol does exist, but for some reason it ended up positioned at latitude/longitude 0,0 in the Atlantic Ocean. I suspect the script responsible for migrating maps from v2 to v3 has an issue here. Thanks for reporting this.

      I’ve just reimbursed 5 credits to your account for the lost render.

  • Tobias Cichon

    Team•

    Dec 3, 2025

    Hi Craig,

    Thank you for taking the time to share this — I hear your frustration and everything you mentioned is completely valid. The issues with altitude resetting, zoom levels, and timeline lengths shouldn’t be slowing you down like this, especially on a project of your scale.

    I want you to know that I’ve been working on a completely new version of AvoMap for the past couple of months that directly addresses these problems. It’s a major upgrade to how segments, stops, and camera logic are handled, and it should remove exactly the kind of repetitive work you’re running into now.

    I just need a little more time to finish it properly, but I’m on track to release the new version before Christmas.

    Thank you for your patience — and truly, thank you for sticking with it while working on such a big client project.

    Best, Tobias

    • Craig Wells

      •

      Dec 4, 2025

      Thanks for your response, I appreciate it. On another note, I just exported a 4k video and in the timeline the final pin was correct, on the export it was not…costing me another round of 4k credit.

      • Tobias Cichon

        Team•

        Dec 4, 2025

        Craig, I’ve just reimbursed you for the credits lost during the export — and added a bit extra for the inconvenience.

        A new version of AvoMap is coming out soon, addressing all the issues you mentioned. Hang tight!