Where is Matt with fixes for constructor?

#1 His time has been well-spent on other GG tech.

#2 And who fix the bugs in constructor?

#3 Matt, when he has time and other projects aren't kicking him in the head.

EDIT:
There may be others, but C'tor has long been Matt's baby.

#4 Its not funny for me to compile a complex model when all map2dif modes complete crash!

My model with detailbrushes crash export to dif, export to legacy dif and map2dif plus tge!
When i delete alle detail brushes , then export to DIF work ...

#5 Then to me at least it would make sense to break your model up into smaller sections? You are almost certainly generating too many vertices with such a complex models.

#6 I keep seeing people having problems with detail brushes but I can't seem to replicate them. Most of my tests aren't complex (trying to find the common errors).

#7 I hate to keep saying the same things over and over. I dont build ANYTHING in Constructor. I use QUARK. Everything i have built in QUARK exports great. It will most often import into Constructor for light and texture placing then exports FROM Constructor just fine, as long as i dont use any of the DTS junk, and watch my zones VERY carefully. I have said it before, and here i go again; Constructor have fundamental flaws deep in the way its doing BSP math, (then lump on top of that a bunch of other little flaws, what do you get?).

You wish to see the errors yourself? Make a cube subtract a cube from the side of the first cube, do this a few times. OR, make a tall rectangle handle the top face, and resize the hight a few times. AND LAST, select a few brush and move them around a bit. Each example above will seem to be working fine, but at some point the DIF will stop exporting correctly. If you actually expect to build and export something complex, dont use Constructor. BUT if your very careful and think about what your building, so there is not alot of fussing around, Constructor quite often will not mess up at all. But for the sake of development speed, you can wast many hours trying to get Constructor to behave itself, OR you could use that same time to learn a more stable BSP editor.

It is sad how Constructor seemed to be dumped from the day it was born, it is also sad that the GG people never seem to have any problems with it. But it is most sad that many people are expending great amounts of time on a very dead horse and wondering why they are not getting anyplace.....

#8 My problems with contrustor is when i load up some DTS models on a hollow cube, give it a light, and try to export. I may be hitting some vertex limit, but i thought there wasn't one.

#9 Damn, Ramen. I'm not sure if my test had the same results as yours...but it was strange. I created a big cube, hollowed it (0.5) and put the DTS test crate in it with an omni light. I just used a blue texture. I used Export to DIF and everything exported fine. I loaded it up and put it in the mission. Everything outside of the box is blue, like it should be. But once I move inside the box, it is as if there are no textures. Just an outline of the box (if selected).

Weird.

#10 If you can send me a map that is guaranteed to crash, then I will see what I can do.

#11 @caylo
I had take a look on Quark for any weeks, but its a very "other" workstyle. I had many problems to add my textures into the editor...

@jaimi
Many thanks, i will send you a crashmap.

#12 I think the problem of the Constructor is it allows too many digits after the decimal point which make the Snap to Grid never snapped seamless.

After practiced for a not short time, also with the help from the m8s in this forum, finally I can build detailed things with less leak point, but it cost me more energy to be careful with every step.



Constructor ought to be a good software, if GG can do more work on it.

#13 @alex

If my hotmail account won't accept the attachment, send it to jaimi@aztica.com

I have time this weekend to look at it, so the sooner you can get it to me the better.

Jaimi

#14 @Sun Yu

That is very nice, looks like it was hard work. Are you making an RPG?

#15 Also, build a tube maybe 12 by 12 by 12 and give it 60 sides. Hollow it to 0.5 and save. Then reload and there's 0% chance that you can escape Constructor's 'Malformed brushes' wrath.

#16 60 sides is asking alot from any BSP editor...

#17 @Jaimi

Thanks. It really cost some time, it includes incline wall with corner piece. I am making an FPS. ;)

#18 @Alex

Alex, I haven't recieved your map - Have you sent it?

Jaimi

#19

Quote:
Also, build a tube maybe 12 by 12 by 12 and give it 60 sides. Hollow it to 0.5 and save. Then reload and there's 0% chance that you can escape Constructor's 'Malformed brushes' wrath.

My take on this is that hollowing it is creating a ton of "micro brushes". These are fine when they reside in memory, but when they are serialized to XML they lose precision. At load time, the precision lost leads to non-planar faces (etc).

What do you think it should do at this point - Give you the option to ignore all other malformed brushes, or stop loading the map, or both options (or something else)?

#20 Ignore them- they convert fine. Constructor is just to picky.