4.13.2 de-bugging

[Nil]

Here is a little bug I spotted, normaly easy to fix
when we open the canopy,
We can hear the wind.
When we close it, we could not hear the wing anymore.
This is the normal behavior

The problem is that when we go to a gunner posision (like in the d3a or b5n) we hear the wind (normal), but, when we come back to the pilot position, we can still hear the wind even if the canopy is closed.
to stop the noise of the wind, we have to open and close the canopy.

[Janosch]

On occasion, a particularly funny thing can happen on online servers. What follows is a combination of theory and observations: apparently player aircraft that should be removed (e.g. after landing & hitting refly) can somehow leave an unoccupied static plane behind (!). It's not just a graphic bug, these ghost planes, although rare, are very real and solid.

I landed a MC200 on an airfield, hit refly, and flew a 109 sortie instead. I took off using a taxiway, so I didn't notice the MC200 then...
As I landed, I did see an unoccupied (no friend icon) MC200 in the middle of the runway, but I thought it was a non-corporeal ghost. I had seen them before, probably "left behind" by other players. But, this one took my wing off - I tried to dodge just to be safe, but there wasn't enough room. On the resulting .ntrk film, the plane is nowhere to be seen, but my wing comes off - my 109 collides with an invisible object! Eventlog.lst says that I collided with something called 54_Static.
Also, on the airfield that this happened, MC200 can't be spawned as far as I know - they're on another airfield.

I hope it got removed for good after I disconnected. Ghosts, I tell you!

[Baddington_VA]

On occasion, a particularly funny thing can happen on online servers. What follows is a combination of theory and observations: apparently player aircraft that should be removed (e.g. after landing & hitting refly) can somehow leave an unoccupied static plane behind (!). It's not just a graphic bug, these ghost planes, although rare, are very real and solid.

It does happen when the online mission allows spawning from static aircraft.
If you land at a field that is not the one you took off from, a static plane remains where you landed.
It's good practice to get off the runway before hitting refly.

It also happens that if you take for example an A20 from airfield A
And land at airfield B which also happens to spawn A20s, a static plane will be left where you finished. But then you can spawn at airfield B in an A20, and
it will spawn you where your previously flown A20 was standing as a static aircraft.

It's not so much a bug as a useful tool
All these static aircraft disappear once the mission ends.

[Pursuivant]

Originally Posted by Baddington_VA

It's not so much a bug as a useful tool

Could someone else at Airfield B then spawn using a plane that a previous player left behind? (Assuming you can spawn that sort of plane at Airfield B)

If so, what's the fuel, ammo and damage state of that aircraft? If the new player gets an undamaged, fully fueled and armed airplane, this seems like a "backdoor" method of instant Rearm, Refuel, Repair.

In any case, it seems like there should be an option for server admins to "despawn player aircraft after landing". That is, making player-controlled aircraft vanish some number of seconds after they land and the engine is turned off. That would get rid of the "collisions with static planes" bug/feature.

[Music]

I don't know if this is a 4.13 thing, a server thing, or my connection, but yesterday I spawned beside myself


I have had a wretchedly bad connection this month for some reason, , So bad that I have been unable to play, ,so that may be the cause?, but I have never seen that happen before.

(Sorry SVK, congrats =irss=drawer65)

Janosch said "apparently player aircraft that should be removed (e.g. after landing & hitting refly) can somehow leave an unoccupied static plane behind (!). It's not just a graphic bug, these ghost planes, although rare, are very real and solid".

We noticed that on the SkiesofFire server, and found if when landed, the player puts chocks on, it solves the problem, or seems to.

**edited to add Janosch's quote and observation/solution**