Can't connect to Blender from a distant machine anymore #71459

Closed
opened 2019-11-09 20:15:14 +01:00 by Samuel · 8 comments

System Information
Operating system: Windows 10
Graphics card: Nvidia GTX 1070

Blender Version
Broken: 2.8
Worked: 2.79

Short description of error
Hey, I used to stream Blender from my main rig to a remote laptop, but can't do that anymore.
(My main rig is connected to internet pretty much 24/7, and I use my laptop to connect remotly to it, and use like apps ... Through steam).
This used to work on previous versions of Blender, but I can't get it to work anymore. It only shows fully white screen - both through steam streaming or through teamviewer.

I just tested Blender 2.79, and that one doesn't work neither. I have tried hardware encoding on and off, that didn't solve it.

Exact steps for others to reproduce the error
Run blender on a remote machine, that should do it.

**System Information** Operating system: Windows 10 Graphics card: Nvidia GTX 1070 **Blender Version** Broken: 2.8 Worked: 2.79 **Short description of error** Hey, I used to stream Blender from my main rig to a remote laptop, but can't do that anymore. (My main rig is connected to internet pretty much 24/7, and I use my laptop to connect remotly to it, and use like apps ... Through steam). This used to work on previous versions of Blender, but I can't get it to work anymore. It only shows fully white screen - both through steam streaming or through teamviewer. I just tested Blender 2.79, and that one doesn't work neither. I have tried hardware encoding on and off, that didn't solve it. **Exact steps for others to reproduce the error** Run blender on a remote machine, that should do it.
Author

Added subscriber: @Mahrkeenerh

Added subscriber: @Mahrkeenerh

Added subscriber: @grosgood

Added subscriber: @grosgood
Garry R. Osgood self-assigned this 2019-11-11 21:19:08 +01:00

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

I use my laptop to connect remotely to it, and use like apps ... Through steam

Hi Samuel,
Alas, we can't fix the World. The little piece of it that we try to keep in order is (mostly) the source code for Core Blender (the application itself, and some key add-ons), so that it compiles into a binary that some operating system like Windows can start up and connect to the local computer hardware - so that when people use Blender, it behaves in ways that more or less conform to descriptions in user manuals. Yes, people run Blender in virtual containers or use streaming software to project Blender - or other applications like games - to remote systems. These kinds of tools interact with the operating system; applications like Blender are unaware that some other agent is projecting whatever the computer is doing over a network, or that the hardware the operating system thinks it has is actually a container virtualized construct.

Streaming and virtualization services are just outside of our World. Sorry. I wish I could write you a better answer, but I can't. We don't have direct control over these tools work and can't change how they interact with Blender. I suggest you visit one of the websites in the Blender Community where people do use Blender in these environments. Perhaps someone there can help you with pointers.

I'm archiving this report for future reference. If you are new to reporting bugs about Blender, I recommend How to Report a Bug in 5 Steps - Blender by Pablo Vazquez. Take care!


