Sorry if these have been covered, but I had no luck searching.
I’ve managed to build a sample project and deploy it to the Xbox one (just a simple scene with a few textured cubes) and wondered if anyone could help with the following.
The app doesn’t seem to run full screen on the xbox, there is a large white border all the way around. Is there a setting or two I need to change to fix this. (changing to D3D mode seems to remedy this, not sure if that will impact performance at all)
It seems to automatically bring up a debug console in the bottom left corner, is it possible to get rid of this? (edit* I’ve checked the Development Build option is unchecked in the settings)
It seems to always show a mouse cursor on screen on the xbox, is it possible to get rid of this as I don’t want that moving around as I move the joysticks of the controller. (changing to D3D mode seems to fix this)
The app doesn’t seem to run full screen on the xbox, there is a large white border all the way around. Is there a setting or two I need to change to fix this. (changing to D3D mode seems to remedy this, not sure if that will impact performance at all)
It seems to automatically bring up a debug console in the bottom left corner, is it possible to get rid of this? (edit* I’ve checked the Development Build option is unchecked in the settings)
You have to select Master configuration in Visual Studio solution, it seems you have Debug or Release selected.Development build option doesn’t do anything in this case.
It seems to always show a mouse cursor on screen on the xbox, is it possible to get rid of this as I don’t want that moving around as I move the joysticks of the controller. (changing to D3D mode seems to fix this)
All switching from XAML to D3D did for me was make the mouse cursor unresponsive for a while… apart from that, nothing. Still no on screen keyboard when I click on a text input field, still the ugly cursor on the screen whether I want it there or not, still the massive empty border around my scene.
Is there no “How to use Unity for XBO” guide anywhere? I think being able to show and hide the cursor that I didn’t place in the game the first place is rather important and so is being able to use the input fields, no? Isn’t clicking on them supposed to automatically pop up the keyboard?
I have seen tutorials from MS about the safe area around your visuals, how to deal with it and , basically, all this stuff I am asking about now… They have tutorials for how to fix these “issues” when coding in VS directly. Doesn’t Unity have something similar?
Which Unity version are you on? Is your Xbox One console have the latest updates? They’ve been fixing many of these issues on the OS side.
I am not aware of the cursor issue you mentioned. Can you post some screenshots of what’s going wrong? Cursor is usually drawn by the OS, but it shouldn’t be there on D3D.
I am on Unity 5.5. Updated XBO 2 days ago. Cursor looks like the “Male” sign, just pointing to the left instead of the right.
The pointer I can try to fix using the pointer visibility you mentioned earlier. I was just a bit surprised to see it, is all. For now it serves my purposes because I need to select the input fields. As such, I’ll worry about the cursor later. For now I have 2 far more pressing concerns:
How do I go full screen instead of having this huge safe area or whatever that is meant to be drawing around my scene
How do I get the keyboard to pop up so I can actually enter text into the text fields?
Thanks.
p.s. Will get you some screenshots once the sun rises again. My camera sucks at night time photos under florescent lights…but like I said, the cursor I will worry about later. One of my potential customers asked me if my kit is compatible with consoles and without the ability to enter text into the fields I have no way of testing that and giving him an answer… So keyboard is my number 1 priority.
I don’t know what I did differently but I started a new project and set everything as it’s supposed to be set and this time round the game worked as expected. Full screen and as stated earlier, no mouse. Awesome… Except then I needed a mouse cursor and setting Curcosr.visible to true did not do the trick…
So I tried to bypass the need for the mouse by having a button pop up the keyboard only to realise I have no idea how to see the on screen keyboard. I know I keep asking about the keyboard and all answers keep dancing around answering that question so I just HAVE to ask:
Does Unity even support showing the native keyboard or not? Is it possible to make an XBO game and actually type in text at some point? This careful sidestepping of any mention of it has me worried…
Any feedback on how to use TextFields in Win10 builds… specifically XBO… please?
Does TouchScreenKeyboard class not work? It calls the same system API to display the system screen keyboard on all UWP platforms (except HoloLens, which has a special path). That generally requires no keyboard to be connected to the device though, as then the system just makes those APIs do nothing otherwise.
Can confirm that using below does work to hide the cursor. Unfortunately it still appears on the Unity splash screen, but disappears immediately once scene is started. Makes sense since my code snippet only runs at scene start. Anyone know how to kill cursor over the splash screen? Side info : This is info from a build I just did today, latest SDK, lastest OS stuff from Microsoft, etc.
public class HideCursor : MonoBehaviour
{
void Start()
{
Cursor.lockState = CursorLockMode.Locked;
Cursor.visible = false;
}
}
@JamesArndt1 is there any reason you want to use Xaml build type? Using D3D would solve both the mouse issue, make your game startup faster and make it use less memory.
Ignorance. I really didn’t know the differences. I was just following an online guide and the person giving the tutorial had mentioned using Xaml as the build type. I was just testing, so I can delete the built folder and rebuild the project as D3D. I had no idea it had advantages like that. Thank you for the information!
@Tautvydas-Zilys I’m having a similar issue and switching to D3D did remove the cursor and made the game display at full screen without the white border. However, now I don’t get any joystick interactivity in the menu once its on the Xbox One. It will work perfectly in Visual Studio and in the Editor, but not on Xbox One. It does show that my first button is active, it just won’t change to any of the other buttons, and won’t allow me to actually select the first button.
Update: My second issue must have been separate, forcing the eventsystem active fixed my problem.
A bit late to the party, but the fix for Unity’s event system not responding to controller input on Xbox One by default using UWP is solved by checking “Force Module Active” on your EventSystem instance in the scene. Also verify there’s only one EventSystem instance.