-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unit ignores terrain geometry #150
Comments
The tilesets are automatically imported so my best guess is that the original engine was a bit stricter and didn't count that as a pathable gap so the mapper was never punished for sloppiness. |
Okay. Thank you for quick responding. I just tested this with other vehicles as well. Happened with them, too. Exactly same terrain spot. I used spawn "H" (middle left) as my starting point. |
No, this isn't a map bug. Apparently all such RA2 bottom cliffs are affected. I'm still figuring out why though, but this have happened with all my terrains I could've import in to OpenRA. |
Actually I saw this one also in TS |
This specific situation does look like a map bug. The tile that the chronominer drives over is a regular clear tile, and not part of the cliff. |
We don't ship that map so closing here. You can try investigating this further with the "Show Custom Terrain" debug command we recently added here. |
Fixed by #540. |
Don't ask me how's this possible but this happened to me on a map named as "tn03t8". Multiple times. The map is one of the original RA2 maps just converted to oramap format.
Is this a
The text was updated successfully, but these errors were encountered: