blender 2.81 (and 2.80 as well) its running damn slow in windows 7. #71649

New Issue

Michael Colina · 2019-11-17T20:20:28+01:00

Michael Colina commented

2019-11-17 20:20:28 +01:00

System Information
Operating system: Windows 7 Home Premium 64 bits, RAM 4GB
Procesor: Intel(R) Core(TM) i5 M 460 2.53 GHz
Graphics card: none?

Blender Version
v2.80
v2.81 beta eba4a4bd73 date 2019-11-15 16:32

ok what its happening its that i try to do simply stuff like get to edit mode, navigate,edit some thing in the topology of my model, try to sculpt in medium high resolution mesh with or without using dyntopo and multiresolution, also connect,move, add nodes to the shader editor, try to change rendering mode (whether it is material preview or rendered) with EEVEE engine becomes more slower and freezes and crashes blender when rendering a not too complex node setup that i was trying to, but in with cycles it does properly and slightly faster than 2.79b with 32 samples, also i click in some icon hide or unhide options, tabs, tool icons, tool menus all that kind of stuff makes the blender get non responding state immediately for about 3 or more seconds and its damn overwhelming and also i started to use b3d 2.8 since yesterday due that i didnt know how to solve the opengl problem which i just had to paste a opengl.dll file in the blender folder and i was happy that i could finally test it but then not suprised at all when all this came... anyway same shit happens in 2.8 but probably slightly less buggy. i dont really know if this is due to that i dont have any graphic card (except the opengl).

**System Information** Operating system: Windows 7 Home Premium 64 bits, RAM 4GB Procesor: Intel(R) Core(TM) i5 M 460 2.53 GHz Graphics card: none? **Blender Version** v2.80 v2.81 beta eba4a4bd73ba date 2019-11-15 16:32 ok what its happening its that i try to do simply stuff like get to edit mode, navigate,edit some thing in the topology of my model, try to sculpt in medium high resolution mesh with or without using dyntopo and multiresolution, also connect,move, add nodes to the shader editor, try to change rendering mode (whether it is material preview or rendered) with EEVEE engine becomes more slower and freezes and crashes blender when rendering a not too complex node setup that i was trying to, but in with cycles it does properly and slightly faster than 2.79b with 32 samples, also i click in some icon hide or unhide options, tabs, tool icons, tool menus all that kind of stuff makes the blender get non responding state immediately for about 3 or more seconds and its damn overwhelming and also i started to use b3d 2.8 since yesterday due that i didnt know how to solve the opengl problem which i just had to paste a opengl.dll file in the blender folder and i was happy that i could finally test it but then not suprised at all when all this came... anyway same shit happens in 2.8 but probably slightly less buggy. i dont really know if this is due to that i dont have any graphic card (except the opengl).

Michael Colina commented

2019-11-17 20:20:29 +01:00

Added subscriber: @Michael-Colina

Philipp Oeser commented

2019-11-19 10:41:00 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2019-11-19 10:41:00 +01:00

Changed status from 'Open' to: 'Archived'

Philipp Oeser closed this issue

2019-11-19 10:41:00 +01:00

Philipp Oeser self-assigned this 2019-11-19 10:41:00 +01:00

Philipp Oeser commented

2019-11-19 10:41:00 +01:00

Thx for the report, but:

we have like 10 different issues reported here at the same time (this is just not practical to handle in a single report)
it is not clear what we should be looking at opening that file
I suggest you split these up into multiple reports, and for each of them, concentrate on a single issue and describe exactly what needs to be done to reproducce the issue
Also please make sure to use Help > Report a Bug from within blender [this fills out some required information for you, e.g. GPU...]

This is our official statement regarding multi-reports:

Thanks for the report. However to properly track issues we need them to be reported separately.
Please submit a new report for every individual bug.

Thx for the report, but: - we have like 10 different issues reported here **at the same time** (this is just not practical to handle in a single report) - it is not clear what we should be looking at opening that file - I suggest you split these up into multiple reports, and for each of them, concentrate on a single issue and describe exactly what needs to be done to reproducce the issue - Also please make sure to use `Help` > `Report a Bug` from within blender [this fills out some required information for you, e.g. GPU...] This is our official statement regarding multi-reports: > Thanks for the report. However to properly track issues we need them to be reported separately. > Please submit a new report for every individual bug.

Michael Colina commented

2019-11-19 19:32:36 +01:00

ok i should edit it right now? well actually anyway already did it and put them separately.

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

blender 2.81 (and 2.80 as well) its running damn slow in windows 7. #71649