Page MenuHome

USB Peripherals (keyboard, mouse) disconnect during backing/ other intense task
Closed, ArchivedPublic

Description

System Information
Operating system: Windows 10 Pro
Graphics card: Vega 8 Graphics (On Cpu)

Blender Version
Broken: V2.82
Worked: V2.81

Short description of error

During backing or applying sub division modifiers etc the keyboard and mouse disconnect from computer and require reboot. doesn't happen during render

Exact steps for others to reproduce the error

Bake physics (smoke) / Apply Sub-Division modifier to procedural displaced plane.

Event Timeline

I'm having a similar Problem: Ubuntu 18.04.4 LTS

Title: Keyboard Stops Working [Urgent] Blender 2.82 Unusable
Link: https://developer.blender.org/T74532

Richard Antalik (ISS) changed the task status from Needs Triage to Needs Information from User.Mar 9 2020, 3:23 PM

@emanuel chrysmas (noel), Can you share .blend file? Does this happen every time with provided steps? Does this happen only while using blender?

Also in case your root USB hub is dying (happened to me with almost every PC I had), can you try to disconnect all USB devices, and connect mouse and keyboard to other port like on front panel and see if this still happens?

I don't think this is same as T73507 because all reports there are from linux users.

Its not a specific blend file it happens every time i do as i stated it doesn't happen on 2.81 and i tried disconnecting and re connecting to other ports (including front I/O). and also if you see the previous reply to my post a similar problem happened to a Ubuntu user.

Its not a specific blend file it happens every time i do as i stated it doesn't happen on 2.81 and i tried disconnecting and re connecting to other ports (including front I/O). and also if you see the previous reply to my post a similar problem happened to a Ubuntu user.

Yes that report linked to BlenderKit addon issue.
Are you using that addon?

No, what is blenderkit.

Please add help > save system info & upload.

More than a week without reply or activity.
Due to the policy of the tracker closing for until required info/data are provided.

If the problem persists please open a new report with the required information.