Game

WebGL Viewer and livery editor update

Hi all,

Sorry it has taken so long but we believe we have now fixed the out of memory issues some people are encountering on the webGL platform.

Just a few of things to note. 

Please can you make sure you are up to date with your browser and running 64 bit versions of that software.

If you are still getting issues can you please try to open the development tools for your chosen browser and look for some sort of console output. Then take a screen shot or a copy and paste of all the details. This will help us debug your issue faster.

There is still an ongoing issue we are still investigating, which is on all platforms, where there is apparent lag where the cars warp after a few seconds or you get an out of sync error come up. We have added debugging tools to our belt to get to the bottom of this. Please bear with us as it may take a few more days to get to the bottom of that one.

Regards
Darren

What about the app closing in race? I've had to stop racing because of this. Can't win races if app won't stay on. Is that being fixed aswell

Thank god :) I don't mind waiting long as it's gonna be fixed thank you :) 

A simulator patch has gone out this afternoon (3pm UTC 19/10/2018) to combat the out of sync issues some people have been experiencing.

If you have out of sync or any out of memory please post them on this thread.

Thanks

Doesn't work. The error occurred again this evening at 19:00 GMT+1. I did a screen shot with consol opened but i've some difficult to post it. If you give me an email address a could to send it by mail.

maybe i can post it now

Still getting multiple crashes in both browsers, Opera crashes were terminal so no console.

This is the firefox console. NB: My Firefox is an old version so may possibly be 32bit but it may still be of help. 

