Smoke (both quick effect or "standard") - Immediate Crash #48455

Closed
opened 2016-05-17 13:42:00 +02:00 by Luca Crisi · 8 comments

System Information
Windows 8.1, nVidia GT740

Blender Version
Broken: 2.77a
Worked: 2.76

Short description of error
Smoke (both quick effect or "standard") - Immediate Crash on effect selection

Exact steps for others to reproduce the error
ANY file, even the simplest startup with a default Cube.
1 - Select the cube
2 - Object / Quick Effects / Smoke

BOOM! crash


By the way, since I'm here (should I open another BugReport, for this one?)...

What's the sense in writing all those stupid empty (!!) files called OGLdpf.log?!
I find it really useless. And they take space on my hard disk (they allocate at least one full cluster size).

Not only, they also generate an unnecessary disk write, compromising my defragmentation,
since I always delete them manually.

So... WHY does Blender write them?!
What's their purpose, other than breaking my nerves?
Since they are ALWAYS EMPTY, no info is written in them... I really hate them.

**System Information** Windows 8.1, nVidia GT740 **Blender Version** Broken: 2.77a Worked: 2.76 **Short description of error** Smoke (both quick effect or "standard") - Immediate Crash on effect selection **Exact steps for others to reproduce the error** ANY file, even the simplest startup with a default Cube. 1 - Select the cube 2 - Object / Quick Effects / Smoke BOOM! crash --- By the way, since I'm here (should I open another BugReport, for this one?)... What's the sense in writing all those stupid **empty** (!!) files called **OGLdpf.log**?! I find it really useless. And they take space on my hard disk (they allocate at least one full cluster size). Not only, they also generate an unnecessary disk write, compromising my defragmentation, since I always delete them manually. So... WHY does Blender write them?! What's their purpose, other than breaking my nerves? Since they are ALWAYS EMPTY, no info is written in them... I really hate them.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @BugFinder

Added subscriber: @BugFinder

Added subscriber: @Sergey

Added subscriber: @Sergey

Does the crash happen with the latest builds from builder.blender.org?

Ad for the OGLdpf.log -- it's not a blender fault, see discussions in the internet, such as https://www.reddit.com/r/Surface/comments/20sljo/oglpdflog/

Does the crash happen with the latest builds from builder.blender.org? Ad for the `OGLdpf.log` -- it's not a blender fault, see discussions in the internet, such as https://www.reddit.com/r/Surface/comments/20sljo/oglpdflog/
Author

MY FAULT, sorry!
THIS TIME is really NOT A BUG - Can you remove it for me?

Note on why that happened.

After updating the nVidia drivers (you normally think it's a good thing to kee them up to date), the Windoes settings were reset to their default, NON OPTIMIZED configuratio.

Re-setting them properly in the nVidia Control Panel solved the issue.

Not sure WHY these settings affected the 3D ViewPort, though.

Again, THIS TIME (steressed: THIS TIME) it's REALLY NOT A BUG.

Thank you

MY FAULT, sorry! THIS TIME is really NOT A BUG - Can you remove it for me? Note on why that happened. After updating the nVidia drivers (you normally think it's a good thing to kee them up to date), the Windoes settings were reset to their default, NON OPTIMIZED configuratio. Re-setting them properly in the nVidia Control Panel solved the issue. Not sure WHY these settings affected the 3D ViewPort, though. Again, THIS TIME (steressed: THIS TIME) it's REALLY NOT A BUG. Thank you

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Sergey Sharybin self-assigned this 2016-05-17 15:38:51 +02:00

No worries! Let us know if you'll run into real bug :)

No worries! Let us know if you'll run into real bug :)
Author

I often do...

But I always receive "Not - a bug. Closed", "It's a feature. Closed", "Can't reproduce, Closed"... :(
Even on REAL BUGS

So frustrating.

I often do... But I always receive "`Not - a bug. Closed"`, `"It's a feature. Closed"`, `"Can't reproduce, Closed"`... **:(** Even on REAL BUGS So frustrating.
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#48455
No description provided.