Spawn in for Multiplayer

[Skycarl]

I built several dogfight missions so far. It seems at certain bases with hangers,
that the first plane in will explode inside the hanger when spawning in.
This is without any AI aircraft on the field.
The second and planes after seem to spawn in okay.
And, sometimes the first plane will come in okay. Mostly not though.
I haven't seen this problem spawning into bases with no hangers as they spawn
on the field okay.

I have not tried this with the single missions yet. Any ideas on what is going on
with this? Could be a glitch that has yet to be ironed out.
Any feedback would be most appreciated.
Thanks.

Sky

[Ataros]

Please report airfield names and screenshots of hangars in both bugreports threads if you want it fixed.
1) http://forum.1cpublishing.eu/showthread.php?t=19629&page=43
2) http://forum.1cpublishing.eu/showthread.php?t=21096&page=20

You can overwrite default spawn places by placing a new airfield object on top of the old one and adding new airfield points. Set a key in game Controls Options Menu - Builder category to place Branches of airfield points as discussed here http://forum.1cpublishing.eu/showthread.php?t=23129

[Skycarl]

Ataros,
Thank you so much. I will try what you are suggesting and if it continues, I will
take the screenshots and report in the threads.
The fast help is much appreciated.

Sky

[SNAFU]

Does anyone have a list of airfield for which the spawnpoints do actually work?

I used the prebuilt spawnpoints and after about the 4th or 6th spawing plane, they loose track of the spawnpoints and just spawn anywhere in the area.

This also happens when I use my own spawnpoints with a customized runway and spawnpoints.

Generally the customzid runway spawnpoints do not seem to work on prebuilt runways. I tried to minimize the custom runways and put them over the prebuilt ones, minimized the radii and put a spawnarea directly on the customized runway, doesn´t help.

I tried "Guines" and "Theville", both spawn somewhere after the 4th or 6th plane, only "Carquebut" seems to work, so I deleted the spawnpoints.

