MacPro - video oddness, anyone else?

[AdamT]

No problems on my Mac Pro with the same video card. Have you tried with OGL disabled?

[lllab]

no problems either.

by the way Adam, did you manage to get the numberblock to be activated under winxp?

cheers
stefan

[designbytes]

No problems on my Mac Pro with the same video card. Have you tried with OGL disabled?

as soon as I move to "software shading", the problem goes away
when I return to "openGL shading", problem returns

Adam, are you using QT7.1.3? that is the new version that gets loaded with itunes7...

any thoughts how to fix? shouldn't behave differently on same machines/same cards/same app but different users....at least I wouldn't think ;-)

I have reported it to Maxon support as well

thx

[AdamT]

Stefan, what is numberblock?

phudy, I'm using the same QT version. Sounds like it's probably a video card driver problem or possibly a hardware problem with your video card. I don't know how you go about reinstalling drivers for video cards in OSX, but that's what I'd do if I was you.

[lllab]

i mean the number keys on the right side of the keyboard(0,1,2,3,4-....8,9)

cheers
stefan

[AdamT]

Ah, I see. Yes, I was able to get them to work. You have to be running the "Apple Keyboard Support" app from Bootcamp. Then the "clear" key works like a normal Numlock key.

[lllab]

thanks Adam,

good to hear. where is the apple keyport support- cpouldnt find it?

edit: foundit-thanks!

cheers
stefan

[lllab]

edit: forget it it works all now:-)
cheers
stefan

[designbytes]

Stefan, what is numberblock?

phudy, I'm using the same QT version. Sounds like it's probably a video card driver problem or possibly a hardware problem with your video card. I don't know how you go about reinstalling drivers for video cards in OSX, but that's what I'd do if I was you.

Adam

as a favor, could you boot your macpro in "safe" mode and tell me if the "cube primitive, make editable, select point" process in the orginal post behaves normally for you?

[safe mode on mac = shutdown machine, power on, when you hear the chime sound, press and hold the shift key, keep it pressed until you see the gray mac screen and the spinning progress dial - then let go....you will then be presented with your login screen, but it will note it is in "safe" mode. booting in safe mode seems to take longer; proceed normally and fire up cinema]

when I do this, the screen scramble does not occur, but the select tool doesn't really work as it should - it selects the first point but not others.....just wanted to see if that is normal behavior in safe mode.

still researching updating or re-installing drivers. Nvidia doesn't even list drives for the Mac on its site - refers everything to Apple. I am trying to avoid complete resintall of the OS, but may pursue that

I hoping hardware prognosis is wrong! I use some pretty intensive graphic apps - photoshop, illustrator, aperture, all the i-apps, golive, nikon capture nx, etc - and this little piece of cinema is the only problem found so far. My gut tells it should show up elsewhere if there was an hardware problem. I thinking corruption or software conflict of some sort.

thanks in advance

[wbj]

still researching updating or re-installing drivers. Nvidia doesn't even list drives for the Mac on its site - refers everything to Apple. I am trying to avoid complete resintall of the OS, but may pursue that

I hoping hardware prognosis is wrong! I use some pretty intensive graphic apps - photoshop, illustrator, aperture, all the i-apps, golive, nikon capture nx, etc - and this little piece of cinema is the only problem found so far. My gut tells it should show up elsewhere if there was an hardware problem. I thinking corruption or software conflict of some sort.

thanks in advance

No need to reinstall the OS. I can reproduce it on my machine too. It seems to be an NVIDIA OGL driver problem (as the ATI card doesn't show this problem).

Best regards,

wbj

[SinCity]

seems to be a driver issue

[designbytes]

thanks wbj and sincity...appreciate the feedback.

I thought I was a "lonely soul" out there....;-)

...there must be some rev differences or software load differences between our machines and Adam's machine

...I haven't heard from Maxon yet on this issue

[SinCity]

Help us please! I don't want to be limited with software-shading...

[Srek]

I noticed already, but confirming and solving a problem are two different things. So far i can only say that i can confirm the problem.
Cheers
Björn

[designbytes]

thanks Srek

I haven't heard anything from my support report to Maxon....hopefully they are working on it.

for what its worth...same behavior in 9.6 ppc version, 9.5, and v8.205; all of course in Rosetta and probably not surprising.

[pbar]

On my MacPro 3ghz I've found that system update 10.4.8 seems to fix this problem, although makes no mention of any driver issues.

best regards
pbar

[designbytes]

On my MacPro 3ghz I've found that system update 10.4.8 seems to fix this problem, although makes no mention of any driver issues.

best regards
pbar

...just back from 8 days out of town and uploaded the 10.4.8 upgrade and can also confirm that the bug is gone...


now to read all v10 Cinema!

thx

Paul

[CGTalk Moderation]

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.