Moving Samples Results In Error - RESOLVED

Support
#1

“Sorry, something went wrong. We have already been notified with more specific error details.”

I get that when I change the order of samples in an element. I have some combat music that I want to play sequentially, and I want a specific song first, so I moved it up to the top, and got the error, then I moved the second song I wanted to play, and it gave the error.

While they show in correct order, when I play the sequence, the third song plays first, not the first or second that I moved.

So then I deleted the third song as a test, and then I played the 4th song that moved into the third position.

So this is a bummer, since I wanted this a certain way for tomorrows game, but I get it - bugs happen. Hopefully it is a simple fix.

#2

Interesting, I coped the element, and when I compared it’s playlist order, it was different than the original, that I had moved the samples with and had the error with. The copy is showing the first song and the third song as the original, so yeah, moving the samples screws things up.

To get around this for now, I will just copy the element, delete all the songs that I don’t want to play first, and have that play once and then switch over to the other one with a timer.

#3

In addition, sometimes I can’t even move samples at all, and the only way I know how to fix this is to close chrome and open it back up again. I noticed this also happens in Edge at times. (Update: refreshing the website also fixes it, but then I have to navigate back to where I was, which is a pain. :stuck_out_tongue: )

#4

OK, so new day, and another attempt to see if I can successfully move sample order within my element. Nope, same error. They look like they are moved now, but they are not and will still play in the previous order.

Let me try a different soundset to see if it is this one specifically.

1 Like
#5

@dorpond Thanks for this bug report. I’ve fixed the issue in code but it has not been deployed yet. I’ll report back again once the fix is live.

1 Like
#6

@dorpond This should be fixed on production now.

1 Like
#7

Cool, I’ll test it out this week and report back!

1 Like
#8

Confirmed. Fixed!
You rock, @sonofconan!

2 Likes