PS CC issue on a Surface Pro 2

Howdy!
So, everything is working great in PS CC on my Surface Pro 2, except if i rotate my tablet to portrait mode..
The main window stops with a bunch of empty space below it. It will not stretch any further down than what you see. Also, looks like the ui on the top right is a bit cut off. I'd love to be able to use the full screen in portrait mode, but just haven't been able to figure out what the issue is. I'm running a fully updated Photoshop CC on an up to date Windows 8.1.
Thanks!

Hah, awesome. This seems to work great! Thanks man.
I've got another strange issue, which you or someone may be able to help with. I've got the updated Wacom Feel drivers, but in PS, when I have transfer mode on, or opacity set to pen pressure, no matter how hard I press, I cannot get a fully opaque stroke. I've set the tip feel to all of the softer settings, and nothing (I don't like this, because it limits the amount of sensitity I get). Whenever I turn opacity control off of pen pressure/turn off transfer mode, my strokes go back to being fully opaque. It's almost as though my opacity is set to 95% or something, even though its not.
Thanks again!

Similar Messages

Issues with the Surface Pro 3's pen in Photoshop CS6

I used photoshop CS6 with no problems on my old computer that was connected to a graphics tablet.
However, I recently bought a new windows computer called the Surface Pro 3. Everything works perfectly with the trackpad and touch, but I've had some issues with the Surface pen.
The pen can draw on the canvas, but whenever I click something on any of the windows with the pen, the entire application freezes and I would have to click the computer's taskbar at the bottom to unfreeze the application.
It's impossible to work like this. Is there any solution to fix this problem? It says that the version of photoshop I have is Adobe Photoshop Version: 13.1.2

If you have Photoshop CS6 version 13.1.2 which is the Subscription version of Photoshop, You shoule Isstall Photoshop CC 2014 on your surface Pro 3. It will work without problems on the surface Pro 3 and you will also have the option have the option to use Photoshop CC 2014 preference 2x UI to scale Photoshop's UI up in size on your Surface Pro 3.
If you do not have a subscription the Perpetual version of windows CS6 should be version 13.0.1.3. In that case the only way to scale Photoshop UI is to have windows do it. You would need to to update your windows 8.1 registry and add an external Photoshop manifest file in your Photoshop CS6 folder. To get the Surface Pro 3 pen to work with Photoshop you would need to install NTig pen device drivers the support the wintab APIs.
You will not be able to use Photoshop without a keyboard popping up the windows onscreen keyboard is too cumbersome. You can use a utility like Touchkey to create Overlay touch keys on Photoshop and use Photoshop without a keyboard.
The differece betweek Adobe 2XUI scaling an windows scaling ise windows scaling scalet the image areas as well as the Photoshops UI
A couple of touchkey overlat keyboards could look something like this

Video Issues with Surface Pro 3 9926 .4079 Driver

I am thinking that most of us are aware, but I wanted to bring some visability to the graphics issues for the Surface Pro 3 and the 9926 update. If you are doing an upgrade then you will eventually end up with version x.4079 of the Intel Graphics driver.
If you are performing a clean install, be ready as the screen will flicker and boot loop every few minutes, but if you can get to Windows update and get the 1/22/2015 firmware update this is the x.4079 driver.
Issue are:
1. Internet Explorer is not able to play most embedded videos such as YouTube etc. The Bing homepage today keeps crashing for me.
2. .MP4 video will not play in the Video app or Windows Media Player. Work around - use the Chrome Browser and play the videos right in the window or convert to .avi or .mkv
I have seen lots of people posting that they uninstalled and deleted the drivers and then the standard video card driver would install. This is true but if you use the docking station or an external adapter then the external screen will not work AND
your machine will keep on trying to update the driver to the broken Intel one.
At this point we will have to wait for Microsoft to issue an updated Intel driver as I cannot seem to get the most current x.4080 to install (even when installing manually by having disk).
A.

Hi,
According to statistics recently, this seems like a commen issue as other people also encounter display problem after install Windows 10 preview 9926.
Please make sure Windows update work properly ane install all accessable updates.
Roger Lu
TechNet Community Support

When Will Microsoft Fix The Problem With Hosted Networking on a Surface Pro 3?

