Hi,

I seem to recall this problem. Openstreetmap changed their url or something and Magix fixed it with a patch in version 2013. Make sure that you update to the latest patch.

Good luck.

Thanks John,

I did download the latest patch when I Installed Video Pro - do you think an uninstall/reinstall will make any difference?

Richard

Hi Richard,

You mentioned Video Pro. Did you mean Movie Edit Pro or Video Pro? They are 2 different Magix products.

If Video Pro, which version? I just checked X6 and there is no problem with the Travel route.

I don't have MEP 2013 operational anymore. Perhaps Terry could check.

Richard, John,

I started MEP 2013 and get the same problem with the Travel Route Wizard. Same in MEP MX.

Worse, the same occurs in MEP 2014 too, my current version. And I suspect in MEP 2015?

Haven't used this important feature for some months, so pleased you spotted it, Richard.

Seems an obvious bug to me, so I'll email Magix Support.

Hi Terry,

My 2014 version 13.0.5.4 is working now. Just tried Travel Route Animation in 2014 and it works well, as it does in 2015. Just checked it too.

So it must be something else causing the problem.

Hi John,

It is Magix Movie Edit Pro 3013 Plus ver 12.0.4.2 (UDC).

Regards,

Richard

Hi John,

It is Magix Movie Edit Pro 3013 Plus ver 12.0.4.2 (UDC).

Regards,

Richard

I doubt it Richard. As in your initial post, you're still a millennium ahead of the rest of us! 

Hi Terry,

My 2014 version 13.0.5.4 is working now. Just tried Travel Route Animation in 2014 and it works well, as it does in 2015. Just checked it too.

So it must be something else causing the problem.

Thanks for checking John. I reckon it's a Java problem of some sort. I thought maybe it was connected with the warning I had (when I updated to the latest Java version yesterday) that it didnt fully support XP. But I assume Richard has Win 7 or later, so that's now an unlikely explanation.

I vaguely recall that previous MEP upgrades, from 16 onwards, have all triggered issues with the wizard?

Whatever it is I'd like to get it fixed asap, as I anticipated using it soon myself.

Hi

Just to confirm - the Travel Route Animation wizard works OK in MEP MX, 2013, 2014 and 2015.

Earlier versions of MEP do not work - IIRC there was a change in the Geomodule from version 17 to MX.

@RichYard

Assuming you are running at least Windows 7 64 bit then make sure you install the latest versions of both the 32 bit and 64 bit versions of Java and also check the security settings in Control panel, Java.

Also check that your Internet Explorer is up to date ie at least version  9, preferably 10.

@ Terry

. . . . I reckon it's a Java problem of some sort. I thought maybe it was connected with the warning I had (when I updated to the latest Java version yesterday) that it didnt fully support XP. . . . .

The message you are getiing is because there are some 'functions' in Java which are not backwards compatible to XP.

John

@ John EB

Thanks John. So it's just Richard, and me with the problem so far! Any thoughts on that obscure message?

Hi Terry

Which obscure message, yours or Richards?

For Richards paras 3 and 4 of my previous post.

For yours para 6 of my previous post.

John

Hi John,

So it looks like two separate problems.

This was the error I got:

High res: https://dl.dropboxusercontent.com/u/4019461/MEP2013-TravelRouteWizard-Bug.jpg

So you're saying that's unrelated to Richard's? Except for both being script errors when running the Travel Route wizard. Anyway, I was hasty in assuming it looked like an MEP bug.

But I'm still anxious to fix my problem. So, with apologies to Richard who no doubt is still keen to fix his own, I'll continue my discussion with you in this thread too. And maybe a fix for mine might even lead to a fix for Richard's.

To start with, can you confirm that this is a javascript issue, nothing to do with Java after all? I frequently confuse them, and I think I've already done so here! But in your reply are you too implying it is a Java problem, as I thought but now do not?

BTW, the two don't seem entirely unrelated:

High res: https://dl.dropboxusercontent.com/u/4019461/Java-Updated7Feb2015-PossiblyPoorDecision-4.jpg

Hi

@Terry

Yes there could be two seperate problems. 

The error messages indicate that your version of the Javascript engine is failing to start running the javascript, whereas Richards is running but failing at line 7.

The reason I advised updating the Java is because I have come across issues like this being fixed by updating.

Java and Javascript are two distinctly seperate 'programming languages' and are not related to each except for almost identical programming language syntax. 

However it is possible that there is a Javascript call to a Java method in Travel Route Animation.

HTH

John

Hi

@Terry

Yes there could be two seperate problems. 

The error messages indicate that your version of the Javascript engine is failing to start running the javascript, whereas Richards is running but failing at line 7.

The reason I advised updating the Java is because I have come across issues like this being fixed by updating.

Java and Javascript are two distinctly seperate 'programming languages' and are not related to each except for almost identical programming language syntax. 

However it is possible that there is a Javascript call to a Java method in Travel Route Animation.

HTH

John

 

 

Thanks John and everyone else who has tried to assist me

 - I discovered that my Windows 7 auto update utility had a problem and after fixing that eventually and installing about 168 Windows Updates, Travel Route Animation worked perfectly!

Regards,

Richard

To close off the thread, here's the very latest status on my issue, which has now survived testing over the last hour or two.

It now looks as if Firefox is indeed irrelevant, as should be logically expected. Whether JavaScript is ON or OFF in Firefox, but ON in Internet Explorer, this is what happens:

1. Start MEP 2014 and run the TRA
2. TRA gives that scripting error
3. Close error messages and TRA, then run TRA again
4. TRA now works. And does so consistently from that time on in that MEP session.

You can see how confusing that is, given that my initial natural reaction after step 2 was to change something!

So I now simply repeat the attempt to run TRA afresh after the initial error.