Open Dental Forum

I updated to vers 6.9.3.
Prior to that I had no unhandeled error messages.
I noticed that procedures that required a missing tooth (extraction, pontic, RPD,implant, etc)could not be posted (got message that I needed to choose a tooth even though I had).
Then I noticed I could not make a tooth "missing".
The only chart tooth change would be that the "new" sectional circles on the occlusal graphic would change color.
Jordan suggested that I update OD. I did (v6.9.7). Same result.
Jordan also suggested to try using a different graphics setup (File/Graphics/)
I changed to the third choice, the "circles" went away, the chart looked normal, however selected tooth would not go "missing".
Another suggestion, as I interpreted, was to update DirectX.
I googled DirectX. Found the Microsoft DirectX update sight and undated.
When it was done, I opened Open Dental.
The chart graphics were now only about 10% there. Just some squiggly lines.
Rebooting did not help.
I elected to restore my system to a previous period.
I chose the period before updating to v6.9.7.
After reboot, Open Dental was missing from my desktop.
I went back into system restore and noticed that the task prior to updating open dental was uninstalling open dental.
I restored back to that period (before uninstall of od).
After reboot, Open Dental was on the desktop.
I tried to open OD. A message appeared that the version were had a conflict (something like that) and it wanted to update files to v6.8.30.
Which I did.
Now OD won't open at all.
I get an Unhandled Exception error message.

It seems to me, there is a significant underlying problem with the way we update OD.
There should be some warning or message that something critical could take place causing a severe issue.
The graphics problem is not isolated to one computer. It occurs with all my Dell GX270s, one new dell precision 350 purchased within that last 6 months, IBM ThinkPad and Acer Netbook.

Fortunately, I tried all the fixes on my home computers not the office.
The office OD is accessible, I just can't chart or post any "missing" teeth procedures........which is a problem.

I can't be the only one.....so BE CAREFUL!
May I suggest removing the graphic update portion from v6.9 until someone has a definite way, that has been tested, to fix the issue.

Beta versions are for people who don't mind dealing with these issues, especially for the first week or two. There are nearly always workarounds for the annoyances in a beta version. In this case, switch to OpenGL graphics. As for the missing teeth issue, you can always add any procedure manually. When the procedure edit window comes up, enter the tooth number. Unless there's something I'm missing. I just tested it and it works just like it always has. I was able to set teeth missing, add pontics, etc. Works for me in both OpenGL and DirectX. I was also able to do it in 2D mode, although it just looks different than the other two modes. The missing circle indicates a missing tooth. You won't see the tooth graphic itself disappear because the background is just fake.

When you restored your system, it naturally removed the recent Open Dental installation. Somehow you ended up back on version 6.8 rather than 6.9. That is not surprising at all. As for the unhandled exception, I would have to see it. We were open today, Saturday morning. Maybe if you had called and showed us the error? Or at least post it here.

There is not any underlying problem with the way OD is updated, as far as I can tell. You are really pushing the envelope, so please don't get frustrated if things don't work perfectly. I'm seriously considering blocking all users from being allowed to use beta versions for the first few weeks except those users who call us and specifically request to be allowed to use beta versions. Those users must understand that errors are expected.

Ok, I'm now back working fine after doing my restore as listed on the other post.
I changed the graphics to OpenGL Format#7.
My graphics card is NVIDIA GeForce 8300GS
3.0GB RAM
DirectX version 9

What do I need for the OpenDental graphics to work correctly?

What exactly is wrong with the graphics? I need specific tooth numbers, procedure codes, button click sequences, etc.

If using Direct X Tooth Chart:

Chart graphics shows previous 3D teeth with white sectional circles on the occlusal/incisal.
If there is a restoration, the circles, only, have color representing the surfaces involved.
If there were charted previous missing teeth, the teeth graphic is there, the circle is not.
If the previous charting was for a pontic, the circle is colored but the tooth is still there.
A patient that had been charted with missing teeth #30,29 and 19,20 and wore a RPD replacing the teeth, the previous graphic showed no teeth, yet a colored crown portion indicating replaced teeth.
The current graphic shows the tooth with the circles filled in with color.
That patient broke #20.
I tried to TP "repair broken teeth (D5640).
An error message popped up that said I needed to choose a missing tooth.
It wouldn't accept it.
So I changed the code such that it didn't need a tooth # and it was fine, then added tooth # manually.
If having just the circle go away, leaving the tooth behind is the way it should work, then it works fine.
But ......you already replied earlier that if I see the circles, my graphics aren't working correctly........

Jordan said: "If you are seeing those circles, then your DirectX is not working and it is defaulting to 2D mode. You need to go to File, Graphics, and switch to OpenGL mode. Or update to possibly get DirectX working."

I thought you said you were in OpenGL mode. If so, you won't see any circles, and everything will work just fine.

Everything works in OpenGL.
I want to know how to get it to work using DirectX.

You can't yet. That's why I said to use OpenGL mode.

I feel like I'm in an Abbott and Costello skit......

Are you saying, I can't run in Direct X,
or, No one can run in Direct X.

It works for some people and not for other people. If it doesn't work, then just be patient until we release a version that does work for you. It's been listed as a known bug since the moment 6.9 was released.

Oh!

This might sound a bit sarcastic but....I wish I got that reply from you last night. If so, this thread would never occurred.
In any case, I now understand.

Thank you (sincerely).
Cheers!!!

Sorry, Abbott. I thought that was what I said.