STOP BREAKING THE DAMNED GAME WITH UNTESTED HOT FIXES!!!!!!!!!!!!!!!!!!!!
Small, incremental patches like the most recent one have never been tested on the PTS beforehand, and I doubt that will ever become practice. Generally speaking, PTS is for testing new content like DLCs, not for verifying if bugs have been addressed in a particular patch that's going to be pushed on live. I'm glad they have such a high update frequency -- putting everything on PTS before releasing would be detrimental to it.No, damned if they DON'T TEST! We're basically beta testing these patches because they aren't tested on the PTS, or through a smaller but broad enough beta testing group to identify issues BEFORE they push it live!
KhajitFurTrader wrote: »Small, incremental patches like the most recent one have never been tested on the PTS beforehand, and I doubt that will ever become practice. Generally speaking, PTS is for testing new content like DLCs, not for verifying if bugs have been addressed in a particular patch that's going to be pushed on live. I'm glad they have such a high update frequency -- putting everything on PTS before releasing would be detrimental to it.No, damned if they DON'T TEST! We're basically beta testing these patches because they aren't tested on the PTS, or through a smaller but broad enough beta testing group to identify issues BEFORE they push it live!
Also, since the version number has changed, all addons that had been updated to work with 2.3.5 are theoretically now outdated again since 2.3.6 hit live.
And good luck, @LaucianNailor!
KhajitFurTrader wrote: »Also, since the version number has changed, all addons that had been updated to work with 2.3.5 are theoretically now outdated again since 2.3.6 hit live.
Well, honestly I don't know, and you may be right. But after repeatedly reading reports today that removing Master Merchant fixed crash issues after character load for some people, I guesstimated that sometimes, new game versions and existing addons don't mix well. It might be caused by side effects form bug fixes, or (undocumented) changes to the API. Me, I'd wait with enabling/using addons until their authors explicitly released them for the latest game version.LaucianNailor wrote: »Are you sure this is correct? My understanding is that ZoS push an approved API version (currently 100014), which providing add-ons adhere to, remains valid (up to date) until a changed API version is required. These updated API sets usually relate to significant patches (full point i.e. .X) and not incremental (part point i.e. .(n).X)
Therefore all add-ons written to run with 2.3 should not be flagged as out of date until 2.4 as no documented API changes have been made or communicated shouldn't they?
Good idea. Alas, I tried to reproduce it by logging through my characters, but no luck: I still have yet so see a single pink texture. If anything, the client runs stable and very, very smooth -- I'm getting 30+ FPS on ultra-high settings (Shadows tuned down to high, and HIGH_RESOLUTION_SHADOWS turned off) at 2560x1440 in very crowded urban areas. Same machine as yours (the amount of RAM above 8 GB doesn't really matter). This is a weird bug, I hope they can find the cause and squash it.LaucianNailor wrote: »Additionally, on 1st run, all appears to be fine for that character. Missing textures and add-on's being recognised, then vanishing only occurs following logging out a character and logging in a different one. If I close the client and load up the character I had the problems with, they are cleared. Not sure if this relates to some problem with unloading assets at character log-out or some memory problems when swapping characters?
KhajitFurTrader wrote: »Could you please take a look into your UserSettings.txt file? It's possible that the LUA memory limit has been reset to its default value of 64 MB. Look for the line
SET LuaMemoryLimitMB "xx"
where xx is the current value. Theoretically, this value could be boosted up to a few gigabytes now on a machine with ample memory, but 640K 512 MB "ought to be enough for anybody".
LaucianNailor wrote: »Hey @KhajitFurTrader
Your post above re the 'set LUA memory' had me thinking about some of the errors I've been getting with vanishing add-on's etc. I set this to 512 and verified it had changed after I closed the file.
I logged out a couple of hours ago, but decided to have another look at the UserSettings.txt file in /Users/*****/Documents/Elder Scrolls Online/liveeu.
Interestingly, the value has been re-set to 0:
SET FOVChangesAllowed "1"
SET AgreedToPEGI "1"
SET LuaMemoryLimitMB "0"
SET GamepadSensitivityFirstPerson.2 "0.72000003"
SET GamepadSensitivityThirdPerson.2 "0.85000002"
This shows as being modified at the time I logged out. I wouldn't have thought this was normal behaviour and wonder if this is a cause?
LaucianNailor wrote: »@capricorn152245ub17_ESO
To answer your question, I wiped the settings folder to allow the game to build a new default settings file. For LUA memory, this is 64mb afaik. I amended this to 512mb prior to launching the game and so for it to reset to 0 on exit is puzzling.
My concern with this was that some in game event, say triggering /reloadui is changing this value and shutting down add-ons or at least causing some game anomalies and crashes.
I can't load any add-on anymore. I select them, reload ui and nothing happens. By the way, when I load another character the game crash with a message (the first time I saw this error with a 'crash button' made me laugh lol) I wonder if It's just a problem of mine or you have it too...?
I can't load any add-on anymore. I select them, reload ui and nothing happens. By the way, when I load another character the game crash with a message (the first time I saw this error with a 'crash button' made me laugh lol) I wonder if It's just a problem of mine or you have it too...?