@damage_inc thanks for that will reverse engineer, This is a blast. 

Hey,

So I started mapping a few days ago and I've recently hit a brick wall. I've been working on a Quake map in Trenchbroom, compiling it with ericw-tools, and now suddenly, upon compiling, my map is just refusing to run and I have no idea why.

https://i.imgur.com/uWF4N9f.png

^ That is all I see upon compiling and attempting to run the map. I have a .BSP of my map, it IS in the correct location, I can run an older version of my map and the default maps, but for no apparent reason Quake has just decided to not let me run my map anymore. Using the console and typing "map mymapname" leads to the same result as the image posted above.

I have no idea what the solution is and would appreciate some help because I can't test my map anymore until this is resolved. 

Running any mod or is this vanilla id1? 

Some Googling says:

This is also the error given when giving a func_plat a negative "height" value. 

Yeah got it now, thank you. I wasn't aware that you couldn't reverse the direction of a func_plat with a negative integer, that's why the game was freaking out. 

Very often if you want a platform, you should use a func_door. Moving downwards is certainly one of those cases. 

Dear all,

I experience a very annoying bug. I'm afraid it's a well-known issue. Sorry in advance for maybe being the 1000th one to ask about it but I didn't figured out the right keywords in the search engine to find how to fix it.

For some unknown (to me) reason, some of the brush entities in my map turn non solid. They are still drawn but don't block the player movements anymore and can't be touched either, just like illusionary walls: doors looking closed but being wide open, button not triggerable anymore unless they have a health value, breakable brushes needless to break...

Trenchbroom doesn't give me a clue about the problem. There is no leak... What the hell is going on???

Shall I precise that curiously SOME of the brush entities in the same map react the right way and can be normally interacted with. o_O;

Thank you in avdance for enlighting my mind, I'm going mad! 

Are you building things near the origin coordinates in the space, or are you building far away from the origin? If things get more than 4096 units away from the origin then weird stuff can happen in most Quake engines. 

so, what it feels to me is like a vis problem.
Some brushes may overlap eachother on a 0.01 unit which causes the compiler choose between both of them.

Isn't there a command "force all brushes on grid" in Trenchboom? 

In TrenchBroom, under the Edit menu you will find Snap Vertices to grid and snap to integer. 

Are there any maps with identical versions for both Quake 1, UT99 and/or UT2K4?

I've been reading about Q3A to UT map converters, but I'm not sure if that would work well for Q1 maps:
https://ut99.org/viewtopic.php?t=2799 

For long time now i ask myself how you guys to angled brushwork in Radiant, like arches that lie on 45°, 33° or any other weird angles on the grid.

A great example for what i mean would be the huge chains in czg's q1 map Honey.

I try avoiding building stuff on grid 90° on grid an then rotaing it, as this brings the vertices off grid.
Some stuff i manage to do via a mix of csg_subtract and clipping, but for more complex constructs my brains 3D projecting algorithms fail ^^'

Are there any "cleaner" methods to do it? 

i did a post here once about "magic" (aka on-grid) rotation, but fuck knows where that's gone - same technique czg did for those angled bridge ruins in saint.bsp

These days though, misc_external_map is your friend for a lot of this stuff...

http://ericwa.github.io/ericw-tools/doc/qbsp.html 

i could do it with .ase geometry, as i am using Darkplaces with q3map2.
It's for a total conversion and use advanced features of both.

In some cases using .ase or a model instead of brushwork are not practical, at least that is what it seem to me.
And i guess the main problem in what i am trying to do is not the brushwork and it's limits, but my geometric understanding of things.

Here some screenshots of things i try to do:
https://imgur.com/a/Eg0E4ry

Maybe i asked even the wrong question, so i rather ask: how would you guys do that stuff depicted in the screenies? 

If you are doing stuff for the q3bsp format then it's a pretty good idea to use meshmodels/ase to work around the times when brushes just won't cut it.

For "seamless" joins of arbitrarily rotated meshmodels to surrounding brush geo, you'll want to use some artistic license and design the model in such a way so you have some "wiggle room" to be able to butt things into each other a bit and not look ugly - e.g. hide the joins with some raised trim or raised brick quoins or something 

I will for sure use that approach for more complicated geometry.

Just saw that screenshot of Wrath: Aeon of ruins in another thread:
https://imgur.com/Qg3VSqU

Would be interesting to know how that hall, especialy its in multiple directions facing door arches, where made.
At least that domed ceiling would be no problem with a trisoup.

PS:
Is Sock still around? 

Built this ship for someones map and I wanted it to be a rotate train. I got it all working fairly well despite some tuning I can do later. But for now I have this movewall that doesn't rotate. So if you ride the thing straight or fairly straight everything is fine. Once the boat turns the func_movewall doesn't. Is there a way to make the rotate_object solid so I can remove the movewall entirely?

A video showing it does work on my server.
https://drive.google.com/open?id=158gR5W8kGsF8pER2jKuH7wUifnlQOuv0


A link to the bsp. It meant to run on teamfortress with hipnotic ents added. So that means megatf and custom. I haven't tried other mods to see how it works.
https://drive.google.com/open?id=1JP77gLYtk6RX0D6FpH84gemy13pCwzeN 

bsp collision can't rotate without an engine feature. (this does exist for some engines, can't remember which, but Baker had it in MarkV I think?)

The movewalls are basically a hack to get around this -- you actually need many small movewalls, each one will not rotate, but the positions of them all will orbit the origin of the object to sort of make it work. For example if you put a movewall for just the mast of the ship, it would correctly move with the mast. Warning: You will need a lot of movewalls. 

Yes, I read through preaches site on all this. The server I intend it to run on will be FTE. I wont do the many funcwall thing, but I appreciate you suggesting. It would take way to many to simulate what i need here. I am pretty sure it can work, a non solid into a solid, but setting movetypes and avelocites blows my mind.