PDA

View Full Version : Graphic error with "Copy"


StefVdM
05-15-2008, 03:40 AM
Hi,

I recently installed CoCreate Modeler Personal Edition. When I tried the first exercise (the little "LEGO"-block), I ran into the following problem, trying to Copy a feature:

I use the copy command, select "recognise feature" and select the feature. No problem up to here. Then I select "dynamic position" and on the model the symbol appears with axis in the three main directions. My cursor is still over the "Copy"-dialogue.
When I now move my cursor back over the Modelling area, I get the following error:

"vport1 frozen because of Graphic error". The model locks up and the only thing I can do is close it.

What can be the problem here?

I'm working on WindowsXP Profesional, service pack 2, Pentium 4 (3.6 GHz), 2.0 GB RAM.

Regards,

Stefan

clausb
05-15-2008, 03:52 AM
This error message is displayed when critical errors occur while redrawing the model. Such critical errors can be graphics driver issues, or in some cases they could also be caused by severe model corruptions. From the message alone and your description, it's hard to tell where the problem cause really is.

Let's start with the graphics hardware and driver - can you give us some more graphics configuration info?

Thanks,

Claus

StefVdM
05-15-2008, 07:55 AM
Dear Claus,

I'm not so good at looking at the innards of my PC. Does "ATI FireGL V3100 graphics accelerator" tell you enough?

Regards,


Stefan

clausb
05-15-2008, 07:57 AM
That's good enough for a start; it tells me that the graphics card itself is probably not the problem. It can still be a problem in the driver, or in the driver installation, though.

The next thing to check: When this problem occurs again, could you please enter the following in the user input line:


(display (f2::get-last-exception))


This will print some stuff to the output box, from where you can copy it to the clipboard or save it as a file. This information might give me additional hints on what's happening.

Claus

StefVdM
05-16-2008, 07:18 AM
Dear Claus,

Here is the dumped info:

Exception 0xC0000005 at 0ED2FBD0 00:3C4395BE
EAX=00000001 EBX=00000000 ECX=00000000 EDX=0E7547E8 ESI=19B18FD8
EDI=00000001 EIP=0ED2FBD0 ESP=0E7547C0 EBP=00000000
CS=001B DS=0023 ES=0023 FS=003B GS=0000 Flags=00010202

Stefan

clausb
05-16-2008, 07:47 AM
Stefan,

thanks for the data. It's an access violation; unfortunately, I cannot see more here.

CoCreate Modeling may also have produced a so-called minidump file when the internal crash happened. This minidump file usually contains more data, so if we could find that and analyse it, chances are we'd learn what really happened.

The minidump files are usually stored to "C:\Documents and Settings\username\Local Settings\Temp", and the filenames look like "CoCreate_Modeling_someversionnumber_Dump.mdmp". Can you find some of those on the affected system?

Claus

StefVdM
05-20-2008, 12:36 AM
Dear Claus,

Attached a dump-file created when the error occured. I had to change the extension to "txt", because the "mdmp" extension is not accepted as a valid file extension for uploading/attaching files.

regards,

Stefan

clausb
05-20-2008, 01:22 AM
OK, thanks! The minidump file shows that the crash occurs in atioglgl.dll, i.e. in the graphics driver.

I'd recommend to try and properly reinstall either the same driver version or the latest driver version, as explained at http://www.clausbrod.de/CoCreateModeling/OsdmFaqGraphics#ProperInstallation .

If this doesn't help, check the driver options for application-specific settings. Many drivers can be switched into application-specific modes. If you find such a mode for "SolidDesigner" or "OneSpace Modeling", use it and see if this fixes the problem.

Hope this helps,

Claus

StefVdM
05-20-2008, 05:16 AM
Dear Claus,

As you recommended, I downloaded and installed the latest driver available from ATI, and guess what? It works!
So I'm up and running now. Thanks a lot for your support (and your prompt replies)!

Regards,


Stefan

clausb
05-20-2008, 05:37 AM
Glad it worked. (If it hadn't, the next debugging steps would have become more and more difficult, so we both avoided some unpleasant work here :D )