Array Modifier #45653

New Issue

Leon Brown · 2015-08-02T05:33:16+02:00

Leon Brown commented

2015-08-02 05:33:16 +02:00

Mac OSX 10.10.1 with an AMD Radeon R9 M295X 4096 MB
Operating system and graphics card

Blender Version
Broken: 2.75a
Worked: (optional)

Short description of error
Array Modifier stacked all duplicates on top of one another at the location of the original

Exact steps for others to reproduce the error
I was following this tutorial "https://www.youtube.com/watch?v=nHVYYMG3QVY" and followed the instructions to create the pile of blocks using the array modifier on a cube. First I added the texture and physics to the cube before using the array modifier, then followed the instructions in the video and ran the animation, everything worked fine, saved my file and then returned to the first frame to begin rendering. When I returned to the first frame it appeared all of the cubes were gone except for the original, however when I ran the animation again all of the cubes exploded out of the one that was in the original location. What seemed to have happened was that all of the cubes had just stacked into the same place, when I ran the animation the physics I had applied forced them to explode away from one another. I am new to blender and had tried several ways around this, including building the blocks in a separate .blend and appending the two files together. I rebuilt these blacks several times with the same result before I completed the file by abandoning the array modifier in favor of duplicate and manually placing them. As I am new to this and didn't even know there was such a convenient way to report bugs I do not have a .blend file.

I had submitted this earlier however there was an error on my part when sent that deleted the body of the copy, so I am re-submitting.

Thank you

Mac OSX 10.10.1 with an AMD Radeon R9 M295X 4096 MB Operating system and graphics card **Blender Version** Broken: 2.75a Worked: (optional) **Short description of error** Array Modifier stacked all duplicates on top of one another at the location of the original **Exact steps for others to reproduce the error** I was following this tutorial "https://www.youtube.com/watch?v=nHVYYMG3QVY" and followed the instructions to create the pile of blocks using the array modifier on a cube. First I added the texture and physics to the cube before using the array modifier, then followed the instructions in the video and ran the animation, everything worked fine, saved my file and then returned to the first frame to begin rendering. When I returned to the first frame it appeared all of the cubes were gone except for the original, however when I ran the animation again all of the cubes exploded out of the one that was in the original location. What seemed to have happened was that all of the cubes had just stacked into the same place, when I ran the animation the physics I had applied forced them to explode away from one another. I am new to blender and had tried several ways around this, including building the blocks in a separate .blend and appending the two files together. I rebuilt these blacks several times with the same result before I completed the file by abandoning the array modifier in favor of duplicate and manually placing them. As I am new to this and didn't even know there was such a convenient way to report bugs I do not have a .blend file. I had submitted this earlier however there was an error on my part when sent that deleted the body of the copy, so I am re-submitting. Thank you

Leon Brown commented

2015-08-02 05:33:16 +02:00

Changed status to: 'Open'

Leon Brown self-assigned this 2015-08-02 05:33:16 +02:00

Leon Brown commented

2015-08-02 05:33:16 +02:00

Added subscriber: @Lou_Cipher

Julian Eisel commented

2015-08-02 17:02:08 +02:00

Added subscriber: @JulianEisel

Julian Eisel commented

2015-08-02 17:02:08 +02:00

Hey @Lou_Cipher, a .blend is important for us to recreate this. Please provide one with the necessary steps to recreate the issue.

Leon Brown was unassigned by Julian Eisel

2015-08-02 17:02:21 +02:00

Julian Eisel commented

2015-08-09 17:46:16 +02:00

Changed status from 'Open' to: 'Archived'

Julian Eisel closed this issue

2015-08-09 17:46:16 +02:00

Julian Eisel self-assigned this 2015-08-09 17:46:16 +02:00

Julian Eisel commented

2015-08-09 17:46:16 +02:00

No answer for one week -> closed! Sorry, but we have to be very strict in order to keep our bug tracker organized. We can consider reopening after we've got the requested information.

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

Array Modifier #45653