View Full Version : Weird viewport crash
destroyer83 09-21-2007, 02:17 AM I've been having problems with Cinema 4d running on a 32-bit windows xp pro.
Whenever one viewport,for example perspective, is maximized and i tried to restore it to the original size (4 viewports) the program crashes.
I run cinema 4d 10 on a mac too and this problem has never happened.
I turned off the Open GL shading and switched to Software shading. After that, the problem was gone.
What are the pros, cons and/or differences between Open GL and Software shading? Is it only for display purposes? Does it affect the final render?
I'm sure it has to with windows and maybe the hardware. This is my current config.
AMD Athlon 64 X2 6000+ Windsor 3.0GHz 2 x 1MB L2 Cache Socket AM2 Processor
EVGA 320-P2-N811-AR GeForce 8800GTS 320MB 320-bit GDDR3 PCI Express x16 HDCP Ready SLI Supported Video Card
4gb of Ram.
Any help will be greatly appreciated.
|
|
gildattack
09-21-2007, 02:35 AM
i experienced some crashes myself aswell. Though i'm not totally sure, i think it happens sometimes (don't know why not every time), while switching or dragging to re-arrange between views while being in 'points mode'...
LucentDreams
09-21-2007, 07:40 AM
best to contact maxon on that one.
Kuroyume0161
12-26-2007, 09:53 PM
This thread is a bit old, but I'm experiencing a similar situation. Worse, not just a mild C4D crash - but a catastrophic ELE taking down my entire computer (three times already)! And this is just editing points using the Brush in Point mode.
Windows XP Pro SP2
Intel Quad-Core 6600
8GB memory
1.5TB HDD
NVidia 8800 GTX 768MB (ForceWare 158.19)
Cinema 4D R10.111
OpenGL - Cg compiler (but GLSL doesn't make a difference).
Before the system goes bye-bye, the Editor display shows some funny artifacts and the system freezes solid as carbonium ice requiring a hard reset.
Any ideas? Update ForceWare? C4D OpenGL settings?
Per-Anders
12-27-2007, 04:17 AM
This sounds simply like a driver crash, you need to update your graphics driver. Remember though that sometimes the most recent version isn't the best either, go and look at www.ngohq.com to find some variants of the driver software and try a few out.
Kuroyume0161
12-27-2007, 04:37 AM
I've found that even Software shading doesn't protect from this type of crash - though not as disastrous (only C4D freezes) - same Editor weirdness. Polygon selection was also strange but didn't result in any crashing.
Could be the graphic driver - but the crash-and-burn is *only* when point editing so far. I've had no problems with a myriad other operations including some rather complex scenes.
Per-Anders
12-27-2007, 05:26 AM
Well if you're having crashes with Software Shading then make sure to send the crash report to Maxon, if you're experiencing a freeze you can force quit using LEFT SHIFT + RIGHT SHIFT + DELETE (Windows only) and this will also allow you to send the bug report to Maxon.
With regards your other issues I would seriously recommend following my advice, I wont bother to repeat it, but I will say that the NGO Optimized drivers do tend to be more stable here than the drivers that Apple for instance offer for Bootcamp which are terrible and cause a similar crash to what you are describing apart from the addition of random colored lines in OGL viewports when i quad-views before the crash, you can also turn off highlighting if you wish, however that wont solve the root problem.
CGTalk Moderation
12-27-2007, 05:26 AM
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.