Drag-and-Droping images only works on first Blender start #45951

New Issue

mathieu menuet · 2015-08-29T16:35:47+02:00

mathieu menuet commented

2015-08-29 16:35:47 +02:00

System Information
Windows 7 x64

Blender Version
Broken: c749fe4

Short description of error
When making file -> new after first start, D&D of images doesn't open it as background image anymore

Exact steps for others to reproduce the error
Start Blender, hit ctrl+N and enter, drag and drop an image in the 3D view from explorer, no background images is created.
Strangely, it works perfectly many times only on first blender start.
Can't attach a test blend file in this case as it's triggered by file ->new

**System Information** Windows 7 x64 **Blender Version** Broken: c749fe4 **Short description of error** When making file -> new after first start, D&D of images doesn't open it as background image anymore **Exact steps for others to reproduce the error** Start Blender, hit ctrl+N and enter, drag and drop an image in the 3D view from explorer, no background images is created. Strangely, it works perfectly many times only on first blender start. Can't attach a test blend file in this case as it's triggered by file ->new

mathieu menuet commented

2015-08-29 16:35:47 +02:00

Changed status to: 'Open'

mathieu menuet commented

2015-08-29 16:35:47 +02:00

Added subscriber: @bliblubli

Julian Eisel commented

2015-08-29 19:39:44 +02:00

Added subscriber: @JulianEisel

Julian Eisel commented

2015-08-29 19:39:44 +02:00

Working totally fine here.

Bastien Montagne commented

2015-08-29 21:45:43 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2015-08-29 21:45:43 +02:00

Works OK here as well (linux though). Can you please:

Give us your exact Blender, OS and GPU versions, as requested in the template!
Ensure both your OS and drivers are fully up-to-date.
For Windows 7, at least service pack 1 is mandatory, please ensure it is installed on your machine.
Try the latest build from our buildbot.
Try to start Blender in factory settings (--factory-startup commandline option) (this will ensure whether this is a userpref or addon issue or not).
Launch Blender from the command line with -d option and attach here any error printed out in the console.

