Kudjate said:
1- ...this game will not be playable on pc in 2019 the reason is simple, the more content is added the bigger the memory will have to be...
2- ... i have 16GO of Ram - Intel Core i7-8086K (4.0 GHz) - GeForce GTX 1080 Gaming X - 8 Go - 1GO Internet speed...
3- ... i think every update should not be released befor its tested by the dev...
let begin with "2-" ... have a old computer ( 11 year old next month ) with windows xp pro x64... have the usual error as everybody but not very often...
old computer have 2 processor xeon quad core... game use 80% of 1 thread... total 5% of all computer power... the game is not made for multicore or hyperthreading... best to have a single core at 4 ghz that 16 thread at 2 ghz...
as memory use, it is 1.186.412k in my case with firefox but it is a naked version of firefox with bare minimum... add-on and plugin are loaded only on demand, not toolbar, etc... only developper tools
"2-" adding thing don't mean bigger... working code for feature are pretty small when compare to size of graphic asset... what plarium need to do is optimize their graphic asset...
I have be in a modding team for years, working on a mod who optimize skyrim... after around 2 year of work, remaking the uv map of model, correcting mesh error, and optimizing texture... the mod team was able to reducing the memory use of skyrim by 40%... who have give room to other modding team to add plenty of content... point is that plarium need to make some optimization work as future update before adding new feature...
plarium is already working on freeing memory as java console log show :
Unloading 1682 unused Assets to reduce memory usage. Loaded Objects now: 26152.
but i am not sure that it is the road to follow for reduce the unity webgl memory error... unity need a continuous chunk of memory for work correctly... load and unload continuously assets in memory greatly fragment the memory and somehow will make appear the memory error more often... from my point of view, the hard work to optimize/correct the graphic asset to use less memory is the way to go...
"3-" agree with it but i think that plarium devs don't use the devs tools in their own browser else they will see directly some of the problems as show below from my own log...
(Filename: Line: 1515)
bugTracker.js:1:3968
The referenced script on this Behaviour (Game Object 'ASphere') is missing!
(Filename: Line: 1758)
bugTracker.js:1:3968
The referenced script on this Behaviour is missing!
(Filename: Line: 1515)
bugTracker.js:1:3968
The referenced script on this Behaviour (Game Object 'ASphere') is missing!
(Filename: Line: 1758)
bugTracker.js:1:3968
Decode error. bugTracker.js:1:3968
The referenced script on this Behaviour is missing!
(Filename: Line: 1515)
bugTracker.js:1:3968
The referenced script on this Behaviour (Game Object 'FlagYarl') is missing!
(Filename: Line: 1758)
bugTracker.js:1:3968
The referenced script on this Behaviour is missing!
(Filename: Line: 1515)
bugTracker.js:1:3968
The referenced script on this Behaviour (Game Object 'FlagYarl') is missing!
(Filename: Line: 1758)
bugTracker.js:1:3968
Unloading 3 Unused Serialized files (Serialized files now loaded: 3)
bugTracker.js:1:3968
Unloading 1682 unused Assets to reduce memory usage. Loaded Objects now: 26152.
bugTracker.js:1:3968
Total: 250.000000 ms (FindLiveObjects: 0.000000 ms CreateObjectMapping: 0.000000 ms MarkObjects: 188.000000 ms DeleteObjects: 62.000000 ms)
bugTracker.js:1:3968
@@@socket send bugTracker.js:1:3968
1
(Filename: /Users/builduser/buildslave/unity/build/artifacts/generated/WebGL/runtime/DebugBindings.gen.cpp Line: 51)
bugTracker.js:1:3968
warning: 2 FS.syncfs operations in flight at once, probably just doing extra work bugTracker.js:1:3968
Decode error. bugTracker.js:1:3968
@@@socket send bugTracker.js:1:3968
Unloading 3 Unused Serialized files (Serialized files now loaded: 3)
bugTracker.js:1:3968
Unloading 598 unused Assets to reduce memory usage. Loaded Objects now: 27358.
bugTracker.js:1:3968
Total: 202.000000 ms (FindLiveObjects: 0.000000 ms CreateObjectMapping: 0.000000 ms MarkObjects: 186.000000 ms DeleteObjects: 16.000000 ms)
bugTracker.js:1:3968
Decode error. bugTracker.js:1:3968