#R4D1 Bugs

1 messages · Page 1 of 1 (latest)

lyric hazel
#

Friends and I have been on this for far too long with too many problems disrupting runs:
1: Staggered waves and spawns:
a: We initially assumed it was lag causing the bad spawns due to one of our friends being from the UK and the rest of us from Asia, but when we had an all Asian team we still had this problem, though not to that extent.
b: Second assumption was running between rooms and zones would cause spawns to bug out but this isn't the case either since we held out in a room (not the reactor) and spawns were staggered for 3 or more minutes
c: Third assumption was that we were potentially sitting on spawn zones since some of the rooms we held may be spawnpoints but results here are inconsistent, sometimes the spawns went away in time, sometimes they didn't.

2: Network problems causing enemy spawns and waves to not appear correctly, the rest of the group could be seeing smth different than me, timers don't work correct, etc.

3: Some instances where teammates are not able to use their tools, resources, revives, interacting with doors, etc

This was our first plan:
1: For the first reactor wave we held in the middle of the spawn bridge leading into the reactor, no issues here.
2: For the second, third and fourth reactor wave we held the area in between the spawn bridge and reactor, enemies would have staggered spawns here but results can vary on how bad a wave is staggered/delayed.

Second plan:
1: First reactor wave was the same as the first plan.
2: Second reactor wave is similar to first plan too.
3: We would hold the third wave in the room with the yellow circle.
4: We would fall back to the yellow room and push on to the security scan where we never got any further.

Third plan:
1: First reactor wave remains the same.
2: We would hold the second wave in the room with the blue circle, this caused immensely delayed spawns, up to 3 minutes after the alarm is cleared it still wouldn't go away.

#

Fourth plan:
1: Same
2: We held the reactor instead, the waves instantly disabled the moment the reactor alarm went offline.
3: We held the yellow room, pulling the enemies from the next room with a purple arrow, the spawns were extremely staggered here causing us to lose.

Fifth plan:
1: Same
2: We held the bridge and it caused staggered spawns.

#

I've been advised to stay in the same room/zone until we felt the spawns stopped, pulse goes down, music goes away, but it didn't help.

rapid tartan
#

since alt r1, reactor spawns get messed up if youre not in reactor.

#

r2d2 especially, spawns occurred as far north and south as they could (reachable areas), delayed them much

#

so i would suggest have someone in reactor, if able. switch places when low ammo.

lyric hazel
#

Do we only need to have 1 person in reactor?

rapid tartan
#

it could be all it takes, or, some say, u all have to..

#

but u correct, when not defending at reactor, spawns be funky. delayed. horrible.

lyric hazel
#

gotcha, thanks for the input, that's rough tho

rapid tartan
#

it is

lyric hazel
#

that we can't hold a specific zone we want to

rapid tartan
#

r4e1 secondary looms ahead. 😦

lyric hazel
#

is it more challenging in terms of bugs or gameplay? LOL

rapid tartan
#

u used to, but something changed when alts started coming out

lyric hazel
#

Alright, thanks for the insight, I'll let the others know

whole cosmos
#

having a bug with the bot not standing in the scan to open the blood door after the second wave. we had to kick the bot to scan but it was already to late to get the code

neat locust
#

thats a non-specific to d1 bug but yeah somoene wrote about it right down ur post so