All of the axles and fixates are blocks!

[daddadhad]

Algodoo used to work fine up until now. Now the axles and fixates are blocks and when you zoom in on them at first they look like the scene that you are in . But when you zoom in even more the block turns into the normal looking fixate or axle. This is cause problems with the function of the axles. Please fix this because it is rendering algodoo almost not usable. Hope you can fix this.

Specs: Macbook Late 2008, 64-bit, OS X 10.7.5(11G63), RAM: 3GB 667 MHz, CPU: 2.4 GHz Intel Core 2 Duo, Graphics Card: Intel GMA X3100 144 MB

[Kilinich]

Did you try to update graphics drivers?

[pnvv]

As Mr. K said, updating graphics drivers will probably help. But I want to see a screeny of what it's doing because I've never seen anything like that happen before

EDIT: Total brain fart, updating graphics drivers won't help unless it started doing it if they were changed.

[MrLucasManSwe]

Guys, he said ''Algodoo used to work fine up until now'' so it can't be his graphics card drivers.

I have also gotten a problem with my hinges a few months ago,
when a group of hinges are auto-braked they act like a fixating and glues all parts they are attached to to the background. Tried re-installing Algodoo, didn't help.

[daddadhad]

Same with MrLucasManSwe I will post a screeny when I can

[electronicboy]

Reinstall Algodoo, download drivers from your vendor, best suggestion as to a fix.

[daddadhad]

He is a screeny. The block is the same color as the stick so it may be hard to see.

[daddadhad]

Here is another screeny. That dark purple block is a axle.

[pnvv]

Whaaaaaaaaaat??

[daddadhad]

Whaaaaaaaaaat??

i know its really wierd. If thats what you mean.

[daddadhad]

Also I cant update my graphics driver becuase the update utility is only for windows and I cant find one for mac.
btw i have a intel graphics card.

[daddadhad]

Also I noticed that for some reason in my Application Support folder I cant find the Algodoo folder.
I tried reinstall Algodoo and it did'nt work. Could this be the problem?

[electronicboy]

Try downgrading Algooo, if it was caused by upgrading Algodoo to 2.1 then it would mean that the graphics chip in your machine doesn't meet the requirements for openGL 2.1, best option is to downgrade to a version before 2.1.

[Kilinich]

Try downgrading Algooo

Bad idea, half of modern scenes will stops working.

[electronicboy]

Well, true, but if 2.1 ain't gunna work on your hardware then downgrading is really your only option unless you can buy a cheap GPU

[daddadhad]

Nope i am pretty sure that my graphics card supports OpenGL 3.1

[electronicboy]

It's an intel, true support and 'half assed intel driver support' are usually two different things.

[Kilinich]

Also, it could indicate hardware (memory) problem. Did you ever see bsod or artifacts in other 3D games??

[daddadhad]

I am just confused as to why it used to work and now it doesn't. I haven't changed any hardware on my mac at all.

[electronicboy]

Algodoo 2.1 had a complete rewrite of the whole rendering system requiring a minimum of openGL 2.1; according to Wikipedia;

'The GMA X3100 is the mobile version of the GMA X3000 used in the Intel GL960/GM965 chipsets and also in the GS965 chipset. The X3100 supports hardware transform and lighting, up to 8 programmable shader units, and up to 384 MB memory. Its display cores can run up to 333 MHz on GM965 and 320 MHz on GL960. Its render cores can run up to 500 MHz on GM965 and 400 MHz on GL960. The X3100 display unit includes a 300 MHz RAMDAC, two 25–112 MHz LVDS transmitters, 2 DVO encoders, and a TV encoder. Under Windows, the driver supports DirectX 10.0,[10][11] Shader Model 4.0 and OpenGL 1.5.[11][12][dead link] Under Linux, OpenGL 2.1 is supported.'
http://en.wikipedia.org/wiki/Intel_GMA#GMA_X3100

So, if the issue was caused by upgrading to 2.1.0, then that is most likely to be your problem.

Just looking over some apple documentation, the GMA X3000 does support a large portion of openGL 2.1, however it is missing a few instructions compared to other 2.1 GPUs, which is most likely the issue here.