Skip to content
This repository has been archived by the owner on Jun 28, 2022. It is now read-only.

As of Simulator v1.1 the drone spawns inside a building and collides on most activity #392

Open
arush opened this issue Mar 24, 2020 · 10 comments

Comments

@arush
Copy link

arush commented Mar 24, 2020

Issue Template

  • Use tags in an effort to as specific as possible.
  • If the issue is related to the simulator it's helpful to include log files described here. The Player log is likely the most relevant.

image

I posted this in the Q&A but received an unsatisfactory answer. Another student has posted the same question. It seems we are being overlooked now so am seeking help here.

How do we change the spawn location so it is not inside a building?

Thanks

@arush arush changed the title As of v1.1 the drone spawns inside a building and collides on most every activity As of Simulator v1.1 the drone spawns inside a building and collides on most every activity Mar 24, 2020
@arush arush changed the title As of Simulator v1.1 the drone spawns inside a building and collides on most every activity As of Simulator v1.1 the drone spawns inside a building and collides on most activity Mar 26, 2020
@pomiradek
Copy link

I have the same problem, is there any update ahead from @udacity?

@sunsided
Copy link

sunsided commented Apr 29, 2020

Sadly I ended up in udacity/FCND-Simulator-Releases#11 (comment) first, so I'm going to cross-post.

I'm able to consistently toggle between two broken states by using SHIFT-R, and it also happens on 0.1.0 of the simulator.

One of them is empty:

Screenshot from 2020-04-29 07-40-41

The other one has that long building right on top of the starting position. Attempting to start the drone will immediately make it collide with the environment, breaking everything.

Screenshot from 2020-04-29 07-40-17

I mean, there is some beauty to it, it's just not particularly helpful.

video

Here's what happens after starting motion_planning.py as described in the project description:

video2

@midnight-dev
Copy link

@arush , @sunsided , @pomiradek I just happened to come upon this thread while browsing something completely unrelated. I don't have a fix, unfortunately, but it's clear that @udacity isn't planning to address any issue, be it new or old. There's not much that can be done short of asking around if anyone could contribute a fix or suggest a workaround.

I'm a bit disappointed that the code is not available to be browsed on GitHub, but perhaps the source is available through releases. If so, someone could put up a fork if they feel like maintaining this.

Seems the last maintainer was @domluna who is still very active. Might be worth a ping. Otherwise, the project may remain abandoned. At the very least, they would know who to contact regarding maintenance.

Best of luck to you all. Cheers o/

@wi1k1n
Copy link

wi1k1n commented Jul 4, 2020

I have the same issue. Windows 10. Simulator v0.1.1 from Mar 18, 2018.

@onoelle
Copy link

onoelle commented Aug 22, 2020

Same issue here as of Aug 2020 - still no update on this issue?

@Hesham-HA
Copy link

Hesham-HA commented Sep 18, 2020

Been dealing with the same issue, so here is what I got..
I navigated through different releases of this simulator so as to find one without any problems, and this one v0.1.0 gives not very satisfying result, but at least helps to keep you working on project properly..
The thing is that the drone will fly passing through the building as if it isn't there and continue its path (no flips)

ezgif com-video-to-gif (5)

Still though it won't land on ground but on the building, but you can change the goal position anyway and land anywhere else!

@vitalii-bulyzhyn
Copy link

Any updates on this issue?

@cptanalatriste
Copy link

cptanalatriste commented Apr 26, 2022

Facing the same issue, on Ubuntu 20 (64 bits). No updates from @udacity?

@romanmandryk
Copy link

same issue on macOS 12.1

@JeffRubin
Copy link

Hesham-H98's comment is quite helpful. It's a good workaround. Note that Hesham-H98's comment refers to a version of Motion Planning, it's not the Simulator; the simulator seems to have come after Motion Planning and incorporated Motion Planning along with other tools, e.g. Backyard Flyer into one application.

An alternative workaround to Hesham-H98's approach is, with obstacles present, manually drive the vehicle through the mysterious building (and collide with it) and then manually move the vehicle to another location on the map where there is no obstacle. Then run the path planning algorithms from there. This has the added benefit of proving that the path planning algorithms can work from anywhere on the map, not just from the initial spawn point. It's a messy workaround but it is pretty straightforward.

Much of this discussion was also captured in my question to the mentors (where they pointed me here): https://knowledge.udacity.com/questions/846330

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests