Constructor is getting slower.

#1 Have you thought about splitting your building up into several DIF files? If your building is the huge one that you were working on, then that would be the best option as it is a HUGE amount of brushes to deal with.

#2 Yes have thought about it but as of right now the way that the building has to operate don't think it will work and it would be nice to have it all as one file and then if it needs to be cut up can just do so and everything will line up the way it is intended to. I am at 2692 brushes right now is that to many?

Thanks for the suggestion..

#3 That doesn't seem like that many brushes, but are some of them extremely large? I know that Radiant had some issues back in the day with huge brushes. Cutting them in half would give dramatic increases in performance. On another note, does map2dif still have problems with the number of brushes that it compiles? I believe that Tim Aste cut up his castle pack because of the amount of brushes (or was it the size?).

#4 My brushes I don't think are that big.. I do have a 4 dts files I am working with to build this file the correct size as my max file I had built all ready that my have something to do with it but if there is a hard limit that map2dif can do pleas some one late me know before I get there so to look out for it?

#5 Well, I believe the Castle pack was done pre-Map2Dif_Plus, so Matthew Fairfax may have removed any hard limits. I cannot remember and I do not have the source code installed here at work (for obvious reasons) so I can't see if there are any defined.

#6 Well if it does and I hit that magic number I will know the answerer to it. thanks

#7 It as come to my attention that selecting thing gets a little be slow..

Now if you have 1 brush all ready selected and you go to select a second brush by holding Shift it seems to select the second brush fairly fast. It is when you select that first brush (vertices, edge, face) that Constructor slows down and takes fore ever to select that first thing.

Is this a bug?

#8 What beta are you using ?

There are some speed issues with selection in Beta 13 and below due to the treeview. Try removing the layers form and see if that speeds things up for you. I hacked in a new treeview control last week so theoretically it should be better from the next beta, but I've been more concerned about stability and getting it running thus far.

Re: Tim's castle pack, Matt made some minor changes to map2dif for that. They would have rolled back into stock a long time ago, however.

I also second David's advice about splitting your map up into multiple difs.

T

#9 Try the latest beta (15) and see if that makes a difference. Keep in mind though that we haven't done much optimization at all to Constructor beyond keeping the performance "decent" for an average scene. We will be doing more optimization later.

#10 Thanks for the heads up..

#11 What would constitute an "average" scene? My team is always wanting these huge models and the term "average" has little meaning to me. Does "average" mean a single house or what?