2011 Software releases
Learn about the 2011 versions of some of Autodesk’s Digital Entertainment Creation tools.
  • 1/2
You are here:Forum Home / Autodesk® Sketchbook Pro / General Discussion / Can't save work in SBP 2010
Feedback

Tell us what you think of the site.

 
Autodesk Maya 2011
Autodesk 3ds Max 2011
Autodesk Softimage 2011
Autodesk MotionBuilder 2011
Autodesk Mudbox 2011
Autodesk Maya 2011 Entertainment Creation Suite
Autodesk 3ds Max 2011 Entertainment Creation Suite
Autodesk FBX 2011
Autodesk Kynapse 7
Autodesk Human IK 4.5
 
Latest Blogs
With Design in Mind
Mastering mental ray
Mayalicious
The View from GDC
More Blogs
Software Trials
Autodesk® 3ds Max®
Download Trial
Autodesk® Maya®
Download Trial
Autodesk® Softimage®
Download Trial
Autodesk® MotionBuilder®
Download Trial
Autodesk® Mudbox™
Download Trial
Autodesk® ImageModeler™
Download Trial
Autodesk® Sketchbook® Pro
Download Trial
Autodesk® Smoke on Mac®
Download Trial
Quick Links
Fake or Foto
Autodesk Masters
Professional Instructor Community
Creative Careers
System Training Tutorials
My First Flame
Maya 10th Anniversary
Autodesk Maya Bonus Tools
Autodesk Sketchbook Pro
Autodesk FBX
  RSS 2.0 ATOM  
2 pages: 1.2 first

Can't save work in SBP 2010
Rate this thread
 
36522
 
Subscribe to this thread
avatar
  • Lars82
  • Posted: 09 January 2010 04:25 AM
  • Total Posts: 2
  • Joined: 2009-12-18 12:48:18

I actually had the latest driver for my Intous 3 version 6.1.2-5. I got in in december, however Wacom seems to have done one more update in January but with the same filename, 6.1.2-5 and using that one worked. Now I can actually save and open at first start, still it lags alittle takes some time before the save menu pops up but it works…


Replies: 0
avatar
  • flaye
  • Posted: 25 January 2010 12:11 PM
  • Total Posts: 9
  • Joined: 2006-10-26 02:52:44

Just updated latest Wacom drivers to 6.13-5 and problem is appearing again.

Can that be verified?

Thanks.

Wacom Intuos 3 6X8 (PTZ-630)
Windows 7 Pro x64


Replies: 0
avatar
  • Orb
  • Posted: 08 February 2010 06:44 PM
  • Total Posts: 9
  • Joined: 2009-11-09 20:46:26

Original problem is still the same for me using any of the Wacom drivers, inc the latest ones (6.1.3-5) Personaly I don’t this issue has anything to do with Wacom drivers, I think It’s more likely the way Sketchbook Pro interacts with Windows 7 x64 bit.


ASUS Maximus II Formula
Q9650 @ 4.2GHz / VenomousX (Lapped)
8GB OCZ platinum PC8500
ASUS GTX 295
60GB OCZ Vertex Turbo
3x SATA II Seagate HDD’s (5TB)
Dual Digital TV
Enermax Revolution85+ 1250W
Windows 7 Ultimate x64
26” IIyama Prolite
Replies: 0
avatar
  • Total Posts: 3
  • Joined: 2010-02-09 12:15:55

Just for info, and it could be useful for the staff to know this, I have been running SBP 2010 in Windows 7 32bit on a Toshiba Tablet and it is working normally.  So it may only be the 64bit version that’s causing issues.  Even when I updated with the service pack, I didn’t see any noticeable difference, which is probably a good thing.

The one minor glitch I noticed when first saving my work as a PSD file, SPB creates an additional Background layer.  Other than that, the software works normally even with a dual monitor set-up and 2 different screen orientations (one landscape, one portrait).

Hope that bit of info helps, somewhat.


Replies: 0
avatar
  • McCue
  • Posted: 17 February 2010 10:30 AM
  • Total Posts: 1
  • Joined: 2010-02-17 15:16:56

