Screen.SetResolution and the Touchpad

MightyRabbit · February 2013

I've just forced our game down to 720p to get a better framerate and have noticed that doing so has completely thrown off the cursor for the touchpad. It moves around the screen as it should, but the actual coordinates Unity gets never match up with what is being pointed at onscreen (everything is a little over to the left and up). I used Screen.SetResolution to force the resolution - does that cause an issue with the touchpad? If so, does anyone have a fix for it?

tgraupmann · February 2013

Hmmmm I was seeing in the Unity beta about some bug posted that was incorrectly returning the screen resolution on Android.

This might be a good reason to get the X, and Y cursor position from Java.

It's on the todo list.

tgraupmann · February 2013

In your case, I would create a small repro project and a video that reproduces the issue. And send that with your bug report using the Unity bug report tool. It doubles your chances of getting fixed.

oddeven · February 2013

Any news on this issue? I'm experiencing the same problem and I can't figure out a workaround..

If I don't set the resolution, the touchpad works as expected and I get the following screen boundaries:

(0, 1080) (1919, 1080)

---------------------

| |

---------------------

(0, 1) (1919, 1)

When I set the resolution: Screen.SetResolution(1280, 720), I get bizarre boundaries

(0, 720) (1919, 720)

---------------------

| |

---------------------

(0, -359) (1919, -359)

MightyRabbit · March 2013

I didn't figure anything out - we were using the touchpad to debug our menu, but I'm working on a menu with full controller support right now (which makes the problem moot for us). We're still using the TouchPad for one other thing, but it doesn't require any precision.

tgraupmann · March 2013

I would have to guess you can wrap Screen.width and Screen.height. When you change resolution, you update your wrapper.

You translate the x,y that you get and scale it to the intended resolution to get your expected x,y.

shreek · March 2013

We had to do something similar; we're working on getting performance to a place we're happy with, so we're just using the mouse right now. We just grab the original resolution in a readonly at startup, and on OUYA we add the difference in current resolution height and original resolution height and scale by their ratio (and also scale the width by the ratio or original:current).

tgraupmann · March 2013

If you added a wrapper class, can you paste bin and share it here?

oddeven · March 2013

Hi shreek, would you mind sharing your calculation code? I'm unsure how to account for the screen dimensions that Unity reports (see diagram above). Would really appreciate your help, thanks!

oddeven · March 2013

We got it working:

mx = Input.mousePosition.x * 0.666f;

my = (Input.mousePosition.y + 359f) * 0.666f;

0.666 is 720/1080

tgraupmann · March 2013

I added an example with GUI buttons that change the resolution. And as soon as you switch to the 480p, 720p the OnGUI buttons no longer click. Did you do something for those?

oddeven · March 2013

You're running on device right? I believe this is a Unity bug so GUI Buttons probably won't work at all when forcing lower resolutions on device.. Assuming that is correct, there is probably nothing you can do about it because Unity manages the input on those objects.. We're using EZGui so this hasn't affected us.

tgraupmann · March 2013

I'm wondering in Java if I need to notify the Unity player that the resolution changed...

jujubeedev · March 2013

Did anyone notice problem with fullscreen GUITextures after changing resolution? We have screens that cover whole scene while loading and after changing resolution to 720p. It seems to change bitmaps position rather than scalling.

tgraupmann · March 2013

I'm thinking there must be a screen resolution change event that we need to pass to the unity player.

Where do resolution change events happen?

http://developer.android.com/reference/packages.html

tgraupmann · March 2013

Looks like we can get the size from the view:

http://developer.android.com/reference/android/view/Display.html

jujubeedev · March 2013

The problem is that screen resolution is managed by GUITexture system. When GameObject's position is (0.5, 0.5, 0) and scale is (1, 1, 1), the bitmap covers the whole screen. I don't have to manually change any value, at least I didn't have to ;).

I set resolution to 720p on first (init) scene in Start method. Fullscreen bitmaps are in preloaders between menu and game scenes.

tgraupmann · March 2013

I can change the layout size with this coming in the next update...

                        IOuyaActivity.GetLayout().getLayoutParams().width = 1920;
                        IOuyaActivity.GetLayout().getLayoutParams().height = 1080;
                        IOuyaActivity.GetLayout().requestLayout();

tgraupmann · March 2013

Change Log: (1.0.1.8)
- SetResolution example now calls Java code to change the layout size
- SetResolution example mouse clicks work after resolution change

In this example you can change the resolution and the input positions are correctly clicking GUI elements.

