I see the areas you're referring to - after revisiting the map I can only confirm that there is no flickering or other problems there when using OpenGL so I can only report what I see. This is not to say of course that you are not correct.sektor2111 wrote: ↑Sat Mar 20, 2021 7:17 pm Wrong answer.
Brushes mixed like that are doing these effects, at least I noticed that in previous version they weren't only mixed into each-other but not having merged polys for reducing those lines from surfaces.
I suppose it serves to demonstrate that mappers need to test their creations with all the renderers that people are likely to use (and possibly to test maps in different UT versions as well).
No differences, right ? 
I don't get the duplicated ) and then I filtered things through 227. There was needed recoding swJumpPad for being compatible with 227. Then some textures were splitting hair at D3D and I had to fix them using 469b. Then I have aligned textures from those caves for getting them as a single wall not pieces, then... I deleted some PathNodes, adding a forced MyLink in that "velo-ramp" ( code includes a feature anti-crap aiming NewNet ) - I did not tested if all goes fine because I won't install any NewNet here - pathing was done for 512 Scout ScanRange generating this way around 760 reachSpecs, I don't see why would be more in here. Then, I have to re-hunt reachSpecs causing damage or heavy paths, perhaps tinkering a bit one of swJumpPads - and it needs again tested... Later I made a bit visible several coronas BEHIND a translucent surface (these are not normally visible) and I was toying with a few lights a bit. If game will show some clumsy Bot in whatever place I will need to destroy evil reachSpecs with a trip through 227, grrr...
.