I’m currently having the same problem with Windows 7 64bit, sketchbook pro 10, and a Wacom Intuos 3.  This is a new problem for me, when I first upgraded to windows 7 64-bit sketchbook worked fine for a few weeks.  Then with no warning or changes that I can remember I wasn’t able to save, open etc… I can also open files by dragging them to the sketchbook icon.  In my case re-opening the software does nothing to fix it, so the only workaround that I’ve been able to find is to use the “send mail” functionality to e-mail my sketches to myself.  I’ve tried uninstalling and reinstalling sketchbook and running in Win XP SP3 compatibility mode (that’s what I upgraded from) neither worked.  Base on some of the previous posts I uninstalled the Wacom driver and then I could save and open, so I think they are related.  I was guessing that it was a problem with the newest driver (6.1.3-5) so I went to the Wacom website and downloaded version 6.1.2-5 from Nov 25th.  I installed it and could still save and open so I thought I was golden.  However after a computer restart I’m back to where I started.  Again I uninstalled the Wacom driver and again sketchbook worked fine.  This is obviously a very serious problem.  If sketchbook can’t work with the Wacom tablet it is obviously worthless.  I’m grateful that at least I’m not the only one with the problem, but very frustrated that you all have been having this problem for months with no solution from Autodesk.  As far as I can tell they don’t even provide support of any kind for sketchbook!  Please if anyone knows anything post it.


Replies: 1
/userdata/avatar/5422tmd7y_sbp.png

hi McCue:

thanks for your feedback.
Just wanted to tell you that we are looking into this issue. Our QA team is trying to reproduce it and then development can take it from there.
We have to rely on the quality of the hardware drivers and if they fail either we try to find a workaround or just wait for a fix from the driver author.
Hopefully we’ll soon be able to reproduce it and find a fix for this.

Author: Ivan Pinzon
Replied: 18 February 2010 09:22 AM  
avatar
  • rseven
  • Posted: 18 February 2010 03:33 PM
  • Total Posts: 5
  • Joined: 2010-02-18 20:28:38

Another Win7 x64 user here. I’ve found that I can restore the save dialog by completely unchecking “Read Only” on /Program Files (x86)/Autodesk/ or /Program Files (x86)/Autodesk/SketchBookPro2010. The problem is that flag gets set every time Windows starts up, so it has to be done after every boot. I’ll try installing it in another location and see what happens.

EDIT: Alright, my mistake on the flag - it doesn’t appear to take effect when you hit OK, even though the program starts working after it’s been toggled. Interestingly, installing SBP to a directory I have full control over (like, a storage partition or /Users/me/) breaks this workaround.

DOUBLE EDIT: Now this is interesting. Here’s what I did:

Try #1:

1) Ran the program in a vanilla state; no flags or compatibility.
2) Tried to save; didn’t work.
3) Restarted the program. Save still didn’t work.

Try #2:

1) Toggled the XP compatibility flag and ran it again.
2) Save didn’t work.
3) Restarted SBP; save worked fine.

So it’s like somebody said earlier - start the program and then restart it, and saving will work until reboot. BUT!

4) Untoggled the compatibility flag and ran the program again. Save worked fine.

And it’s continued to work fine since, in spite of the compatibility flag being off. Weird.


Replies: 2
/img/forum/dark/default_avatar.png

rseven,

Great observations!  I’m not able to reproduce the problem on our win7-64 setup.  I’ve tried the following wacom drivers.
6.1.4-3
6.1.3-5
6.1.2-3
6.1.0-6

The problem may not necessarily lie with the wacom drivers, so all other areas of investigation are valid.  I’m trying to acquire other test machines, particularly laptops. 

QA reference (bug 350081)

Author: Sydney Cheang
Replied: 18 February 2010 07:39 PM  
/img/forum/dark/default_avatar.png

Sydney: I attached a debugger to SBP and found out some more stuff - not sure if it’s as helpful as I hope it is, but it IS interesting. When running SBP before doing the compatibility flag, here are the DLLs it calls when you try to save:

ModLoad: 748e0000 7490f000 C:\Windows\SysWOW64\xmllite.dll
ModLoad: 6da60000 6daf4000 C:\Windows\SysWOW64\MsftEdit.dll
ModLoad: 748e0000 7490f000 C:\Windows\SysWOW64\xmllite.dll

But after the compatibility flag tweak AND restarting the program, it access way more than just those two DLLs:

Thu Feb 18 20:23:39.926 2010 (GMT-5): ModLoad: 747e0000 748d5000 C:\Windows\SysWOW64\propsys.dll
Thu Feb 18 20:23:39.928 2010 (GMT-5): ModLoad: 74d10000 74d31000 C:\Windows\SysWOW64\ntmarta.dll
Thu Feb 18 20:23:39.928 2010 (GMT-5): ModLoad: 77630000 77675000 C:\Windows\syswow64\WLDAP32.dll
Thu Feb 18 20:23:39.942 2010 (GMT-5): ModLoad: 03400000 0347b000 C:\Windows\SysWOW64\comdlg32.dll
Thu Feb 18 20:23:40.018 2010 (GMT-5): ModLoad: 06b60000 077a9000 C:\Windows\SysWOW64\shell32.dll
Thu Feb 18 20:23:40.049 2010 (GMT-5): ModLoad: 69060000 691cf000 C:\Windows\SysWOW64\explorerframe.dll
Thu Feb 18 20:23:40.050 2010 (GMT-5): ModLoad: 6cbf0000 6cc1f000 C:\Windows\SysWOW64\DUser.dll
Thu Feb 18 20:23:40.051 2010 (GMT-5): ModLoad: 68fa0000 69052000 C:\Windows\SysWOW64\DUI70.dll
Thu Feb 18 20:23:40.066 2010 (GMT-5): ModLoad: 74790000 747db000 C:\Windows\SysWOW64\apphelp.dll
Thu Feb 18 20:23:40.069 2010 (GMT-5): ModLoad: 10000000 10024000 C:\Program Files (x86)\ASUS\ASUS Data Security Manager\ShlExt\x86\OverlayIconShlExt.dll
Thu Feb 18 20:23:40.074 2010 (GMT-5): ModLoad: 06ce0000 06d03000 C:\Program Files (x86)\ASUS\ASUS Data Security Manager\ShlExt\x86\OverlayIconShlExt1.dll
Thu Feb 18 20:23:40.090 2010 (GMT-5): ModLoad: 6c950000 6c981000 EhStorAPI.DLL
Thu Feb 18 20:23:40.105 2010 (GMT-5): ModLoad: 6c950000 6c981000 C:\Windows\SysWOW64\EhStorShell.dll
Thu Feb 18 20:23:40.230 2010 (GMT-5): ModLoad: 6ce30000 6ce9f000 ntshrui.dll
Thu Feb 18 20:23:40.243 2010 (GMT-5): ModLoad: 6ce30000 6ce9f000 C:\Windows\SysWOW64\ntshrui.dll
Thu Feb 18 20:23:40.245 2010 (GMT-5): ModLoad: 72770000 72789000 C:\Windows\SysWOW64\srvcli.dll
Thu Feb 18 20:23:40.250 2010 (GMT-5): ModLoad: 6f080000 6f08b000 C:\Windows\SysWOW64\cscapi.dll
Thu Feb 18 20:23:40.251 2010 (GMT-5): ModLoad: 6cf00000 6cf0a000 C:\Windows\SysWOW64\slc.dll
Thu Feb 18 20:23:40.296 2010 (GMT-5): ModLoad: 748e0000 7490f000 C:\Windows\SysWOW64\xmllite.dll
Thu Feb 18 20:23:40.323 2010 (GMT-5): ModLoad: 6da60000 6daf4000 C:\Windows\SysWOW64\MsftEdit.dll
Thu Feb 18 20:23:40.330 2010 (GMT-5): ModLoad: 06ee0000 06fac000 C:\Windows\SysWOW64\msctf.dll
Thu Feb 18 20:23:40.336 2010 (GMT-5): ModLoad: 06ee0000 06fac000 C:\Windows\SysWOW64\msctf.dll
Thu Feb 18 20:23:40.338 2010 (GMT-5): ModLoad: 6cbc0000 6cbea000 C:\Windows\SysWOW64\msls31.dll
Thu Feb 18 20:23:40.345 2010 (GMT-5): ModLoad: 6d2f0000 6d348000 C:\Program Files (x86)\Common Files\microsoft shared\ink\tiptsf.dll
Thu Feb 18 20:23:40.374 2010 (GMT-5): ModLoad: 748e0000 7490f000 C:\Windows\SysWOW64\XmlLite.dll
Thu Feb 18 20:23:40.379 2010 (GMT-5): ModLoad: 720c0000 720c9000 C:\Windows\SysWOW64\LINKINFO.dll
Thu Feb 18 20:23:40.405 2010 (GMT-5): ModLoad: 6cf70000 6d00f000 C:\Windows\SysWOW64\SearchFolder.dll
Thu Feb 18 20:23:40.605 2010 (GMT-5): ModLoad: 74e70000 74eac000 C:\Windows\SysWOW64\OLEACC.dll
Thu Feb 18 20:23:40.607 2010 (GMT-5): ModLoad: 68f10000 68f9c000 C:\Windows\SysWOW64\UIAutomationCore.dll
Thu Feb 18 20:23:40.607 2010 (GMT-5): ModLoad: 75d00000 75d05000 C:\Windows\syswow64\PSAPI.DLL
Thu Feb 18 20:23:40.611 2010 (GMT-5): ModLoad: 07280000 0730c000 C:\Windows\SysWOW64\uiautomationcore.dll
Thu Feb 18 20:23:40.615 2010 (GMT-5): ModLoad: 6f300000 6f35f000 C:\Windows\SysWOW64\SXS.DLL
Thu Feb 18 20:23:40.620 2010 (GMT-5): ModLoad: 6d290000 6d2ec000 C:\Windows\SysWOW64\StructuredQuery.dll
Thu Feb 18 20:23:40.621 2010 (GMT-5): ModLoad: 72210000 72218000 C:\Windows\SysWOW64\Secur32.dll
Thu Feb 18 20:23:40.670 2010 (GMT-5): ModLoad: 6e240000 6e24c000 C:\Windows\SysWOW64\mssprxy.dll
Thu Feb 18 20:23:40.681 2010 (GMT-5): ModLoad: 6cef0000 6cef6000 C:\Windows\SysWOW64\IconCodecService.dll
Thu Feb 18 20:23:40.883 2010 (GMT-5): ModLoad: 6f490000 6f4a6000 C:\Windows\SysWOW64\thumbcache.dll
Thu Feb 18 20:23:40.941 2010 (GMT-5): ModLoad: 68ab0000 68b56000 mssup.DLL
Thu Feb 18 20:23:40.952 2010 (GMT-5): ModLoad: 6dde0000 6de0e000 C:\Windows\SysWOW64\SHDOCVW.dll
Thu Feb 18 20:23:40.953 2010 (GMT-5): ModLoad: 6afe0000 6ba5c000 C:\Windows\SysWOW64\ieframe.DLL
Thu Feb 18 20:23:40.959 2010 (GMT-5): ModLoad: 68a00000 68aa6000 C:\Windows\SysWOW64\mssvp.dll
Thu Feb 18 20:23:40.959 2010 (GMT-5): ModLoad: 6cba0000 6cbb6000 C:\Windows\SysWOW64\MAPI32.dll
Thu Feb 18 20:23:41.024 2010 (GMT-5): ModLoad: 08590000 085cc000 C:\Windows\SysWOW64\oleacc.dll
Thu Feb 18 20:23:41.162 2010 (GMT-5): ModLoad: 68820000 689b8000 NetworkExplorer.dll
Thu Feb 18 20:23:41.172 2010 (GMT-5): ModLoad: 68820000 689b8000 C:\Windows\SysWOW64\NetworkExplorer.dll
Thu Feb 18 20:23:41.314 2010 (GMT-5): ModLoad: 74500000 74512000 C:\Windows\SysWOW64\MPR.dll
Thu Feb 18 20:23:41.317 2010 (GMT-5): ModLoad: 72740000 72748000 C:\Windows\SysWOW64\drprov.dll
Thu Feb 18 20:23:41.318 2010 (GMT-5): ModLoad: 74e30000 74e59000 C:\Windows\SysWOW64\WINSTA.dll
Thu Feb 18 20:23:41.319 2010 (GMT-5): ModLoad: 6cf50000 6cf64000 C:\Windows\SysWOW64\ntlanman.dll
Thu Feb 18 20:23:41.320 2010 (GMT-5): ModLoad: 6ceb0000 6cec6000 C:\Windows\SysWOW64\davclnt.dll
Thu Feb 18 20:23:41.320 2010 (GMT-5): ModLoad: 72730000 72738000 C:\Windows\SysWOW64\DAVHLPR.dll
Thu Feb 18 20:23:41.336 2010 (GMT-5): ModLoad: 72760000 7276f000 C:\Windows\SysWOW64\wkscli.dll
Thu Feb 18 20:23:41.341 2010 (GMT-5): ModLoad: 72790000 72799000 C:\Windows\SysWOW64\netutils.dll
Thu Feb 18 20:23:41.343 2010 (GMT-5): (c60.8fc): Unknown exception - code 000006ba (first chance)
Thu Feb 18 20:23:41.397 2010 (GMT-5): ModLoad: 685e0000 68818000 WPDSHEXT.dll
Thu Feb 18 20:23:41.410 2010 (GMT-5): ModLoad: 683a0000 685d8000 C:\Windows\SysWOW64\wpdshext.dll
Thu Feb 18 20:23:41.420 2010 (GMT-5): ModLoad: 6cd10000 6cd99000 C:\Windows\SysWOW64\PortableDeviceApi.dll
Thu Feb 18 20:23:41.436 2010 (GMT-5): ModLoad: 77230000 7725d000 C:\Windows\syswow64\WINTRUST.dll
Thu Feb 18 20:23:41.457 2010 (GMT-5): ModLoad: 6cb60000 6cb9f000 SHMEDIA.dll
Thu Feb 18 20:23:41.472 2010 (GMT-5): ModLoad: 6af80000 6afbf000 C:\Windows\SysWOW64\audiodev.dll
Thu Feb 18 20:23:41.481 2010 (GMT-5): ModLoad: 68130000 68397000 C:\Windows\SysWOW64\WMVCore.DLL
Thu Feb 18 20:23:41.482 2010 (GMT-5): ModLoad: 6cb60000 6cb9d000 C:\Windows\SysWOW64\WMASF.DLL
Thu Feb 18 20:23:41.517 2010 (GMT-5): ModLoad: 6cce0000 6cd02000 C:\Windows\SysWOW64\EhStorAPI.dll

