Suggestion

[Daniel M]

Not sure if this should go under the wish list section:

 

Don't allow spawn if pad is occupied

[Nate--IRL--]

That's not a suggestion - its a bug report. :)

 

Nate

[159th_Viper]

Does that not depend on whether you landed at a spawn point other than where you spawned into the SIM? In other words, take note of your allocated spawn area and return thereto for rearming/refuelling - that way you will not be imploded prematurely :P

 

To prevent a spawn if you are occupying another's spawn-point could effectively halve the number of clients on the server.

[Grimes]

or just spawn on the next available pad.... or allow multiple pads to be linked to a single "atc command" and just spawn wherever is available. What I am saying is its a stupid limitation. Especially if you want to have 2+ groups of AI helicopters be spawned at a farp and use the "uncontrolled" feature at the same time. It simply doesn't work, the first group must take off in order for other flights to be allowed to spawn.

[Daniel M]

Does that not depend on whether you landed at a spawn point other than where you spawned into the SIM? In other words, take note of your allocated spawn area and return thereto for rearming/refuelling - that way you will not be imploded prematurely :P

 

To prevent a spawn if you are occupying another's spawn-point could effectively halve the number of clients on the server.

 

The problem occurs when someone else lands on your/ the pad(though i'm guilty of it as well). Plus sometimes a farp is 30 minutes closer than your original spawn point. Maybe have atc say "you're not allowed to land" :D

 

How would this work in RL? Would ATC say land on pad x? Granted RL you don't have magically spawning helicopters

 

It's more the no message warning of impending doom that would be nice to say "you can spawn here, but you may blow up"

 

 

A tiny detail that hopefully will eventually get updated/cleaned up more than anything

 

 

or just spawn on the next available pad.... or allow multiple pads to be linked to a single "atc command" and just spawn wherever is available.

 

Maybe something like "flight 1-1 through 1-4 is assigned farp 1" and at moment of spawn pick an unoccupied pad.

That's not a suggestion - its a bug report. :)

 

Nate

 

It's "working as designed", doesn't that make it a "feature" :D

Edited April 15, 2012 by Daniel M
clarify your/the

[Nate--IRL--]

It's "working as designed", doesn't that make it a "feature" :D

 

Ehh yes <cough><cough> that is what I meant to say. :)

 

Nate

[Auroraw]

meh...

[JG14_Smil]

It's not a bug when people don't note where they took off from. No one to blame but yourself for this one...

[sobek]

In his defense , you don't start every mission from the pad.

[Daniel M]

It's not a bug when people don't note where they took off from. No one to blame but yourself for this one...

 

I wouldn't mind and would take the blame if it was my fault, the problem comes when someone else lands on "your" pad. You click "fly" and get an instant team kill, and in a couple of instances I got kicked from servers for "to many tk's". It's not a deal breaker, just frustrating; something that I think would be nice to clean up.

 

Unless I"m missing something? Is there a way to check if the pad is unoccupied before spawn?

Edited April 17, 2012 by Daniel M