Anyway, I tried to repair it by myself, as always to the goal and I reach the success.
I write everything what you have to do when you have this error like me, as I thought my map is 99% correctly made but this error, so let's begin.
I use to mapping GtkRadiant's version 1.4.0 and I never change it and I don't need. (the newest versions had another keyboard shortcuts and few options that made me nervous in normal uses)
I had the latest version of q3map2 2.5.16. WIth 2.5.17 when I tried, it also make this error MAX_EDGE_LINES so I decided to install NetRadiant, because with NetRadiant we get q3map2 2.5.17n version and what's happened when I try compile my map by using this compiler? Everything finished correctly, BUT file*.map from version GTK 1.4 when you load it in NetRadiant and vice-versa, entietes script_mover and KEY "origin" in it change brush position in your map and you have to delete it from script_mover and make new brush with texture ORIGIN connected to whole SCRIPT_MOVER, then your script_mover stay on good position (just making it like in old'school), every brush must have another ORIGIN brush, because when you add "origin" in key then problem with position on map starts again.
Hehe! Yeah saw the YT vid, Map looks awesome, something out of Quake1! I like the tricks you have put in this. The Angles key i mentioned to Skepty a while back, it works well in this Plus some of the OB are awesome too!
Or you can simply use my map starting tool (MS.exe) that is included with ET Mapping IDE.
Set your hotkey in MScfg.ini for fast map reloading.
If your ET is already open then you can reload your current map just by pressing the hotkey.
Args line in MS.exe means additional parameters.
I usually use these args: +con_drawnotify 1 +developer 1
Use MS.exe in combination with etmin.exe (Hotkey: Alt + Z)
When you do some updates in Radiant, keep your ET open and minimized
and when you need to test just compile your map,
press MS.exe hotkey and maximize your ET with Alt +Z for fastest possible testing!