Scene viewport rendering incorrectly on Surface Pro 3 #470

Closed
AvengerDr opened this Issue Oct 21, 2016 · 6 comments

Projects

None yet

5 participants

@AvengerDr

I was trying Xenko on my SP3. However, as you can see from the image below, the scene viewport is displayed incorrectly.

capture

@manu-silicon
Contributor

This is a known issue (see #464). Which OS version are you using on the Surface Pro 3?

@AvengerDr
AvengerDr commented Oct 22, 2016 edited

Oh sorry about that. I am using Windows 10.
Afterwards, I noticed that problem on my main desktop PC. I think it's because on the SP3 the zoom level was set at 150%. Some game or multiple screen setting must have (temporarily) altered that on my desktop PC too.

I have also noted another problem, but I am not sure if it has already been reported. It's about shaders, I tried to search the open issues but I haven't found any reference. Basically if a shader is supposed to return a color, and it is not returned, the mesh disappears but I can see some polygons flashing in and out. In some more severe cases the editor goes in full seizure mode and starts flashing on and off very rapidly. If this has not been reported yet I'm happy to open a new issue.

@manu-silicon
Contributor

Just to be sure, is this the anniversary update?

@0xFireball
0xFireball commented Oct 25, 2016 edited

I noticed this too: Anniversary update, Surface Pro 4

This is my screen:

image

I look forward to using Xenko but it's very hard on this computer like this

@manu-silicon
Contributor
manu-silicon commented Oct 25, 2016 edited

Note that if you open Explorer where you installed Xenko, look for the folder GamePackages\Xenko.1.8.3-beta\Bin\Windows-Direct3D11 (replace 1.8.3 with your version of Xenko installed), thrn open the Windows properties of Xenko.GameStudio.exe. Make sure to check Disable display scaling on high DPI settings in the compatibility tab.

Then relaunch Xenko. It should be fine with the downside that the UI elements would appear quite small.

@0xFireball

Thanks for the workaround. Will this be fixed in the next release?

@Kryptos-FR Kryptos-FR self-assigned this Nov 24, 2016
@xen2 xen2 closed this Nov 24, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment