I solved the problem of the gates and the columns, but how do I modify the .dgbangerdata file of the stone column if I want it not to move, like a normal wall?
For first thing you have to make the stone column as new object and save it as .pkg file, then you can well add it in the city as PKG object through the .inst file, so it can't be moved. The gate object has to be obviously added as PROP object trough the props.pathset file, to get it movable. Is pretty made in this way with the London Buckingham Palace gates and columns and gate doors. At the end you have to accurately place copies of the column and gate objects where they have to be placed.
Anyway, if you already have the column object as separated object from the gate and it's already added as PROP object, is better do as you ask, you'll save time and get the same result. Probably you have to increase a lot the ImpulseLimit2 value, do some tries checking and copying from the .dgbangerdata files of the game PROP object of the tree palm (sp_treepalm4_f.dgbangerdata) and of the bridge column (sp_fwsupport_f.dgbangerdata).
The older problem maybe could depend by the BOUND object, but I don't think so, because sometimes it's indeed given by the .dgbangerdata file; it there's to one of the billiard balls of the Billiard Burnout track.
For the issue of the light spot above each gate prop type object, you have to edit its .dgbangerdata file with Notepad deleting the GlowOffset row and setting 0 to the NumGlows value; as alternative, you can change this file taking the one used for an in-game object that sure doesn't use the light glow.
I mostly like the scenery around the Parliament...
