Not a bug report

Oops, a senior moment between machines.
Of course, the upgrade overwrites them, here are the new ones.

Your old 2.7 config has a MinFerror of 0.25 for A
The new 2.8 config has a MinFerror of 0.10 for A

If you change the value, you will have the same behavior in both configs!

Norbert

Thanks but actually it made no difference whatsoever that was only where I had previously been changing due to reading false information about the error.
The behavior remains the same regardless of those values but from the little research I had done the advice was to change them.

upgreating to 2.8 is not recomended is this a real Gantry so a need for double axis homing
why dident you stay with 2.7.14

I just tested 1_wrap on my setup and it runs fine, however I get a following error with 1.ngc (on both 2.8 and 2.7)

Since this behavior is very setup dependent, can you _please_ plot the following
error on your configuration so developers have something to work with...

EDIT
Here are a couple example plots:

freeby.mesanet.com/28ferror.png
freeby.mesanet.com/28ferrorb.png

The acceleration limit on my machine is 200 (the acceleration reaches almost 1000)

I have stayed with 2.7.14 and it works well, in fact, flawless as previously stated.
I am not daft enough to fix something that isn't broke but it seems that's exactly what has happened with the upgrade.
Whether recommended or not, if the new versions are not tested thoroughly we would have a substandard system which the current version is not but the upgrade will be if released too soon.
I have no intentions of fault finding or effecting fixes, that's for the developers to do but I can assist by pointing out any issues I may have and supply the goods for them to replicate my issue.
The issue was not present in all previous versions of that mentioned above but remains in the current version.