It seems weird that it would skip all the UI stuff and go straight for the XML stuff, which doesn’t happen until after it’s done all its dialog voodoo in the sort-of-fixed executable.

I’m running Win 7 x64 Enterprise on an Asus G60 with a non-English system locale, by the way.

Author: rseven
Replied: 18 February 2010 08:32 PM  
avatar
  • Total Posts: 34
  • Joined: 2008-09-30 00:02:18

Hi rseven,

Thanks for the log.  I’ll have Ivan our developer look at it.

One thing worth investigating is the Aeroglass look on Win7.  I know there have been improvements to it over previous OSs and I also know that it’s been a thorn in our sides for some of our other products.

Maybe try to disable Aeroglass. 

1. Go to your Control Panel
2. Click ‘Appearance and Personalization’
3. Under the ‘Personalization’ category click ‘Change window glass colors’
4. Toggle off ‘Enable transparency’
5. Save changes

Now run Sketchbook and let me know if the problem is still there.

Since I’ve not been able to reproduce the problem myself, I’m relying on you for feedback.

Cheers,
syd


Replies: 1
/img/forum/dark/default_avatar.png

I toggled off the transparency. No effect, unfortunately.

Author: rseven
Replied: 19 February 2010 04:59 PM  
avatar
  • Total Posts: 34
  • Joined: 2008-09-30 00:02:18

