Demonic tents! Number 8 (Naval) 1917 airfield issue

[jadebullet]

Hey guys, 

I recently started a Sopwith Tripe career with the Number 8 Naval in 1917. 

 

When I spawned on my first mission, I was surprised to see a tent sitting just off my left wing. My flight lead was obviously even more surprised as his prop immediately shredded itself on the same tent. 

 

Shrugging, I took off on a balloon busting mission, only for one plane to clip a wing into a tent and crash. I followed the remaining two planes to no man's land only for the AI to turn around 4km short of the mission so that they could try and form up with the broken prop flight lead. Flew the mission solo, got shot up by a flight of Albatrosses, but managed to limp home. 

 

Next mission my luck ran out and the Central Powers aligned tents got me. I spawned in with a tent in front of me, a tent to the left, and one to the right. I tried to maneuver out of my predicament but sadly broke a wing. 

 

 

It appears that there is an issue with the spawn locations on the aerodrome that causes planes to spawn in the area reserved for base scenery. 

 

I ended up deleting the career and trying a different squadron. 

 

 

Edit: 1917, not 1916

Edited April 17, 2023 by jadebullet

[TG-55Panthercules]

3 minutes ago, jadebullet said:

I recently started a Sopwith Tripe career with the Number 8 Naval in 1916. 

 

I assume you're talking about a PWCG campaign?  You can't start a career mode career in 1916.

[jadebullet]

Whoops, meant 1917. Will edit. 

[76SQN-Minimayhemtemp]

Relates to my issue with flights spawning in front of tree's.  Seems to be an issue that slipped through QA.

[LukeFF]

6 hours ago, 76SQN-Minimayhemtemp said:

Relates to my issue with flights spawning in front of tree's.  Seems to be an issue that slipped through QA.

 

Again, post the needed information about what airfields need to be addressed. 

[76SQN-Minimayhemtemp]

17 hours ago, LukeFF said:

 

Again, post the needed information about what airfields need to be addressed. 

I am not responsible for plugging the gaps in QA resources at 1C.

[Madmatt]

 

4 hours ago, 76SQN-Minimayhemtemp said:

I am not responsible for plugging the gaps in QA resources at 1C.

 

You know, in the time you took to post that reply you could have just listed what airfields you saw this issue occurring so that the devs could have a look. No one is asking you to act as a dedicated QA associate, but if you encounter a problem, everyone benefits by reporting it. Just my two cents though as a former Beta Test Lead for a different game developer in my past.

Edited April 20, 2023 by Madmatt

[AEthelraedUnraed]

On 4/20/2023 at 11:25 AM, 76SQN-Minimayhemtemp said:

I am not responsible for plugging the gaps in QA resources at 1C.

No, you're not. But look at it this way: based on your refusal to post where you spawned into that tree, 1C can either:

A) Hire someone to check every airfield once again for all different trees along all possible spawn points, accounting for different aircraft types. I wouldn't be surprised if this takes someone a whole day - time that has to be taken from other development tasks, as well as paid for. Furthermore, there's always the chance they miss it this time around as well. In other words, costs time and money while no success is guaranteed. Repeat this process for every other person reporting a bug somewhere on the map.

B) Shrug it off since you seem to be the only one who's had trouble with that particular tree so far, and wait for when/if someone else ever reports the location.

 

Regardless of your personal opinions concerning what constitutes an acceptable amount of bugs, the Devs are very unlikely to choose A. You can either report where you spawned into that tree and have them fix it, or wait for the cold day in hell when this bug spontaneously disappears.