>> I use my laptop to connect remotely to it, and use like apps ... Through steam Hi Samuel, Alas, we can't fix the World. The little piece of it that we try to keep in order is (mostly) the source code for Core Blender (the application itself, and some key add-ons), so that it compiles into a binary that some operating system like Windows can start up and connect to the local computer hardware - so that when people use Blender, it behaves in ways that more or less conform to descriptions in user manuals. Yes, people run Blender in virtual containers or use streaming software to project Blender - or other applications like games - to remote systems. These kinds of tools interact with the operating system; applications like Blender are unaware that some other agent is projecting whatever the computer is doing over a network, or that the hardware the operating system thinks it has is actually a container virtualized construct. Streaming and virtualization services are just outside of our World. Sorry. I wish I could write you a better answer, but I can't. We don't have direct control over these tools work and can't change how they interact with Blender. I suggest you visit one of the websites in the [Blender Community ](https://www.blender.org/community/) where people do use Blender in these environments. Perhaps someone there can help you with pointers. I'm archiving this report for future reference. If you are new to reporting bugs about Blender, I recommend [How to Report a Bug in 5 Steps - Blender ](https://www.youtube.com/watch?v=JTD0OJq_rF4) by Pablo Vazquez. Take care! ``` ```
Author

The thing is, I tried talking to steam about this, and they said it's blender's responsibility, and they can't do anything about it.
This is basically throwing the problem around and putting your hands off it.

I understand you can't do anything about this, but who can ??

The thing is, I tried talking to steam about this, and they said it's blender's responsibility, and they can't do anything about it. This is basically throwing the problem around and putting your hands off it. I understand you can't do anything about this, but who can ??

they said it's blender's responsibility

The difficulty is with the word "it", Given the circumstances stated thus far in this bug report, this pronoun "it" represents a fairly vague set of circumstances - too vague in which to begin an investigation to isolate fault. In terms of detail, this bug report is on the level of "I lost my car keys in Central Park." What is needed is more precise information on time and place. The art of bug reporting entails narrowing the realm of possible search areas with specific facts that eliminate places to look, and the bug reporter's efforts along those lines actually represents a material contribution to the project - and to solving the bug.

Here is a brief example of this narrowing down of the realm of possibility. Blender 2.79 used to work, according to your report. Now, Blender 2.79 doesn't work. What changed? Certainly not Blender 2.79. It has been frozen; the team's effort has been on the 2.8x series. That something changed is undeniable, but Blender 2.79 has been in a static state for some time now. This points to other areas of investigation outside of Blender.

Some things to consider: Has a Windows update happened recently? If so, can you narrow it down to a specific update? Ditto Steam? Any changes in how you use the software? Any changes to hardware? Consider going to blenderartists.org or other community groups and posting the problem there, perhaps other people have experienced similar problems. Their experiences can furnish facts to help narrow the search field.

Bug reporting actually is a lot of work. But if that work isolates a tractable problem area in the realm of Blender's responsibility, I'll be happy to open up this report again with the specifics you provide. But they have to be specifics - the kind of particulars which isolate areas of search and correction. In the end, that hard work will make Blender a better product and we'll thank you for your time and effort, which will be a good and valuable contribution to the project. Thank you for taking the time for reading this. Take care.

> they said **it's** blender's responsibility The difficulty is with the word "it", Given the circumstances stated thus far in this bug report, this pronoun "it" represents a fairly vague set of circumstances - too vague in which to begin an investigation to isolate fault. In terms of detail, this bug report is on the level of "I lost my car keys in Central Park." What is needed is more precise information on time and place. The art of bug reporting entails narrowing the realm of possible search areas with specific facts that eliminate places to look, and the bug reporter's efforts along those lines actually represents a material contribution to the project - and to solving the bug. Here is a brief example of this narrowing down of the realm of possibility. Blender 2.79 used to work, according to your report. Now, Blender 2.79 doesn't work. What changed? Certainly not Blender 2.79. It has been frozen; the team's effort has been on the 2.8x series. That something changed is undeniable, but Blender 2.79 has been in a static state for some time now. This points to other areas of investigation outside of Blender. Some things to consider: Has a Windows update happened recently? If so, can you narrow it down to a specific update? Ditto Steam? Any changes in how you use the software? Any changes to hardware? Consider going to blenderartists.org or other community groups and posting the problem there, perhaps other people have experienced similar problems. Their experiences can furnish facts to help narrow the search field. Bug reporting actually is a lot of work. But if that work isolates a tractable problem area in the realm of Blender's responsibility, I'll be happy to open up this report again with the **specifics** you provide. But they have to be specifics - the kind of particulars which isolate areas of search and correction. In the end, that hard work will make Blender a better product and we'll thank you for your time and effort, which will be a good and valuable contribution to the project. Thank you for taking the time for reading this. Take care.
Author

I think I have found the core of the problem.

Some time ago (a few days), I bumped to a problem of not being able to change the brightness of my monitor. Looked through youtube, it took me about a week, but I found the solution. TeamViewer. I have changed something about it - that it should start on windows launch, and I also installed some black monitor driver thing.

So, after I installed it, I couldn't change the brightness, and it appears I couldn't connect to blender either (hence the white only screen). I found out the solution, changed back to my old monitor driver (so I fixed the brightness issue), and today I tried connecting to Blender one more time - why not. It worked. So every problem was just the TeamViewer's fault.

If you need any info regarding this, I will be happy to provide to my limits.

Hope this helped someone else as well. Have a nice day

I think I have found the core of the problem. Some time ago (a few days), I bumped to a problem of not being able to change the brightness of my monitor. Looked through youtube, it took me about a week, but I found the solution. TeamViewer. I have changed something about it - that it should start on windows launch, and I also installed some black monitor driver thing. So, after I installed it, I couldn't change the brightness, and it appears I couldn't connect to blender either (hence the white only screen). I found out the solution, changed back to my old monitor driver (so I fixed the brightness issue), and today I tried connecting to Blender one more time - why not. It worked. So every problem was just the TeamViewer's fault. If you need any info regarding this, I will be happy to provide to my limits. Hope this helped someone else as well. Have a nice day

Great! Thank you for sharing the results of your work. There is this post at the TeamViewer's blog that may be of interest: [Gray screen instead of app interface when opened via TeamViewer ]], A Blender user that had similar experiences and may be of use to other people. If time permits, you might consider posting your solution in a high traffic Blender site such as [https:*blenderartists.org/c/support/technical-support | Blender Artists Technical Support Forum . You can link back to your report here and save repeating yourself. Thanks in advance for sharing the knowledge!

Great! Thank you for sharing the results of your work. There is this post at the TeamViewer's blog that may be of interest: [Gray screen instead of app interface when opened via TeamViewer ]], A Blender user that had similar experiences and may be of use to other people. If time permits, you might consider posting your solution in a high traffic Blender site such as [[https:*blenderartists.org/c/support/technical-support | Blender Artists Technical Support Forum ](https:*community.teamviewer.com/t5/General-Questions/Gray-screen-insted-of-app-interface-wnen-opened-via-TeamViewer/m-p/68943#M31535). You can link back to your report here and save repeating yourself. Thanks in advance for sharing the knowledge!
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#71459
No description provided.