I guess C4D doesn't work well with dualcore systems...

[Per-Anders]

C4D works with dualcores just fine. Make sure you have good graphics card drivers installed (either the latest or occasionally you ahve to use a slightly older version, usually there are poeple out htere hwo know which verisons are good to go). Also make sure your memory is good and doesn't have any bad blocks (run a memory test application to find this out). I believe if you follow those old threads through they generally come to solutions for their problems (that are usually install/hardware or plugin related).

[AdamT]

There's no problem with Cinema and dual cores. You've got some kind of hardware issue. These are often OpenGL related. Have you tried with OGL disabled in the viewports? Have the latest drivers installed? Have the proper/latest motherboard drivers and bios installed?

[Rabbitroo]

Works fine on dual-dual cores.
-K

[marcorabellini]

Make sure the RAM is good and properly seated. Also, newer boards are very specific about what types of RAM they'll handle and they usually all need to be the same size. I had a problem a while back and it turned out to be that one of four RAM sticks got rotten somehow. Took me a month to narrow it down. There's a few free RAM test programs out there if you google something like "RAM testing". Memtest is a good one.

It could also be a HD going bad. I also had a box a while back where the MB was shorting out on the case. It was a cheap, old case so now I spend a few extra bucks on a decent case.

To test OpenGL, start with all the options off and work your way up until it crashes.

m

[KingHussien]

All drivers are up to date. Software shading doesn't give me a problem, but its a lot slower and all the lines are aliased.

I run a memory test every two weeks and so far no problems with the memory.

[KingHussien]

My Case is a Gigabyte 3D Aurora. Cost me rougly 140$. Also I have two sticks of RAM, both from the same manufacture and of the same size. My HDD's are basically brand new WD (I believe) SATA 3.0Gbps 7200RPM 80 GB.

[KingHussien]

Sorry for triple post, but I want to make sure people get this info.

In Preferences > Viewport > OpenGL Shading, I have everything unchecked except Smart Window Refresh, Smart Live Selection, Use Textures, Shared Textures, and Rotate Quads.

Edit:

I turned off Smart Window Refresh and Smart Live Selection and opened up my scene. Its a roman-like column. I arrayed an object with 15 copies and boolead it into the main column. All went smooth and then I rotate the camera to the other side and crash.

[marcorabellini]

Hmm. These things are difficult to diagnose with the machine right in front of me. However, some ideas.

Make sure that you've definitely go the right video driver for your card/OS. Don't over clock anything. If it works with software shading it definitely sounds like an OpenGL thing. In the past, some newer video drivers didn't work as well as older ones. Try a few older versions of the video drivers and see if that helps at all.

Since you've only got one video card, make sure none of the SLI stuff is running. Last time I checked with Maxon, they were not supporting SLI yet.

And since its a consumer level card, turn off anything that says "planes" as that kind of card doesn't support planes.

m

[marcorabellini]

In Preferences > Viewport > OpenGL Shading, I have everything unchecked except Smart Window Refresh, Smart Live Selection, Use Textures, Shared Textures, and Rotate Quads.

Try turning all of it off, exit and re-launch C4D and see if it still crashes.

m

[KingHussien]

Hmm. These things are difficult to diagnose with the machine right in front of me. However, some ideas.

Make sure that you've definitely go the right video driver for your card/OS. Don't over clock anything. If it works with software shading it definitely sounds like an OpenGL thing. In the past, some newer video drivers didn't work as well as older ones. Try a few older versions of the video drivers and see if that helps at all.

Since you've only got one video card, make sure none of the SLI stuff is running. Last time I checked with Maxon, they were not supporting SLI yet.

And since its a consumer level card, turn off anything that says "planes" as that kind of card doesn't support planes.

m

SLI is turned off and anything planes is off.

By the way C4D keeps producing a bug report. Will the report help you guys or Maxon in solving this problem I'm having?

[marcorabellini]

The bug report is a new 9.6 thing. Send it to Maxon support; they'd know a lot more than I would.

m

[KingHussien]

Argh! I don't have the most recent video card drivers. Upgrading now. Will let you guys know how it turns out.

[3DKiwi]

I would also check that your bios is up to date and your mother board drivers are up to date as well. I build my own PC's and these are often out of date.

In your bios make sure the graphics system matches your card. On AGP motherboards the default setting isn't usually this and needs changing.

Dare I suggest that you were a bit quick to blame C4D for your problems. I would be checking my system first and then getting on to Maxon before bashing C4D quite so publicly.

3DKiwi

[Tank_3D_Attack]

I would also check that your bios is up to date and your mother board drivers are up to date as well. I build my own PC's and these are often out of date.

In your bios make sure the graphics system matches your card. On AGP motherboards the default setting isn't usually this and needs changing.

Dare I suggest that you were a bit quick to blame C4D for your problems. I would be checking my system first and then getting on to Maxon before bashing C4D quite so publicly.

3DKiwi


I didn't see him bashing C4D at all. He is having an issue and asking for help now what harm can there be in asking others in public? I read his posts twice and fail to see him bashing C4D.

Thomas

[3DKiwi]

The title was hardly flattering:

" I guess C4D doesn't work well with dualcore systems..."

Think I would have titled the topic a little softer.

3DKiwi

[AdamT]

Well, the thread title had a certain bashiness to it--"I guess C4D doesn't work with dual cores" as opposed to "wtf is wrong with my new PC?"

[Tank_3D_Attack]

Oh my! Come on folks...he is having an issue and surely wasn't good mooded when he wrote that post. He was frustrated which is understandable so don't make a big deal out of it.

Just my 2 cents.

Peace


Thomas

[KingHussien]

3DWhatever: You are overly defensive fool.

-Now thats bashing.

Anyways, after updating my drivers just now, its stopped crashing, so thank you for all your helpful posts, guys.

Also, before I made this post, I downloaded the 3DS MAX demo, because these crashes were seriously making me look at other options. Well I ran 3DS MAX in OpenGL with absolutley no problems. And I play WoW, which I believe runs in OGL.

Nothing else was crashing. Nothing else was giving me problems. I tested my memory. Extensively I might add (I let it run for 8 hours, last time I did it).

And finally, I checked all drivers to make sure they were up to date. And they were, upto June 23. The crashing didn't become a recent issue. It started rougly 3 months ago, when I got my new system. After I knocked 'drivers' off my list of things that could be wrong, I decided to ask the C4D community, but didn't get around to doing it until today.

Did the thread-title have a little bashness to it? Maybe. Was it intentional? No.

Have a good day, 3DWhatever. :)

[Billabong]

Well I can see this is gonna get out of hand

[Per-Anders]

Guys, please behave in an appropriate manner for this forum. That means no personal attacks, let me re-post the rules that are shown every time you post on CGTalk and that you agree to with each post:

Before posting, please review the following:
Be courteous and polite. Show respect to the opinions and feelings of others. Use of the forums is a privilege, not a right.
Engage your brain before your mouth. You are responsible for your own words and any harm they may cause.

To be honest, the title and tone of couldn't be construed as blaming anything other than the application - as it turned out in a pretty unfair manner, it's not unreasonable for some other users to see this is bashing, after all there is no basis for the blame apart from misguided frustration. The best way to not make a big deal out of such things is to simply ignore them.

As it turned out KingHussien didn't have the latest drivers that he thought he did, an easy mistake to make and fortunately updating the drivers resolved the issue. However please be courteous and polite to other members of the forum.

As this thread has now run it's course I feel it is best for this forum that we close it.