Construct 0.99.82 released (unstable)

Oh, wow, you've got to be kidding me, the 3D Box is disappearing when it's scrolled around again. I'm getting really sick of re-posting this bug to the tracker.

Switching back to the 0.99.72 versions of the 3D Box plugin fixes it again, but I don't think that is the intended course of action.

You just have to enable 3D layering on the layer. And it will work fine.

> Oh, wow, you've got to be kidding me, the 3D Box is disappearing when it's scrolled around again. I'm getting really sick of re-posting this bug to the tracker.

>

> Switching back to the 0.99.72 versions of the 3D Box plugin fixes it again, but I don't think that is the intended course of action.

>

You just have to enable 3D layering on the layer. And it will work fine.

No, you're thinking of when it displays weirdly. It doesn't display at all. My layer has had 3D layering enabled for quite a while. And while my example file that I uploaded to the bug tracker all the way back in 0.99.3's time finally worked in 0.99.72 after displaying incorrectly in every prior version that had the "new" renderer, It seems that whatever changes were made to the plugin for 0.99.8x (the only thing I see is the bounding box fix) break it again. Cool!

Mr. K, are you by any chance using Unbounded Scrolling? I can confirm that the box does this for me when that's checked. It disappears near the edge of where the layout is.

Otherwise it seems to be fine.

Edit:

Made an example .cap:

http://dl.dropbox.com/u/529356/3dboxdissapears.cap

I'll post the bug to the tracker if you haven't already.

Sourceforge seems to be down atm, both this version and the one on the site cannot be downloaded, mirrors could solve this incase sourceforge could be down like now, I used to use the one on the site but now I feel interested on using .82, dunno if it's a good idea to make a game on this version or this one is a merely experimental version anyway.

Mr. K, are you by any chance using Unbounded Scrolling? I can confirm that the box does this for me when that's checked. It disappears near the edge of where the layout is.

Otherwise it seems to be fine.

Edit:

Made an example .cap:

http://dl.dropbox.com/u/529356/3dboxdissapears.cap

I'll post the bug to the tracker if you haven't already.

Nope, no unbounded scrolling. I believe my previous bug report is still in the tracker but marked as fixed, with an example attached, which no longer works.

Ah, I see.

Well, if it's the same issue that Mr. Wolf was having then it's probably already fixed for 0.99.83. Check out his thread:

The example he posted there works fine for me using the 0.99.83 3D Box runtime. I'd forgotten that David added it because it's not in the changelog for 0.99.83, go figure.

The example I posted earlier is still an issue though.

Yes, that seems to be it. If it's fixed again, then, I have nothing to complain about. I'll be eagerly awaiting the next version.

OK, Now I have something to say about it.

Main bug is in Texture editor. ZOOM making blur motion effect when I (+) or (-) picture.

It is unacceptable. I think that You should remove this bug easily. It also need some visual and clean corrections.

Now look: "baddas":

http://img709.imageshack.us/img709/8898/problemlu.jpg

And what I (maybe We) want to see in the Construct:

http://img534.imageshack.us/img534/1251/newt.png

You can compare it and think.

Now look: "baddas":

http://img709.imageshack.us/img709/8898/problemlu.jpg

It doesn't look like that at all for me. In fact, on my computer it looks exactly like your second example. I'm guessing it's your graphics card.

Just posted a bug report on Sourceforge:

I'm using custom movement on a sprite, and when I switch to fullscreen, the speed is way higher than on windowed mode.

here's the cap, please test it to see if this is happening on more computers (I don't know, could be something that's happening here)

http://www.gamma-beam.com/construct/fullscreenbug.cap

Also, I am currently unable to test it on previous versions to see if it happens on them...

here's the cap, please test it to see if this is happening on more computers (I don't know, could be something that's happening here)

It's not happening for me. The speed tops out at 310 in both windowed and fullscreen.

Sorted out what was happening. The V-Sync was forced off on my card, and the custom movement reacted differently when in Fullscreen. However, another movement behavior (I used 8 direction) doesn't seem to be affected the same way... Weird stuff!