@Brent – Was jonjonsson’s bug not sufficient?
What is the number on that bug report? I can’t seem to locate it in our database (or perhaps I’m searching for the wrong query).
Brent
It is 28784.
I’m not sure, but can this be a clue to why it’s happening?
If you run this code, you’ll see that the last iteration of a transition is never called ( t never becomes tMax ):
local rect = display.newRect(0, 0, 100, 100) rect:setFillColor(1, 1, 1, 1) rect.x = display.contentCenterX - 100 rect.y = 50 local rect1 = display.newRect(0, 0, 100, 100) rect1:setFillColor(1, 1, 1, 1) rect1.x = display.contentCenterX + 100 rect1.y = 50 local function transitionF(t, tMax, start, delta) print(t, tMax, start, delta) local cy = start + delta \* t / tMax rect1.y = cy return cy end transition.to(rect, {time = 200, y = 300, transition = transitionF})
Console output:
2013-12-14 15:31:38.651 Corona Simulator[19283:507] 0.066000000000003 200 50 250
2013-12-14 15:31:38.667 Corona Simulator[19283:507] 15.884 200 50 250
2013-12-14 15:31:38.686 Corona Simulator[19283:507] 34.942 200 50 250
2013-12-14 15:31:38.713 Corona Simulator[19283:507] 62.658 200 50 250
2013-12-14 15:31:38.727 Corona Simulator[19283:507] 76.281 200 50 250
2013-12-14 15:31:38.743 Corona Simulator[19283:507] 92.605 200 50 250
2013-12-14 15:31:38.759 Corona Simulator[19283:507] 108.819 200 50 250
2013-12-14 15:31:38.776 Corona Simulator[19283:507] 125.142 200 50 250
2013-12-14 15:31:38.792 Corona Simulator[19283:507] 141.021 200 50 250
2013-12-14 15:31:38.808 Corona Simulator[19283:507] 157.038 200 50 250
2013-12-14 15:31:38.824 Corona Simulator[19283:507] 172.871 200 50 250
2013-12-14 15:31:38.839 Corona Simulator[19283:507] 188.705 200 50 250
Seems to be a bug in the latest build as previous build I didn’t have this issue. Mine is a bit different. I set an object alpha to 0 just before creating another different named object then doing a transition movement with that, but the first object alpha remains as 1 visually.
@Brent were you able to locate the bug report? Is there anything else we can provide to get this moving?
Hi @max84,
Yes, I located the report and we’re looking into it. Thanks to all for describing the symptoms in detail.
Brent
I’m experiencing a nearly identical issue. The issue is also sporadic for me, and seems to occur after a transition has just occurred. I also thought it was strange, but was able to trigger the touch events by touching where the button should be.
Thanks for chipping in, as you mentioned the behaviour you’re experiencing is thought provokingly similar to mine, with any luck we’ll be able to catch the dev’s attention and get a fix 
I too have seen this.
However I’ve failed to write a sample project for a bug report as it’s very sporadic, but it only occurs after a transition.
I see this issue as well. Sporadically, display objects that should have an alpha of 1 are shown partially transparent instead. Across runs it affects the same objects even though there are other objects of the same type on screen. Not sure if this is just a coincidence but the objects affected in my app seem to be near either the top of the screen or at the top of their local display group (i.e. yPos near 0 in either group or screen coordinates).
I noticed this with Graphics 1.0 compatibility on, so I bit the bullet and switched everything over to G2 but I’m still seeing the issue. 
I see it on Mac simulator and iOS devices I’ve tested on using various and current G2 dailies.
Hi all,
Can others in this thread confirm that the common issue may be transitioning to a certain alpha level? Or does this occur when just explicitly setting the same alpha on various objects?
Brent
@Brent: For me, it occurs when transitioning a scene. The scene which is being transitioned to has an alpha being set (to 1) on a single object in the enterScene event handler.
I reported a bug last monday that is probably connected to this:
“When groups are going off screen in mid transition, and then come back onscreen, the alpha transition never finished.”
[lua]
local group = display.newGroup()
local box = display.newRect(50,50,100,100)
group.alpha = 0
group:insert(box)
– Transition the group to full alpha in 800 ms
transition.to(group, {alpha = 1, time = 800})
– Transition group offscreen where above transition will not finish
– On complete, bring it back, it will not be 100% white since
– alpha transition above did not finish.
transition.to(group, {x = -200, time = 900, onComplete = function() group.x = 0; end})
[/lua]
I noticed this issue as well but never could get any small code to cause it. I am glad someone pinned it down. Another odd detail is when I checked the alpha property it would always return 1, even though the items were clearly transparent. Very odd bug.
@brent, max84’s description sounds like it could be identical to what I’m seeing; On a scene transition that fades in, certain objects in the newly transitioned to scene may show up partially transparent. I hadn’t made the connection that it might be related to the transition, but as far as I can tell objects in the scene that are added after the scene transition never exhibit the problem. And it seems like when the problem does happen it is only to a single display object in a scene, and always to the same object in that scene. To reiterate, it doesn’t always happen and scenes usually load and transition without issue.
I’d also like to point out I’ve had this happen to multiple DO’s in one scene, although it’s usually the same objects.
Also, as @Anderoth stated, inspecting the alpha values of these objects reveals they are set to 1 despite being transparent.
As @HardBoiledIndustries has said I’ve also noticed this on display objects at the top of the screen.
The object I have is at the top left of the screen. Alpha = 1 even though it appears at random alpha’s on screen.
I have my own scene transitioning in place (this code was written before storyboard was available).
I have two objects that fade to alpha=0 on the way out. One on the top-left, and one on the middle-right. The transition is a slide left movement, so the top-left is the object that goes off-screen first.
On the way back in (slide right) the object at the top-left will occasionally be transparent but have an alpha=1. The other object (middle-right) always transitions correctly.
One thing I noticed is that if I *increase* the alpha=0 transition time from 100ms to 200ms on the top-left object, it always transitions back properly.
Hi all,
Has somebody in this thread already filed a bug report for this, or can you? We’d like to see the most simple, stripped-down example possible, showing what is clearly occurring.
@jonjonsson, I see you filed a bug… is this clearly showing the issue? If so, we can use that as a test case.
Thanks,
Brent