Construct 2 103 - preview error

Bugs will be moved here once resolved.

Post » Wed Sep 12, 2012 4:30 pm



Help !!!!
Create HTML5 games

Create HTML5 games
B
11
S
3
Posts: 12
Reputation: 1,535

Post » Wed Sep 12, 2012 4:38 pm

Please see how to report bugs. We cannot do anything about your problem unless you share the affected .capx file.
Scirra Founder
B
359
S
214
G
72
Posts: 22,952
Reputation: 178,600

Post » Thu Sep 13, 2012 3:37 pm

Does r103.2 fix this?
Scirra Founder
B
359
S
214
G
72
Posts: 22,952
Reputation: 178,600

Post » Fri Sep 14, 2012 2:22 am

@PixolPalette had about the same issue, and I've reproduced it in this capx.

Click a white cat, it make it fade.
On destruction, event 4 destroys the "Cat" instance (again ?) and makes the crash happen.

Happened in FF and chrome.

It's not the way the behavior is supposed to be used anyway, but C2 could handle the issue a bit more elegantly perhaps ^^
New to Construct ? Where to start

Image Image
Image Image

Please attach a capx to any help request or bug report !
Moderator
B
247
S
85
G
40
Posts: 7,000
Reputation: 57,795

Post » Fri Sep 14, 2012 8:46 am

[QUOTE=Ashley] Does r103.2 fix this?[/QUOTE]

@Ashley: I could still see this failure in r103.2. But I am not able to get a short repro for you(because of the way my project is setup and the size of it). Taking a hint from @kyatric, when I eliminated a case where an explicit Destroy and FadeOut destroy can happen on the same object, the crash is gone.

As you know C2 used to handle this in r101 fine. Would you consider fixing this?
B
18
S
7
G
5
Posts: 71
Reputation: 4,991

Post » Fri Sep 14, 2012 5:28 pm

I found and fixed the issue in @Kyatric's capx example. However since I don't have .capx files from @vnHarry or @iunkn, I cannot confirm that it is fixed for you as well, but I would think it is likely that it is fixed. This fix will go in to the next beta release (104).
Scirra Founder
B
359
S
214
G
72
Posts: 22,952
Reputation: 178,600

Post » Fri Sep 14, 2012 9:24 pm

Woop - I'll disable fade/destroy for now then? I thought I'd seriously broken something - I learned how to use the Chrome Console though, now it's much quicker to track down what is actually causing the error and where.

Image
B
27
S
9
G
5
Posts: 487
Reputation: 11,939


Return to Closed bugs

Who is online

Users browsing this forum: No registered users and 1 guest