wxWidget Debug Error

[dj_buckley]

The native one in windows called 'Remote Desktop'.

In answer to your second question.  I wouldn't know.  It's happening on one particular node and I only ever connect to that node through Remote Desktop.  It's just sat in the corner of the room with no monitor or peripherals.  I have another node that I also connect to through Remote Desktop and I've not seen the error on that node.

The problematic node is a Threadripper 3990x running Windows 11.  The other node AND my main workstation are both Intel i9's running Windows 10 if that helps.  Although I should stress I've been using this setup for years with no issues, it's only since upgrading to Corona 11 and now Corona 11 Hotfix 1 that I've started encountering the issue.

[maru]

Unfortunately, I don't think we can help if we don't reproduce the error. If you can share any scene where it has appeared at least once, please do.
Other than that, it will be most likely fixed with the new VFB, which is planned to be a part of Corona 12.

[dj_buckley]

it will be most likely fixed with the new VFB, which is planned to be a part of Corona 12.

Afraid not

[dj_buckley]

This is really bugging me now.  C12 and the new VFB rewrite have not fixed this issue at all.  I can't be the only one experiencing it

[Avi]

Hi,

Can you share more details about your network setup? Are you using any specific network/firewall settings on the windows 11 machine?

[dj_buckley]

Nothing specific at all.

I have a workstation and 2 nodes.  They're all plugged into a network switch.  All reading from a NAS which is also plugged into the switch.  The switch is directly connected to the modem/router.

[dj_buckley]

Here's the error again if it helps, it just happened again now, although this error seems different compared to the first one I posted when I started the thread

[dj_buckley]

I just uploaded a scene for a different thread Request #312794

It just so happens that this issue has also just appeared on that file.