User Details
- User Since
- Sep 25 2014, 7:27 AM (437 w, 1 d)
Sep 30 2014
Hi Mont29
I certainly don't want to waste your time, but I did not at least not to my knowledge (install addons already part of the distribution), and there were no doubles as in double representations in appdata. However, removing the offending items:
development_api_navigator.py
scene_amaranth_toolset.py
space_view3d_simple_align.py
from appdata also removed the double entry warning without disabling the addons. I might be wrong, but neither of them as far as I know is part of the distribution. No big deal, problem solved as far as I am concerned and thanks.
Hi psy-fi
Resolved in this context meant all these issues were entirely vbo related. I turn vbos off and thus turn of the problems! Whether this can/should be error handled I don't know. My own developments might crash on occasion, but they don't quit. An unexpected quit is always disconcerting, but I am with you on this it's probably driver related.
Turning off vbos in user preferences/ system resolves this issue.
I encountered two other vbo related issues simultaneously, now resolved:
Unexpected quit on object selection in object mode with armature present.
Mesh representation deterioration in clipped (AltB) region on zooming in object mode.
Turning off vbos in user preferences system resolved the issue
Screenshot:
Sep 29 2014
Sep 25 2014
found it!
Hi psy-fi,Sergey
You want me to send the .blend? If so where to, or should I just paste it into the box?
Hi Sergey
Bit erratic at the moment.
First quit on add-on enabled, then it seemed to work with it being disabled, but might have changed the screen layout.
Meanwhile I believe the issue is related to screen layout rather than the add-on.
My default screen is tools open, outliner open, properties open, text editor open, 3d-view open. Add any primitive mesh to this, select texture paint from either menu: blender quits. Same with blender default layout of the environment. This happens with add-on disabled or enabled and does not happen in the UV editing layout when Blender behaves as expected. It does not happen in 3d-full view layout, though I am getting a warning: obj did not have UV-map etc.
Cautiously I am saying here: Quits in certain screen layouts with no UV-map present.
Sysinfo below,mgf