[Airdromes]
airdrome0 43246.94 70691.76 2 500 1000 0
airdrome1 283906.92 204953.32 2 500 700 0
[airdrome0_Runways]
43246.36 70698.49 365.00 20.00 5.00 0
[airdrome0_Points]
44380.24 70364.31 116 108 99 88 77 65 53 40 26 12 7 1
44437.34 70400.23 2
44386.92 70542.67 3
44371.87 70656.59 4
44358.53 70833.80 5
44457.05 70831.74 6
44455.34 70905.30
44440.15 70403.58 8
44386.24 70543.70 9
44373.58 70655.90 10
44477.24 70652.83 11
44474.94 70732.80
44441.36 70402.82 13
44384.72 70542.84 14
44369.95 70654.77 15
44358.05 70833.85 16
44352.33 71025.32 17
44341.38 71049.14 18
44319.94 71062.95 19
44273.74 71069.14 20
44192.30 71076.76 21
44159.91 71090.10 22
44079.89 71178.69 23
43941.29 71164.40 24
43707.90 71174.41 25
43680.30 71229.12
44440.41 70399.97 27
44385.37 70541.45 28
44369.08 70653.54 29
44356.63 70832.69 30
44352.26 71022.95 31
44339.88 71050.10 32
44318.44 71065.34 33
44189.37 71076.29 34
44157.45 71090.58 35
44080.29 71178.70 36
43940.74 71164.41 37
43814.52 71170.60 38
43708.78 71175.36 39
43748.29 71226.88
44440.21 70401.41 41
44386.56 70542.07 42
44371.37 70655.53 43
44358.20 70833.91 44
44351.34 71025.87 45
44341.39 71051.41 46
44319.08 71064.05 47
44189.63 71077.62 48
44158.71 71091.20 49
44084.78 71178.71 50
43942.15 71164.60 51
43814.58 71170.78 52
43818.08 71236.25
44439.04 70402.66 54
44386.06 70541.45 55
44369.65 70655.48 56
44357.65 70834.11 57
44351.34 71025.57 58
44342.30 71050.61 59
44318.31 71063.44 60
44189.13 71077.33 61
44159.25 71089.74 62
44080.56 71180.00 63
43941.91 71165.06 64
43903.78 71215.53
44440.21 70401.06 66
44386.56 70541.17 67
44369.37 70657.00 68
44356.63 70834.08 69
44351.36 71024.19 70
44341.66 71049.68 71
44319.22 71063.26 72
44189.22 71077.13 73
44158.10 71089.66 74
44081.71 71179.75 75
43942.29 71165.37 76
43995.40 71214.50
44439.13 70401.69 78
44385.45 70541.67 79
44370.03 70655.74 80
44352.82 70988.29 81
44352.52 71025.97 82
44340.95 71050.74 83
44318.70 71063.79 84
44189.06 71077.29 85
44158.21 71090.49 86
44081.38 71179.64 87
44107.04 71227.10
44438.38 70401.62 89
44383.06 70541.94 90
44371.61 70655.22 91
44359.57 70835.09 92
44352.88 70988.36 93
44351.25 71027.45 94
44342.03 71052.43 95
44318.84 71064.32 96
44192.33 71078.15 97
44158.88 71090.04 98
44190.40 71131.07
44442.47 70400.37 100
44384.03 70542.34 101
44366.98 70655.33 102
44357.35 70834.40 103
44352.92 71026.48 104
44341.36 71051.04 105
44319.30 71064.14 106
44274.87 71068.29 107
44282.43 71114.32
44440.62 70397.97 109
44386.89 70542.93 110
44370.81 70655.84 111
44356.20 70834.52 112
44350.35 71025.64 113
44340.48 71049.75 114
44447.91 71063.64 115
44448.65 71114.58
44439.81 70400.69 117
44385.56 70542.33 118
44368.79 70655.22 119
44355.11 70834.48 120
44349.98 70988.43 121
44391.71 70987.40 122
44444.81 71022.54
[airdrome1_Runways]
283855.00 204878.49 40.00 20.00 5.00 0
[airdrome1_Points]
283840.19 204869.39 106 103 100 97 93 88 82 75 72 69 67 64 62 60 57 53 49 45 41 37 34 30 26 21 16 11 6 1
283866.46 204842.54 2
284003.54 204941.54 3
284097.08 204953.50 4
284206.11 204951.11 5
284236.87 204979.59
283865.42 204842.54 7
284002.85 204941.89 8
284097.42 204953.43 9
284209.74 204950.42 10
284210.01 204917.74
283866.46 204841.85 12
284002.71 204942.11 13
284096.38 204953.39 14
284172.18 204949.97 15
284170.05 204916.60
283866.12 204842.19 17
284001.46 204941.54 18
284097.22 204953.43 19
284171.77 204950.19 20
284200.80 204990.91
283866.81 204840.81 22
284003.05 204942.25 23
284096.65 204953.63 24
284132.59 204951.64 25
284164.25 205000.53
283867.15 204842.19 27
284002.72 204942.01 28
284094.63 204955.27 29
284121.89 204993.72
283866.46 204841.50 31
284003.28 204942.69 32
284064.46 204950.19 33
284083.81 204983.42
283829.02 204909.45 35
283862.40 204950.90 36
283890.82 204969.52
283829.83 204908.38 38
283862.94 204950.90 39
283843.29 204984.01 40
283871.83 205002.66
283829.02 204909.45 42
283863.47 204950.09 43
283829.83 205009.31 44
283856.06 205025.74
283830.10 204908.91 46
283863.47 204950.63 47
283814.22 205038.11 48
283839.15 205053.48
283831.45 204909.45 50
283863.47 204948.75 51
283811.19 205041.54 52
283808.82 205065.98
283831.18 204908.65 54
283862.94 204949.29 55
283812.14 205037.87 56
283781.71 205047.56
283813.81 204893.91 58
283783.27 204867.20 59
283761.04 204897.82
283806.33 204891.68 61
283788.20 204915.69
283831.71 204908.11 63
283810.65 204934.19
283866.85 204841.94 65
283845.50 204813.15 66
283862.24 204793.72
283866.50 204842.41 68
283889.18 204819.02
283866.03 204843.68 70
283894.52 204862.85 71
283915.43 204841.29
283866.22 204844.00 73
283919.51 204880.95 74
283937.12 204862.17
283867.75 204842.85 76
284002.51 204942.32 77
284097.41 204953.64 78
284247.53 204950.77 79
284288.00 204959.02 80
284312.43 204950.01 81
284332.71 204950.38
283866.72 204844.53 83
284002.84 204942.11 84
284096.90 204953.75 85
284247.31 204950.73 86
284265.51 204924.43 87
284287.96 204921.58
283866.17 204843.63 89
284002.61 204942.32 90
284096.46 204953.59 91
284132.59 204951.66 92
284130.01 204921.03
283866.37 204842.88 94
284002.86 204942.29 95
284063.79 204949.88 96
284065.94 204920.84
283866.51 204844.08 98
283963.71 204913.16 99
283972.11 204891.53
283862.64 204950.61 101
283813.86 205036.82 102
283783.75 205021.93
283862.26 204949.82 104
283828.65 205008.62 105
283798.77 204994.38
283862.18 204949.85 107
283843.19 204982.96 108
283810.34 204967.07
[BirthPlace]
"III./JG27 - Carquebut" 2 52693 39771 0 1 1 1 de Luftwaffe_Fighter_1940 BoB_LW_JG27_III
"III./JG27 - Theville" 2 43246 70684 0 1 1 1 de Luftwaffe_Fighter_1940 BoB_LW_JG27_III
"III./JG27 - Guines" 2 283855 204878 0 1 1 1 de Luftwaffe_Fighter_1940 BoB_LW_JG27_III
[BirthPlace0]
Aircraft.Bf-109E-3B
Aircraft.Bf-109E-3
[BirthPlace1]
Aircraft.Bf-109E-3B
Aircraft.Bf-109E-3
[BirthPlace2]
Aircraft.Bf-109E-3B
Aircraft.Bf-109E-3


