AEC errors again :(

[Chri688m]

Hi everyone im faced with a error regarding AEC.

When i am trying to make a floorplan with alot of different walls attached together and i begin to place walls to boolean with the aec doors / windows it crashes after a certain amount of door or windows are places this is a common issue in AEC for me atleast...

I posted a video on youtube to show what exsactly happens - i have also run windows logs to check what windows sais and it is described as a Application hang or fault bucket

UPDATE: If i chose not to attach the walls together but have 35 different walls it does not crash although this is not optimal at all 😕 (Would still like a solution if anyone has one)

https://www.youtube.com/watch?v=MpIL342m_Mc&feature=youtu.be

@Alfred.DeFlaminis Maby you know a fix to this issue aswell as the other issue regarding AEC? - in case you want to check out the file then i can send it to your email...

_______________________________

One Does Not Simply Receive Kudos!

_______________________________

[irishman_team_kilber]

that is not a max problem that is a windows problem. so you will need to contact microsoft and see if there are any solutions why this happens is max stops interacting with windows.  i get them all the time, and it can be annoying

A fault bucket identification number is a number assigned by the system to identify specific types of errors, usually based on a specific application. You should see a corresponding error in the Event logs which you have already done. The source  ID is what is sent to Microsoft when you send an error report.

[irishman_team_kilber]

yeah that is what happens to mine when clone a door a window, max freezes the only way around it is to recreate the door from the menu and then copy the dimensions to the new doors and avoid copying it even in the lower version of max 9 i have this issue, i always get error message hangB max has stopped interacting with MS windows.

[Alfred.DeFlaminis]

Hello @Chri688m,

I'd be happy to take a look if you'd like.  There are two things I'd try though.  The first is to separate some of the walls into new objects, no reason the walls all have to be 1 piece.  The 2nd thing is that the door is intersecting sideways into that wall, maybe rotate it before you place it so Max isn't trying to perform an impossible boolean.  Feel free to send it along though if you'd like.

Best Regards,

[irishman_team_kilber]

@Alfred.DeFlaminis IMHO it was nothing to do with the walls it has to do with the cloning issue, if you clone a window/door and the it freezes and max stops interacting with the windows OS, i am not sure if its just related the newer versions of windows but this freeze issue never happened with windows, 98, xp or ME but it does have a issue with the newer version of windows.

[irishman_team_kilber]

the other way of beating the bug is to completely close down max and reopen it but no one wants to do this every 2 hours when you have a client or a dead-line!

[Alfred.DeFlaminis]

Hmm.  I don't have an issue logged for that.  Do you have a scene where this happens 100% of the time or some easily to repro steps?  Looks like I should log this.  

Have either of you submitted a CER from this crash recently?  If you do, please note the report number and I'll look it up to see whatever info I can.  Testing on Win 7 I am not seeing this happen at all, and I'll test on Win10 when I'm back in the office.  It may be a combination of things which causes the issue so any scene files would help a lot.  Thanks!

Best Regards,

[irishman_team_kilber]

@Alfred.DeFlaminis I don't get a crash reporting error only when autodesk 3ds max crashes and it's not an autodesk problem, it's a windows problem, i cannot make max crash sometimes max crashes when it wants too or it,  

here is an old error from max that i got in my event viewer

The program 3dsmax.exe version 9.2.0.114 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
 Process ID: 1598
 Start Time: 01d34d766ef50528
 Termination Time: 292
 Application Path: C:\Program Files (x86)\Autodesk\3ds Max 9\3dsmax.exe
 Report Id: 5dbb8e21-b96c-11e7-bcce-902b3438e12e

[Alfred.DeFlaminis]

Wow Max 9, that was my favorite build for the longest time.  Typically rock solid, but also made for XP/W2000 if memory serves.  Is that running on Vista?

Typically if it's crashing suddenly there is a Visual C runtime or something that needs to be updated.  So the cause may be Windows but I still want to see what can be done.  

Best Regards,

[irishman_team_kilber]

It does not matter if you updated mines completely up to date, max crashes anyway,

if you create a walls and then add the windows or doors and clone them across max is likely to crash and gvie you the same reason max has stop interacting with windows, and it asks you to close not saying it will, 

but that is the error Chris and myself get all the time for some reason max doesn't crash when you first load it up if you been working on a scene for 2 hours then max crashes. on a completely black scene it doesn't crash,

i am not sure why i am running windows 7

[Alfred.DeFlaminis]

Likely the problem there is that Max 9 wasn't built for Windows 7.  It's looking for OS hooks that no longer exist in that version.  However it must still be an issue since the OP is on 2018 and W10 which it is built for.  I can't seem to repro on Win7 though no matter how hard I try.  (I prefer Win7 both at work and at home.)  I'll try to do some testing on W10 but if anyone has a scene which this always happens that would be great and thank you.

Best Regards,

[irishman_team_kilber]

if it was just max 9 on a windows 7 then Chris would not get the crash on max 2012 i am not sure what OS he's using, but i deffo know it's not max itself! i can send you my file i am working on but you need to send me the a private folder, and my units are both in meters so you would need to change them back to the system units and the units setup to whatever you were using before!  

[Alfred.DeFlaminis]

Thanks very much @irishman_team_kilber,

I have set up a private folder for you if you'd like to upload your files there. You should get an email about it shortly, and if you don't see it please check your SPAM folder. These files are private and will not be shared with anyone but yourself and the support staff. Please let me know if you have any questions. Please use at least an 8 character password or the Box account may not work properly. Once you have uploaded your files, please post a comment here or send me a PM so I know to check the Box account. Thanks!

Best Regards,

[irishman_team_kilber]

@Alfred.DeFlaminis sent.

[Alfred.DeFlaminis]

Hmm, I'm not seeing it.  Is it possible it's in your root but not the shared folder?  If not, maybe you can PM me a direct link to it, thanks so much!

Best Regards,

[irishman_team_kilber]

@Alfred.DeFlaminis i have PM you directly with another link,

[Alfred.DeFlaminis]

Excellent, could repro on the first try.  I'm messing around with this right now to see if I can find a workaround.  Thanks!

Best Regards,

[irishman_team_kilber]

@Alfred.DeFlaminis the only work around i found is by closing it down and opening the scene file or create new windows/doors and copying the dimensions from one to another!

[Alfred.DeFlaminis]

Hello @irishman_team_kilber,

I think the problem here is the same as that other thread, at least with this file.  When I subdivide that wall a bit it all works fine.  Copied the window all the way down the line after 6 or so segment subdivs.  (Didn't test lower.)   The event viewer does show the crash happening in Max through Windows, so it's does seem to be coming from Max.   

It's clearly getting confused when it tries to copy that last window in terms of how to subdivide the mesh.  But the divided segments help it to find the nearest vert for the boolean operation.  So, I think we chalk this up to the exact same problem... parameterization.  It's a problem that it crashes Max but at least you know why.  I will log it but I think it's a design limitation and also the reason the segment subdivisions are there in the first place.  It shouldn't freeze the app though.  For now though the easy workaround is subdivide those segments a bit more.  

@Chri688m if you have a simple file I can test that would also be awesome.  Thanks!

Best Regards,

[irishman_team_kilber]

@Alfred.DeFlaminis Autodesk won't do anything, i mite as well start boolean the AEC walls and then putting the windows and doors in place, but with boolean or pro-boolean it gonna make a mess on the mesh, it's not like the AEC walls are not a mess already with all the trangles in the mesh,