CS2 Pressure Functionality on Surface Pro 3

Hello all,
I just got a Surface Pro 3 and have been struggling to get pressure support with the Pro Pen.
I've read support topics that suggest downloading the wintab driver and the Wacom driver, although when I do that, I just get the error that there's no supported devices detected. My pen is paired and working fine.
I guess my main question is:
Has anyone been successful getting this to work? If so, can someone point me in the direction of an answer, or help me get it set up?
Thank you all. Every bit of feedback is helpful!

Just figured it out myself, but for anyone who's interested:
Wintab - N-trig
You'll need the 32-bit driver installed, and pressure sensitivity will work.

Similar Messages

Surface Pro 3 no pen pressure in CS6?

I have just purchased a Surface Pro 3 and have downloaded Adobe Suite, particularly to use Photoshop CS6.
However, I have no pen pressure in Photoshop CS6! It's incredibly frustrating!
I can draw with the Surface Pen, but there is no pressure sensitivity - even when I switch sensitivity on. (I am experienced using Photoshop and understand how to use these functions).
The Surface Pen seems to be working fine in all other applications.

You say the pen is "working fine" in all other applications, but does this mean you're getting pressure sensitivity in other applications?
I just got a SP3 a couple of months ago and as I recall, once you calibrate it and pair it the Surface Pen will function, but without pressure sensitivity. After doing some research I ended up downloading and installing the N-trig Wintab driver and I now have pressure sensitivity in a variety of art programs, e.g. Photoshop CC & CC 2014, ArtRage, Sketchbook Pro, Manga Studio 5, and Painter 2015.
I understand that Microsoft has now released Surface Hub, an app that enables sensitivity adjustment and is available in the Microsoft store. My impression is that you would install this for newer apps and only if you have not already installed the Wintab driver. The Surface Hub seems to be getting mixed reviews.
See this Microsoft page for further information and links: http://www.microsoft.com/surface/en-us/support/touch-mouse-and-search/troubleshoot-surface -pen#pressure

Surface Pro pen pressure is not working in Photoshop

I just bought Microsoft Photoshop.
But Adobe Photoshop doesn't provide pen pressure sensitivity.
I tested Microsoft OneNote, Fresh Paint, and Autodesk Sketchbook. They are working well.
Please provide the pen pressure function in Photoshop too.

On the Main photoshop forum, one of the Adobe staff is stating that the issue is with Microsoft and not Adobe. I can not see the code nor do I own a surface pro therefore I can not confirm nor deny it. In other words, I am a poor lonely user with the same access as every other user. LOL.

Pen Pressure in Photoshop on MS Surface Pro..

Did anyone get the new update today and did it fix the pen pressure issue for Photoshop use on the MS Surface Pro Tablet???? I know this is an aging die hard issue but man do I need it bad,.....-Joe

Hey there folks,
I figure I take some time to respond to the surface pro things,.....
@Alanomaly, yes pretty good so far, I can not complain about the pen pressure. MS had nothing to do with it except to communicatge with Adobe, and Wacom..as things go, all three needed to agree on working on this. The driver is through Wacom on their site under the Tablet PC select. Thats it. You load, restart PC an it works.
Now as far as comparing it to Intuos/Cintiq, well, its not a question really. The Surface Pro tablet functions like a PC but is smaller than a 9x12 Intuos and Cintiq, with the exception of the smallest sizes of eother of those. But, I do not use the smaller sizes. I do have a Cintiq 24 HD, love it!!! When Im away, the road, at the shore,..or at work and want to doodle, sketch, concept draw, whatever, Im not using Surface Pro to do full fledged digital content, ..Ill take it home and finish or expand on it.....but I wont divulge my personal reasons for using it , but, that is why I think Surface Pro exists, so I can use it for what I want and be happy. Now, if Wacom comes out w a tablet and its a tablet like Surface Pro, and a user wont need to hook up a Wacom type of tablet to a PC to work on it as a mobile device, then, I ll be rethinking my options....maybe.
Now, I have a Xeon cpu in my machine and a second one when Im ready to use it, and I see the i5 and i7 cpus really taking advantage of the mixer brushes and interactive brushes better than my xeon cpus. I wish to make that better on my machine but thats another story.
I hope tht helps.....
-J

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.

Photoshop CS6 Brush pressure sensitivity not working on the Microsoft Surface Pro.

I have just purchased a Microsoft Surface Pro in anticipation of running Photoshop on it. I installed Photoshop and tried to do some sketches. I created a new file and started sketching. I Immediately felt like something was wrong. I checked my brush settings and saw the pressure sensitivity was not available. Everytine I tried to turn it on it was marked with an exclamation point.
Does anybody know if Adobe is supporting the new pressure sensitive pen from microsoft, or if there is some sort of setting that I am missing? I have tried sketchbook pro 2011, and that works amazingly well with the pen. I hope someone can help me along here, because if this tablet can truely run photoshop, it would be a Game Changer.

Just curious.... has any of you tried the shape dynamics in photoshop and turning on pen pressure?
and in illustrator to modify the size to pressure and variation to maximum? (and of course select that brush preset that you just modified and draw with it using SHIFT+B for blob brush or B for regular brush)
I am also interested in purchasing a Surface pro so please report if this helps.
what I recently discovered in other forums is that Sketchbook Pro works flawlessly in desktop mode. Sketchbook Express in the APP mode doesn't support pressure yet.
there is no official confirmation that the surface pro uses a wacom digitizer, however a few artist friends of mine have gone to the microsoft store... brought their own wacom pens (cintiq 15x pen - older models that works with general tabletpcs) and the pro recognized it. which means that it is a wacom digitizer. it wouldn't make sense if a wacom pen works with a different digitizer board like N-trig.
also read in another forum about adobe using wintab and windows 8 wintab drivers are not there yet.
anyway... I'd be glad to know if this works or not
thanks!

