PDA

View Full Version : 3-4 second delay when selecting in XSI 7


SheepFactory
08-08-2008, 03:42 PM
So this is weird.

The selection speed in xsi 7 on my computer is totally dependant on the mesh density. For example a newly created a cylinder selection\deselection is instant but as soon as I add 150 subdivisions on U and V there is a 3-4 second pause where the software locks up and the pointer blinks like crazy while I select.

Does anyone else experience this? I am on a macbook pro with the ATI X1600 card and running xp pro. Xsi 6.5 on the same computer doesn't have a single problem. I have installed the latest gfx drivers from the ati site but the problem is still there.

thanks in advance.
-A

DougNicola
08-08-2008, 03:46 PM
Related to this? (in XSI 7 CGNews thread):
http://forums.cgsociety.org/showpost.php?p=5312971&postcount=50

edit: Just noticed that you just noticed this post :)

SheepFactory
08-08-2008, 03:50 PM
Yea :(

I guess no xsi 7 for me till I get my mac pro with the gforce card. :(

vauric
08-08-2008, 05:56 PM
yep, got an 1950xt here. Same issue.

Hope ATI gets it sorted asap.

Sbowling
08-09-2008, 03:29 AM
yep, got an 1950xt here. Same issue.

Hope ATI gets it sorted asap.

With ATI's record, they'll fix this problem, but cause 10 other problems in the process.

neso
08-09-2008, 08:32 AM
In case you've missed in the post on xsibase...

AMD/ATI display driver,at the bottom of this page here:
http://www.softimage.com/downloads/XSI_Advanced/default.aspx

Bullit
08-09-2008, 08:36 AM
That drivers are only for FireGL family of cards not generalist ones.

neso
08-09-2008, 11:15 AM
Well,guess you have to wait then.

vauric
08-09-2008, 11:52 AM
(I posted this on another thread)

Downloaded the latest ATI drivers "8.7" for winXP32. (x1950 gaming card drivers)

It fixed the selection lag issue in XSI 7.

tc
08-09-2008, 05:19 PM
http://www.xsibase.com/forum/index.php?board=1;action=display;threadid=37055;start=1

pete
08-12-2008, 03:30 AM
Hi there SheepFactory,
I had the same problem, and I can't install those update drivers as I have a macbook pro and it will only allow you to run some kinda old drivers. But I have a solution, well it seems to work for me even though it's pretty naff. Go to the view mode and switch from whatever to OpenGL then back and it seems to work fine after that.
Kind of anoying though, maybe you could make it into a temperary event script so when you start a new scene it does it.

Chirone
08-12-2008, 03:52 AM
it seems to me that ATI has a lot more problems with graphics than nVidia...

and i thought XSI didn't support windows running on macs, or was that just for a short time?

SheepFactory
08-12-2008, 04:02 AM
Hi there SheepFactory,
I had the same problem, and I can't install those update drivers as I have a macbook pro and it will only allow you to run some kinda old drivers. But I have a solution, well it seems to work for me even though it's pretty naff. Go to the view mode and switch from whatever to OpenGL then back and it seems to work fine after that.
Kind of anoying though, maybe you could make it into a temperary event script so when you start a new scene it does it.

Wait where is this view mode thing?


edit: If you mean viewport display type, it didn't work. :(

DecWest
08-12-2008, 08:51 AM
there's an old GFX industry nursery rhyme that goes..."Never Buy.....ATI"

Sage advice indeed

LOL

bunker
08-12-2008, 12:54 PM
As far as I'm concerned, ATI isn't good at doing anything. I had the exact same problem with Houdini, 10 seconds delay after every selection, and many other bugs with Maya with Radeons and FireGL cards. ATI should just give up, send all their money to Nvidia, and appologise for their terrible hardware and/or drivers.

ThE_JacO
08-12-2008, 01:09 PM
The houdini delay issue is the same thing XSI suffers from.
In Maya it's still there, but less noticeable, because of different viewport calls.

It's an ATI drivers issue they have beta drivers with a fix for, and hopefully will have a new release out sometime soon. They might artificially inflate the value in professional DCC of their fireGL line by not porting this to their gaming lines, but this is speculation.

In general my problem with ATI is that when this kind of stuff shows up it takes them forever, if they bother at all, to fix it.
nVIDIA has much better response time and addresses a lot more issues than ATI ever did, and apparently the disparity is even more accentuated since AMD bought ATI.
Apparently only some cad firms (and only their main CAD products, not their artistic DCC ones) get some attention from them in terms of drivers, probably because of market size and the fact they are easier to con into buying gaming cards at thrice the price for a different eprom and drivers.

I'm not a C4D user, but I read that Maxon has been having the same issue when it comes to ATI and nVIDIA and the amount and quality of support they get from the respective brands.

I don't question the quality of their hardware, but it will be many years before I'll ever give ATI an ounce of trust when it comes to 3D. Even if they had a solid diver cycle nobody knows what might or might not happen the following one given the current track record.
Maybe if they stop treating their customers and partners like rubbish for more than a month every two years I'll start considering the brand again.

WillBellJr
08-12-2008, 02:27 PM
it seems to me that ATI has a lot more problems with graphics than nVidia...

and i thought XSI didn't support windows running on macs, or was that just for a short time?

...And this is the exact reason why I ONLY buy NVidia based graphics cards and laptops...

-Will

pete
08-12-2008, 03:27 PM
that sucks because I don't plan on changing my macbook anytime soon ad it works pretty well for the rest of my PC based stuff at home... I think I'll have to stick to my nasty open GL hack for the moment (which is already starting to drive me nuts)
Sorry Sheepfactory , I meant display mode, you know like wireframe hidden line ect.

mocaw
08-12-2008, 03:28 PM
Well I'm not seeing delays anywhere except in the FX tree a small bit...and in the ICE tree in a big way!

Sometimes when trying to connect things in the ICE tree it takes for ever to update...and there are major graphical glitches too (like I can't see the tree refresh and update when panning until I close the Ice tree and re open). Makes learning a new tool just that more frustrating- instead of fun!

This is on Vista 64 (don't even get me started- worst install next to NT4) with a cr*ptastic ATI card. I'll roll back my drivers and see if it makes a difference.

So should I chalk this one up as an ATI issue too or is it a separate issue?

SheepFactory
08-12-2008, 03:52 PM
Well I'm not seeing delays anywhere except in the FX tree a small bit...and in the ICE tree in a big way!

Sometimes when trying to connect things in the ICE tree it takes for ever to update...and there are major graphical glitches too (like I can't see the tree refresh and update when panning until I close the Ice tree and re open). Makes learning a new tool just that more frustrating- instead of fun!

This is on Vista 64 (don't even get me started- worst install next to NT4) with a cr*ptastic ATI card. I'll roll back my drivers and see if it makes a difference.

So should I chalk this one up as an ATI issue too or is it a separate issue?


Obviously its a ATI issue, why do you even ask. :(


I might need to sell my MBP and get one of the newer ones with the nvidia cards in them.

vauric
08-12-2008, 03:55 PM
Yer got slow downs in the ice tree window with ati card.

Had enough and just got a 8800gt relatively cheap.

Now, Nvidia, dont let me down :curious:

revert
08-12-2008, 04:48 PM
I can't help with your ATI problem but maybe something to help that isn't so drastic, rather than closing the ICE Tree, click outside of it, see if that helps. If not, try clicking outside of XSI.

Well I'm not seeing delays anywhere except in the FX tree a small bit...and in the ICE tree in a big way!

Sometimes when trying to connect things in the ICE tree it takes for ever to update...and there are major graphical glitches too (like I can't see the tree refresh and update when panning until I close the Ice tree and re open). Makes learning a new tool just that more frustrating- instead of fun!

This is on Vista 64 (don't even get me started- worst install next to NT4) with a cr*ptastic ATI card. I'll roll back my drivers and see if it makes a difference.

So should I chalk this one up as an ATI issue too or is it a separate issue?

Chirone
08-12-2008, 10:03 PM
my friend is saying that ATI has a lot issues fixed up

also its cheaper than nvidia for equivalent cards

but then he only plays games, doesn't do anything like what we do...

i'm quite reluctant to go with his advice to get an ATI seeings as how you guys all have problems...
btw, how old are your ATIs?

3dtutorial
08-12-2008, 10:13 PM
My experience has been this...

Avoid ATI cards with XSI at all costs regardless of what the game dudes might say.

Words to the wise.

BTW - I've got nothing against ATI other than all the aggro that I've had with them and XSI over many years.

Me, I avoid ATI like the plague.

But... it's up to you of course.

Cheers mate,

J

Bullit
08-12-2008, 10:14 PM
I have an old ATI the only problem i have is selecting meshes for the first time for the second time the lag is almost reduced to nil. No problems with ICE. This card only give me problem with V7.0 .

pete
08-12-2008, 10:46 PM
do you think it would work if we could somehow install the 8.7 version on the macbook, it seemed to work for vauric (earlier in this thread)

liquidik
08-12-2008, 11:16 PM
Haven't tried with xsi 7 yet. But I know for sure that v 8.7 solved the same problem in blender too.

If your notebook maker doesn't have v 8.7 out yet, you can use this little utility

http://www.driverheaven.net/modtool.php

And install the regular desktop driver. If you read that page you'll find out!

It worked great with my friend's sony vaio.

-Gian

luceric
08-13-2008, 02:54 AM
...and there are major graphical glitches too (like I can't see the tree refresh and update when panning until I close the Ice tree and re open). Makes learning a new tool just that more frustrating- instead of fun!

This is on Vista 64

never pop a context menu and pan the ICE Tree view in Vista with Aero off, or you run into a weird problem where the ICE tree stops refreshing. I believe this is a Windows problem.
Avoid the problem with either turning Aero on, or fix the problem with resizing the view when it happens.

mocaw
08-13-2008, 03:27 AM
luceric - thank you for the low down on the odd aero thing!

So I have to run with aero on all the way or just a few features? I'll experiment...just ordered a Nvidia card so I don't know if that will help either.

Is anyone running XSI without the annoying wiz bang of aero on and doing OK?

*****Happy to report back that so far it's working as advertised- thanks again luceric!

tuna
08-13-2008, 03:37 AM
never pop a context menu and pan the ICE Tree view in Vista with Aero off, or you run into a weird problem where the ICE tree stops refreshing. I believe this is a Windows problem.
Avoid the problem with either turning Aero on, or fix the problem with resizing the view when it happens.

Is this the same issue that occured in XSI 6 where the f-curve editor wouldn't refresh when using the Classic theme in Vista? (Workaround was to use Vista themes - Aero was simply nicer). Does this still happen at all?

[edit] this question isnt specific to ATI

pete
09-13-2008, 04:28 AM
Hey Sheepfactory,
Don't know if you managed to fix the problem but I just installed the latest drivers with mobility modder as liquidik mentioned before and now it works fine!

SheepFactory
09-13-2008, 07:08 AM
Thanks for the heads up. I am gonna try that tomorrow.

digitalguest
09-13-2008, 12:27 PM
hi everyone, well I'm using a Imac, and same problem here, i have to keep hiding and isolating to keep working once the mesh gets complicated. I din't try yet the modder tool if someone with mac fixed the problem with it let me know please.

thanks in advance

CGTalk Moderation
09-13-2008, 12:27 PM
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.