Surface Pro 3 512GB
Windows 8.1 with all patches.
The following is from this thread:
http://answers.microsoft.com/en-us/windows/forum/windows8_1-networking/netsh-wlan-start-hostednetwork-not-working-on/f414cea9-c110-483c-a3a2-840a4ce317e2?rtAction=1423330004507
A Microsoft member said it would be better to raise it in technet.
netsh wlan set hostednetwork mode=allow ssid=test key=12345678
The hosted network mode has been set to allow.
The SSID of the hosted network has been successfully changed.
The user key passphrase of the hosted network has been successfully changed.
netsh wlan start hostednetwork
The hosted network couldn't be started.
A device attached to the system is not functioning
One of the comments in the thread said:
"I have the same issue on a Surface pro 3.
It is related to the fact that they removed VAP support from the wifi driver."
Now a new wifi driver was included with the latest firmware update (01/15/2015) but it did not fix the problem.
I
Please note this is a Surface Pro 3 problem as it works on a Surface Pro 2 running Windows 8.1.
This problem has been reported to Microsoft by me and I was told "the developers are working on it." That was six months ago. I see posts going back a year saying the problem was reported to Microsoft Support.
When will this be fixed?

On Sat, 7 Feb 2015 18:06:38 +0000, saberman_Plus_1 wrote:
>This problem has been reported to Microsoft by me and I was told "the developers are working on it." That was six months ago. I see posts going back a year saying the problem was reported to Microsoft Support.
Do you have a case number? From
http://answers.microsoft.com/en-us/surface/forum/surfpro2-surfnetwork/how-do-i-get-the-wireless-hosted-network-feature/03657fe5-b8c1-48c5-940a-ae3e13ffe25f
you've had a couple of contacts with support.
If you provide case numbers, it would be helpful in escalating further. And more
specifically, it might help someone from Microsoft determine IF the issue has
been escalated. While Microsoft has been doing work on the wifi driver for
nearly the entire time since the SP3 was released, there is no information
anywhere as to whether this bug is known or not.
As you also know, I sent it in to the"right" people inside Microsoft and as you
also know, I did not get a response. (I'm an end user just like you even though
I'm a Community Moderator on the Surface Forum in Communities).
-- Barb Bowman

Surface Pro 3 is not able to connect to standalone aironet

Hello,
we are having issues with several Surface Pro 3 device connecting to a standalone Aironet. Other Device connect to this AP no problem. SP3 connect to other APs (not cisco) no problem. So there seems to be an issue between the two devices. When I look in the logs of the AP I get the following message:
Jan 15 19:59:52.513: %DOT11-7-AUTH_FAILED: Station 501a.c5e5.aeff Authentication failed
I tried to run aaa debug but nothing shows up but that message above. We use WPA2 AES/TKIP.
I proceeded to run debug all on the AP and this is what I got. Keep in mind that we are troubleshooting 501a.c5e5.aeff
Jan 15 19:55:19.646: Setting client MAC 501a.c5e5.aeff radio slotunit 0 address 0x7E2CE90
Jan 15 19:55:19.646: Adding client 501a.c5e5.aeff client->reap_flags_1 0
Jan 15 19:55:19.646: Dot11Radio0: Adding client 501a.c5e5.aeff aid 6
Jan 15 19:55:19.646: dot11_mgmt: drv add resp for client 501a.c5e5.aeff aid 6
Jan 15 19:55:19.646: dot11_mgmt: dot11_mgmt_sta_ref (ref=2, sta_ptr=0x7530010, mac=501a.c5e5.aeff)
Jan 15 19:55:19.646: SM: ---Open Authentication 0x7530010: Drv Add Resp (8)
Jan 15 19:55:19.646: SM: Drv_Add_InProg (8) --> DONT CHANGE STATE (255)
Jan 15 19:55:19.646: dot11_mgmt: [168D368F] response from driver for client 501a.c5e5.aeff
Jan 15 19:55:19.646: Setting global apsd config before assoc rsp
Jan 15 19:55:19.646: dot11_driver_client_apsd_settings Client(501a.c5e5.aeff) not found for APSD settings
Jan 15 19:55:19.646: about to perform cac before cac resp
Jan 15 19:55:19.646: dot11_tsm_delete_ts_not_reassociated:Clean streams not in REASSOC
Jan 15 19:55:19.646: dot11_mgmt: [168D36F5] send assoc resp, status[0] to dst=501a.c5e5.aeff, aid[6] on Dot11Radio1
Jan 15 19:55:19.646: There is nothing to add from qosie_set in ASSOC Rsp
Jan 15 19:55:19.646: Dot11Radio1: Tx AssocResp client 501a.c5e5.aeff
Jan 15 19:55:19.646: dot11_aaa_auth_request: Received dot11_aaa_auth_request for client 501a.c5e5.aeff
Jan 15 19:55:19.646: dot11_aaa_auth_request: SSID: Executive, Mac Address: 501a.c5e5.aeff, auth_algorithm 0, key_mgmt 1027074
Jan 15 19:55:19.646: AAA/API(00000000): aaa_util_unique_id_alloc(), pc 0x185F920, enter {
Jan 15 19:55:19.646: AAA/ID(NA): DOT11 allocating
Jan 15 19:55:19.646: AAA/ID(00000023): Call started 14:55:19 -0500 Jan 15 2015
Jan 15 19:55:19.646: AAA/DB(00000023): add Intf/7D3D488
Jan 15 19:55:19.646: AAA/DB(00000023): add DB 7E2910C
Jan 15 19:55:19.646: AAA/ID(00000023): DOT11 allocated
Jan 15 19:55:19.646: AAA/API(00000023): } aaa_util_unique_id_alloc()
Jan 15 19:55:19.646: dot11_mgr_disp_wlccp_update_auth: unknown auth type 0x1
Jan 15 19:55:19.646: dot11_aaa_add_dot11_client_entry: AAA Client entry (501a.c5e5.aeff, 4106500) is added to the client list
Jan 15 19:55:19.646: dot11_aaa_start_auth_sequence: dot11_aaa_start_auth_sequence for client 501a.c5e5.aeff [key_mgmt] = FAC02
Jan 15 19:55:19.646: dot11_aaa_start_auth_sequence: dot11_aaa_start_auth_sequence for client 501a.c5e5.aeff [key_mgmt] = FAC02
Jan 15 19:55:19.646: dot11_mgr_sm_start_wpav2_psk: Starting wpav2 4-way handshake for PSK or pmk cache supplicant 501a.c5e5.aeff
Jan 15 19:55:19.646: dot11_mgr_sm_send_wpav2_ptk_msg1: Starting wpav2 ptk msg 1 to supplicant 501a.c5e5.aeffCould not find station pointer for client 501a.c5e5.aeff. Using vlan number from aaa_client
Jan 15 19:55:19.646: dot11_dot1x_send_ssn_eapol_key: wpav2 msg 1 pak_size 121
Jan 15 19:55:19.646: dot11_dot1x_send_ssn_eapol_key: eapol->length 117
Jan 15 19:55:19.646: dot11_dot1x_build_ptk_handshake: building PTK msg 1 for 501a.c5e5.aeff
Jan 15 19:55:19.646: dot11_dot1x_build_ptk_handshake: ptk key len 16
Jan 15 19:55:19.646: dot11_dot1x_build_ptk_handshake: ptk key data len 22
Jan 15 19:55:19.646: dot11_dot1x_build_ptk_handshake: wpav2 pmkid[DOT1X]: 0CBC860AAF0DBBA764ED9D51BB113194
Jan 15 19:55:19.646: dot1x-registry:registry:dot1x_ether_macaddr called
Jan 15 19:55:19.646: dot11_mgr_disp_client_send_eapol: sending eapol to client 501a.c5e5.aeff on BSSID c025.5ca5.3c40
Jan 15 19:55:19.646: dot11_mgr_sm_send_wpav2_ptk_msg1: [1] Sent PTK msg 1 to 501a.c5e5.aeff, no timer set
Jan 15 19:55:19.650: dot11_mgmt: dot11_mgmt_sta_deref (ref=3, sta_ptr=0x7530010, mac=501a.c5e5.aeff)
Also, on windows end I checked the Event Viewer and I see that SP3 is not getting any response back from the AP.
Any help would be greatly appreciated. Thanks.

I rolled out a batch of these to our wireless network a couple of months back. A couple of tips:
- From a wireless perspective these devices are extremely buggy out of the box (I'm not exaggerating). They basically won't function using the built in wireless with anything other than the most very basic wireless setup of a home router until you apply ALL of the patches and updates for them in Windows Update. In my case I had to install all the updates via ethernet dongle and/or a Linksys USB Wireless dongle (the drivers were much better for the USB dongle and allowed connectivity to work). The built in Marvell adaptor looks to be good from a features perspective but poor from a driver perspective. Once the updates were applied it mostly worked.
- I experienced a similar problem with FT (Fast Transition) enabled - the SP3 will not connect with FT enabled. In my view there were two issues - (1) the devices won't even connect if FT is enabled and (2) they don't support the FT feature for seamless roaming.
I took it up with Microsoft and they acknowledged the problem but wouldn't commit to fixing the buggy behaviour (allowing the connection and ignoring the FT attribute like many older clients do) nor would they commit to when they will support the FT feature (fast roaming).
These tips might not be the cause of your problem but hopefully they will help you get it up and running.
Fortunately all of these problems can be fixed with driver updates, so maybe in the future they may end up being pretty good wireless clients afterall :-)

MDT 2013 Fails to Format or Partition disk on Surface Pro 3

I have been trying to image a Surface Pro 3 using MDT 2013 and have been unable to get past the Format and Partition portion of the deployment. At first I would get an error that it was unable to format or partition the drive and then after that it
just reboots after trying for so long. I am able to image any other device with the same task sequence and have no issue just having an issue with the Surface Pro 3. Any help would be great.
Thanks in advance.
I am getting the error FAILURE (5210)
ZTI Error - Unhandled error returned by ZTIDISKPART: Object required (424)

I think our problem is also hardware failure although without re-imaging a working surface pro 3 I can't be sure.
I tried what imfusio suggested in this thread.
https://social.technet.microsoft.com/Forums/en-US/d31384bc-4e96-4a5b-a400-637bd6006d81/failure-5456-unable-to-determine-destination-disk-partition-and-or-drive-surface-pro-3?forum=mdt
Unfortunately the deployment failed with the same ZTI Error - Unhandled error returned by ZTIDISKPART:
Object required (424)
I then rebooted into WinPE and ran diskpart, I could see the two volumes (EFI and OSDisk). I then tried to format the OS disk volume using diskpart. I got a paramater is incorrect error and the disk was no longer visible with a 'list disk' command. So it's
like the format is putting the disk offline. I'm going to try restore one of these surfaces, apply all firmware updates then re-image. If that doesn't work I'm out of ideas.

Bricked: Surface Pro Firmware Update

This is incredibly frustrating. We ordered 80 surfaces pros and I can't get any real support. I get transferred to consumer grade support who has absolutely no idea WTH they're talking about. I do not want to talk to someone
in India following a flowchart designed for consumers. 50 grand on tablets, and no support.
We need to deploy an image to these machines. It's my understanding that they can't PXE boot without a firmware update. I I manually applied the Firmware as per this blog:
https://blogs.technet.com/b/deploymentguys/archive/2013/05/16/deploying-drivers-and-firmware-to-surface-pro.aspx?Redirected=true
Now it's bricked. How can I manually apply this firmware update. I tried applying the update through windows update, then get errors from sysprep that it can't sysprep an updated system.

45 Minutes in, 4 different reps and departments. Not one knows what they're talking about. One of them even asked what product I was calling about after I said I was having issues with a Surface Pro.

Surface Pro 3 Display/Video/Graphics Driver Issues - DisplayPort, External Monitors, Windows 10 Build 9926

Surface Pro 3 - i5 with Intel HD Graphics 4400
Windows 10 build 9926
All Latest updates installed
Intel Graphics Driver 10.18.15.4079.
Latest system update released on Jan 22nd (which I understand is just the latest intel graphics driver?).
The display driver status has this error message: Windows has stopped this device because it
has reported problems. (Code 43) - I assume it's
reverting to the basic Microsoft driver when this occurs. Which explains why my displayport (External monitors) will not work.
I have uninstalled the driver completely (and deleted the driver files), tried the Windows basic driver,
and rebooted several times with no luck.
I cannot get my docking station displayport or the displayporton my surface pro 3 working.
According to Microsoft (see below), this is a known issue UNTIL you update to display driver
version 4079 - which I have.
Known issues on Surface after updating to Windows 10 January Technical Preview
On Surface Pro 2 and Surface Pro 3, the Mini DisplayPort won’t work on the Windows 10 January Technical Preview until you’ve installed graphics driver 4079 or later. Check Windows Update often for the most recent graphics driver.
On Surface Pro 2 and Surface Pro 3, you’ll notice poor graphics rendering on the Windows 10 January Technical Preview until you’ve installed graphics driver 4079 or newer from Windows Update. Check Windows Update often for the most recent graphics driver.
If you’re using video driver 3496, you may need to start in safe mode and remove that driver. Then restart Surface in normal mode and go to Windows Update to get the most recent graphics driver.

Hi Nicholas,
Similar issue has been asked here:
Surface Pro 3 restarting after a series of blank screens!
For error code 43, here is a reference:
Code 43: Windows has stopped this device because it has reported problems
For the current situation, please try to wait for the driver update, as display driver version 4079 didn't work well at your side, please submit this through Windows Feedback Tool.
Best regards
Michael Shao
TechNet Community Support

Surface Pro 2, Functionality Issues with Photoshop

I've been working with PS for years, and previously used a Cintiq, but i would like to branch out somewhat to a Surface Pro 2 by Microsoft. However, i've been having issues with the way the pen works and how the program reacts to swiping.
I would like to know if i can change the functionality of the button on the stylus on the Surface Pro, as i often have with my Cintiq tablet. Currently it pulls up the brush menu, when i would like it to function as an eraser.
Further, PS seems to react to any upward swipe from my finger by throwing the view of the canvas wildly to the upper corner, rather than a gentle scroll.

I've been working with PS for years, and previously used a Cintiq, but i would like to branch out somewhat to a Surface Pro 2 by Microsoft. However, i've been having issues with the way the pen works and how the program reacts to swiping.
I would like to know if i can change the functionality of the button on the stylus on the Surface Pro, as i often have with my Cintiq tablet. Currently it pulls up the brush menu, when i would like it to function as an eraser.
Further, PS seems to react to any upward swipe from my finger by throwing the view of the canvas wildly to the upper corner, rather than a gentle scroll.

Surface Pro Wifi Issues

I'm currently running Arch on my Surface Pro, and I'm having an issue with the wifi. I'm using wpa_supplicant with wpa_gui, and whenever I connect using the mwifiex_usb module, it works for a bit (like 3 minutes), then it stops working and I have to reboot and start again. Can anyone help me get the wifi working properly? Also, if I try to start wpa_gui, it just says "Cannot get status from wpa_supplicant." I checked if wpa_supplicant was running, and everything is fine with that. I always have to start it from terminal. Thanks in advance.
Last edited by kkeller (2013-06-11 06:46:02)

kkeller wrote:I'm currently running Arch on my Surface Pro, and I'm having an issue with the wifi. I'm using wpa_supplicant with wpa_gui, and whenever I connect using the mwifiex_usb module, it works for a bit (like 3 minutes), then it stops working and I have to reboot and start again. Can anyone help me get the wifi working properly? Also, if I try to start wpa_gui, it just says "Cannot get status from wpa_supplicant." I checked if wpa_supplicant was running, and everything is fine with that. I always have to start it from terminal. Thanks in advance.
So I figured out the issue with wpa_gui. It was because every time I boot I have to run
sudo modprobe -r mwifiex_usb && sudo modprobe mwifiex_usb
When I run that, wpa_gui works, but the problem with it disconnecting after a few minutes and having to reboot still persists. Also, if I don't run that, and try to connect with wpa_supplicant in terminal, my computer shuts off instantly and reboots. If you need any more info to help me, please tell me.
Last edited by kkeller (2013-06-11 20:32:40)

Having issues with Surface Pro 3 downloading boot image over PXE

Hi,
We've recently started to buy the new Surface Pro 3 with the new USB 3.0 Gigabit Ethernet adapter and we have some issues deploying them through SCCM. Basically, with the Pro 2 and Fast Ethernet adapter we have no issue at all, of course the deployment is
a bit longer than on any other computer, but it is still quite faster than the latest Surface.
We have the new 8.13.414.2014 driver injected in the Win 8.1 boot image for the USB 3.0 Gigabit adapter and all the drivers assigned to the new Surface in SCCM.
The problem occurs when we try to load the boot image after choosing PXE, it takes more than an hour to load it when it shouldn't take more than 5 minutes.
I tried rolling back to the old driver (8.6.128.2013) and use the Fast Ethernet adapter, use the Fast Ethernet adapter with the new driver and use the new adapter with the old driver, but it's still slow in any case, so
I'm pretty sure it has something to do with the new Surface and not the Ethernet adapter.
Anyone have an idea what could be the problem here? Anyone having issues with Surface Pro 3 and SCCM 2012?

I would imagine you have upgraded to R2, have you also applied KB2905002.
This hasn't got anything to do with the TFTP loading phase of the boot image.
Similar thread to this can be found here:
http://social.technet.microsoft.com/Forums/en-US/a6d80714-dc26-43db-a071-93eaee267122/surface-pro-2-surface-ethernet-adapter-super-slow-pxe?forum=configmanagergeneral
I already asked in that thread the same question, but how about normal PCs that are connected to the same network segment as the Surface devices, do they boot slow also?

Brush issue on surface pro 3 (screenshot)

This is happening on my canvas when I try to draw with the pen tool. When I make a stroke, the line becomes long and straight automatically, thus make me unable to draw.
Could someone tell me why this happening?
I'm using the latest update of flash professional CC. I'm using the 64-bit surface pro 3, Intel Core i3-4020Y CPU @ 1.50GHz, 4.00 GB of RAM, using windows 8.1 pro

Hi All,
Thanks for your patience. Patch for FlashPro CC 2014 (Build No. 14.2.0.20) was released yesterday, requesting you to please update and try and let us know if you still face any issues.
You can update your Flash CC 2014 build by just going to Help>Updates or through Creative Cloud App.
You can learn more about the update at Flash Professional Help | New features summary
Rgds,
Mukesh

Surface Pro 3 - MBAM/BitLocker/TPM: "An Error Has Occurred" Issue

We are trying to implement full disk encryption using MBAM Server/Client and BitLocker. We have been successful on standard Windows 7 Ent and Windows 8.1 Ent laptops and the MBAM Console reports encrypted/compliant.
The Surface Pro 3 running Windows 8.1 Ent however has been a pain in the you-know-what! It just will not work like our laptops. The Event Viewer error we get is as follows:
"An error occurred while applying MBAM policies.
Volume ID:\\?\Volume{dfd94fd0-206c-45d1-a19a-6a39019ada1e}\
Error code:
0x80310018
Details:
You must initialize the Trusted Platform Module (TPM) before you can use BitLocker Drive Encryption."
For reference, here is our workflow:
1. Enable TPM in UEFI.
2. Install .NET 3.5 since this is apparently a Windows 8.1 requirement for MBAM. Reboot. Install related updates from Microsoft Update. Reboot.
3. Verify relevant MBAM & BitLocker GPOs are applied by running "gpupdate /force" in an elevated command prompt. Reboot.
4. Run the following elevated PowerShell commands and then reboot:
$tpm=get-wmiobject -class Win32_Tpm -namespace root\cimv2\security\microsofttpm
$tpm.DisableAutoProvisioning()
$tpm.SetPhysicalPresenceRequest(22)
5. Install MBAM Client 2.5 and KB2975636 hotfix.
6. Run MBAMClientUI.exe and set PIN. On our laptops, encryption begins, but on the Surface Pro 3 we get a generic "An error has occurred". Event Viewer shows the above error.
Can anyone help?? There has got to be others that have used MBAM on the Surface Pro 3.

More testing today and I *think* I may have found my issue.
I failed to mention that on step 5 above, I have been rebooting after installing the MBAM Client and hotfix. It appears that this extra reboot breaks the process and does not allow the MBAM Client to initialize the TPM when running MBAMClientUI.exe. If I do
not reboot, then everything seems to work great.

Surface Pro 3, Remote Desktop, multiple monitors, Windows 8.1 DPI scaling issues

I have been evaluating Surface Pro 3 and once of the attributes is the display. Here is the description of the environment and the remote desktop display issue.
Surface Pro 3 (Windows 8.1 with latest firmware and Windows updates) has 12 inch built-in screen with native resolution 2160x1440. The Surface is docked and an external monitor (native resolution 1920x1080) is connected to the docking stations. The
display configuration doesn't allow for different scaling for each monitor, single scaling value is used for multiple monitors. This is an issue as the recommended scaling of 150% is optimal for small built-in screen of Surface but it is not optimal for
large screens of external monitors. Also this scaling is "inherited" by a remote desktop session which results in objects being too large on the remote desktop sessions or sometimes even blurry/fuzzy.
Can the blurriness/fuzziness of the remote desktop session be resolved?
Z

Hi Colin,
Thanks for the response. I installed the latest firmware and patches about a week ago and the scaling issue improved. It is not optimal yet as some graphical elements are still out of proportions but I do not want to spent more resources on this subject
anymore.
Best regards,
Zbysek
Z

Surface Pro pressure sensitivity issue...

Anyone out there have an update on the issue to use the pressure sensitivity on the Surface Pro, yet???ANY info will be appreciative from Adobe of MS....THANKS!!!-
joe

This is a user forum you may wat to as on the Microsoft website and on Adobe site http://feedback.photoshop.com/photoshop_family/ I'm sure Adobe will point you at Microsoft. Microsoft uses a different API in its device driver then the API supports for tablet support

PS CC issue on a Surface Pro 2

Similar Messages

Maybe you are looking for