Works OK here as well (linux though). Can you please: * Give us your exact Blender, OS and GPU versions, as requested in the template! * Ensure both your OS and drivers are fully up-to-date. * For Windows 7, at least service pack 1 is mandatory, please ensure it is installed on your machine. * Try the latest build from [our buildbot](https://builder.blender.org/download). * Try to start Blender in factory settings (`--factory-startup` commandline option) (this will ensure whether this is a userpref or addon issue or not). * Launch Blender from the command line with `-d` option and attach here any error printed out in the console.

Aaron Carlisle commented

2015-08-29 22:36:00 +02:00

Added subscriber: @Blendify

Aaron Carlisle commented

2015-08-29 22:36:00 +02:00

works fine here on windows 8.0 w/ Intel card

mathieu menuet commented

2015-09-01 21:12:36 +02:00

In #45951#331295, @mont29 wrote:
Works OK here as well (linux though). Can you please:

Give us your exact Blender, OS and GPU versions, as requested in the template!

Blender 2.75 hash c749fe4, Win 7 x64 SP1, AMD R9 280X with catalyst 15.7.1 (latest)

Ensure both your OS and drivers are fully up-to-date.

For Windows 7, at least service pack 1 is mandatory, please ensure it is installed on your machine.

Try the latest build from our buildbot.

always the case

Try to start Blender in factory settings (--factory-startup commandline option) (this will ensure whether this is a userpref or addon issue or not).

Launch Blender from the command line with -d option and attach here any error printed out in the console.

I did it, here is the log:

drop file C:\Users\test\Desktop\Pixar128 Library\converted2\Alloy_diamond_plate_pxr128.jpg
read file C:\Users\test\AppData\Roaming\Blender Foundation\Blender\2.75\config\startup.blend
  Version 275 sub 4 date 2015-08-21 07:48 hash 59e166c

ordered
 OBCube
 OBLamp
 OBCamera
read file C:\Users\test\AppData\Roaming\Blender Foundation\Blender\2.75\config\userpref.blend
  Version 275 sub 4 date 2015-08-21 15:18 hash dc40670
Read new prefs: C:\Users\test\AppData\Roaming\Blender Foundation\Blender\2.75\config\userpref.blend
AL lib: (EE) UpdateDeviceParams: Failed to set 44100hz, got 48000hz instead
drop file C:\Users\test\Desktop\Pixar128 Library\converted2\Alloy_diamond_plate_pxr128.jpg

Which showed me that you have to first D&D an image, then file->new, then D&D an image again. If you directly create a new file without having done any D&D, the bug doesn't trigger.

> In #45951#331295, @mont29 wrote: > Works OK here as well (linux though). Can you please: > * Give us your exact Blender, OS and GPU versions, as requested in the template! Blender 2.75 hash c749fe4, Win 7 x64 SP1, AMD R9 280X with catalyst 15.7.1 (latest) > * Ensure both your OS and drivers are fully up-to-date. > * For Windows 7, at least service pack 1 is mandatory, please ensure it is installed on your machine. > * Try the latest build from [our buildbot](https://builder.blender.org/download). always the case > * Try to start Blender in factory settings (`--factory-startup` commandline option) (this will ensure whether this is a userpref or addon issue or not). > * Launch Blender from the command line with `-d` option and attach here any error printed out in the console. I did it, here is the log: ``` drop file C:\Users\test\Desktop\Pixar128 Library\converted2\Alloy_diamond_plate_pxr128.jpg read file C:\Users\test\AppData\Roaming\Blender Foundation\Blender\2.75\config\startup.blend Version 275 sub 4 date 2015-08-21 07:48 hash 59e166c ordered OBCube OBLamp OBCamera read file C:\Users\test\AppData\Roaming\Blender Foundation\Blender\2.75\config\userpref.blend Version 275 sub 4 date 2015-08-21 15:18 hash dc40670 Read new prefs: C:\Users\test\AppData\Roaming\Blender Foundation\Blender\2.75\config\userpref.blend AL lib: (EE) UpdateDeviceParams: Failed to set 44100hz, got 48000hz instead drop file C:\Users\test\Desktop\Pixar128 Library\converted2\Alloy_diamond_plate_pxr128.jpg ``` Which showed me that you have to first D&D an image, then file->new, then D&D an image again. If you directly create a new file without having done any D&D, the bug doesn't trigger.

Aaron Carlisle commented

2015-09-01 21:33:13 +02:00

sometimes i do this and it shows up and sometimes it does not

mathieu menuet commented

2015-09-01 22:17:41 +02:00

then it maybe one of those nasty cmake bugs (random bugs happens since the switch from scons to cmake in buildbots) :( but for me it's pretty reproducible, every time actually so far.

Aaron Carlisle commented

2015-09-01 22:19:36 +02:00

well if you think it is related to cmake try the 2.75a release because that was still built with scons afaik

Julian Eisel commented

2015-09-01 22:53:38 +02:00

Please, stop spreading around that cmake is the reason for some weird bugs or so. Technically this is pretty unlikely. There are much more differences between buildbot and release build configurations and much more variables that could cause some weird glitches. In fact I guess CMake builds are more stable, since most (actually almost all) developers use CMake.
So again: As long as there is no technical proof, please don't spread such myths, this just causes trouble for us for the final switch to CMake.

Please, stop spreading around that cmake is the reason for some weird bugs or so. Technically this is pretty unlikely. There are much more differences between buildbot and release build configurations and much more variables that could cause some weird glitches. In fact I guess CMake builds are more stable, since most (actually almost all) developers use CMake. So again: As long as there is no technical proof, please don't spread such myths, this just causes trouble for us for the final switch to CMake.

mathieu menuet commented

2015-09-02 19:32:59 +02:00

I agree to not spread wrong things, but do you use Blender 8 hours a day or more on heavy projects using a lot of Blender functions and data types on Windows ? I mean, people reporting those bugs that are random are not kids playing around or some casual users. Aaron seems to be a long time user also. So if he says it is random on it's computer, I think we can believe him just like Marco and me?

Oh well, I don't care if your find your strong guess/theory stronger that long time user practice, I build myself with Scons, so do what you want with your userbase. I'll not bother anymore.

I agree to not spread wrong things, but do you use Blender 8 hours a day or more on heavy projects using a lot of Blender functions and data types on Windows ? I mean, people reporting those bugs that are random are not kids playing around or some casual users. Aaron seems to be a long time user also. So if he says it is random on it's computer, I think we can believe him just like Marco and me? Oh well, I don't care if your find your strong guess/theory stronger that long time user practice, I build myself with Scons, so do what you want with your userbase. I'll not bother anymore.

Aaron Carlisle commented

2015-09-02 19:48:55 +02:00

can a developer try this on windows because most likely this is only reproducible on windows

mathieu menuet commented

2015-09-02 21:44:15 +02:00

In #45951#331918, @Blendify wrote:
well if you think it is related to cmake try the 2.75a release because that was still built with scons afaik

The bug doesn't show up on 2.75a (tested twice), but I thought it is build with c-make?

> In #45951#331918, @Blendify wrote: > well if you think it is related to cmake try the 2.75a release because that was still built with scons afaik The bug doesn't show up on 2.75a (tested twice), but I thought it is build with c-make?

mathieu menuet commented

2015-09-02 21:46:24 +02:00

yep bpy.app.build_system on 2.75a gives 'CMake', so in this case at least, it seems to not be due to Cmake. I apologies for the bad accusation.

mathieu menuet commented

2015-09-02 21:52:27 +02:00

well I tried again on latest buildbot and sometime it triggers, sometime not... so, no idea.

Julian Eisel commented

2015-09-02 22:02:46 +02:00

@bliblubli,
I never said I don't believe you, nor do I think someone lies to me about this... why should one? There are just technical issues with your assertion: Technically, it doesn't make sense to blame CMake for this, or similar randomly appearing issues. CMake doesn't have an influence on run-time, only on compile-time. Of course you can never be sure with computers - there is always this 1% of probability - but there are a hundred of other variables that are much more likely to cause such trouble, so blaming CMake in the first place is technical non-sense.

As you said, you are a user, and for you these things may not be so obvious as they are to us. No issue with that. But just as we need to trust you when you tell us about random crashes, you have to trust us when we say that it doesn't make much sense to blame CMake for anything here.

All I ask for is if you could do us a flavor by not telling people that CMake causes these issues.
In such a big & active community, we all have to be careful with what we're saying. Misunderstanding, confusion and wrong knowledge is easy to create, but hard to undo. Well... I guess you get what I mean ;)

@bliblubli, I never said I don't believe you, nor do I think someone lies to me about this... why should one? There are just technical issues with your assertion: Technically, it doesn't make sense to blame CMake for this, or similar randomly appearing issues. CMake doesn't have an influence on run-time, only on compile-time. Of course you can never be sure with computers - there is always this 1% of probability - but there are a hundred of other variables that are much more likely to cause such trouble, so blaming CMake in the first place is technical non-sense. As you said, you are a user, and for you these things may not be so obvious as they are to us. No issue with that. But just as we need to trust you when you tell us about random crashes, you have to trust us when we say that it doesn't make much sense to blame CMake for anything here. All I ask for is if you could do us a flavor by not telling people that CMake causes these issues. In such a big & active community, we all have to be careful with what we're saying. Misunderstanding, confusion and wrong knowledge is easy to create, but hard to undo. Well... I guess you get what I mean ;) </off-topic>

Campbell Barton commented

2015-09-08 20:26:16 +02:00

Added subscriber: @ideasman42

Campbell Barton commented

2015-09-08 20:26:16 +02:00

Tested on windows7, cant redo.

@bliblubli. Could you record a video of the error?

I realize its some effort, but its hard to fathom how this can happen and would be interested to see exact steps.

Tested on windows7, cant redo. @bliblubli. Could you record a video of the error? I realize its some effort, but its hard to fathom how this can happen and would be interested to see exact steps.

mathieu menuet commented

2015-09-08 21:56:50 +02:00

Here is a video, without cursor sorry, seems to be a limitation of Gifcam, but I D&D the image selected in viewport (and wait every time to ensure the little + is visible near the cursor)

Sometime it takes 20 trial to happen, sometime it just happen on second one...
Here is the image, also I don't think it matters.

Here is a video, without cursor sorry, seems to be a limitation of Gifcam, but I D&D the image selected in viewport (and wait every time to ensure the little + is visible near the cursor) ![bug d and d image blender.gif](https://archive.blender.org/developer/F231532/bug_d_and_d_image_blender.gif) Sometime it takes 20 trial to happen, sometime it just happen on second one... Here is the image, also I don't think it matters. ![Blue_glazed_pxr128_bmp.jpg](https://archive.blender.org/developer/F231534/Blue_glazed_pxr128_bmp.jpg)

mathieu menuet commented

2015-09-08 22:07:46 +02:00

Found it!!! ... I guess... If you drop the image on/near the sun or cube, or sun dashed light ray (the threshold is unclear) it doesn't work, so it's not random actually. Don't know if it's a wanted behavior, but on normal scenes full of objects or with a terrain, it can't work anymore with this behavior. (because there is no "void" space anymore) So it's not really a good Idea I think.

Bastien Montagne commented

2015-09-08 23:02:54 +02:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2015-09-08 23:02:54 +02:00

Bastien Montagne self-assigned this 2015-09-08 23:02:54 +02:00

Bastien Montagne commented

2015-09-08 23:02:54 +02:00

Well, yes, that’s totally intended behavior from code - when you drag'n'drop, if you drop over an object it calls a different operation (e.g. over a mesh it assigns the dragged image to its UVMap…). May not be always optimal, but no bug here.

mathieu menuet commented

2015-09-09 08:03:15 +02:00

If that would be the case, that would be great, but when I D&D an image on the cube, it does nothing. The image is not available in the image/UV Editor.

Campbell Barton commented

2015-09-09 09:52:42 +02:00

Note that we could have dropping report in the header what happens.

"Assigned image to lamp", "Added background image".

Its not so obvious for eg, what happens when you drop an image into the perspective view.

Note that we could have dropping report in the header what happens. *"Assigned image to lamp"*, *"Added background image"*. Its not so obvious for eg, what happens when you drop an image into the perspective view.

mathieu menuet commented

2015-09-09 19:26:52 +02:00

Good Idea. A text or visual feedback, would really help to understand and ensure the work has been done properly.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Drag-and-Droping images only works on first Blender start #45951