It needs one more thing on the java side which is to change the size of the view.

Bovine · May 2013

Hi Tim,

So when I was making the Java call in the latest drop on git (yesterday at least) this is sticking my framebuffer in the upper right as you saw in that issue I raised - is there something else I need to do here or is just an issue that's going to get fixed at some point?

We don't long term care about the cursor tbh, but it'd be nice if it worked as we're in the business of porting the controls....

Cheers

Ian H

tgraupmann · May 2013

If you don't care about the cursor position you can just call:

Screen.SetResolution(1280, 720, m_fullScreen);

and skip the call to:

OuyaSDK.OuyaJava.JavaSetResolution("1280x720");

which is still under investigation.

Bovine · June 2013

I found that the X was reporting 0-1919 and the Y was reporting -359 to mmm some other number, so I've applied some scaling at source in NGUI while this gets resolved.

const float mouseScaleX = 1280.0f / 1920.0f;

const float mouseScaleY = 720.0f / 1080.0f;

const float mouseYAdj = 359;

static Vector3 mousePos = Vector3.zero;

public static Vector3 GetMouse()

{

#if UNITY_ANDROID

mousePos.x = Input.mousePosition.x * mouseScaleX;

mousePos.y = (Input.mousePosition.y + mouseYAdj) * mouseScaleY;

mousePos.z = Input.mousePosition.z;

return mousePos;

#else

return Input.mousePosition;

#endif

}

Technically the scale should be the same as the aspect ratio is the same, I was just having trouble so checking my maths very manually :D

Am I missing some way of entering code in these comments?

tgraupmann · June 2013

I link code most times with paste bin if there are any greater-than or less-than symbols.

carmineg · June 2013

Any word on this issue?

- If I use Screen.SetResolution ... it does go into 720p no problem, however, the mouse pointer is telling Unity the wrong coordinates. It's "mouse-overing" buttons when it's off to the side of them

- If I use OuyaSDK.OuyaJava.JavaSetResolution("1280x720"); (after screen.setresolution) it ends up doing that window in the upper left corner thing.

-Carmine

tgraupmann · June 2013

Yep. We should check what they do in the Java part of the forums to change resolutions.

tgraupmann · June 2013

As for changing resolutions, apparently there's an example of doing this in the tegra toolkit. So I'll look into making that easy.

https://developer.nvidia.com/tegra-android-development-pack

carmineg · June 2013

Tim,

Is there a way to get the 720p thing to happen that doesn't mess up the mouse coordinates being off?

tgraupmann · June 2013

I think the ideal change would actually change the tv to the exact resolution. In case stretching impacts performance.

There's supposed to be an example of how to change resolution here:

https://developer.nvidia.com/tegra-android-development-pack

carmineg · June 2013

Tim,

To save you some time and a ton of digging/downloading/signup. I zip'd the dynamic resolution example and put it on my site for you:

http://quintet.us/files/dynamic_resolution.zip

There example is in C++ which doesn't really help me in Unity.

I really just need the mouse coordinates to report to Unity properly so mouse-hover and clicking works with Unity GUI (I don't use NGUI)

Like the original poster on here, the only way to get a decent frame rate from my game is to put it at 720p. I think this feature really needs to be part of the OuyaSDK.

tgraupmann · June 2013

sweet thanks, I know just what to do with this...

// request the new size (through whichever method we are using...)

setRenderSize(mApp->window, w, h, mEgl.getFormat());

// These are the function calls that should be made to set the render target

// size

void Engine::setRenderSize(ANativeWindow* window, int width, int height, int format)

{

LOGD(">> setRenderSize %d x %d", width, height);

mRequestedWidth = width;

mRequestedHeight = height;

switch( mMode )

{

case RenderMode::MODE_SBG:

ANativeWindow_setBuffersGeometry(window, width, height, format);

mBufferNeedsResize = false;

break;

case RenderMode::MODE_FBO:

// only an app doing benchmarking or something would touch _sBG here.

//ANativeWindow_setBuffersGeometry(window, mWindowWidth, mWindowHeight, format);

// for FBO, the request == being set.

mRenderWidth = width;

mRenderHeight = height;

break;

default:

LOGD(">>>>>>>>>>>>>>>>>> unknown mode set! %s, %d", __FILE__, __LINE__);

}

carmineg · June 2013

Tim,

What are we supposed to do with the code you pasted in there? Are you adding something to the SDK?

-Carmine

Howdy, Stranger!

Categories

Screen.SetResolution and the Touchpad

Comments