Hi Everyone -
Here are the Release Notes for the R190 Update.
R190
"Dunadd Hill Fort"
What's Changed
Thank you!
MegaBee said: It's Wolfsbane!
firethorne said:Unless, that's what they want us to think.
bluewolf said: I hope that the boss bug fix means that another one is coming soon.....I wonder who was able to avoid downloading the daily patch. It just happens for me, no choice in the matter. Maybe it's a Steam thing.
bluewolf said: Maybe it's a Steam thing.
supergarv said: the former is what kills your PVP red nodes once a day when you just want to enter the open game and it goes to the loading screen.
bluewolf said: supergarv said: the former is what kills your PVP red nodes once a day when you just want to enter the open game and it goes to the loading screen. Once a day? I wish it was only once a day...... darn app resets so often.
supergarv said: bluewolf said: supergarv said: the former is what kills your PVP red nodes once a day when you just want to enter the open game and it goes to the loading screen. Once a day? I wish it was only once a day...... darn app resets so often. I should rephrase to „at least once a day“ The game also restarts when you‘re out of RAM. On iOS, opening the stock Camera app for example kills MPQ. Which is why I rarely take pictures with my cam, godlady knows how many times I‘ve lost a paused match this way.
TeamStewie said: supergarv said: bluewolf said: supergarv said: the former is what kills your PVP red nodes once a day when you just want to enter the open game and it goes to the loading screen. Once a day? I wish it was only once a day...... darn app resets so often. I should rephrase to „at least once a day“ The game also restarts when you‘re out of RAM. On iOS, opening the stock Camera app for example kills MPQ. Which is why I rarely take pictures with my cam, godlady knows how many times I‘ve lost a paused match this way. The newest version of iOS has an issue with multitasking. Typical Apple.
TPF Alexis said: TeamStewie said: supergarv said: bluewolf said: supergarv said: the former is what kills your PVP red nodes once a day when you just want to enter the open game and it goes to the loading screen. Once a day? I wish it was only once a day...... darn app resets so often. I should rephrase to „at least once a day“ The game also restarts when you‘re out of RAM. On iOS, opening the stock Camera app for example kills MPQ. Which is why I rarely take pictures with my cam, godlady knows how many times I‘ve lost a paused match this way. The newest version of iOS has an issue with multitasking. Typical Apple. What amuses* me about that is that is that back around MacOS6 or so, they made some fundamental breakthroughs on keeping multiple applications running at once. But they seem to have forgotten all that.*"Amuses" could be equally read as "frustrates" in this context
TPF Alexis said: What amuses* me about that is that is that back around MacOS6 or so, they made some fundamental breakthroughs on keeping multiple applications running at once. But they seem to have forgotten all that.*"Amuses" could be equally read as "frustrates" in this context
I'm not sure you'd really want to go back to the days of classic Mac OS though. You'd probably find it far less resilient than you remember. It relied on cooperative multitasking, so it was possible for one application to monopolise the CPU to the exclusion of all others. It also lacked memory protection, so there was nothing stopping one application from overwriting the code or data of another running application.
It worked fairly well if you only ran relatively bug free well behaved applications, but that's the best case scenario for a system like that. You certainly wouldn't be able to implement the kind of application confinement systems found on modern mobile operating systems, which is a core part of what makes their app stores relatively safe to use.
jamesh said: TPF Alexis said: What amuses* me about that is that is that back around MacOS6 or so, they made some fundamental breakthroughs on keeping multiple applications running at once. But they seem to have forgotten all that.*"Amuses" could be equally read as "frustrates" in this context I'm not sure you'd really want to go back to the days of classic Mac OS though. You'd probably find it far less resilient than you remember. It relied on cooperative multitasking, so it was possible for one application to monopolise the CPU to the exclusion of all others. It also lacked memory protection, so there was nothing stopping one application from overwriting the code or data of another running application.It worked fairly well if you only ran relatively bug free well behaved applications, but that's the best case scenario for a system like that. You certainly wouldn't be able to implement the kind of application confinement systems found on modern mobile operating systems, which is a core part of what makes their app stores relatively safe to use.