View Full Version : keyframe coomand bug?
JoelOtron 12-06-2006, 09:01 PM for some reason, My little red "add keyframe" button goes gray on me sometimes without rhyme or reason. I can click on any object in my scene --but it stays gray. If I add a new object to my scene (then delete it) it turns red again and I can keyframe once again. Never had this problem b4.
|
|
LucentDreams
12-06-2006, 09:48 PM
hmm next time it happens could you post a file or at least a screencap? can't think of why it would happen as really it should only go gray when nothing is selected, but
JoelOtron
12-07-2006, 12:51 AM
hmm next time it happens could you post a file or at least a screencap? can't think of why it would happen as really it should only go gray when nothing is selected, but
Will do. I remeber you mentioning somwehre that using the timeline (and I had many objects/tracks visible in it) can slow down performance. MAybe loss of functionality (ie greyed out keyframe button) is a symptom of this.
I'm also noticing slowdowns and pauses in screen response (like when things lock up completely for 10 seconds) with some scenes. Happens whther enhancedd ogl is on or off.
(sorry if I'm changing the subject--I actually have a running list of bugs I've run into in the pasr week or 2--but dont know if it would be welcomed here or I should just keep it between me and maxon)
JoelOtron
12-07-2006, 02:25 AM
I just have to say--R10 is a great upgrade in terms of new tools and functionality. Enjoying the process of learning the new tools and new ways of working.
But I also need to vent my frustration in how friggin buggy it is :(
Just crashed for the 5th time today. This is on different computers, different installs from different dvds, and different project files. Just need to get my work done. I broke my own rule of not diving into new projects with new software. Guess thats my fault.
Kuroyume0161
12-07-2006, 02:33 AM
I've been following and noting the increased mention of bugs and crashing in R10. Interestingly, I've only experienced crashes (esp. the disappearing C4D crash which doesn't even do a BugReport) when playing with the demo before receiving the release version. On the other hand, I have only been using R10 for plugin testing and have not done much else so I'm probably not a good example.
Seems that the extensive changes and improvements have not gone unnoticed by the crash-gods. Let's hope that Maxon is collecting bug reports and will soon release an update that remedies these problems!
Simon Wicker
12-07-2006, 07:59 AM
maxon have always made it known that crashing bugs are their absolute number one priority for fixing so if you get a crash and crash report from cinema you MUST send it off to maxon to get this fixed in the next .001 release!
please. it is in everyones best interests that these work zapping problems are dealt with as soon as possible (and looking at how maxon have scheduled a bug-fix version to be released soon after every major release it doesn't take a mind reader to know that they are in the process of fixing stuff right now). if you have a reproducible error report it and the 3d gods will bestow much good karma upon you!
cheers, simon w.
LucentDreams
12-07-2006, 08:41 AM
Also should point out a lot of crashes are going to be OGL related Ever wondered partly why apps like max crash so much welcome to fancy graphics capabilities inside your 3D app. ;)
As simon said, the key thing is every crash every bug big or small report it. Sometimes when a bug is reported its not reproducable or hard to track, so the more reports that show the same behavior the better. Personally R10 crashes very rare for me, and far less than 9.6 thats for sure, and I do know that after 9.6 was released a few bugs that have haunted maxon for years were finally tracked because of the new crash analyzer which shows things our descriptions will never be able to convey
JoelOtron
12-07-2006, 01:43 PM
Yeah--I got you.
I actually didnt send the last few reports--as I was busy slamming my mouse on the desk :)
I do see that there are archived bug report files in my maxon folder---I suppose there still hope for me in the eyes of those 3d gods if I send them off.
The crashing usually happen when keyframing, moving keyframes or editing keyframe parameters in the AM.
The brief freeze-ups usually happen when moving the camera around in my editor view. Usually regain control in about 10 seconds or so.
Thanks for the input and excuse/understand my frustration boiling up due to being in the heat of a deadline.
Hi Joel,
i haven't found a single crash report from you in our database. Without it we are unable to determine the cause and fix the problem.
Cheers
Björn
JoelOtron
12-07-2006, 04:23 PM
OK--If I crash again today--I'll send along.
There are some files in my folder (recovery scenes, prfs, l4d, and a txt fle)-as I mentioned above--but none of them are the files that I am talking about. Also realize that when the crash windows do pop up--sending a bugreport at that moment in time isnt on the top of your list of things to do. But I guess it should be. I'll be more dilligent in the future.
Thanks
No sweat, i just wanted to show that it's not a waste of time, we are listening ;)
Cheers
Björn
CGTalk Moderation
12-07-2006, 05:16 PM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.
vBulletin v3.0.5, Copyright ©2000-2012, Jelsoft Enterprises Ltd.