Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to copy from UV and image editors #24

Open
PiorGit opened this issue Oct 19, 2021 · 12 comments
Open

Unable to copy from UV and image editors #24

PiorGit opened this issue Oct 19, 2021 · 12 comments
Assignees
Labels
bug Something isn't working Windows Related to Windows platform

Comments

@PiorGit
Copy link

PiorGit commented Oct 19, 2021

Describe the bug

Hello,
Using Blender 2.91 (Windows) and version ImagePaste 1.8, I seem unable to copy to clipboard an image shown in the UV editor or the Image editor. Here is some footage :

https://youtu.be/4yhi8ad-Nus

Step to reproduce

  • Have an image shown in the UV editor
  • Perform Image > Copy To Clipboard (bpy.ops.imagepaste.imageeditor_copy())
  • It prompts "Unable to copy image"

Relevant log output

No response

Expected behavior

Image should be copied to clipboard (and if needed, saved to the temp location)

Platform

Windows

Platform version

1.8

Blender version

2.91

@PiorGit PiorGit added the bug Something isn't working label Oct 19, 2021
@thanhph111
Copy link
Collaborator

Thank you for your useful video. There're just some details I'd like to know:

  1. Does the error only occur on version 1.8?
  2. I see the images has been saved to the %temp%/blender_a01676 folder in the video. Is that the "temp location" you are expecting, or you want them saved to the directory C:\ you specified in the preferences?
  3. Can you provide us some debug logs from the command window when you encounter the issue? You can open it with Window|Toggle System Console.

@PiorGit
Copy link
Author

PiorGit commented Oct 19, 2021

Hello Thanh,
1 - I have only tried 1.8 so far. Is there a specific older version I should try ?
2 - Regarding the save location : as far as I am concerned this location doesn't matter, it could be anywhere really. Is there a preferred/suggested location, avoiding spaces in the path perhaps ? I can tell that the settings provide quite a few options but things are somewhat unclear and convoluted.
3 - Sure thing. I don't know if the logs can be saved to file, so for lack of a better way here's a screenshot :
https://imgur.com/a/iypxDXn

@b-init
Copy link
Owner

b-init commented Oct 19, 2021

  1. Try 1.7.1

on 3, could you scroll up and get the rest the error?

And could you also tell me the latest version of .NET Framework you have installed? You can check that by entering reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\full" /v version into the command prompt

@PiorGit
Copy link
Author

PiorGit commented Oct 19, 2021

Hello Yeetus,
Here's a full capture after reproducing the error during another session :
https://imgur.com/a/fsVAjI5

The query states : 4.8.03761
(btw, simply typing it directly in the command prompt from anywhere doesn't work by default as reg is located in windows/system32)

I am getting the same error with 1.71.

@thanhph111
Copy link
Collaborator

thanhph111 commented Oct 20, 2021

@Yeetus3141 The first exception raised when setting the default encoding, looks like the $PSDefaultParameterValues is missing, it might come from the incompatible PowerShell version. Although Blender drops Windows 7 support from 2.93, but because the 2.83 is on the LTS, should we still try to maintain it? And what do you think about other error logs?

@PiorGit What is the output of $PSVersionTable from your command line? Can you try logging with the version 1.70? It may prevent the encoding error.

@thanhph111 thanhph111 added the Windows Related to Windows platform label Oct 20, 2021
@b-init
Copy link
Owner

b-init commented Oct 20, 2021

@Yeetus3141 The first exception raised when setting the default encoding, looks like the $PSDefaultParameterValues is missing, it might come from the incompatible PowerShell version. Although Blender drops Windows 7 support from 2.93, but because the 2.83 is on the LTS, should we still try to maintain it? And what do you think about other error logs?

@PiorGit What is the output of $PSVersionTable from your command line? Can you try logging with the version 1.70? It may prevent the encoding error.

I suppose supporting supporting win 7 wouldn't hurt? What would it need?

@PiorGit
Copy link
Author

PiorGit commented Oct 21, 2021

Hello @thanhph111 , @Yeetus3141 ,

  • Regarding "$PSVersionTable" : I do not understand what you mean, please be fully explicit.
  • Here is the log with 1.7.0. The behavior is a bit different here, as there is also an error window being displayed (as opposed to just the red error in the console) :

https://imgur.com/QqN2nSM

https://imgur.com/EsJJIc4

By the way, whenever we get this up and running I would be more than happy to help with the text instructions in the addon settings, as these are quite unclear atm. But that's a different topic of course.

@thanhph111
Copy link
Collaborator

@Yeetus3141 I'm just afraid our current PowerShell methods aren't compatible on Windows 7, but never mind, we should investigate this first.

@PiorGit It's just a command like you entered the reg query earlier in the Windows PowerShell window. BTW, the version 1.7.0 doesn't support unicode filename/filepath so you might see that error because of some special characters in the image name. Can you check that again?

By the way, whenever we get this up and running I would be more than happy to help with the text instructions in the addon settings, as these are quite unclear atm. But that's a different topic of course.

Glad to know that. I opened #26 for further discussions. The description hasn't been added yet but I will update soon.

@PiorGit
Copy link
Author

PiorGit commented Oct 21, 2021

Hello -
FWIW, I also just tested out the latest version on a win10 machine with Blender 2.91 and I am getting the same error with this setup as the one initially reported in this thread. So perhaps this can help narrowing down the issue.

My test process consists of first attempting the action (copying from the UV/Image editor) with all the settings left as default, and then trying again with the forced folder location set to the desktop. So if you have any suggestion for a barebones, foolproof action I could reproduce by all means let me know.

@thanhph111
Copy link
Collaborator

@PiorGit So the issue also occurs on the Windows 10, it might be caused by some specific setup, but I don't think the folder location is the cause. Can you collect logs again on Windows 10? And a GIF recorded from Blender startup can be helpful, too. You can directly upload it here.

@PiorGit
Copy link
Author

PiorGit commented Oct 23, 2021

Hello -
Absolutely, I will test this out asap.
On an different note : I was working on an unrelated project today and after creating a new folder to save a .blend file in as well as some FBX exports, I've noticed that an "ImagePaste" folder appeared there out of nowhere without any instruction from me to do so. So there is definitely something odd going on with that too.

@PiorGit
Copy link
Author

PiorGit commented Oct 24, 2021

Here's a win10 log of the issue :
https://imgur.com/PgWKqCL

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Windows Related to Windows platform
Projects
None yet
Development

No branches or pull requests

3 participants