Don't expect responses for ENet control messages to fix GFE 3.16

This commit is contained in:
Cameron Gutman 2018-11-15 12:55:22 -08:00
parent 11ea2b1053
commit 8665d80697

View File

@ -378,10 +378,7 @@ static int sendMessageAndForget(short ptype, short paylen, const void* payload)
}
static int sendMessageAndDiscardReply(short ptype, short paylen, const void* payload) {
// Discard the response
if (AppVersionQuad[0] >= 5) {
ENetEvent event;
PltLockMutex(&enetMutex);
if (!sendMessageEnet(ptype, paylen, payload)) {
@ -389,14 +386,6 @@ static int sendMessageAndDiscardReply(short ptype, short paylen, const void* pay
return 0;
}
if (serviceEnetHost(client, &event, CONTROL_STREAM_TIMEOUT_SEC * 1000) <= 0 ||
event.type != ENET_EVENT_TYPE_RECEIVE) {
PltUnlockMutex(&enetMutex);
return 0;
}
enet_packet_destroy(event.packet);
PltUnlockMutex(&enetMutex);
}
else {
@ -406,6 +395,7 @@ static int sendMessageAndDiscardReply(short ptype, short paylen, const void* pay
return 0;
}
// Discard the response
reply = readNvctlPacketTcp();
if (reply == NULL) {
return 0;