October CC 2014 update causes crash on OBJ import.

I have been trying to import an OBJ file (created in c4dr16, saved as .obj) into AE CC 2014 for use with the Trapcode Form plugin; without fail it causes AE to crash on import.
I've tried going thru the import menu, dragging the file into the prj with the same results - crash.
Connecting to all media via network to servers uptairs.
black trash can
OS 10.9.4
is it just me?

You will have to take it up with Red Giant/ Trapcode. That being said, C4D simply outputs crappy OBJ files. Download Blender, open your file in there and export it again as a much better OBJ file.
Mylenium

Similar Messages

Source and Program Monitor not working after October CC 2014 Update

I updated to the October 2014 Replace of Premiere Pro and since then I have had major issues with the Source and Program monitors.
I can select a clip from the media browser and have it appear in the source monitor - click play. The clip will play for a bit and the picture will stop, but the audio will keep going. After a few seconds the source monitor will just display a red screen and the audio will keep going. The same things happens in the program monitor (different clips that worked before the October 2014 update) will start displaying the yellow media pending screen - and then go to red after a few seconds. Again - this is a mutli-camera sequence that worked before the October 2014 update.
I am pretty much dead in the water at this point. And yes, I have rebooted, changed the Mercury play back engine from hardware to software. Nothing seems to correct the issue.

I have had similar problems. In fact playback is so sluggish it is unworkable.
In addition Audio in nested sequences doesn't play back, and when it does it is intermittent. Totally unworkable!

Sec. update causes crash. help using DiskWarrior

hello folks
I updated via Software Update and crashed mightily. I think I'm back up and running now.
1.Used Disk Utility once I booted in Safe Mode.
2.I used Diskwarrior to rebuild the "directory". Is that correct term?
Can someone plz coach me correctly using DiskWarrior to prevent HD problems.I installed the software but I would really like to use it correctly.
Thanks
Chuck S
iBook G4 Mac OS X (10.4.6)

"Just use it!" DiskWarrior is a great program which does its own thing very well and safely. Macs have an invisible "directory" file which the operating system itself (OS 8.x, 9.x, X v. 10.x.x, etc.) uses for itself to keep track of where it puts every bit of information stored on your hard drive, as a "file" is not stored in one contiguous space necessarily (like a single can on a pantry shelf) but pieces of the file are poked into the convenient spaces wherever on your hard drive. Because it gets changed so often by the operating system, the directory file itself can get fragmented and/or write-errors can occur to it, such that it becomes less than 100% reliable as a road map for your OS. Hence, DiskWarrior. In a couple minutes or so, DW collects all the information to create a brand new directory file, writes it unfragmented to your hard drive, and then erases your old fragmented directory file. (You can also run the "graph" function to see how fragmented is your directory file at any given time. I personally keep my fragmentation level at below 1-2% by running DW whenever it is over that. Consequently, I have not had crashes (as opposed to things freezing up for lack of sufficient memory requiring simply a restart) which are damaging since getting DW years ago.)
Should you ever have a catastrophic problem nonetheless, do not try to use your own computer, as the directory file may get further damaged. Alsoft's tech support is very good about helping using DiskWarrior under such circumstances, so contact them by telephone, or email from a different computer.
You might want to make a backup copy of your DW disk and use it routinely to keep your original disk pristine. When you run DW, you should/must boot up your computer using the DW CD and use the program on the CD. DW cannot rebuild the directory of an active system hard drive (as obviously, the active system's hard drive's directory file is the one needing rebuilding and it itself would be trying to rebuild itself if it were also the boot drive!)
PM9600/233 (OS 8.6); PM9600/G4 (OS 9.1); Perform 6320 (OS 8.1); MacPlus-OS 6.0.8 Mac OS 8.6 or Earlier

2014.3 Update causing crashes and data loss

I have recently update to Adobe Muse 2014.3 edition. Since then I have been experiencing many crashes, difficulty saving and file corruption. I was not sure if it was Muse or Mac Os errors until now. I can confirm my Mac is in good working order.
See attached screen capture for the latest problem - cannot save a file after making edits. Muse feezes on save.
Is it possible to reinstall the previous version of Muse? I cannot complete work reliably with the new update.
CY

