# \[IGN-14525\]Ignition v8.3.1 Vision Client - Buffering Capacity Exceeded Error

**URL:** <https://forum.inductiveautomation.com/t/ign-14525-ignition-v8-3-1-vision-client-buffering-capacity-exceeded-error/112595>\
**Category:** Ignition\
**Tags:** vision, ignition83\
**Created:** [December 3, 2025, 3:42pm UTC](https://forum.inductiveautomation.com/t/ign-14525-ignition-v8-3-1-vision-client-buffering-capacity-exceeded-error/112595 "2025-12-03T15:42:18Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [December 3, 2025, 4:09pm UTC](https://forum.inductiveautomation.com/t/ign-14525-ignition-v8-3-1-vision-client-buffering-capacity-exceeded-error/112595/2 "2025-12-03T16:09:49Z")

</div>

Probably the same problem and fix as in the Designer:

> [@Error when trying to read custom device tags](https://forum.inductiveautomation.com/t/error-when-trying-to-read-custom-device-tags/110948/2):
>
> You can set -Dignition.designer.websocketMaxBinaryMessageSize=4096 (default value is 2048) in your designer launcher configuration: This raises the maximum message size the designer will accept, which should allow you to get past this issue for testing. In some near future release (possibly as early as 8.3.1, potentially later) we're going to change the way large notification messages are delivered to the client/designer to help work around this issue as a stopgap. In some farther f…

---

_[View the full topic](https://forum.inductiveautomation.com/t/ign-14525-ignition-v8-3-1-vision-client-buffering-capacity-exceeded-error/112595)._
