To fix it, you need to increase Anti Aliasing till x8 in option menu. Also in some video cards may be Smooth Adjusting option which also could help.

The nature of the error could be any, but first of all you need to figure out which of your model is buggy. Try to export them separately by selecting them one by one till it gives error.
The usual way to loose an error - copy your buggy model and move it in any direction far enough. Select both models and merge them in one (with merge textures). In polygon mode crop and delete no needed copy. Now the model must loose all errors.

QuoteOkay, so I have to freeze it. How do I do it? Is there a special button/key to do it?

Yes, you need to selcet models and click at the right panel Transform>Freeze All Transforms.

QuoteThe only elements that have been placed randomly are collisions.

All of the usual collisions must be freezed. All of the collision primitives must not.

Most likely you forgot to freeze your models. Make sure everything is freezed except collision primitives. Also you should never move the Nulls.

It say it can't export camera, so don't do this. Try export only your model by select it.

The game uses 2 types of collision: 1) usual collision: could be any shape, and named collision. 2) primitive collision: could be only cube, sphere or cylinder, and named p_cube, p_sphere and p_cylinder. It uses mostly for vehicles or doors, but as you can see it's also may be useful for buildings.

Making deal with your visual perspective would be the best solution. Still it's curious why are you try to rename those primitive collisions... Their names looks correct, and should work in game. (I hope you know p_cube means "primitive collision cube").

Nope. This thing just can't be installed at my Windows version (I have Windows XP).

It say it can't work with Win32.

Perhaps you forgot to freeze all transforms for your collisions and they are appears elsewhere. Mostly, there is no reason to making a lot of collision meshes. You need just merge them in single collision, and yes, you need to remove -nocollision line from the .msh option file.

QuoteAlso, when I click on an element with the name "p_-so-XXXYYY" it seems that no geometry is selected on the screen (I don't understand why there is an H underneath and what means).

The ''H'' means hide. You need to click H button on your keyboard to unhide it.

QuoteBut my question is: Is there any way to check which geometry has collision or not? And is there any way to add the collision to geometry that which doesn't have?

Weird question. The geometry and collision geometry - the different geometries... Anyway, to add collision to certain geometry you need just to copy it and rename as collision (perhaps also you may need to reducted it and remove textures).

Quote from: Ginev on July 21, 2017, 08:50:54 AM
I think it will be best send personal message to sereja directly regarding your problem.The creator know best.

Not this time. This question is beyond of my competence, since I do not know anything about multiplayer and have no any idea is my maps will work or not in this mode.

The 'AI meditation' in BF2 conversions caused by certain unnecessary barriers, which may have purpose in BF2 history campaign, but no needed in BF1. So you just need to found and delete them.

Well, since your map was too big (mostly because of the overhuge textures), I had manage to take only terrain&water with its belonged textures, REQ, .wld .pth .pln .rgn sky, Mission LUAs and only few props (CP's and palms). So those oranges may be was from stock Geonosis start map, automaticaly generated by BFbuilder.
I had totaly replace your .sky file by my version (which was sent to you), and add detail texture to the terrain via BFbuilder. That was all changes or at least some of of them which I remember... 

When / if this map will be fixed, the terrain should looks like this or so:
[spoiler][/spoiler]
Unfortunately, seems I can't explain correctly how it's could be fixed. Perhaps I have different type of video card, or just made too many changes at once...