Skip to content
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

Only one plane can land in the Airforce center... #87

Open
yaaaaa opened this issue Jan 23, 2016 · 6 comments
Open

Only one plane can land in the Airforce center... #87

yaaaaa opened this issue Jan 23, 2016 · 6 comments

Comments

@yaaaaa
Copy link

yaaaaa commented Jan 23, 2016

In Original RA2 game was 4 planes on 1 Airforce center.

image

@abcdefg30 abcdefg30 added the Bug label Jan 23, 2016
@Mailaender Mailaender changed the title Only one plane can landing in the Airforce center... Only one plane can landing in the Airforce center... [$5] Feb 19, 2016
@Mailaender Mailaender changed the title Only one plane can landing in the Airforce center... [$5] Only one plane can landing in the Airforce center... Feb 21, 2016
@Mailaender Mailaender removed the Bounty label Feb 21, 2016
@Mailaender Mailaender changed the title Only one plane can landing in the Airforce center... Only one plane can landing in the Airforce center... [$5] Feb 21, 2016
@ghost
Copy link

ghost commented Mar 28, 2016

This is far from the only issue with harriers, but I think that we would be best served by a proper notion of docking.

@Mailaender Mailaender changed the title Only one plane can landing in the Airforce center... [$5] Only one plane can land in the Airforce center... [$5] May 16, 2016
Mailaender pushed a commit that referenced this issue May 19, 2016
Decoupled fences and sandbags into a new CrushClass
@Grantelbart4 Grantelbart4 mentioned this issue Jun 4, 2016
21 tasks
@Mailaender Mailaender changed the title Only one plane can land in the Airforce center... [$5] Only one plane can land in the Airforce center... Nov 10, 2016
@Mailaender Mailaender removed the Bounty label Nov 10, 2016
@pchote
Copy link
Member

pchote commented Jun 17, 2020

I suggest adopting the solution from RV ASAP so that @MustaphaTR can claim the bounty and prevent BountySource from taking it for themselves.

If no Solution is accepted within two years after a Bounty is posted, then the Bounty will be withdrawn and the amount posted for the Bounty will be retained by Bountysource. For Bounties posted before June 30, 2018, the Backer may redeploy their Bounty to a new Issue by contacting support@bountysource.com before July 1, 2020. If the Backer does not redeploy their Bounty by the deadline, the Bounty will be withdrawn and the amount posted for the Bounty will be retained by Bountysource.

@Mailaender
Copy link
Member

I probably would have already, but I am not sure if a hack with a disabled Mobile would be accepted here.

@MustaphaTR
Copy link
Member

I'm not sure how much that is necessary. I first noticed that dummies were moving around, but wasn't sure why. But i later noticed it was because i removed the passability check from the "Minefield" logic and it was spawning another set of dummies. I fixed that by revering it and making that bits of Airfield passable but didn't remove the don't move hack. I'm not sure if something else can trigger them to move. But tbh the proper fix would be to remove respawning logic and passability checks from "minefield" logic. Then the dummies can probably be a building instead, which can' t move anyway.

@Mailaender
Copy link
Member

When I experimented with it, the mobile was required so it could spawn onto the existing building.

@Mailaender
Copy link
Member

Wait, you are right. The mobile hack is indeed not required.

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

Successfully merging a pull request may close this issue.

6 participants
@pchote @Mailaender @abcdefg30 @MustaphaTR @yaaaaa and others