Thanks rseven,

There are a few other test platforms available here.  I’ll do some further digging.


Replies: 0
avatar
  • Total Posts: 34
  • Joined: 2008-09-30 00:02:18

Here’s a few further suggestions:

Disable flicks.  This might not sound related, but we’ve had the flicks behavior interfere with our products in the past in unpredictable ways.  To disable flicks,

1. Right click on the flicks icon in the system tray (That bunch of icons on the right side of the windows task bar)
2. Select ‘Turn off Flicks’.

Unless I missed it in the thread, can someone confirm that the next/previous image allows you to open and save images?

Also can anyone remember if they had any system updates or hardware driver (except Wacom) updates before the problem occured?  Any feedback regarding this might be a clue.

Thanks,
syd


Replies: 1
/img/forum/dark/default_avatar.png

Flicks was already disabled, so no dice there. Next/previous image allows saving, but not Save As or Save a Copy As - the dialog won’t come up. SBP was installed on a brand-new Win7 x64 Enterprise installation; I’ve never been able to save files without doing any of the previously mentioned tweaks.

Author: rseven
Replied: 24 February 2010 03:22 PM  
avatar
  • Location: Shanghai
  • Total Posts: 17
  • Joined: 2009-05-08 08:41:26

Hi All,

One more question that I want to ask, where did you install Sketchbook? Is it in the default install location or a customized one? Is it on another partition or another hard disk?

Thanks,
Junjie


Replies: 2
/img/forum/dark/default_avatar.png

It’s currently installed in the default location, but I got the same problems when I installed it in a custom location on another partition.

Author: rseven
Replied: 25 February 2010 08:19 AM  
/img/forum/dark/default_avatar.png

Same here, I’ve had it installed on a few different partitions inc C: still the same problem though. I’ve actually got used to opening the program twice now though as I learned my lesson after loosing work when the save dialog box wouldn’t show after drawing :)

Author: Orb
Replied: 03 March 2010 08:07 PM  
2 pages: 1.2 first




   
  Settings Choose Theme color:  
 
The Area
© Copyright 2010 Autodesk. Inc.
All rights reserved
Legal Notices & Trademarks - Privacy Policy
Autodesk