"Theville" max. 14 spawn points regular
http://www.Schwaan.info/Snafu/CoD/bugreport/spawnbug_theville1.jpeg



"Guines" ma. 12 spawn points regular
http://www.Schwaan.info/Snafu/CoD/bugreport/spawnbug_guines1.jpeg

Has anyone experience with the location of the spawnpoints, customized and prebuilt ones? Or airfields which actually work?

[Ataros]

Prebuilt spawnpoints are already there you do not have to place them again. Airfields are already built in the map. You can use them unless you experience explosions in hangars on spawn.

The spawnpoints you place manually probably do not work if not branched properly, i.e. aircraft do not have a direct route to taxi from the point. You are using a key for branching that you assigned, right? Check how prebuilt points are branched. The new ones have to be branched similar. And I think you have to use certain level of map zoom to place spawnpoints properly on map as it is bugged at other levels of zoom.

If the points can not be used aircraft spawn on airfield circle. Reduce circle radius to prevent them exploding on spawn. you can manually reduce it below 500m editing mission file with Notepad.

Another alternative is to use just half of the circle for spawn when not enough space available. To achieve this I cover the other part of the circle with really huge runway like 1000x700m. This prevents aircraft spawning on the part of a circle that is covered. But this was a temp solution I used before I learned about spownpoints branching key and afterwords I did not make any manually created airfields.

[SNAFU]

Yes Ataros,

When I use the prebuilt spawnpoints I can spawn about 14 in Theville and 12 in Guines. The 15th / 13th plane will not spawn on the spawnpoints anymore but somewhere around the perimeter, as I tried to explain.

