Responsiveness

I've had the same issue; compared to V8i Connect seems painfully slow.  The primary purpose of the revamp seems to be a more logical grouping of tools to make it easier to access across multiple disciplines.  Since I only use the architecture part the other pieces don't matter to me.  If I were just learning the software the new grouping would be helpful but to someone familiar with the system, it simply involves more clicks and having to reach further than the tool windows that can be located on top of the drawing.

I'm a solo architect, not the main market for Bentley, and any modification or customization to the program is a painful endeavor with my middling computer skills.

I've gone back to V8i which now seems blazingly fast.

Is this just me or have others had a similar experience? 

Thank you Twoseas,

I feel less alone.

I am surprised to have so few reactions on this matter.

I suppose nobody really switched to Connect for production (MS Connect Update .1.2.3.4.5.6.7.8.9.10.11 is not really engaging and AECOsim is so complicated to configure and set up.. especially for small companies.).

I really hope this responsiveness issue will be solved. This is the number 1 priority for me.

regards,

Xtov

Christophe, 

I can back you up here. I find that, although yes, U4 is an improvement on U3/2 etc, it is still way too laggy. 

I find the most common cases of this are when initiating a datagroup tool, ie place wall/slab/stair, and again when quitting the tool. 

Closing properties and only opening when required does speed up element selection massively, but is is pain because I like to be aware of what I am selecting

What annoys the most is the time wasted when it just decides to go into spinny circle mode, usually after some quitting a command. sometimes this can be a fraction os a second, most of the time it feels like forever.  

Amazingly though, this is quicker than V8 SS6 for me

I'm also having responsiveness issues, especially when changing between files with reference attachments that are from old V8i projects. The application hangs from anywhere between 30 seconds and 5 minutes. Obviously, this isn't really acceptable, especially as V8i was so fast.

Our tech support has said to compress reference attachments, but it hasn't helped.

Any tips?

We have the same issue as I used to jump from file to file designing as I go.  Now opening files is very slow and too many time it will revert to an hour glass in the middle of tasks.  I did notice a change to 4 but also found out with our hiring some support that modifications have to be done in particular was - duplicates for example are now more of an issue and can cause crashing and lags.

Our old datasets are bad as we cannot tell where things are updated and no tools to update them so I have to take each library and remove the items that are duplicate to the originals and then run the one utility we have seen to update each again for assurance.

Things are smoother but way to slow and bumpy.

Too many times I wait to see if it will open or the hour glass stop - could be 10 sec or 30 minutes.  Some times it crashes and some time I have to crash it and open again.  It it spins for 10 minutes and I crash it and reopen.  It may open immediately, justifying the reason for me to crash it.  But not always - SO I can never tell it is crashing or needs the time to process.

I did notice when looking at my resources - as i did in the original Bentley Architecture what appears to be a memory leak or a point to where the limit or memory usage is not enough and the processing is being handled below a threshold and trying to get everything finished in very little memory or process.

It appears processing is capped at about 18% of my processing power and 20% of my memory.  If I watch both when working a task I see that as I get to those limits things either complete and the resources reappear or it get slower to the point of almost stopping - as if it needs the memory and CPU to work but now only has a small ceiling of resources and creeps.