R10 slow as hell

[Per-Anders]

If there was no difference between using OGL & Software mode then perhaps there is an issue with your graphics card driver, or even possibly a problem with your Cinema install itself. Try deleting all your preferences for R10 and starting it up from scratch, see if thta makes any difference. Also you can try using enhanced opengl mode, depending on yrou setup and scene this can give either a speedup or a slowdown.

[re:disco]

same behavior after clean install
updated catalyst also


when i rotate scene - its fast

but when zoom or select object - slow
wtf?

[Per-Anders]

You're not using Vista perchance are you (known to have terrible ogl)? Otherwise you might want to try using the ngo drivers instead www.ngohq.com , or even an older driver (occasionally the latest driver isn'tthe one to go for).

Personally I've not had any slowdown going to R10 on my PC, I didn't bring accross my old preferences (make sure you don't, not even for layouts), and I'm using an nvidia 7800gt in this machine, in most situations if something did seem slow switching on Enhanced OGL resolved that. You may also want to check your OGL settings in the Cinema preferences with regards things like dualplanes etc which you may have set up in R9 but haven't in R10 yet, and in the control panel for switching off things like vertical sync.

[re:disco]

strange

when i opened same cars from another c4d file
all is pretty fast

may be problem with texture path?
they are placed in tex folder inside folder of =fast= scene

slow scene was in another folder
and used textures according to path in preferences

[Per-Anders]

Possibly it has some relation, when it has to search for a file that could potentially slow things down. If you can recreate this in a file that's not too big to send then it might be worth sending to Maxon technical support to have a look at.

[re:disco]

found a problem:

it somehow because of tags on these cars
if group where cars located
is closed in object manager - no lags

[unseenthings]

I was going to suggest checking the tags... I've found that if one or more objects have a lot of tags (which is very common if you're importing from 3ds or lightwave, for example) then everything slows *way* down... opening the same scene in 9.6 (as mentioned) works fine.

[Ernest Burden]

It would be simple enough to render the test file with textures turned off, or delete all materials and see what happens.

[laurent]

"when i rotate scene - its fast but when zoom or select object - slow
wtf?"
"when i opened same cars from another c4d fileall is pretty fast"

that means that you have an extreme zoom on your camera.
change your camera setings to military (for example) and back to perspective.
remember to dolly your camera and not to usethe zoom icon.

[LemonNado]

There is also a problem with multi core machines. When you zoom in and out a few times then it can happen that one cpu get's thrown into a loop. In that case I either exit and restart or cover the viewports with another window and close that. After that the loop is broken for some odd condition and all is well again. Maxon is also working on that.
So before you render... check your cpu load. There could be one missing.
Rainer

[Kuroyume0161]

I was going to reply earlier about this interesting problem - now I am even more interested with the comment concerning tags.

I can confirm this with laser precision. interPoser Pro runs in everything from R8.2 to R10, Windows and MacOS. Part of the way that it handles Poser 'channels' (or dials) is with tags. The tags are hidden in the Object Manager to avoid bogging it down. The tags are set up as sliders on the object's Attributes Manager (as dynamic descriptions using GetDDescription() - Per will know what I'm talking about).

In R9.6 and earlier, lots of sliders (i.e.: tags) have no deliterious effect. In R10, both users and myself have noticed real sluggishness working with sliders if there are like (and the magic number, please) 50 or more sliders (i.e.: tags). On Windows, there is just a pause before you can change the slider or scroll the A.M. On MacOSX, there is that darned 'beach ball' at every turn.

V4 was the Poser content that brought this to light. Since this figure has all of the morphs included (no Inj/Rem stuff like V3 and other Daz3D Millenium figures), the head dials are particularly frustrating.

So I will concur with the tag hypothesis for now as that makes two of us who can relate to that as a probable cause (in MB talk: Plausible).

Robert

[LemonNado]

Maxon has to Profile the V10 Code. Probably they have done so already.
Time for a fractional update 8).
R

[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.