So I tried it with customized spawnpoints and branched them all to taxi clearly out of the boxes around the objects to the runway, put the 0-point close to the touch-down-T on the customized runway. I tried different sizes of runways and "counquer-circles", but that didn´t change anything. After some planes spawned, they do not spawn at the defined (prebuilt or customized) points anymore, just end up somewhere. But I didn´t minimize the "airfield radius" manually, because it was set for Theville to 700m and Guines 500m, without contribution from my side and maskfield was grey. Will try this next in the *.mis file, but i am not very optimistic, cause all spawnpoints in my testruns with the prebuilt airfields were clearly free, but the planes just used some point far a way as the screenshots show. And if you use the prebuilt airfield spawnpoints you cannot define a "spawn circle" like in the old 1946.
You said you cover a spawnarea with an unassigned runway? This will block certain spawnpoints of another "aerodrome"? But will not see the "spawnarea" the new runway as a useable field too and start to fill the planes on starting position, even if the option "spawn parked" is checked? That`s what is happening to me also, if I spawn more planes at the same time.

I hoped the customized spawnpoint work, but if they only work randomly up to certain percentage of available and set spawnpoints, they are quite useless.



In 1946 I used to make screenshots of the planes spawned, put a static plane on the coordinates of the log-file and copied the coordinatesinto the *.mis file, to know where the player spawn, but I thought this would be solved in CloD.

[Ataros]

Theville to 700m and Guines 500m

I do not think you can even see the radius of AF built in the map. If you can see AF properties this means you are working with manually placed AF on top of a built-in AF I think. You may wish to delete them completely to try clean built-in airfields.

You can edit manually created AF's radius before you place any runways only. Thus delete runways and change radius first then create runways again. If you do not have any spawnpoints AC spawn on internal AF circle. If you placed spawnpoints AC would spawn on external circle which is 700m in your case when all spawnpoints are used.

This will block certain spawnpoints of another "aerodrome"?
No, I do not mean another AF I mean the same AF the runway belongs to. If I face hangar explosions issue with built-in AF, I do not use the old built-in AF but create new one on top of it. I place birthplace (spownpoint) in the center of the new one to make players use the new one instead of old one. Then if the circle of new AF does not fit into available space i use only half of it covering another half with runway.

I do not know what are you trying to achieve as I never needed as many spawnpoints. For players 5-10 is enough. For bots it is better to uncheck "spawn parked" to let them spawn on runway.

[SNAFU]

I do not think you can even see the radius of AF built in the map.
No, you can´t and can only change them in the *.mis file.

If you can see AF properties this means you are working with manually placed AF on top of a built-in AF I think.

That was my second approach.

You may wish to delete them completely to try clean built-in airfields.
That is what I mean with prebuilt airfields and just where I started with. :-P

On the cleanairfield I set a "spawnarea" and define color, type, squad and plane. I can spawn 14 planes on the built-in spawnpoints, the 15th of Theville just spawns somewhere. Same happens in Guines with the 13th planes. Ok, for small numbers that are playing acitve CloD at the moment, but if more players join one airfield? For squad training we need about 12 spawnpoints and for events we need definitly more.

So I put a customized runway over the built-in runway, define an airfield and points, put the customized spawnpoints with branches almost identically to the in-built spawnpoints, but now only the first 6 planes spawn on the spawnpoints I defined. After a certain number, they do not spawn on the spawnpoints anymore, but somewhere in the woods nearby. So this was a setback from the clean airfields.


You can edit manually created AF's radius before you place any runways only. Thus delete runways and change radius first then create runways again. If you do not have any spawnpoints AC spawn on internal AF circle. If you placed spawnpoints AC would spawn on external circle which is 700m in your case when all spawnpoints are used.

That is the problem, not all spawnpoints are used, but they start spawning on the outer circle. That`s why I tried it with customized spawnpoints, but that even got worse. :evil: ;)


No, I do not mean another AF I mean the same AF the runway belongs to. If I face hangar explosions issue with built-in AF, I do not use the old built-in AF but create new one on top of it. I place birthplace (spownpoint) in the center of the new one to make players use the new one instead of old one. Then if the circle of new AF does not fit into available space i use only half of it covering another half with runway.

Yes see above. I also experimented with the position of the custom-airfield and put them off the built-in-airfield so just

1. the runway is only a small 10mx10m box and lies totally on the built in runway and in the radius (approximated) of the airfield
2. the runway is only a small 10mx10m box and lies outside on the built in runway but in the radius (approximated) of the airfield
3. the runway is only a small 10mx10m box and lies outside on the built in runway and outside in the radius (approximated) of the airfield
4. same as 1-3 but with a runway size that is larger than the built in runway.

But I didn´t change the radius of the airfield, just moved the position around, to see if that influences the spawnpoints order or chosen to spawn on.

All over 3hrs testing...