[FIXED] [BUG v2.03] Cannot move the seedlings to neighbor asteroids

[Harsha]

The v2.03 update fixed many bugs and also provided many new features, but also a new bug which i found while playing DMM 11.

1. As per the image "Not Possible 1" you can see that i cannot move the seedling from (a) to (b) even though the below asteroid is under my boundary. [see the green arrow mark in (a)]

2. Image "Not Possible 2" reports the same problem but with an different asteroid. [(c) to (d) not possbile]

3. In image "Possible" - It is possible to move the seedlings from (e) to (d). But i was possible to move from the asteroid (c) to (d) after (d) was discovered.

4. BUT - i was NOT able to move the seedling from (a) to (b) even after (b) was discovered. Whenever i wanted to move the seedling from - say from (e) - to (a) the seedlings would move through (f) or (g), that is, taking the longer route.

----------------------------------------------------------------------------------------------

On other note:

There was problem with the asteroid (a) in DMM sometimes when playing in v2.02. It was that the boundary of (a) was so small that it was not possible to move the seedling from it to any of the other asteroids, but only to (a).

[TorchFire]

I had the same experience as conditions 1 and 2.  Roid b is in range but inaccessible.  It is also not included in pathfinding routes.  I attempted to send a flower to b, which worked in similar situations, but was not successful.  When sending flowers, mines, or nearby seeds was attempted the sound and animation indicated success, but nothing was actually sent.

[Alex]

Thanks guys, will look into it.

[Cuisi]

Hi, new here.  Just made an account to get info about this same bug.  Is there any way to roll back to v2.02?

[dj-anon]

Hi, I would like to say that the patch for this bug should be released immediately after being fixed since it actually breaks the game as levels can't be finished most of the time, at least in my case, because the complete map can't be explored due to this glitch.

This being my first post, I would also like to say: thanks for making a great game.

[Bonobo]

I guess it should be possible to install anew and apply the 2.0.2 patch if you've saved it. I for one have deleted it after loading the 2.0.3 patch

[Cuisi]

I reinstalled the 2.02 patch (over the 2.03 version) and it fixed it.

[Alex]

I've uploaded the 2.0 - 2.02 patch:
http://www.dyson-game.com/files/patch%202.0%20-%202.02.zip

[Alex]

New patch should come today.

[Bonobo]

Thanks, Alex, just downloaded the "retro" patch to 2.0.2.

And the new patch is anticipated ... I'm sitting in a puddle of saliva

[Alex]

OK guys, try patching up to 2.04 and see if this helps:

http://www.dyson-game.com/files/PatchEufloria.exe

[dj-anon]

OK guys, try patching up to 2.04 and see if this helps:

http://www.dyson-game.com/files/PatchEufloria.exe

It seems the problem has been fixed, I'd like to test the patch a bit more to be 100% sure. Thanks a lot.

[Harsha]

It seems the problem has been fixed, I'd like to test the patch a bit more to be 100% sure. Thanks a lot.

Ditto 

[Grizzly]

I still have the same problem in 'Dark Matter mode' level 14.

Case A1 - works
Case A2 - doesn't work
Case B1 - works
Case B2 - doesn't work

[Alex]

Drat. And you're definitely on v2.04?

[Grizzly]

I'm 100% 2.04!

[Grizzly]

I played it through now.
No further problem. So it's only level 14.

[Alex]

OK. I had a look over the weekend and couldn't reproduce any problems on level 14. I'll keep looking.