The update fixed the problem, however I am now encountering a new one.
Uploading to ftp locations slows dramatically at about 60% progress, by about 70% progress I get the Mac spinning wheel, sometimes the transfer will progress incredibly slow, or Muse will freeze.
Today I could complete an ftp transfer and muse crashed. See attached screen capture.
I am now exporting html and then uploading va ftp app however when exporting I am still seeing a dramatic slow down at some point after 60%.
I am also seeing the following message pop up in web browsers (see attached image). I have been seeing this message a lot since the first update 2014.3
I thought these problems may be have related to my ISP, however I am in a different country now using two different IPS's but the errors still remain.
Regards,
CY

Does Software Update CAUSE crashes, or come up AFTER crashes?

Over the past 6 months or more my machine has only hung (i.e. requires a press of a hardware button to restart), about 3-4 times. Each of those times, when I restart the first thing I see is the Apple Software Update screen. At least a couple (if not all) of those times the second thing I see is the Microsoft Office Automatic Update Screen.
I was in the office over the weekend, and no IT guys were around, and the OSX SERVER crashed (which knocked me off the internet, and also off the file server). When I restarted that machine, the first thing that came up was the Apple Software Update.
The question I have is:
* Could the Apple Software Update application be causing my crashes, or
* Am I seeing a feature where OSX says "hey you just crashed, let's check for updates now, even if it hasn't been a week (which is what your preferences say I should wait)".
Does anyone know? I've asked my IT guys here, and they've gone back and forth on it.
Thanks,

Why speculate? Chances are, if you look in the system console, you can find some information that might shed some light on this problem. The console is located in the Utilities folder.

Windows 7 Update causes Crash BSOD KB981957 on 11" Air

Trying to install update kb981957 results In a blue screen on boot with a 11 inch Macbook Air late 2010 running bootcamp Win7 x64.
Has to be rolled back via system restore to use.
Any suggestions?

i have also the same issue i installed windows 7 home basic to my MBA 11" then installed boot camp drivers, then update the windows unknowing this KB issues, now i'm facing the BSOD and have to re install everything..
so its this KB's 981957, 971033 that is causing this problem....i will try all this steps that you guys mentioned and hope for the best.
thanks

Latest CC 2014 update hard-crashes my Mac!

OS 10.7.5
IMac 2.16 GHz Intel Core 2 Duo
4GB Memory
over 100GB free disk space
Is there a way to undo the last update so I can get my Art Dept. up and running again? Should I stop paying for this subscription an go back to CS6? Please tell me I don't have to buy 8 new Macs to support the software.

