Another thing that is very useful is to hold down Ctrl and the Middle Mouse Button to rescale various panels. This is the same for the 3D Viewport when zooming in or out to view a model. The Outliner Area is the only place I've found so far where this does not function yet.
By pressing the HOME key on your keyboard, you can reset the resized panels back ...
I found the solution, right click on the blender shortcut>Run with Graphics Processor>Integrated Graphics. It should run smooth when you do that. No need to roll back any graphics drivers, just use your integrated graphics to model and you can still set your 960m to render in the settings.
In case you are not able to see the option, Open NVIDIA Control ...
The last version of blender that was officially compatible with Windows XP was blender 2.76. Versions after that probably won't work. You can download previous version of blender here.
To quote Martijn Berger (a blender developer) from here on why support for XP was dropped:
We implicitly dropped Windows XP when switching to python 3.5. Python
has the ...
The answer courtesy of fmb501 at blenderartists (thread here) :
This appears to be a bug in the Blender installer, but the fix is
Open the Windows icon in the bottom left corner of your computer
display and search for "command prompt"
Right click on the result and select "run as administrator."
There will be a small ...
I don't have enough reputation to comment on Sam's post, but he's right. I wanted to stream a game last night and downloaded Nvidia's Geforce Experience for Shadowplay (which updated a driver). Opened Blender this morning and had the same issues (extremely delayed input). Rolled back the driver and working fine again!
I think the best way to find out is to try it yourself ;)
Something you can do to ensure your render progress is not lost is to render to an image sequence instead of directly to a video file. See the docs:
The Direct Approach—highly not recommended and not a standard
practice—is where you set your output format to an AVI or MOV format,
It is commonly said that performance is generally faster under Linux based operating systems, both during regular program operation and rendering.
Linux is also commonly said to consume less resources than other operating systems, leaving more available memory and processing power available for applications to use.
According to this recent article's ...
More than likely the problem is that your startup.blend and or userpref.blend file was corrupted. To fix this, just navigate to the user settings directory and delete them.
On Windows, the directory is located at
C:\Users\USER_NAME\AppData\Roaming\Blender Foundation\Blender\2.xx\config. See this post for more information on how to locate this directory on ...
I marked the first correct answer as accepted. This is indeed a problem with network drives. But it seems I found a workaround, so I post it here.
The workaround removes all network drives from Blender, so it doesn't hang while trying to access them. It will also kill the possibility to save / load files to network drives in Blender. I do not need this ...
While this is a harmless error, this is how you can fix it:
Open user preferences with
Ctrl+Alt+U and go to the System tab
In the sound settings below, change the sample rate to 48000 kHz and
save user settings
Assuming your windows are fairly regularly spaced you can separate the individual 'windows' in the window material by using a Modulo function to convert each of the X,Y,Z Object coordinates into a 'stepped' function. This separates the surface into individual 'cells'. By carefully setting the spacing of the 'cells' (the Modulo functions) to match the ...
If you are using CUDA rendering, Linux is faster by 20-40% due to the overhead of WDDM in Windows 8/10. This is regardless of if there is a display plugged into the GPU or not.
To work around the issue on Windows, you have to set your Nvidia Card to Tesla Compute Mode(TCC), which is only supported on Titan and Quadro class cards.
The threading module should take care of it. Just create a separate python thread and run your blocking code (e.g. networking code) in there.
thread = Worker(None)
def __init__(self, args):
self.args = args
From the blender 2.62 release notes
For renders where only the camera or materials are changing, while meshes stay fixed, it is now possible to skip the sometimes slow BVH step, by enabling BVH Cache in the Performance panel. This will store the BVH on disk for subsequent (animation) renders of the same scene. Note that if the scene does change in the ...
How about making a .bat file which will open blender and load a python script, which will load your object? I've made a little proof of concept.
First, the python script. Save it somewhere. It could be next to the .bat file.
pathToImport = sys.argv[-1]
It looks like it is having issues with the audio configuration.
Go to where Blender is installed in the Windows Explorer. The Default Installation Path is C:\Program Files\Blender Foundation\Blender.
When inside the Blender Folder, hold down the Shift key, and right-click any folder inside the Blender Folder (the 2.74 folder will work just fine), then ...
No it doesn't modify your system, provided you are using the self-contained .zip version.
The self-contained .zip version is just that, self-contained. It will - of course - put data where-ever you tell it to. Animation output or other temporary files will be written where you tell Blender to put them. Temporary files (in C:\tmp\ by default) are deleted ...
Yes. Blender 2.75a works in Windows 10.
But I had some trouble making it work. After the upgrade from W8.1 to W10 it didn't work, but it was a problem of the new windows not having the correct drivers.
I didn't have to spend much time working it out. Windows 10 did, after some time and a few reboots, offer to install the correct drivers. That fixed most ...
If i had to guess, from your description I would say it is Blender trying to access some unreachable place. Such behavior seems to be connected to disk reading activity, like when opening or browsing for a file or location.
I've had a similar problem a while ago when I had a faulty DVD drive installed in my computer. I later came to find out that ...
Have the same computer specs on a Dell 7559. Had the same problem when I updated the NVidia drivers to the recent Geforce Experience ver 376.09. I finally uninstalled this driver and went back to the ver 375.95 and things are back to working. Hope this helps!
The Release Candidate seems to be only released as a zip file. This can be unzipped wherever you want and run from the folder, it doesn't need to install.
If you download the latest official release of Blender, currently 2.70, then you have the option of either downloading a regular installer or a zip again.
This is a very unfortunate glitch, at the moment has no nice solution. Both Blender and Python devs are aware of it.
The problem is with importing uuid (which requests happens to use).
For now, you can workaround this by temporarily disabling ctypes with the uuid module.