Problem surface pro 2, windows 8. brush pressure is not working in Ps CC ,

problem surface pro 2, windows 8. brush pressure is not working in Ps CC

Este foro es un Foro de Usuarios en español.
Puedes probar a explicar tu problema con mayor detalle.
Indica por favor detalles de hardware
(Podemos estar familiarizados con Photoshop, pero no con tabletas híbridas)
Concretamente, cómo utilizas el pincel de presión?

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

Polygonal lasso tool not working with stylus on Surface Pro 2

Hi guys,
I'm new here so please bare with me if I'm posting in the wrong place or don't make immediate sense.
Hardeware / software used: surface pro 2 and I'm running photoshop CS5.
Problem is a fairly basic one: I am trying to make basic selections using the polygonal lasso tool (using the stylus that comes with the tablet) but it simply will not work. All I get when I touch the stylus to the screen is the circle that appears then fades. If I attach the keypad and try using that then it works no problem at all.
Does anyone have any ideas as to whether there is a particular setting that I need to switch on or off e.g. something relating to pressure sensitivity (although not sure why this would affect this particular selection tool)?
I've searched the web and come up with nothing so far so any help is greatly appreciated!
Thanks for your time
Scott

same problem on surface pro 3 !!!!
and i think quite significant, for lot of artists using polygonal lasso a lot (including me). How come that the stupid surface cannot work properly

Press and hold on a Surface pro touch screen

Hi,
I am having some problems with my Surface Pro, trying to control a relay 'press-and-hold'. When I connect a mouse to the Tablet, Windows registers the left mouse up and down events perfectly, allowing the user to control the relay exactly the way I intended, but when I use the touch screen with either the stylus pen or my finger it only seems to press the LabVIEW on release.
Does anyone have a solution for this problem?
Chris

Jeff-P wrote:
I just tested this on my touchscreen laptop and got a similar behavior. Windows doesn't seem to be registering the left click when you touch the screen until you release. My guess is that this is related to the press+hold for right click functionality on Windows. When I touch and hold for over a second, I get a right click, but when I touch and hold for a shorter time, I get a left click that only registers when I take my finger off. This is consistent with the way that the Windows UI handles touch as well (test the start button for an example).
Interestingly, if I change the mechanical action of the LabVIEW boolean to 'Switch Unit Released' I can't actually toggle the button ever because the press and hold does not register as a left click, and eventually registers as a right click.
Jeff Peacock
Product Support Engineer | LabVIEW R&D | National Instruments | Certified LabVIEW Architect
Actually, this is expected behavior. Try clicking a button on any Windows app, then, while holding down the button, move off of it. The button does not register as pressed. This feature has saved me any number of times.
edit:
Or do you mean it doesn't even depress the button?
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

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 type cover not working

I just installed arch on my surface pro and the touch screen works well, as does the stylus, but the type cover/touchpad doesn't type or function at all. On startup two error messages are shown:
hid-multitouch 0003:045E:07A9:0005: HID_DG_INPUTMODE out of range
hid-multitouch 0003:045E:07A9:0005: No inputs registered, leaving
lsusb shows this:
Bus 004 Device 005: ID 045e:0794 Microsoft Corp.
Bus 004 Device 004: ID 03eb:8209 Atmel Corp.
Bus 004 Device 003: ID 045e:07a9 Microsoft Corp.
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 045e:0795 Microsoft Corp.
Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 0bda:0307 Realtek Semiconductor Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 1286:2044 Marvell Semiconductor, Inc.
Bus 001 Device 002: ID 040b:2000 Weltrend Semiconductor
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I'm not really sure how to debug this, so any help to get me in the right direction would be great,
Thanks!

As far as I can tell, the answer is buried in this thread: http://ubuntuforums.org/showthread.php?t=2183946

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!

Itunes Video Lag on the microsoft surface Pro

HI,
I recently purchased a Microsoft surface pro and installed itunes on it to watch all of my store bought series, however i noticed that as soon as i started to watch my purchases the HD content especially would stutter, lag and de sync from the audio playing.
i was wondering if anyone had similar problems or if anyone knows of a solution
so far i have tried switching the audio from itunes properties, and it did not work.
thanks

Just curious.... has any of you tried the shape dynamics in photoshop and turning on pen pressure?
and in illustrator to modify the size to pressure and variation to maximum? (and of course select that brush preset that you just modified and draw with it using SHIFT+B for blob brush or B for regular brush)
I am also interested in purchasing a Surface pro so please report if this helps.
what I recently discovered in other forums is that Sketchbook Pro works flawlessly in desktop mode. Sketchbook Express in the APP mode doesn't support pressure yet.
there is no official confirmation that the surface pro uses a wacom digitizer, however a few artist friends of mine have gone to the microsoft store... brought their own wacom pens (cintiq 15x pen - older models that works with general tabletpcs) and the pro recognized it. which means that it is a wacom digitizer. it wouldn't make sense if a wacom pen works with a different digitizer board like N-trig.
also read in another forum about adobe using wintab and windows 8 wintab drivers are not there yet.
anyway... I'd be glad to know if this works or not
thanks!

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 :-)

CS2 Pressure Functionality on Surface Pro 3

Similar Messages

Maybe you are looking for