On our RT preview servers, it can take some time to clear an RTscript from server memory if there is an error in the script. Sometime this can take a long time to clear up, but it usually means that there is an error somewhere else in the code that is causing the problem. It is very unlikely that if this code was working previously, that it would stop so i'd look elsewhere for the problem.
Let us know if you have an example you can share. Thanks, Sean
1 Comment
Customer Support
said
almost 4 years ago
Answer
Hey Vitaly,
On our RT preview servers, it can take some time to clear an RTscript from server memory if there is an error in the script. Sometime this can take a long time to clear up, but it usually means that there is an error somewhere else in the code that is causing the problem. It is very unlikely that if this code was working previously, that it would stop so i'd look elsewhere for the problem.
Let us know if you have an example you can share. Thanks, Sean
Vitaly Evtukh
RTSession.setInterval(function(){
var matchData;
RTSession.newRequest().createMatchDetailsRequest()
.setMatchId(RTSession.getSessionId())
.setPlayerId(RTSession.getPlayers()[0].getPlayerId())
.setRealtimeEnabled(true)
.send(function(response){
matchData = response.matchData;
});
var rtDataToSend = RTSession.newData().setString(1, matchData);
RTSession.newPacket().setOpCode(5).setData(rtDataToSend).send();
}, 10000);
1 hour ago all work. But now, it's not working.
Hey Vitaly,
On our RT preview servers, it can take some time to clear an RTscript from server memory if there is an error in the script.
Sometime this can take a long time to clear up, but it usually means that there is an error somewhere else in the code that is causing the problem.
It is very unlikely that if this code was working previously, that it would stop so i'd look elsewhere for the problem.
Let us know if you have an example you can share.
Thanks,
Sean
Customer Support
Hey Vitaly,
On our RT preview servers, it can take some time to clear an RTscript from server memory if there is an error in the script.
Sometime this can take a long time to clear up, but it usually means that there is an error somewhere else in the code that is causing the problem.
It is very unlikely that if this code was working previously, that it would stop so i'd look elsewhere for the problem.
Let us know if you have an example you can share.
Thanks,
Sean
-
Documentation Notes
-
Design issues with user events
-
Using NoSQL
-
Runtime Collections vs Metadata Collections
-
Anonymous authentication from browser app
-
Modules
-
Movement With Unity
-
Problem with url parameters for downloadables
-
Querying NoSql GameSparks database
-
Challenge accesType
See all 2486 topics