List of AECOSim SS5 Defects

Hi, 

Is there anywhere that I can request a list of known defects in AECOSim SS5? Because I've spent nearly the whole day trying to troubleshoot the structural cutback issue and associated structural report spreadsheet issue. Only to find out later that there are defects filed against what we saw. 

It would be profusely appreciated if I can have a list of AECOSim SS5 defects so that I won't have to waste time trying to identify/fix what can't be fix. 

Parents
  • Must sympathise
    Have just moved on to SS6, so hopefully won't have to go back to it. But that is on small personal project. I know of some people at work still using SS4, and maybe SS5
    This topic has popped up before, and recently. Unfortunately it doesn't seem to be on Bentley Systems radar screen. I think it's a major oversight. Some folk/firms maybe sticking with SS4/5 for a few years as they don't like (understandably) tying to upgrade mid-project. I think it's pretty 'off' that Bentley don't do this a matter of course. Seems clear that a large part of tech support (and therefore the select service) would include informing customers of known issues. This really is an own goal by Bentley here.
    There is an over-focus on 'here, look at this year's latest batch of cool new tools' and not enough effort/support for getting what is already there to work properly/smoothly/reliably

    Regards

    Danny Cooley

    Freelance AEC CAD/BIM Technician Architecture, MEP & Structural  ..... (& ex Low Carbon Consultant, ..... because they weren't that bothered!)

    OBD Update 10, Windows 10 Pro, HP Z4-G4, 64Gb, Xeon 3.6GHz, Quadro M4000

  • Unfortunately, no, we do not have a predefined list that we can offer. If there's a specific issue you're running up against we can certainly check to see if any defects exist in our system for that issue(s).

    One of the more difficult aspects I've come across is what such a list would include - there are issues reported by users and others only ever found internally. And then there are those that require a specific user's DGN file or some other data to reproduce. Oh, and we can't forget those that require you to stand on one leg while facing east with your right arm facing north while alternately picking the Move too and then hovering over the Accudraw window. ;-)) Seriously though, it's often just the attempt at whittling down the list that exceeds available bandwidth...



Reply
  • Unfortunately, no, we do not have a predefined list that we can offer. If there's a specific issue you're running up against we can certainly check to see if any defects exist in our system for that issue(s).

    One of the more difficult aspects I've come across is what such a list would include - there are issues reported by users and others only ever found internally. And then there are those that require a specific user's DGN file or some other data to reproduce. Oh, and we can't forget those that require you to stand on one leg while facing east with your right arm facing north while alternately picking the Move too and then hovering over the Accudraw window. ;-)) Seriously though, it's often just the attempt at whittling down the list that exceeds available bandwidth...



Children
  • Steve, 

    Would it help if I refine my request as: "a list of defects that reproducible using out of the box installation of AECOSIM SS5". 

    As an example, the biggest issue that we are facing in our project at the moment is illustrated below.

    - 2 structural members

    - Connected by "connect form bisector" tool

    - Moved.

    - ...defect!

    Straight out of vanilla AECOSim SS5

    At first, we didn't know what was happening. Someone tried to move a structure and the members would become alive and stretched their arms and legs everywhere. Took me good 3hrs to nail the issue down to the above snapshot. A quick search in the forum, and sure enough, there is defect filed against the issue. 

    I consider myself lucky in this instance, because I was able to determine the issue is a defect recognised by Bentley within 3hrs. And I was lucky because the issue is reported here on the forum. I did raise a SR at pretty much the same time I submitted this post. And so far, I haven't got any reply for my SR. 

    With the mentality "If there's a specific issue you're running up against we can certainly check to see if any defects exist in our system for that issue(s).", I wonder how I can develop a workflow for our office so that we can avoid the issue before we commence the work. I know now for the next project, don't use the defected tools. But what about the current project? The resources went into making these defected connections is pretty much written off, and now extra resources have to be spent to rectify the issue. All the while Bentley is aware of the issue. 

    To be clear, I'm not asking for a list of all the issues reported internally/externally, I'm after the list of issues that Bentley considers as defects and will be fixed/corrected in next release(s) of AECOSim. I'm not interested in improvements. 

    I appreciate that the number of filed issues could be massive, however, I'd rather know about issues that I may never come across, than heading down a wrong path and having to find my way back, only to realise Bentley's keeping direction sign behind closed doors.

    I see there exists this:

    communities.bentley.com/.../defect-lists

    Why can't we have one for AECOSim? 

  • Hi Tuan,
    I found out that the blog you mentioned was only used during an EAP cycle to keep track of user reported issues on that EAP forum, and really just to avoid duplicate reports while the cycle was active. It wasn't intended for commercially released software in any fashion, for all the reasons mentioned above. And since I asked, it was taken down since the EAP had ended.

    Another aspect to this topic is that should one team actually provide something like this, the expectation is that others should do so as well. The blog post you found is a perfect example of this, even though in reality it wasn't what it first appeared to be. So a decision like this would likely have to be made at a higher level and not on a product by product basis. And at this point, at least for V8i, it's just not something that's practical to do. Whether that changes in the future with CONNECT and its more frequent release cycle, I do not know...