Glad to know I'm not alone, Yonkondy. One thing I just tried that seems to be helping performance a lot is to hold down the Shift+Option keys while the project is loading up. This clears the preferences. It won't look like anything happens initially (there's no dialogue box or anything to tell you that the preferences have been cleared), but I was finally able to save my project without it crashing! Baby steps I guess, haha.

Installing new software update causes crash of my ipdo

I just downloadeed the new sofware update.
After installation I tunes wasn't abble to connect with my touch anymore. As I wantet to sett back the settings, its not able reset the ipod and always gets back to the page when asking for setting back the ipod for further use. Afer each set back... I cannot even start it or anything else
It worked properly before that update
Can anybody help

Welcome to the discussions,
try to connect in recovery mode (http://support.apple.com/kb/HT1808?viewlocale=de_DE) and restore "as new ipod" as shown here: http://support.apple.com/kb/HT1414?viewlocale=de_DE

IOS 4 update causes crash on all new vehicles.

I have a 2010 Maxima and have been using the cars usb jack to charge/connect to my Iphone so I can play from my Ipod. It keeps giving the error message that my wires are not compatible, then my car tell me to check my usb connection. Ipod freezes therefore making me manually restart (top,home-center buttons) everything worked perfectly fine before the update. I'm guessing this is the same error many of you guys are getting from the ipod app overall. PLEASE HELP ME SOLVE THIS ISSUE.

Start with page 170:
http://support.apple.com/manuals/#ipad

Why did last Update cause crash making apple tvs unusable?

Both my apple tvs are unusable now since the latest update. Help!
I've tried restarting. I've tried unplugging.

If your problem persists get yourself a micro USB cable (sold separately), you can restore your Apple TV from iTunes:
Remove ALL cables from Apple TV. (if you don't you will not see Apple TV in the iTunes Source list)
Connect the micro USB cable to the Apple TV and to your computer.
Reconnect the power cable (only for Apple TV 3)
Open iTunes.
Select your Apple TV in the Devices list, and then click Restore.

Since 8.1 update, computer crashes during CD import

Hello,
This is driving me crazy... Ever since updating to the latest version of iTunes, my computer crashes when I try to import music from CDs. It begins the ripping process normally, but then by the second or third song, everything goes blank and the machine tries to restart. When I try to run iTunes diagnostics on the CD drive, it does the same thing, so I can't even get a report on the problem. I have been able to import one or two discs seemingly successfully, but then they skip insanely on playback.
I have tried completely removing iTunes / Quicktime / etc. from my machine and reinstalling everything. No luck. I have tried updating my CD drive firmware. Nothing. I tried removing other programs that might possibly be conflicting with iTunes (Roxio, etc.). Same problem. I even edited my registry as per Apple Support instructions for a similar problem. Nada.
I know iTunes 8.1 is driving a lot of Windows users nuts, but I can't find a fix for this specific problem anywhwere. Any help would be greatly, greatly appreciated.
Thanks.

I haven't tried burning any CDs since I installed iTunes 8.1; however, I have been importing them. My problem is that my drive speed when importing has dropped from 20-24x down to 6-10x.
I appreciate the suggestion about saving as mp3s then importing, but why should I have to do an extra step because Apple messed up the new version?
I hope this gets resolved quickly. I was planning to finally upgrade my iPod to a new model, but if this is the hassle to import CD music and burn CDs, the Zune is looking better.

PS CC (since JAN 2014 update) Layer-mask editing causes hangs/crashes

ONLY since JAN 2014 update, PS CC has been hanging/crashing when I paint/edit a layer mask. All may be well at first (or not), but suddenly the display of the mask (or mask overlay on the layer itself, as shown when hitting backslash key) is not shown in full but renders in s-l-o-w-l-y in rectilinear pieces <snapshot below was taken before video card upgraded but is still typical of what I mean>. When I view Windows' Task Manager for PS, I see my CPUs are each working at their upper limits (up to 80+-90+%), varying only by a few points, over a VERY long time... which could be MANY minutes. OR the System has decided PS is Not Responding.
In any case, whenever this happens, it means in all practicality PS CC is not working, so I either kill it or it's crashed.
Now, here's the thing: that VERY file, can immediately be opened in PS CS6 (which I have fortunately kept installed on my computer), and the mask will be as I thought it should be, and I can edit it as I always could, just fine! So it's obviously a PS CC thing, and I do NOT recall this happening prior to the JAN update. It is still a problem after the two subsequent updates.
I have not been able to determine the specific instances when this happens, as it seems to happen whenever I am editing a mask, no matter what size/softness/color brush, what magnification, what view mode, many or few layers, big or small file, etc.
I did upgrade my NVIDIA card (from GeForce GTX 260 [with current driver] to GTX660), just in case it was a factor (maybe kept it from crashing as fast? hard to tell... but it's still an unworkable problem). You can see from my Sys Info shown here from the PS CC Help menu that it should be more than sufficient for any PS CC task, and it's running the latest driver:
Adobe Photoshop Version: 14.2.1 (14.2.1 20140207.r.570 2014/02/07:23:00:00) x64
Operating System: Windows 7 64-bit
Version: 6.1 Service Pack 1
System architecture: Intel CPU Family:6, Model:14, Stepping:5 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2
Physical processor count: 4
Processor speed: 2664 MHz
Built-in memory: 16379 MB
Free memory: 12453 MB
Memory available to Photoshop: 14697 MB
Memory used by Photoshop: 60 %
Image tile size: 1024K
Image cache levels: 4
Font Preview: Medium
TextComposer: Latin
Display: 1
Display Bounds: top=0, left=0, bottom=1200, right=1920
OpenGL Drawing: Enabled.
OpenGL Allow Old GPUs: Not Detected.
OpenGL Drawing Mode: Advanced
OpenGL Allow Normal Mode: True.
OpenGL Allow Advanced Mode: True.
AIFCoreInitialized=1
AIFOGLInitialized=1
OGLContextCreated=1
NumGPUs=1
gpu[0].OGLVersion="3.0"
gpu[0].MemoryMB=2048
gpu[0].RectTextureSize=16384
gpu[0].Renderer="GeForce GTX 660/PCIe/SSE2"
gpu[0].RendererID=4544
gpu[0].Vendor="NVIDIA Corporation"
gpu[0].VendorID=4318
gpu[0].HasNPOTSupport=1
gpu[0].DriverVersion="9.18.13.3221"
gpu[0].Driver="nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um"
gpu[0].DriverDate="20131219000000.000000-000"
gpu[0].CompileProgramGLSL=1
gpu[0].TestFrameBuffer=1
gpu[0].OCLPresent=1
gpu[0].OCLVersion="1.1"
gpu[0].CUDASupported=1
gpu[0].CUDAVersion="6.0.1"
gpu[0].OCLBandwidth=1.16816e+011
gpu[0].glGetString[GL_SHADING_LANGUAGE_VERSION]="4.40 NVIDIA via Cg compiler"
gpu[0].glGetProgramivARB[GL_FRAGMENT_PROGRAM_ARB][GL_MAX_PROGRAM_INSTRUCTIONS_ARB]=[16384]
gpu[0].glGetIntegerv[GL_MAX_TEXTURE_UNITS]=[4]
gpu[0].glGetIntegerv[GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS]=[192]
gpu[0].glGetIntegerv[GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS]=[32]
gpu[0].glGetIntegerv[GL_MAX_TEXTURE_IMAGE_UNITS]=[32]
gpu[0].glGetIntegerv[GL_MAX_DRAW_BUFFERS]=[8]
gpu[0].glGetIntegerv[GL_MAX_VERTEX_UNIFORM_COMPONENTS]=[4096]
gpu[0].glGetIntegerv[GL_MAX_FRAGMENT_UNIFORM_COMPONENTS]=[2048]
gpu[0].glGetIntegerv[GL_MAX_VARYING_FLOATS]=[124]
gpu[0].glGetIntegerv[GL_MAX_VERTEX_ATTRIBS]=[16]
gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_PROGRAM]=1
gpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_PROGRAM]=1
gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_SHADER]=1
gpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_SHADER]=1
gpu[0].extension[AIF::OGL::GL_EXT_FRAMEBUFFER_OBJECT]=1
gpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_RECTANGLE]=1
gpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_FLOAT]
I work on digital-photography files, and use a layer mask in almost every file, so this relatively-recent bug is a big PITA, having to switch back and forth between CS6 and CC!
Until there's a fix... is there a way to roll-back my PS CC version to BEFORE the JAN 15, 2014 update?