Successfully compiled asm.js code (total compilation time 1ms; not stored in cache (too small to benefit)) UnityLoader.js
Successfully compiled asm.js code (total compilation time 0ms; not stored in cache (too small to benefit)) UnityLoader.js
UnknownError UnityLoader.js:4:12067
[UnityCache] indexedDB database could not be opened UnityLoader.js:4:11214
Invoking error handler due to
UnknownError UnityLoader.js:3:16879
Warning: Unsupported graphics API WebGL 2.0 UnityLoader.js:4:9380
[UnityCache] 'https://igpmanager.blob.core.windows.net/raceviewer/v3_2/iGP%20Manager%20V3%20WebGL.asm.memory.unityweb' successfully downloaded but not stored in the indexedDB cache due to the error: Error: indexedDB access denied UnityLoader.js:4:11214
You can reduce your startup time if you configure your web server to host .unityweb files using gzip compression. UnityLoader.js:3:8480
[UnityCache] 'https://igpmanager.blob.core.windows.net/raceviewer/v3_2/iGP%20Manager%20V3%20WebGL.asm.framework.unityweb' successfully downloaded but not stored in the indexedDB cache due to the error: Error: indexedDB access denied UnityLoader.js:4:11214
[UnityCache] 'https://igpmanager.blob.core.windows.net/raceviewer/v3_2/iGP%20Manager%20V3%20WebGL.asm.code.unityweb' successfully downloaded but not stored in the indexedDB cache due to the error: Error: indexedDB access denied UnityLoader.js:4:11214
[UnityCache] 'https://igpmanager.blob.core.windows.net/raceviewer/v3_2/iGP%20Manager%20V3%20WebGL.data.unityweb' successfully downloaded but not stored in the indexedDB cache due to the error: Error: indexedDB access denied UnityLoader.js:4:11214
Successfully compiled asm.js code (total compilation time 6402ms; storage initialization failed (consider filing a bug); 1 functions compiled slowly: neb:16:397240 (261ms)) 69192d30-7af8-45db-a0f2-0dd89c027470
IndexedDB is not available. Data will not persist in cache and PlayerPrefs will not be saved. f39d54d6-9a0a-44ab-a4ca-8780645065a2:2:173
Loading player data from data.unity3d UnityLoader.js:4:9380
Initialize engine version: 2018.3.0b4 (44012bad7987) UnityLoader.js:4:9380
Creating WebGL 1.0 context. UnityLoader.js:4:9380
Renderer: Mozilla UnityLoader.js:4:9380
Vendor:  Mozilla UnityLoader.js:4:9380
Version:  OpenGL ES 2.0 (WebGL 1.0) UnityLoader.js:4:9380
GLES:    2 UnityLoader.js:4:9380
ANGLE_instanced_arrays GL_ANGLE_instanced_arrays EXT_blend_minmax GL_EXT_blend_minmax EXT_color_buffer_half_float GL_EXT_color_buffer_half_float EXT_frag_depth GL_EXT_frag_depth EXT_shader_texture_lod GL_EXT_shader_texture_lod EXT_texture_filter_anisotropic GL_EXT_texture_filter_anisotropic OES_element_index_uint GL_OES_element_index_uint OES_standard_derivatives GL_OES_standard_derivatives OES_texture_float GL_OES_texture_float OES_texture_float_linear GL_OES_texture_float_linear OES_texture_half_float GL_OES_texture_half_float OES_texture_half_float_linear GL_OES_texture_half_float_linear OES_vertex_array_object GL_OES_vertex_array_object WEBGL_color_buffer_float GL_WEBGL_color_buffer_float WEBGL_compressed_texture_s3tc GL_WEBGL_compressed_texture_s3tc WEBGL_depth_texture GL_WEBGL_depth_texture WEBGL_draw_buffers GL_WEBGL_draw_buffers WEBGL_lose_context GL_WEBGL_lose_context MOZ_WEBGL_lose_context GL_MOZ_WEBGL_lose_context MOZ_WEBGL_compressed_texture_s3tc GL_MOZ_WEBGL_compressed_texture_s3tc MOZ_WEBGL_de UnityLoader.js:4:9380
pth_texture UnityLoader.js:4:9380
OPENGL LOG: Creating OpenGL ES 2.0 graphics device ; Context level  ; Context handle 1 UnityLoader.js:4:9380
UnloadTime: 0.310000 ms UnityLoader.js:4:9380
WARNING: Shader Unsupported: 'Mobile/Diffuse' - Pass 'Meta' has no vertex shader UnityLoader.js:4:9380
WARNING: Shader Unsupported: 'Standard' - Pass 'META' has no vertex shader UnityLoader.js:4:9380
LOADING UnityLoader.js:4:9380
Cannot enlarge memory arrays. Either (1) compile with  -s TOTAL_MEMORY=X  with X higher than the current value 536870912, (2) compile with  -s ALLOW_MEMORY_GROWTH=1  which allows increasing the size at runtime but prevents some optimizations, (3) set Module.TOTAL_MEMORY to a higher value before the program runs, or (4) if you want malloc to return NULL (0) instead of this abort, compile with  -s ABORTING_MALLOC=0  UnityLoader.js:4:9380
Cannot enlarge memory arrays. Either (1) compile with  -s TOTAL_MEMORY=X  with X higher than the current value 536870912, (2) compile with  -s ALLOW_MEMORY_GROWTH=1  which allows increasing the size at runtime but prevents some optimizations, (3) set Module.TOTAL_MEMORY to a higher value before the program runs, or (4) if you want malloc to return NULL (0) instead of this abort, compile with  -s ABORTING_MALLOC=0  UnityLoader.js:4:9417

uncaught exception: abort("Cannot enlarge memory arrays. Either (1) compile with  -s TOTAL_MEMORY=X  with X higher than the current value 536870912, (2) compile with  -s ALLOW_MEMORY_GROWTH=1  which allows increasing the size at runtime but prevents some optimizations, (3) set Module.TOTAL_MEMORY to a higher value before the program runs, or (4) if you want malloc to return NULL (0) instead of this abort, compile with  -s ABORTING_MALLOC=0 ") at jsStackTrace@blob:https://igpmanager.com/f39d54d6-9a0a-44ab-a4ca-8780645065a2:2:15319
stackTrace@blob:https://igpmanager.com/f39d54d6-9a0a-44ab-a4ca-8780645065a2:2:15490
UnityLoader

But my firefox is the last version 64 bit and the problem is the same. i'll play again monday. i hope that the problem will be solved monday evening because will be impossible to play in montecarlo's race with the screen taht crashes and the AI (Artificial Idiocy) that burns all the kers when mustn't

I have recurrent problems with both Safari and Firefox. I close all the other applications too. I'll see if I can take some photos tonight.

Thanks for working on this!

Hi Jack,

I tried both Safari and FireFox separately yesterday to attend my race and both gave series of the same "out of memory" error messages. 

A quick google led me to this https://forum.unity.com/threads/webgl-out-of-memory-error.526123/

BTW I emptied the cache before starting the race.

Could you please help us Mac users?

Thanks!

Another one time the error occurred. This time i've the pictures of all console. If you don't find a resolution so, i'll costrained to leave the game because it's very impossible to play so. this time during the crash the AI burned the 7'% of kers. It's impossible.

https://scontent-mxp1-1.xx.fbcdn.net/v/t1.0-9/44566983_10217697731505257_2029596188818276352_n.jpg?_nc_cat=107&_nc_ht=scontent-mxp1-1.xx&oh=f73304410a5f21ac37453405a0c91eeb&oe=5C874015

https://scontent-mxp1-1.xx.fbcdn.net/v/t1.0-9/44563110_10217697732225275_4531641954177384448_n.jpg?_nc_cat=101&_nc_ht=scontent-mxp1-1.xx&oh=5cdc1fc7c95518c7205921535265766b&oe=5C4BB92D

https://scontent-mxp1-1.xx.fbcdn.net/v/t1.0-9/44646663_10217697732785289_8902893104919478272_n.jpg?_nc_cat=111&_nc_ht=scontent-mxp1-1.xx&oh=b8510bfcfd8acaf885698457e9a79d80&oe=5C8384E0

https://scontent-mxp1-1.xx.fbcdn.net/v/t1.0-9/44532875_10217697733185299_2328570374121324544_n.jpg?_nc_cat=100&_nc_ht=scontent-mxp1-1.xx&oh=0923da0b8e01e928edc1ead955127e64&oe=5C55ECE1

https://scontent-mxp1-1.xx.fbcdn.net/v/t1.0-9/44665823_10217697733985319_4634695992183095296_n.jpg?_nc_cat=103&_nc_ht=scontent-mxp1-1.xx&oh=bb21458317a864cc60a37ee9ae013b01&oe=5C3C3DB5

https://scontent-mxp1-1.xx.fbcdn.net/v/t1.0-9/44566135_10217697734705337_5538312340522401792_n.jpg?_nc_cat=104&_nc_ht=scontent-mxp1-1.xx&oh=e805ffb9936ad79e24e570df9a18d313&oe=5C83CD1D

Great, thank you!


I'm using High Sierra on MacBook Air 2015(4GB) and High Sierra on iMac 2017 (8GB). This only started after the recent update.

The kers still not working right. I press kers and it stays on and uses it all nearly. I've updated the app 

i would like to know what do you doing to repair the webgl error. i posted all my console, and now?

Hi Guy's

I still have a sponsor-less car with the new editor. 

And no one even answering our problems can't play the game as it is right now. Getting sicka not being able to race right

We are continually looking into these issues, I am currently dispatching a fix to the servers for some of the issues.

Please remember we are a very small team when I say a very small team there is only 4 developers each with there own area to focus on.

You have the CEO Jack who is involved in the web side of the game as well as all the business aspects of the company.
There is myself who is involved with everything at some point, but mainly focusing on this particular issue with connections dropping and out of memory problems. This involves both the Simulation code and the viewer code.
Sameel who mainly maintains and develops the race viewer part of the app.
Aleksander who mainly maintains and developer the livery editor.

We are constantly fixing and addressing the issues as fast as we can. The app was tested by a group of volunteers as well as the developers, but even they can't match and test the conditions for all of the users we already have and growing all the time.

We are asking for patience on your part while we fix all of these issues. If we don't reply to every post this is because we are busy fixing and looking into the problems.

If you are only in 4, so fix on 0 the automatical use of kers  when the player don't follow the race, because could be manageable a race with some crash if it doesn't use all kers every time that the window crashes. We'll lost one or 2 laps but nothing more. But now the situation is unmanageable. It's impossible to manage a championship  where you are the fastest but lost all races because the AI use all kers any time when mustn't.
With automatic use of ker setted  on 0 we could attend your fixes. The situation wouldn't be ideal, but could be manageable.