UUM-79682 - Unity release-note mentions

Version	Section	Impact	Note
6000.1.0f1	Fixes Web	Fix	Fixed web browser to not hang when using Autoconnect Profiler with Build and Run, when the Unity project is set to log large amounts of text at web page startup. Note however that there will still exist a platform-specific limitation that only about 45000 log messages can be printed back-to-back at web page startup, or otherwise the message send queue gets full. If more than 45000 log messages need to be printed back to the Editor, they should be done at page runtime after PlayerConnection has initialized, to avoid this WebSocket limitation.
6000.1.0b15	Fixes Web	Fix	Fixed web browser to not hang when using Autoconnect Profiler with Build and Run, when the Unity project is set to log large amounts of text at web page startup. Note however that there will still exist a platform-specific limitation that only about 45000 log messages can be printed back-to-back at web page startup, or otherwise the message send queue gets full. If more than 45000 log messages need to be printed back to the Editor, they should be done at page runtime after PlayerConnection has initialized, to avoid this WebSocket limitation.
6000.1.0b14	Fixes Web	Fix	Fixed web browser to not hang when using Autoconnect Profiler with Build and Run, when the Unity project is set to log large amounts of text at web page startup. Note however that there will still exist a platform-specific limitation that only about 45000 log messages can be printed back-to-back at web page startup, or otherwise the message send queue gets full. If more than 45000 log messages need to be printed back to the Editor, they should be done at page runtime after PlayerConnection has initialized, to avoid this WebSocket limitation.
6000.1.0b13	Fixes Web	Fix	Fixed web browser to not hang when using Autoconnect Profiler with Build and Run, when the Unity project is set to log large amounts of text at web page startup. Note however that there will still exist a platform-specific limitation that only about 45000 log messages can be printed back-to-back at web page startup, or otherwise the message send queue gets full. If more than 45000 log messages need to be printed back to the Editor, they should be done at page runtime after PlayerConnection has initialized, to avoid this WebSocket limitation.
6000.1.0b12	Fixes Web	Fix	Fixed web browser to not hang when using Autoconnect Profiler with Build and Run, when the Unity project is set to log large amounts of text at web page startup. Note however that there will still exist a platform-specific limitation that only about 45000 log messages can be printed back-to-back at web page startup, or otherwise the message send queue gets full. If more than 45000 log messages need to be printed back to the Editor, they should be done at page runtime after PlayerConnection has initialized, to avoid this WebSocket limitation.
6000.1.0b11	Fixes Web	Fix	Fixed web browser to not hang when using Autoconnect Profiler with Build and Run, when the Unity project is set to log large amounts of text at web page startup. Note however that there will still exist a platform-specific limitation that only about 45000 log messages can be printed back-to-back at web page startup, or otherwise the message send queue gets full. If more than 45000 log messages need to be printed back to the Editor, they should be done at page runtime after PlayerConnection has initialized, to avoid this WebSocket limitation.
6000.1.0b10	Fixes Web	Fix	Fixed web browser to not hang when using Autoconnect Profiler with Build and Run, when the Unity project is set to log large amounts of text at web page startup. Note however that there will still exist a platform-specific limitation that only about 45000 log messages can be printed back-to-back at web page startup, or otherwise the message send queue gets full. If more than 45000 log messages need to be printed back to the Editor, they should be done at page runtime after PlayerConnection has initialized, to avoid this WebSocket limitation.
6000.1.0b9	Fixes Web	Fix	Fixed web browser to not hang when using Autoconnect Profiler with Build and Run, when the Unity project is set to log large amounts of text at web page startup. Note however that there will still exist a platform-specific limitation that only about 45000 log messages can be printed back-to-back at web page startup, or otherwise the message send queue gets full. If more than 45000 log messages need to be printed back to the Editor, they should be done at page runtime after PlayerConnection has initialized, to avoid this WebSocket limitation.
6000.1.0b8	Fixes Web	Fix	Fixed web browser to not hang when using Autoconnect Profiler with Build and Run, when the Unity project is set to log large amounts of text at web page startup. Note however that there will still exist a platform-specific limitation that only about 45000 log messages can be printed back-to-back at web page startup, or otherwise the message send queue gets full. If more than 45000 log messages need to be printed back to the Editor, they should be done at page runtime after PlayerConnection has initialized, to avoid this WebSocket limitation.
6000.1.0b7	Fixes Web	Fix	Fixed web browser to not hang when using Autoconnect Profiler with Build and Run, when the Unity project is set to log large amounts of text at web page startup. Note however that there will still exist a platform-specific limitation that only about 45000 log messages can be printed back-to-back at web page startup, or otherwise the message send queue gets full. If more than 45000 log messages need to be printed back to the Editor, they should be done at page runtime after PlayerConnection has initialized, to avoid this WebSocket limitation.
6000.1.0b6	Fixes Web	Fix	Fixed web browser to not hang when using Autoconnect Profiler with Build and Run, when the Unity project is set to log large amounts of text at web page startup. Note however that there will still exist a platform-specific limitation that only about 45000 log messages can be printed back-to-back at web page startup, or otherwise the message send queue gets full. If more than 45000 log messages need to be printed back to the Editor, they should be done at page runtime after PlayerConnection has initialized, to avoid this WebSocket limitation.
6000.0.38f1	Fixes Web	Fix	Fixed web browser to not hang when using Autoconnect Profiler with Build and Run, when the Unity project is set to log large amounts of text at web page startup. Note however that there will still exist a platform-specific limitation that only about 45000 log messages can be printed back-to-back at web page startup, or otherwise the message send queue gets full. If more than 45000 log messages need to be printed back to the Editor, they should be done at page runtime after PlayerConnection has initialized, to avoid this WebSocket limitation.
6000.1.0b5	Fixes Web	Fix	Fixed web browser to not hang when using Autoconnect Profiler with Build and Run, when the Unity project is set to log large amounts of text at web page startup. Note however that there will still exist a platform-specific limitation that only about 45000 log messages can be printed back-to-back at web page startup, or otherwise the message send queue gets full. If more than 45000 log messages need to be printed back to the Editor, they should be done at page runtime after PlayerConnection has initialized, to avoid this WebSocket limitation.
6000.1.0b4	Fixes Web	Fix	Fixed web browser to not hang when using Autoconnect Profiler with Build and Run, when the Unity project is set to log large amounts of text at web page startup. Note however that there will still exist a platform-specific limitation that only about 45000 log messages can be printed back-to-back at web page startup, or otherwise the message send queue gets full. If more than 45000 log messages need to be printed back to the Editor, they should be done at page runtime after PlayerConnection has initialized, to avoid this WebSocket limitation.
6000.1.0b3	Fixes Web	Fix	Fixed web browser to not hang when using Autoconnect Profiler with Build and Run, when the Unity project is set to log large amounts of text at web page startup. Note however that there will still exist a platform-specific limitation that only about 45000 log messages can be printed back-to-back at web page startup, or otherwise the message send queue gets full. If more than 45000 log messages need to be printed back to the Editor, they should be done at page runtime after PlayerConnection has initialized, to avoid this WebSocket limitation.
6000.1.0b2	Fixes Web	Fix	Fixed web browser to not hang when using Autoconnect Profiler with Build and Run, when the Unity project is set to log large amounts of text at web page startup. Note however that there will still exist a platform-specific limitation that only about 45000 log messages can be printed back-to-back at web page startup, or otherwise the message send queue gets full. If more than 45000 log messages need to be printed back to the Editor, they should be done at page runtime after PlayerConnection has initialized, to avoid this WebSocket limitation.
6000.1.0b1	Fixes Web	Fix	Fixed web browser to not hang when using Autoconnect Profiler with Build and Run, when the Unity project is set to log large amounts of text at web page startup. Note however that there will still exist a platform-specific limitation that only about 45000 log messages can be printed back-to-back at web page startup, or otherwise the message send queue gets full. If more than 45000 log messages need to be printed back to the Editor, they should be done at page runtime after PlayerConnection has initialized, to avoid this WebSocket limitation.
6000.1.0a9	Fixes Web	Fix	Fixed web browser to not hang when using Autoconnect Profiler with Build and Run, when the Unity project is set to log large amounts of text at web page startup. Note however that there will still exist a platform-specific limitation that only about 45000 log messages can be printed back-to-back at web page startup, or otherwise the message send queue gets full. If more than 45000 log messages need to be printed back to the Editor, they should be done at page runtime after PlayerConnection has initialized, to avoid this WebSocket limitation.
6000.1.0a8	Fixes Web	Fix	Fixed web browser to not hang when using Autoconnect Profiler with Build and Run, when the Unity project is set to log large amounts of text at web page startup. Note however that there will still exist a platform-specific limitation that only about 45000 log messages can be printed back-to-back at web page startup, or otherwise the message send queue gets full. If more than 45000 log messages need to be printed back to the Editor, they should be done at page runtime after PlayerConnection has initialized, to avoid this WebSocket limitation.
6000.1.0a7	Fixes Web	Fix	Fixed web browser to not hang when using Autoconnect Profiler with Build and Run, when the Unity project is set to log large amounts of text at web page startup. Note however that there will still exist a platform-specific limitation that only about 45000 log messages can be printed back-to-back at web page startup, or otherwise the message send queue gets full. If more than 45000 log messages need to be printed back to the Editor, they should be done at page runtime after PlayerConnection has initialized, to avoid this WebSocket limitation.
6000.1.0a6	Fixes Web	Fix	Fixed web browser to not hang when using Autoconnect Profiler with Build and Run, when the Unity project is set to log large amounts of text at web page startup. Note however that there will still exist a platform-specific limitation that only about 45000 log messages can be printed back-to-back at web page startup, or otherwise the message send queue gets full. If more than 45000 log messages need to be printed back to the Editor, they should be done at page runtime after PlayerConnection has initialized, to avoid this WebSocket limitation.
6000.1.0a5	Fixes Web	Fix	Fixed web browser to not hang when using Autoconnect Profiler with Build and Run, when the Unity project is set to log large amounts of text at web page startup. Note however that there will still exist a platform-specific limitation that only about 45000 log messages can be printed back-to-back at web page startup, or otherwise the message send queue gets full. If more than 45000 log messages need to be printed back to the Editor, they should be done at page runtime after PlayerConnection has initialized, to avoid this WebSocket limitation.
6000.1.0a4	Fixes Web	Fix	Fixed web browser to not hang when using Autoconnect Profiler with Build and Run, when the Unity project is set to log large amounts of text at web page startup. Note however that there will still exist a platform-specific limitation that only about 45000 log messages can be printed back-to-back at web page startup, or otherwise the message send queue gets full. If more than 45000 log messages need to be printed back to the Editor, they should be done at page runtime after PlayerConnection has initialized, to avoid this WebSocket limitation.
6000.1.0a3	Fixes Web	Fix	Fixed web browser to not hang when using Autoconnect Profiler with Build and Run, when the Unity project is set to log large amounts of text at web page startup. Note however that there will still exist a platform-specific limitation that only about 45000 log messages can be printed back-to-back at web page startup, or otherwise the message send queue gets full. If more than 45000 log messages need to be printed back to the Editor, they should be done at page runtime after PlayerConnection has initialized, to avoid this WebSocket limitation.
6000.1.0a2	Fixes Web	Fix	Fixed web browser to not hang when using Autoconnect Profiler with Build and Run, when the Unity project is set to log large amounts of text at web page startup. Note however that there will still exist a platform-specific limitation that only about 45000 log messages can be printed back-to-back at web page startup, or otherwise the message send queue gets full. If more than 45000 log messages need to be printed back to the Editor, they should be done at page runtime after PlayerConnection has initialized, to avoid this WebSocket limitation.