I am not qualified to comment on technical issues; I'm just a user whose son in IT is my 'technical support department.' (But he's not much of a PS user.)
I'm pretty sure, however, that all my Prefs were set to the same things BEFORE the Jan 16, 2014 PS CC update as after (unless the update itself changed something I was unaware of... the settings APPEARED to be the same but I can't easily locate my notes of what my Prefs were from long ago).
And they were the same as the PS CS6 I have had installed on this same system for a very long time, with older video card with older driver, with newer driver; newer video card with newest driver, etc. Yet after that CC update, CC has not (until this workaround) worked re 'the masking bug' for me, yet CS6 has always worked just the same.
So I conclude that the only variable (other than the video card upgrade I did in an attempt to solve this and of course those Windows auto-updates) in this scenario IS something to do with PS *CC*, and after Jan 16, 2014.
As for restarting the machine vs. restarting PS, well, PS is the major player of my system, so when I shut that (and LR) down, I might as well 'clean things up' by Restarting. BTW, I am in the habit of closing and reopening PS (CC or CS6) whenever I finish with a file and load another, in order to get back some of that memory which PS never seems to want to let go. (This is not new to the latest versions, I think. My son says it's a 'memory hog'? ;-) ) I track its memory use in Windows' Task Manager and find that seems to let it 'refresh' itself. (See, I told you I'm not a technical person. ;-) ) But I do not think this has anything to do with the bug. Just a quirk of PS. Like when a tool goes all wonky (for example, its little icon becomes just a 'plus' sign even though the tool is still performing correctly, it's telling me, I think, that it would like to be restarted. And that makes it feel all better... I mean, tool icon reappears.)
Anyway... it's up to Adobe to figure out IF and what may be wrong with PS CC -- it still doesn't work for me as I had it configured at first, and I think it should, right? -- and to fix that... PLEASE. SOON.

CC 2014 (18.1.0) | Text Field editing causing crashes (Windows)

Greetings;
I've noticed lately that when saving files from CC 2014 to a CS6 format - and having those files edited on Mac, in either CS6 or CC - when re-opening those files text fields have been causing crashes on the Windows client. When that same file is opened and text fields are edited on the Mac client, a prompt will just appear stating "Cannot Edit text" - yet it still allows it.
This has caused multiple issues for our teams as it has created files we're starting to refer to as "mine fields" - as working with the .ai file is like playing Russian roulette with text fields, you never know which one is going to crash the file.
I would love to work with a team member from Adobe to help find a resolution to the problem, and I'm willing to provide any additional details that might aid in that process.
Thanks!

Hello Pureweb,
Please upload the crashdumps on some file sharing website say Dropbox and share the link with us by sending a mail to "[email protected]". We will analyze the dump and will suggest you the workaround appropriately.
In parallel, please check that you do not have any 3rd Party plugins installed in it. Please try to remove them one-by-one and see which one causes the crashes or do reverse i.e. remove all the 3rd party plugins. Or Uninstall Ai and check at following location:
C:\Program Files\Adobe\Adobe Illustrator CC 2014
Please verify that nothing is left at above location on uninstalling Ai. Then try a fresh install and see if Ai works.
Also, verify that you have the updated Wacom drivers on your system. This might be an issue with the 3rd party program as well. One of the user who was having a similar issue reported on the Ai forum that one of the 3rd party Stahl's ImageWorx DTG RIP - a program for printing to a Direct To Garment printer was causing the issue. So, you may check if the similar thing is not happening in your case.
Regards,
Dhirendra

Recent Update causes my App to crash. What should I do?

Recent update causes my Adobe Revel App to crash. What can I do?

Are you using ios? Is your app crashing or not installing an update?
There is an issue that the Revel version 2.3.2 on iOS does not seem to install. We are working with Apple to resolve it as quickly as possible. We sincerely apologize for the inconvenience this is causing you. In the mean time, you can still access your photos on adoberevel.com from a browser and from our mac, win8, and android apps.
If you are using a different platform, please let us know the details.
Pattie

October 2014 update rollup for Windows Server 2012 R2 and Data Protection Manager 2012 R2

Hello all,
After installing the October 2014 update rollup for Windows Server 2012 R2 (KB2995388) on our Windows 2012 R2 Core Edition backup jobs of System State start to Fail, below the generic error:
The replica of Non VSS Datasource Writer on hostname.domain is inconsistent with the protected data source. All protection activities for this data source will fail until the replica is synchronized with consistency check.
The job was cancelled. The user either cancelled the job or modified the associated protection group.
Removing the update rollup all jobs complete without errors. Somebody is expiriencing the same issue? How can we resolve the problem?
Thnks, Andrea

Hi Andrea,
Have you installed the update 2919355?
To apply update 2995388, you must first install update 2919355 on Windows 8.1 or Windows Server 2012 R2.
According to the official website, the issue which you described is not listed as the known issue.
Please uninstall this update and continue to monitor the official website for the latest news.
Best Regards.
Steven Lee
TechNet Community Support

October CC 2014 update causes crash on OBJ import.

Similar Messages

Maybe you are looking for