Game Development Community

RESOLVED: line on bottom and right of screen

by Justin Mosiman · in iTorque 2D · 05/27/2009 (6:28 pm) · 4 replies

Hi,

Has anybody else seen a transparent line on the bottom and right of their screens? Here's an image to explain:

opsive.com/iTGB/line.jpg
On the left there is absolutely no other objects in the GUI file besides the GUIControl and its default fields. On the right I put a background of type GuiBitmapCtrl so you can see the lines easier. On the left image it's really hard to see, but it's definitely there, I promise.

I tried the behavior shooter component game, as well as debug and release configurations. I also tried different SDKs, 2.0 and 2.2, as well as iTGB 1.1. They all show this line. I don't see it on the PC/Mac version of my game, so I'm thinking it has something to do with transforming OpenGL calls to OpenGL ES.

So, has anybody else seen it? And is there a fix? If there isn't, does anybody have any suggestions where to look first?

Thanks,
Justin

#1
05/27/2009 (7:06 pm)
I don't know what is causing that, however I have a gui I just noticed earlier today has a similar effect happening. On mine it has a weird line on all four edges of the screen. Also for me it happens in the mac build (iTGB 1.2), so my issue may or may not be the same.

On an unrelated note, what did you have to do to get the on screen fps displayed?
#2
05/27/2009 (7:17 pm)
At least it's not only me. I've never seen a line on all four edges, the only variant that I've seen is in the simulator only one line appears on the bottom.

To get the screen fps, place the following in common/gameScripts/levelManagement.cs (it could probably go anywhere, the behavior shooter had it here):

function t2dSceneObject::onLevelLoaded(%this, %scenegraph)
{
   metrics( fps );
}
#3
05/29/2009 (8:02 pm)
I think I spent more time creating the image and post than I did to debug it.

The profiles that I was using for GuiControl and GuiBitmapCtrl had a border that wasn't set to 0. Do "border = 0;" and the lines will disappear.
#4
05/30/2009 (12:35 pm)
Alright, gonna mark this as fixed.