Jump to content

  • Log In with Google      Sign In   
  • Create Account

carkey

Member Since 13 Sep 2013
Offline Last Active Sep 18 2013 07:26 AM

Posts I've Made

In Topic: CopySubresourceRegion copying wrong part on some devices

17 September 2013 - 01:50 PM


Never worked with tablets (Edit: sounds like some virtual desktop or something). For anyone who has you still need to give more clues. How do you determine the windows/desktop/backbuffer size, i.e. what function call do you use ? Also how do you grab the pointer coordinates ?



And another edit: Do you setup the device in fullscreen mode ? I also wonder if the pointer coordinates do have the higher resolution - hardware-wise.

 

It is a windows store app (metro) so windows is supposed to handle all that. Windows decides that this device is this resolution, this other device is another resolution etc.


In Topic: CopySubresourceRegion copying wrong part on some devices

17 September 2013 - 12:26 PM

Ah! I think I'm part way to finding the problem, I'm printing the pointer position out and:

 

My desktop is 1920x1080 and if I move the cursor all the way to the bottom right of the screen it's saying its position is 1920x1080.

 

The tablet that works is 1366x768 and if I go to the bottom right it says its position is 1366x768.

 

Now on the tablet that isn't working: it is also 1920x1080 but if I move the pointer to the bottom right...it says it is 1366x768.

 

So there is something strange going on here where the DirectX DXSwapChain is 1920x1080 (as I get a 1920x1080 screenshot if I use the DirectXTK SaveWic...() function) but the actual windows app itself thinks that it is 1366x768.

 

Does anyone with windows store app experience know how this could have happened? Why does the pointer think its range is only 1366x768?

 

Thanks for your time and the help so far!

 

Edit: I've just taken a print screen on the 1920x1080 device and it saves as a 1920x1080 png...so the app thinks it's 1920x1080, directx thinks it is 1920x1080 but the pointer framework/library thinks it is 1366x768 (which the other tablet is but my desktop isn't).


In Topic: CopySubresourceRegion copying wrong part on some devices

17 September 2013 - 12:02 PM

Edit: Though I consider it unlikely it could be a driver issue, actually. Either use the reference rasterizer (D3D_DRIVER_TYPE_REFERENCE) on the problematic hardware (will need D3D SDK installation) or - if possible - D3D_DRIVER_TYPE_WARP. The latter won't need a SDK install but depending on what D3D11.x you're using, you won't have the full D3D 11 feature set. If it works with either of these driver types, then the driver on the target hardware is bad.

 

I don't really understand how to do what you're saying here, is it a simple thing to set up?


In Topic: CopySubresourceRegion copying wrong part on some devices

17 September 2013 - 09:47 AM

Okay I'll have a go at doing some more debugging.

The thing is I remember it working on this device a few months ago when I first added GPU picking. I've added a lot of other stuff since then but haven't touched the GPU picking class so I really don't know what has happened to make it not work on this device...but I'll keep digging thanks!


In Topic: Trying to write a smoothing algorithm for meshes

17 September 2013 - 09:45 AM

 

The only thing I'm not quite understanding now is that the k for-loop uses the condition k < 2, should this be k < 3?

 

Yes it should. I fixed my first reply.

 

 

Ah okay cool thanks, I'll give this another go because this makes sense to me now :)

 

Thanks for all the help and really quick responses!


PARTNERS